Accessibility
Find and fix accessibility errors.
Tested by hand with a keyboard and a screen reader, fixed in the code and retested, with a dated record of each step.
Sample finding. The site and form are fictional.
For state and local governments
The ADA Title II web rule.
Websites and mobile apps must meet WCAG 2.1 AA, including documents and content supplied by vendors. We test every page, fix what fails, retest and keep a dated record you can hand to counsel.
- Public entities with a total population of 50,000 or more.
- Smaller public entities and special district governments.
Dates from the Department of Justice’s interim final rule of April 20, 2026 (Federal Register 2026-07663).
Method
What we test, and how.
Automated tools cover every page. The tasks that matter are tested by hand. Each finding names the failure, the WCAG criterion, the fix and how the fix was verified.
Tools
- axe-coreautomated WCAG rules
- NVDAscreen reader, Windows
- VoiceOverscreen reader, macOS and iPhone
- Keyboard onlyevery task, start to finish
- Pages and templates Desktop and phone widths AutomatedKeyboardScreen reader
- Forms and tasks Applying, paying, registering AutomatedKeyboardScreen reader
- PDF and Word documents Files people use to take part AutomatedScreen reader
- Video and images Captions and descriptions AutomatedScreen reader
- Color and contrast Text, controls, focus AutomatedKeyboard
The method in every assessment. Your scope sets which pages and tasks.
Assessment options.
Each has a written scope and a fixed price, quoted before work starts. Fixes are quoted after you see the findings.
- 1Assess
- 2Fix, quoted after the findings
- 3Retest
- AssessWhere most start Key tasks Your homepage and five tasks you choose.
- Automated, keyboard and screen reader testing
- A findings report
- A fix list in priority order
- Fixed price, quoted first
- Assess Template review Every page template, plus the key tasks.
- The same testing, on every template
- Findings for every template
- A fix list in priority order
- Fixed price, quoted first
- After the fixes Retest Every fix, whether we made it or your team did.
- The same testing, on each fix
- An updated, dated record
- Fixed price, quoted first
The documents people need.
Agendas, minutes, forms and notices in PDF or Word, rebuilt as accessible pages that read well on a phone.
- New documentsEach new agenda, set of minutes or notice posted as an accessible page. Under a retainer, a routine request.
- Documents already postedThe rule has exceptions for archived content and older documents, unless people still use them to take part in a service. We help you sort which ones need rebuilding.
- The original fileWhen your records rules require it, the PDF or Word file stays posted beside its accessible page.
Check your homepage.
The free audit checks HTTPS, email settings, speed and automated accessibility, from public information only. Results in about a minute.
Questions.
Which WCAG version do you test against?
The version your contract names. The Title II rule adopts WCAG 2.1 AA. Some contracts name WCAG 2.2 AA, which adds requirements such as a minimum size for targets people tap or click. Every finding names the success criterion it fails.
Will our site be ready by our Title II date?
We do not promise compliance by a date. We plan the assessment, the fixes, and the retest around the date that applies to you, starting with the pages and tasks people use most.
Is an automated score proof of compliance?
No. An automated score, including 100, does not establish conformance. Tools find failures such as missing labels and low contrast, but they cannot tell whether a person can finish a task.
Do you install an accessibility overlay or widget?
No. We fix the page itself: its code, its content, and its documents. An overlay adds a script on top and leaves the underlying errors in place.
We already use an accessibility scanner. Can you fix what it finds?
Yes. Send its latest report. We quote the fixes at a fixed price, or make routine ones as small requests under a retainer, and retest each fix before we mark it done.
How is Section 508 different from Title II?
Section 508 governs federal agencies’ technology and adopts WCAG 2.0 AA. The Title II web rule applies to state and local governments and adopts WCAG 2.1 AA. Your contract states which applies.
How do we keep the site accessible after the fixes?
Every new page or document can bring new errors. On the Maintenance with accessibility plan, every page is checked every day and accessibility errors are fixed every month.
What maintenance includesGet a fixed price for an assessment.
Send your website address and the tasks that matter most. We reply within one business day.