Testing
AuraScore 81/100

Public Sector Digital Accessibility Compliance Testing Checklist

Validate public-facing agency software against WCAG 2.2 AA and Section 508 compliance standards before official release.

Use this template when conducting accessibility test reviews for citizen-facing digital services. It ensures thorough verification across screen readers, keyboard navigation, and cognitive accessibility criteria.

Template

Role: Principal Accessibility QA Specialist with fifteen years of experience auditing public sector digital services.

Context

  • Public Authority: {{agency_name}}
  • Digital Service under Test: {{digital_service_name}}
  • Conformance Benchmark: {{wcag_conformance_target}}
  • Tested Assistive Technologies: {{assistive_tech_stack}}
  • Core Citizen Demographics: {{target_user_demographics}}
  • Target Release Window: {{compliance_deadline}}

Task

Generate an exhaustive, field-ready accessibility testing checklist to certify that the digital service meets all statutory accessibility mandates without regressions prior to deployment.

Method

  1. Analyze {{digital_service_name}} workflows against the criteria mandated by {{wcag_conformance_target}}.
  2. Map specific failure modes associated with {{assistive_tech_stack}} across core public user journeys.
  3. Formulate testing checkpoints for non-text content, structural landmarking, and semantic HTML markup.
  4. Define verification items for full keyboard operability, focus traps, and logical tab sequences.
  5. Establish color contrast, zoom reflow up to 400%, and responsive viewport verification criteria.
  6. Detail assistive technology integration checks for dynamic screen reader alerts and live regions.
  7. Detail cognitive accessibility checks tailored to {{target_user_demographics}}, including clear error recovery and session time extensions.
  8. Build pass/fail criteria and sign-off prerequisites ready for {{compliance_deadline}}.

Constraints

  • Every checklist item MUST map to an explicit verifiable acceptance test.
  • Verification procedures MUST NOT require proprietary testing tools unless specifically standard in {{assistive_tech_stack}}.
  • Prioritize critical blocker items that present legal or accessibility barriers for citizen access.
  • Exclude general UI polish items that do not impact accessibility compliance.

Output format

Return a structured accessibility test verification checklist organized into five functional domains: Semantic Structure, Keyboard & Focus, Sensory & Contrast, Assistive Technology Compatibility, and Error Handling. Each section must contain 4-6 markdown checklist items with format [ ] [Critique ID] Check Description | Pass Criteria | Severity.

Self-review

  • Confirm all 6 context variables appear naturally in the execution prompts.
  • Verify every checklist item contains explicit, objective pass/fail criteria.
  • Ensure Section 508 and WCAG alignment without generic placeholder guidance.
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
qa-testing
section-508