The VPAT (Voluntary Product Accessibility Template) is the standard federal format for reporting
how a system conforms to accessibility standards — required by CDRL A006 before the ATO package can be submitted. This is the interim conformance baseline dated Aug 20, 2026, produced during build so regressions are caught before the formal test cycle; the deliverable A006 report is due Nov 14, 2026 and has not yet been submitted.
Testing is performed by P. Duvall's team using both automated scanning and manual assistive-technology testing.
| Name of Product | BenefitConnect Portal (citizen-facing benefits application) |
| Report Date | Aug 20, 2026 (interim baseline — CDRL A006 due Nov 14, 2026) |
| VPAT Version | VPAT 2.5Rev — WCAG Edition |
| Standards Evaluated | WCAG 2.1 Level A and AA, Revised Section 508 |
| Evaluation Methods Used | Automated scanning (axe-core) + manual assistive-technology testing (NVDA, JAWS, keyboard-only navigation) |
| Contact | P. Duvall, 508/Accessibility Lead — Acme Federal Systems |
| WCAG 2.1 Criteria Area | Conformance Level | Notes |
|---|
| Non-text Content (1.1.1) | Supports | All images and icons carry programmatic alt text; decorative elements marked aria-hidden |
| Info and Relationships (1.3.1) | Supports | Semantic HTML and ARIA landmarks used throughout; form field groupings programmatically associated |
| Meaningful Sequence (1.3.2) | Supports | Reading order confirmed to match visual order with screen readers across all workflows |
| Use of Color (1.4.1) | Supports | Status indicators pair color with icon/text, not color alone |
| Color Contrast (1.4.3) | Partially Supports | Status badge component below 4.5:1 ratio — remediation in progress |
| Resize Text (1.4.4) | Supports | Content reflows correctly to 200% zoom |
| Reflow (1.4.10) | Supports | No horizontal scrolling or content loss at 320px equivalent viewport width |
| Text Spacing (1.4.12) | Supports | No content or functionality loss when text spacing overrides are applied |
| Keyboard Navigation (2.1.1) | Supports | Full keyboard operability confirmed across all portal workflows |
| Focus Visible (2.4.7) | Supports | Visible focus indicator on all interactive elements, contrast-checked against adjacent backgrounds |
| Headings and Labels (2.4.6) | Supports | Descriptive headings and form labels confirmed via manual review |
| Link Purpose in Context (2.4.4) | Supports | No ambiguous "click here" links; link text is descriptive out of context |
| Language of Page (3.1.1) | Supports | lang attribute correctly set on all pages |
| Consistent Navigation (3.2.3) | Supports | Navigation structure and order consistent across all portal pages |
| Form Labels & Error Identification (3.3.1/3.3.2) | Supports | All form fields programmatically labeled with inline error messaging |
| Error Suggestion (3.3.3) | Supports | Validation errors include specific correction guidance, not generic "invalid input" messaging |
| Name, Role, Value (4.1.2) | Supports | Tested with NVDA and JAWS against benefits application flow; custom components expose correct ARIA roles/states |
| Status Messages (4.1.3) | Supports | Form submission and validation status announced to assistive technology via aria-live regions |
| Document/PDF Output Accessibility | Partially Supports | Generated confirmation PDFs missing tagged headings — remediation scheduled |