cross-page-analyzer

Analyze aggregated web page accessibility findings to detect cross-page patterns and generate scorecards.

387|42|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill cross-page-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-page-analyzer
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/cross-page-analyzer
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill cross-page-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of identifying systemic accessibility issues across multiple web pages, moving beyond page-specific fixes to address root causes in shared components or layouts.

Core Features & Use Cases

  • Pattern Detection: Identifies systemic, template-level, and page-specific accessibility issues from aggregated scan data.
  • Severity Scoring: Computes a weighted risk score (0-100) and assigns a grade (A-F) to each page based on identified findings.
  • Scorecard Generation: Creates a comparative scorecard for audit reports, highlighting key metrics and trends.
  • Remediation Tracking: Tracks progress on accessibility fixes by classifying findings as Fixed, New, Persistent, or Regressed when baseline data is provided.

Quick Start

Analyze the aggregated accessibility findings from the provided web page scans to identify cross-page patterns and generate a scorecard.

Frequently Asked Questions about cross-page-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify systemic accessibility issues across multiple web pages?

Cross-page accessibility pattern detection works by analyzing aggregated audit findings from multiple web page scans. It identifies systemic, template-level, and page-specific issues, calculating weighted risk scores to reveal root causes in shared components.

What is the best way to generate a comparative accessibility scorecard from audit data?

The best way to generate a comparative accessibility scorecard is to aggregate multiple web page audit findings and compute weighted risk scores. This yields a comparative report highlighting key metrics, severity grades, and trends across the audited pages.

How do I track remediation progress for WCAG findings across a website?

To track WCAG remediation progress across a website, you compare current aggregated accessibility findings against baseline data. This classifies issues as Fixed, New, Persistent, or Regressed, providing clear tracking of your accessibility fixes over time.

Can I compute a severity score for web accessibility findings?

Yes, you can compute a severity score for web accessibility findings. The analysis calculates a weighted risk score from 0 to 100 and assigns a corresponding letter grade from A to F to each page based on the identified issues.

Does this pattern detection approach work for template-level accessibility issues?

Yes, this pattern detection approach works specifically for template-level accessibility issues. By analyzing aggregated findings from multiple page audits, it isolates systemic flaws originating from shared layouts and components.