Testing
AuraScore 81/100

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.

Template

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

  1. Parse the workflow stages of {{digital_service_name}} to isolate high-risk citizen interaction touchpoints.
  2. Cross-reference each interactive element against {{compliance_standard}} success criteria including contrast, keyboard trap, and ARIA attributes.
  3. Determine manual testing parameters across {{assistive_technologies}} alongside automated linters.
  4. Categorize failure severity levels based on citizen exclusion risk for {{target_user_demographics}}.
  5. Construct test assertions combining functional pass/fail criteria with expected semantic HTML behaviors.
  6. Formulate specific remediation guidance calibrated to complete within {{remediation_window}}.
  7. 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

  1. System & Scope Header (4 lines summarizing testing parameters)
  2. 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)
  3. 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}}?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-testing
public-sector-nonprofit
accessibility
section-508
wcag