Insights · 6 min read

Website accessibility (WCAG) for small organizations: what it means and where to start

By Austin Hunter · November 5, 2026

Accessibility means people using screen readers, keyboards, magnification or captions can use your site. The common yardstick is WCAG (the Web Content Accessibility Guidelines), at Level AA. We build to WCAG 2.2 AA from the start, and we've worked on sites with automated accessibility tests in their build pipeline. Here's the practical version.

Who has a deadline

State and local government bodies in the US are covered by the Justice Department's ADA Title II rule, which adopts WCAG 2.1 AA. After a 2026 extension, the compliance date for larger entities (serving 50,000 people or more) is April 26, 2027, and smaller ones have later dates. Check the rule for your situation. Private businesses and nonprofits don't have that specific deadline, but accessibility complaints and lawsuits under the ADA are common, and many grants and public contracts now ask for WCAG conformance.

What WCAG asks, in plain terms

• Text alternatives: images that carry meaning have useful alt text.
• Keyboard access: everything works without a mouse, with a visible focus outline.
• Contrast and resizing: text is readable at normal contrast and when zoomed to 200%.
• Structure: real headings, lists and labels, so screen readers can navigate.
• Forms: each field has a label, and errors say what's wrong and how to fix it.
• Media: videos have captions; nothing flashes or auto-plays with sound.
• WCAG 2.2 adds things like large enough tap targets, focus that isn't hidden behind sticky headers, and logins that don't require solving puzzles or remembering codes.

Where to start

• Run a free automated checker on your key pages. It catches many common issues, but not all of them.
• Try your site with only a keyboard, then with your phone's screen reader.
• Fix the templates (header, navigation, forms, footer) first, since every page inherits them.
• Add an accessibility statement with a way to report problems.
• Make accessibility part of every update, not a one-off project.

A note on overlay widgets

Plugins that promise instant compliance by adding a toolbar don't fix the underlying code, and they aren't a substitute for an accessible site.

How we help

We build new sites to WCAG 2.2 AA, can review an existing site, and keep it accessible on a monthly care plan.