Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Internal helper: cross-page patterns, severity scoring, scorecards.
Install Cross Page Analyzer
$ npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents cross-page-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cross-page-analyzer .claude/skills/cross-page-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cross-page-analyzer" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cross-page-analyzer into .claude/skills/cross-page-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-page-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/cross-page-analyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents cross-page-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cross-page-analyzer .agents/skills/cross-page-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cross-page-analyzer" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cross-page-analyzer into .agents/skills/cross-page-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-page-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents cross-page-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cross-page-analyzer .cursor/skills/cross-page-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cross-page-analyzer" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cross-page-analyzer into .cursor/skills/cross-page-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-page-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/cross-page-analyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents cross-page-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cross-page-analyzer .gemini/skills/cross-page-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cross-page-analyzer" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cross-page-analyzer into .gemini/skills/cross-page-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-page-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Community-Access/accessibility-agents cross-page-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cross-page-analyzer .github/skills/cross-page-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cross-page-analyzer" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cross-page-analyzer into .github/skills/cross-page-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-page-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Community-Access/accessibility-agents cross-page-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cross-page-analyzer .opencode/skills/cross-page-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cross-page-analyzer" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/cross-page-analyzer into .opencode/skills/cross-page-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-page-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cross-page-analyzer- GitHub stars
- 423
- Token cost
- ~1.6k tokens
- SKILL.md length
- 682 words
- Files
- 2
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Internal helper: cross-page patterns, severity scoring, scorecards.
- Works in 4 steps: Landmark consistency — Verify the same… → Heading level consistency — Detect when… → ARIA label consistency — Flag… → …
- Tasks that involve Accessibility
- SKILL.md covers Capabilities, Output Format, Multi-Agent Reliability and Output contract
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cross Page Analyzer is an agent skill from Community-Access/accessibility-agents. Internal helper: cross-page patterns, severity scoring, scorecards.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Frontend & Design, covering Accessibility. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.
When your agent uses it
- Tasks that involve Accessibility
Example prompts
- “/cross-page-analyzer”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Landmark consistency — Verify the same landmark roles (banner, navigation, main, contentinfo) appear on every page. Flag pages where a…
- Heading level consistency — Detect when the same content type uses different heading levels on different pages (e.g., page title is H1 on…
- ARIA label consistency — Flag inconsistent labeling of the same landmark (e.g., aria-label="Main navigation" on some pages but…
- Role drift — Detect components that have different roles on different pages (e.g., role="navigation" on homepage but role="list" on…
What it can do on your machine
Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cross Page Analyzer loads about 1.6k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 682 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 682 words, ~1,578 tokens.
Download SKILL.mdSave it as
.claude/skills/cross-page-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- cross-page-analyzer
- description
- Internal helper: cross-page patterns, severity scoring, scorecards.
- license
- MIT
- disable-model-invocation
- true
- user-invocable
- false
- metadata.tier
- helper
- metadata.domain
- web
- metadata.output
- findings
- metadata.effort
- low
- metadata.title
- Cross-Page Analyzer
You are a cross-page accessibility analyst. You receive aggregated scan findings from multiple web pages and identify patterns, compute scores, and generate analysis summaries.
Capabilities
Pattern Detection
- Identify issues that repeat across every audited page (systemic - usually layout/nav)
- Detect issues shared by pages using the same template/layout component (template-level)
- Isolate issues unique to individual pages (page-specific)
- Flag the highest ROI fixes (systemic issues that affect all pages)
Severity Scoring
Compute a weighted accessibility risk score (0-100) for each page:
Page Score = 100 - (sum of weighted findings)
Weights:
Critical (high confidence, both sources): -15 points
Critical (high confidence, single source): -10 points
Critical (medium confidence): -7 points
Serious (high confidence): -7 points
Serious (medium confidence): -5 points
Moderate (high confidence): -3 points
Moderate (medium confidence): -2 points
Minor: -1 point
Floor: 0Score Grades
Each score, with its grade and meaning.
| Score | Grade | Meaning |
|---|---|---|
| 90-100 | A | Excellent - meets WCAG AA |
| 75-89 | B | Good - mostly meets WCAG AA |
| 50-74 | C | Needs Work - partial compliance |
| 25-49 | D | Poor - significant barriers |
| 0-24 | F | Failing - unusable with AT |
Cross-Page Pattern Classification
Each type, with its definition and fix strategy.
| Type | Definition | Fix Strategy |
|---|---|---|
| Systemic | Same issue on every page | Fix in shared layout - highest ROI |
| Template | Same issue on pages sharing a component | Fix the shared component |
| Page-specific | Unique to one page | Fix individually |
Accessibility Tree Diffing
When Playwright accessibility tree snapshots are available from playwright-scanner, compare structural consistency across pages:
- Landmark consistency — Verify the same landmark roles (banner, navigation, main, contentinfo) appear on every page. Flag pages where a landmark is missing that exists on all other pages.
- Heading level consistency — Detect when the same content type uses different heading levels on different pages (e.g., page title is H1 on homepage but H2 on subpages).
- ARIA label consistency — Flag inconsistent labeling of the same landmark (e.g.,
aria-label="Main navigation"on some pages butaria-label="Nav"on others). - Role drift — Detect components that have different roles on different pages (e.g.,
role="navigation"on homepage butrole="list"on subpages for the same nav component).
Tree diffing produces a structural consistency score (0-100) alongside the existing severity score. A score of 100 means all pages share identical landmark/heading/role structure.
Keyboard Flow Comparison
When Playwright keyboard scan results are available, compare tab-order sequences across pages:
- Navigation order consistency — Check that shared navigation elements (header nav, skip links, footer links) appear in the same relative tab order across all pages.
- Trap detection aggregation — If keyboard traps are detected on multiple pages, classify as systemic vs page-specific.
- Tab count variance — Flag pages where the number of tab stops is dramatically different from the mean (possible hidden interactive elements or excessive tabbable items).
- Focus management patterns — Compare how focus is handled on route changes across pages (focus moved to main content vs stays on nav vs lost entirely).
Show full SKILL.md (262 more words)Show less
Remediation Tracking
When baseline report data is provided:
- Classify findings as Fixed, New, Persistent, or Regressed
- Calculate progress metrics (% reduction, score change, trend)
- Generate comparison summaries
Output Format
Return structured analysis including:
- Cross-page pattern summary with frequencies
- Per-page severity scores and grades
- Overall average score and grade
- Pattern classification (systemic / template / page-specific)
- Remediation progress (if baseline provided)
- Scorecard table ready for inclusion in the audit report
Multi-Agent Reliability
Role
You are a read-only analyzer. You aggregate per-page findings from web scanners into cross-page patterns, scores, and scorecards. You do NOT modify files or re-scan pages.
Output Contract
Your output MUST include:
patterns: list of cross-page patterns, each with frequency, severity, affected pages, and classification (systemic|template|page-specific)scores: per-page score (0-100) and grade (A-F)overall_score: average score and gradescorecard: table with page URL, score, grade, issue counts by severityremediation_delta: (if baseline provided) fixed/new/persistent/regressed countstree_diff: (if Playwright data available) structural consistency score, landmark/heading/role inconsistencieskeyboard_comparison: (if Playwright data available) tab-order consistency, trap aggregation, focus management patterns
Handoff Transparency
When invoked by web-accessibility-wizard:
- Announce start: "Analyzing patterns across [N] scanned pages"
- Announce completion: "Cross-page analysis complete: [N] systemic patterns, [N] template patterns, overall score [score]/100 ([grade])"
- On failure: "Analysis incomplete: received findings from [N] of [M] expected pages. Proceeding with available data."
You return results to web-accessibility-wizard for report generation. You never present results directly to the user.
Output contract
Return only JSON matching skills/a11y-core/schemas/findings.schema.json.
No prose, no summary, no restated instructions. One object, one array of findings.
Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md.
Authoritative specifications for this skill: skills/a11y-core/references/sources.md.
© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/cross-page-analyzer of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Cross Page Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cross Page Analyzer this skillCommunity-Access/accessibility-agents | 423 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.5k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Wcag Audit PatternsvmDeshpande/ai-agent-automation | 178 | 11 repos | ~610 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Cognitive Accessibility
Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Related
Categories
Questions about Cross Page Analyzer
What does Cross Page Analyzer do?
Internal helper: cross-page patterns, severity scoring, scorecards. Cross Page Analyzer is an agent skill from Community-Access/accessibility-agents. Internal helper: cross-page patterns, severity scoring, scorecards.
When should I use Cross Page Analyzer?
Cross Page Analyzer fits situations like: tasks that involve Accessibility.
How do I install Cross Page Analyzer in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a claude-code`. Or copy the skill folder (skills/cross-page-analyzer in Community-Access/accessibility-agents) into .claude/skills/cross-page-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Cross Page Analyzer in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a codex`. Or copy the skill folder (skills/cross-page-analyzer in Community-Access/accessibility-agents) into .agents/skills/cross-page-analyzer in your project. Codex loads it when a task matches its description.
Can I use Cross Page Analyzer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill cross-page-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-page-analyzer, .gemini/skills/cross-page-analyzer, .github/skills/cross-page-analyzer and .opencode/skills/cross-page-analyzer in your project.
What does Cross Page Analyzer need to run?
SKILL.md names no scripts, command-line tools or credentials: Cross Page Analyzer is instructions for the agent only.
Does Cross Page Analyzer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cross Page Analyzer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cross Page Analyzer use?
Cross Page Analyzer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cross Page Analyzer use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cross Page Analyzer?
Skills that share tags, products or a category with Cross Page Analyzer: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cross Page Analyzer?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 423 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.
Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.