Free introduction · about 10 minutes
Learn why accessible websites and documents matter, what your team owns, and when the ADA Title II web rule may require public entities to meet WCAG 2.1 AA.
John has been notified of your readiness answers and selected interest, and will follow up using the email you provided.
Start with the right terms
This is practical education, not legal advice. Requirements depend on your organization and content; confirm your obligations with qualified counsel or the responsible agency.
A federal law and set of standards that applies to federal agencies' information and communication technology. It is already in effect—not a new 2028 law.
The revised 508 Standards use WCAG 2.0 Level A and AA for covered web and non-web electronic content, with additional requirements in some cases.
This is the rule most state and local public entities should be watching. It requires covered web content and mobile apps to meet WCAG 2.1 Level A and AA, subject to defined exceptions and limitations.
Current general deadlines are April 26, 2027 for public entities with a population of 50,000 or more, and April 26, 2028 for smaller public entities and special district governments.
Why it matters
People may use a keyboard, screen reader, magnification, captions, voice input, or a combination. Barriers can prevent residents from finding a meeting, completing a form, or reading a notice.
Accessible content supports residents, students, customers, staff and visitors when they need information or a service.
A documented, ongoing accessibility practice helps leaders address barriers before they become urgent complaints or missed services.
Clear templates, trained content authors and an accessible procurement process reduce rework over time.
Leadership responsibilities
A web vendor can help, but the public entity remains responsible for the content and services it provides directly or through contractual arrangements.
Name a lead, identify the public tasks people rely on most, and give accessibility a place in normal publishing, technology and purchasing decisions.
List websites, forms, PDFs, Word files, videos, portals and mobile apps. Start with high-use and essential services; document a realistic remediation plan.
Train authors, use accessible templates, ask vendors for accessibility evidence, and test before publishing—not only after a complaint.
Use automated and manual testing, correct prioritized barriers, provide an accessible way to report trouble, and track decisions and progress.
What WCAG and performance mean
WCAG is the technical accessibility framework used by the federal 508 standards and the ADA Title II rule described above. It gives testable success criteria for content, design and code.
Speed and reliability matter—especially on phones or slow connections—but a fast page can still exclude a keyboard or screen-reader user. Treat performance as a companion quality measure, not a compliance shortcut.
Automated tools find useful issues, yet no automated checker can certify a complete website or document. Include keyboard use, meaningful reading order, form completion and assistive-technology testing in your process.
Primary references
These official sources explain the standards and current timing in more detail.
Keep learning
Return to the readiness check at any time, use the self-check tools, or ask John to help prioritize the work.