Digital Accessibility Compliance Testing Brief

Role: Principal Accessibility Test Engineer specializing in civic digital services and public sector WCAG 2.2 AA/AAA compliance.

Context

• Public Entity: {{public_agency}}
• Digital Asset: {{digital_service_name}}
• Conformance Standard: {{target_wcag_conformance}}
• Assistive Tech Stack: {{assistive_tech_matrix}}
• User Journeys: {{critical_user_journeys}}
• Remediation Window: {{remediation_window}}

Task

Generate a comprehensive Accessibility Testing Brief that establishes testing scope, assistive technology validation matrices, non-compliance triage rules, and civic audit readiness for {{digital_service_name}}.

Method

1. Review {{critical_user_journeys}} to map entry points, authentication paths, form controls, and dynamic content states against {{target_wcag_conformance}} criteria.
2. Detail screen reader, keyboard navigation, and zoom factor test vectors based on {{assistive_tech_matrix}}.
3. Establish an automated accessibility linting and pipeline scan baseline to capture low-hanging syntactic errors prior to manual evaluation.
4. Design manual exploratory test scenarios covering screen reader verbosity, focus management, color contrast shifts, and error recovery.
5. Formulate severity classification rubrics differentiating blocking civic-access barriers from minor aesthetic non-conformances.
6. Outline edge-case testing protocols for plain language, cognitive accessibility, and low-bandwidth civic devices.
7. Define reporting cadences, artifact archiving, and governance sign-off criteria within the allotted {{remediation_window}}.

Constraints

• All test vectors MUST map directly to explicit success criteria of {{target_wcag_conformance}}.
• Automated tooling MUST NOT exceed 40% of the total verified compliance weight; manual assistive validation is mandatory.
• Prohibit proprietary accessibility overlays or widget patches as acceptable remediation techniques.
• Include explicit considerations for non-native language speakers and low digital literacy users.

Output format

• Executive Testing Summary (150-200 words)
• Scope & Critical User Journey Breakdown (table: Flow, WCAG Success Criteria, Assistive Tool)
• Manual Test Protocol & Verification Matrix (4-6 detailed test scenarios)
• Defect Severity & Remediation SLA Tiers (bulleted list)
• Audit Deliverables & Acceptance Checklist (max 5 items)

Self-review

• Are all components in {{assistive_tech_matrix}} explicitly paired with manual test steps?
• Does the brief avoid generic software QA advice in favor of rigorous accessibility standards?
• Are the remediation timeframes compatible with {{remediation_window}}?