Guides

The short answer: plain-language explanations of the accessibility deadlines, the WCAG 2.1 AA standard, and how to apply your fixes if your site runs on a common government website platform.

Deadlines and testing

• The ADA Title II web accessibility deadline for cities, counties and towns — When state and local governments must meet WCAG 2.1 AA under the Justice Department's ADA Title II rule: April 26, 2027 or April 26, 2028.
• The Section 504 web accessibility deadline for health centers and clinics — When health providers that receive HHS federal financial assistance must meet WCAG 2.1 AA under Section 504: May 11, 2027 or May 10, 2028.
• Website accessibility for dental and doctor's offices — HHS's Section 504 rule requires many dental and doctor's offices to test their websites and patient forms against WCAG 2.1 AA, by May 2027 or May 2028.
• Your agenda and minutes PDFs and the ADA Title II deadline — Council agendas, packets and minutes are web content under the ADA Title II rule. The deadlines, which PDFs are covered, and how EveryRamp tests and rebuilds them.
• PDF accessibility: why PDFs fail screen readers, and how to fix them — Why many PDFs cannot be read by screen readers, how to check your own, and how EveryRamp rebuilds them as tagged PDFs.
• What automated accessibility testing checks, and what it cannot — What EveryRamp's automated WCAG 2.1 AA tests check on web pages and PDFs, including a keyboard-only test, and the limits of any automated testing.
• Already have an accessibility widget? What it does and doesn't cover. — Overlays like accessiBe or UserWay help some visitors but can't fix PDFs, forms or code. What the FTC case and lawsuits show, and how to check your site.

Platform help

Which of your fixes you can make yourself, and which need a support ticket, for seven common government website systems.

• Where each fix goes on your website platform — Which of EveryRamp's fixes you can make yourself and which need a support ticket, across seven common government website platforms.
• BoardDocs: applying EveryRamp's fixes — Which accessibility fixes a clerk's office can make when creating a BoardDocs agenda item, which need BoardDocs support, and wording you can send.
• CivicPlus: applying EveryRamp's fixes — Which accessibility fixes you can make yourself in CivicPlus's content editor, which need a CivicPlus support ticket, and wording you can paste in.
• Granicus GovAccess: applying EveryRamp's fixes — Which accessibility fixes you can make yourself in Granicus GovAccess's page editor, which need a Granicus support case, and wording you can paste in.
• Legistar: applying EveryRamp's fixes — Which accessibility fixes a clerk's office can make when creating a Legistar agenda item, which need a Granicus support case, and wording you can send.
• Municode: applying EveryRamp's fixes — Why your Code of Ordinances at library.municode.com needs a request to Municode instead of a page-editor change, and wording you can send.
• Revize: applying EveryRamp's fixes — Which accessibility fixes you can make yourself in Revize's page editor, which need a Revize support request, and wording you can paste in.

Your platform isn't one of those six? The full platform list covers one more.

This page is general information, not legal advice.