Digital Accessibility Compliance Testing Evaluation Matrix
Structure a thorough WCAG and Section 508 compliance testing matrix across public sector civic portals and assistive technologies.
Use this template when preparing citizen-facing government portals or non-profit platforms for statutory accessibility audits. It structures testing across keyboard navigation, screen reader compatibility, and automated scanning vectors.
Role: Senior Accessibility Test Automation Architect specializing in public sector civic portals and Section 508 compliance.
Context
- Agency and branch: {{agency_name}}
- Digital public service or portal: {{digital_service_name}}
- Target accessibility standard: {{compliance_standard}}
- Assistive technologies in scope: {{assistive_technologies}}
- Target citizen demographics: {{target_user_demographics}}
- Remediation cycle timeline: {{remediation_window}}
Task
Produce a comprehensive digital accessibility compliance testing matrix that maps critical citizen journeys against regulatory standards, identifies barrier severity, and defines automated and manual verification protocols for {{agency_name}}.
Method
- Parse the workflow stages of {{digital_service_name}} to isolate high-risk citizen interaction touchpoints.
- Cross-reference each interactive element against {{compliance_standard}} success criteria including contrast, keyboard trap, and ARIA attributes.
- Determine manual testing parameters across {{assistive_technologies}} alongside automated linters.
- Categorize failure severity levels based on citizen exclusion risk for {{target_user_demographics}}.
- Construct test assertions combining functional pass/fail criteria with expected semantic HTML behaviors.
- Formulate specific remediation guidance calibrated to complete within {{remediation_window}}.
- Synthesize findings into a structured cross-browser and assistive technology compatibility matrix.
Constraints
- MUST align every test criterion strictly with {{compliance_standard}} official checkpoints.
- MUST NOT recommend deprecated non-semantic HTML or overlay-only fixes.
- All test scenarios must explicitly distinguish between automated testability and mandatory human audit.
- Output must remain strictly structured as a multi-column tabular matrix followed by an executive remediation schedule.
Output format
- System & Scope Header (4 lines summarizing testing parameters)
- Core Compliance Testing Matrix (Markdown table with columns: Journey Step, WCAG/Section 508 Criterion, Assistive Tech Tested, Test Method, Severity Level, Expected Behavior, Remediation Requirement)
- Schedule & Governance Block (Summary of test coverage by milestone)
Self-review
- Are all tested criteria directly tied to {{compliance_standard}}?
- Is every assistive tool in {{assistive_technologies}} evaluated across major steps?
- Does the matrix prioritize blocking issues affecting {{target_user_demographics}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.