Federal agencies · Section 508 testing
A grant portal, tested to Section 508 before it went live.
A federal program office was weeks from launching a new online grant application. We tested every screen, form, and download by hand against Section 508, so applicants who use a keyboard or a screen reader could apply on the first day.
- Client
- A federal program office
- Type
- Section 508 testing
- Scope
- 18 screens and 6 PDFs
- Result
- 27 barriers fixed before launch
Context and goals
Applicants use the portal to create an account, complete a multi-step application, upload documents, and check the status of a request.
The office needed proof that the portal met Section 508 before launch, and a list of fixes its developers could finish in one sprint.
What success looks like
- Every step of the application works with a keyboard alone.
- A screen reader announces every field, every error, and every change in status.
- Every PDF an applicant downloads is tagged and reads in order.
What we measured
A DHS Certified Trusted Tester tested all 18 screens and 6 PDFs by hand with a keyboard and a screen reader, following the Trusted Tester process, and we used automated checks to cover every page faster.
Barriers found, by type
- Forms and errors9
- Keyboard access8
- Names for screen readers5
- Documents4
- Timing1
All 27 were fixed and retested by hand before launch.
| Barrier | Screen | Severity | Status |
|---|---|---|---|
| Date fields needed a mouse | Applicant details | High | Fixed |
| Errors never announced | Every form step | High | Fixed |
| No way to extend the session | Every screen | High | Fixed |
| Upload button with no name | Attachments | Medium | Fixed |
| Untagged instruction PDFs | Downloads | Medium | Fixed |
What we found
- The good news: the portal was built on an accessible design system, so most screens already passed.
- The date fields could not be filled in without a mouse.
- Error messages appeared on screen but were never announced to screen readers.
- A session timeout warning gave applicants no way to ask for more time.
- Four of the six instruction PDFs had no tags.
Hear the difference
An applicant who uses a screen reader submits a step with a required field left blank.
Before
What a screen reader says
- “Continue, button.”
- Nothing else. The error appears on screen, but the applicant never hears it and waits.
After
What a screen reader says
- “Continue, button.”
- “Alert. 1 error. Date of birth is required.”
- “Date of birth, edit text, required, invalid entry.”
The path to good
- We ranked the 27 barriers by how badly each one blocked an applicant, so the team fixed the blockers first.
- Each issue came with the Section 508 requirement, where it was, how severe it was, and how to fix it.
- We fixed and tagged the six PDFs ourselves.
Follow-up
We retested every fix by hand. All 27 barriers were closed before launch, and the office kept the report on file with its Section 508 records.
All case studies are samples. Each is based on our past work or on our audits of publicly available websites, documents, and social media. Names and details have been changed to protect privacy.
Before you buy
We start with a free light audit.
We prepare it for you and send you what we find.
- We check your homepageKeyboard, screen reader, contrast, and zoom.
- We review one public documentTags, headings, image descriptions, and language.
- We fix one public document freeYou get it back fixed, with a before and after.
- We send you what we findA short written summary you can share with your team.