Public Sector Citizen Portal Accessibility Compliance Audit Matrix
Evaluate citizen-facing digital services against accessibility standards and generate a prioritized remediation matrix.
Use this template when preparing public sector web applications for Section 508, ADA, or WCAG 2.2 AA certification. It establishes a multi-dimensional matrix mapping UI components to specific assistive technologies and compliance criteria.
Role: Principal Accessibility Testing Engineer with 15+ years evaluating public sector digital services.
Context
- Agency Name: {{agency_name}}
- Portal Service Scope: {{portal_service_scope}}
- Target Accessibility Standard: {{target_wcag_standard}}
- Supported Assistive Tech Stack: {{assistive_tech_stack}}
- Identified Pain Points: {{known_accessibility_barriers}}
- User Demographic Profiles: {{user_demographics}}
Task
Synthesize the provided digital service parameters into a structured Accessibility Compliance & Verification Matrix, diagnosing barrier severity and specifying concrete technical test cases to guarantee inclusive public access.
Method
- Map {{portal_service_scope}} user journeys against mandatory requirements in {{target_wcag_standard}}.
- Correlate critical workflow paths with the assistive profiles in {{assistive_tech_stack}}.
- Isolate reported risks from {{known_accessibility_barriers}} into distinct failure modes (keyboard trapping, screen-reader mislabeling, dynamic focus loss).
- Define test assertions covering visual contrast, ARIA landmarks, keyboard navigation, and semantic DOM structures.
- Score accessibility risk based on the vulnerability of populations in {{user_demographics}}.
- Format test assertions into a prioritized matrix covering criteria, viewport, assistive tool, expected DOM state, and remediation guidance.
- Establish non-functional verification criteria for legacy browser and low-bandwidth compatibility.
Constraints
- You MUST assign explicit WCAG success criterion references (e.g., WCAG 2.2 SC 2.1.1) to every matrix entry.
- You MUST NOT recommend generic automated scans without specifying manual verification procedures.
- Every test scenario MUST articulate a pass/fail condition verifiable via screen readers in {{assistive_tech_stack}}.
- Prioritization must balance legal non-compliance liability with citizen service disruption.
Output format
Provide the response across three sequential sections:
- Executive Summary (150-200 words evaluating agency compliance risk).
- Accessibility Verification Matrix (Markdown table with columns: Component/Flow, Target SC, Assistive Device, Test Procedure, Expected Result, Severity [Critical/Major/Minor], Remediation Fix).
- Manual Testing Protocol (Numbered checklist of 4-6 manual test steps for QA engineers).
Self-review
- Confirm all 6 input variables are explicitly referenced and contextualized.
- Ensure table includes at least 6 distinct component-level test cases.
- Verify WCAG criteria strictly correspond to {{target_wcag_standard}}.
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.