Website accessibility: what small organizations actually need

For almost every small organization, the answer is WCAG 2.1 Level AA. That is the standard named in federal rules, in state grant agreements, and in the settlement terms of nearly every website accessibility lawsuit. You do not need to read the whole specification to get most of the way there, because a short list of fixes resolves the majority of real barriers on a typical small site.

I want to be direct about the legal part before anything else. I build websites; I am not a lawyer, and nothing below is legal advice. If you have received a demand letter, or you are a public entity trying to determine your obligations, your first call is to counsel, not to a web studio.

What does an accessible website actually mean?

It means a person can use your site without seeing it, without using a mouse, without hearing audio, and without fine motor control. That is the whole idea. Everything else is implementation detail.

The practical picture is a parent using a screen reader to find your school’s enrollment form, a person with tremor trying to hit a small “Donate” button on a phone, someone with low vision zoomed to 200 percent, and a deaf visitor watching your program video. If those four people can complete the task they came for, you are in good shape.

WebAIM runs an annual automated scan of the top million home pages. It has found detectable WCAG failures on roughly 95 percent of them every year the study has run. Being inaccessible is not unusual. It is the default, which is exactly why fixing it is a differentiator for the organizations we work with in the nonprofit and disability services space.

What is WCAG, and what do A, AA, and AAA mean?

WCAG is the Web Content Accessibility Guidelines, published by the W3C. Version 2.0 came out in 2008, 2.1 in 2018, and 2.2 in October 2023. Each version is backward compatible: if you meet 2.2, you meet 2.1 and 2.0.

A, AA, and AAA are conformance levels, not versions. They describe how strict the requirement is.

Level	What it covers	Should you target it?
A	The floor. Keyboard access, alt text, form labels, no keyboard traps, captions on recorded video.	Not sufficient on its own. Nothing cites A alone.
AA	Adds 4.5 to 1 text contrast, visible focus indicators, reflow at small widths, 200 percent text resize, live captions, consistent navigation.	Yes. This is the target.
AAA	7 to 1 contrast, sign language interpretation, reading level limits, no interruptions.	No. W3C itself says AAA is not achievable for all content.

WCAG 2.2 added nine new success criteria on top of 2.1, including a minimum target size of 24 by 24 CSS pixels, a rule against burying focus behind sticky headers, and a requirement that logins not depend on a memory test like a puzzle. It also dropped one obsolete criterion about HTML parsing.

Here is the part that confuses people: regulations still mostly name 2.1 Level AA, not 2.2. Build to 2.2 where it is easy, but do not panic if a funder’s checklist says 2.1. The nine new criteria are cheap to satisfy on a modern site, and several of them are things a decent designer does anyway.

Does the ADA apply to my website?

This depends entirely on which bucket you are in, and the answer is genuinely different for each one. Read the row that matches you, then verify with a lawyer.

Your organization	What applies	Practical read
City, county, public school district, public charter school, library	ADA Title II. DOJ published a technical rule in April 2024 adopting WCAG 2.1 AA, with compliance dates phased by population size starting April 2026.	You have a hard technical standard with a date attached. Treat it as a project, not an aspiration.
Nonprofit or clinic receiving federal health funding, including Medicaid	Section 504 of the Rehabilitation Act. HHS finalized a rule in 2024 applying WCAG 2.1 AA to recipients’ web content and mobile apps, phased over two to three years depending on employee count.	If Medicaid dollars touch your organization, assume this reaches you and ask counsel to confirm.
Vendor selling technology to a federal agency	Section 508 of the Rehabilitation Act. The 508 standards incorporate WCAG Level AA.	You will be asked for an accessibility conformance report during procurement.
Private business open to the public - law firm, restaurant, retail, most home care agencies without federal funding	ADA Title III. No federal technical standard for websites exists. Courts are split. DOJ’s position is that the ADA applies to public accommodations’ websites.	No safe harbor, no checklist, and thousands of federal lawsuits filed annually. AA is still the practical benchmark.
Private school or religious organization	Depends heavily on funding sources and the religious entity exemption in Title III.	Genuinely fact-specific. Do not guess.

The pattern across all five rows: WCAG 2.1 Level AA is the standard everyone converges on. Whether it applies to you by rule, by grant contract, or by litigation risk changes the urgency, not the target.

One more thing worth saying plainly. A Minnesota home care agency billing Medicaid under a 245D license is in a very different position from a private roofing company, even though both are small businesses with a ten-page website. Funding source drives obligation more than size does.

What are the 12 fixes that solve most problems?

If you do nothing else, do these. On a typical small business or nonprofit site, this list clears the large majority of what an auditor would flag.

#	Fix	WCAG criterion	Level
1	One H1 per page, headings in order, no skipping levels, never a heading used for visual size only	1.3.1, 2.4.6	A / AA
2	Everything reachable and operable by keyboard, with a clearly visible focus ring	2.1.1, 2.4.7	A / AA
3	Text contrast of at least 4.5 to 1, and 3 to 1 for large text, icons, and form borders	1.4.3, 1.4.11	AA
4	Alt text on meaningful images, empty alt on decorative ones	1.1.1	A
5	Every form field has a real label element, not just placeholder text	3.3.2, 4.1.2	A
6	Link text that makes sense read aloud out of context	2.4.4	A
7	Captions on all prerecorded video with sound	1.2.2	A
8	No keyboard traps - you can always Tab back out of a modal or embed	2.1.2	A
9	Nothing auto-plays or loops more than 5 seconds without a pause control; honor prefers-reduced-motion	2.2.2, 2.3.3	A / AAA
10	Touch targets at least 24 by 24 CSS pixels, with 44 by 44 a better practical goal	2.5.8	AA (2.2)
11	Text resizes to 200 percent and reflows at 320 pixels wide without horizontal scrolling	1.4.4, 1.4.10	AA
12	Meaning is never carried by color alone - red text needs a word or icon too	1.4.1	A

A few of these deserve a sentence of explanation.

Headings are structure, not styling. Screen reader users navigate by heading the way sighted users skim. If your page has an H1, then jumps to H4 because H4 looked the right size, the outline breaks. Fix it with CSS, not with the wrong tag.

Placeholder text is not a label. It disappears the moment someone types, it often fails contrast, and many screen readers handle it inconsistently. This is the single most common form problem I see on small sites, and it is a ten-minute fix.

“Click here” and “Learn more” are the classic link failures. A screen reader user can pull up a list of every link on the page. Twelve links all reading “Learn more” is a useless list. Write “Read our 2025 impact report” instead.

Focus indicators get removed on purpose more often than by accident. Someone thought the blue outline looked ugly and added outline: none. That single line makes keyboard navigation impossible to follow. If you dislike the default, design a better one, do not delete it.

How do I test my own site in 20 minutes?

You can do a genuinely useful first pass yourself, free, today. This will not produce a legally defensible audit, but it will find most of what is actually broken.

1. Install the WAVE browser extension from WebAIM. Run it on your home page, your contact page, and one interior page. It flags contrast failures, missing alt text, empty links, and unlabeled form fields directly on the page. Five minutes.
2. Unplug your mouse. Tab through your home page from the top. Can you see where you are at every step? Can you open and close the mobile menu? Can you get out of any pop-up? Five minutes, and this test finds things no scanner will.
3. Zoom your browser to 200 percent. Does text overlap, get cut off, or force sideways scrolling? Then narrow the window to about 320 pixels wide and check again. Three minutes.
4. Turn on a screen reader and listen to your home page. VoiceOver is built into every Mac (Command + F5) and iPhone. NVDA is free on Windows. You will not be fluent, and that is fine. You are listening for whether your images announce as “image” with no description, and whether your links make sense. Five minutes.
5. Watch one of your videos with the sound off. If there are no captions, that is a Level A failure and it is on the list.

Two honest caveats. Automated scanners are commonly estimated to catch only about a third of real WCAG issues, because most criteria require human judgment. A page can score a clean WAVE report and still be unusable. And a clean Lighthouse accessibility score of 100 means very little on its own.

Log what you find. If you are heading into a rebuild anyway, this list folds neatly into a website redesign checklist rather than becoming its own project.

Are accessibility overlay widgets worth it?

No. I want to be as blunt about this as the evidence supports, because these products are marketed hard to exactly the organizations reading this article.

An overlay is a line of JavaScript you paste into your site. It loads a floating accessibility icon and a panel with toggles for contrast, font size, and “screen reader mode.” Vendors sell them for roughly $500 to $1,000 per year with claims of instant compliance.

They do not work, for a structural reason: an overlay runs on top of your existing markup and cannot know what your images depict, what your form fields mean, or what your unlabeled buttons do. It guesses. Guessed alt text is often worse than none.

The evidence against them is not just my opinion.

• Hundreds of accessibility professionals, including many who are themselves disabled screen reader users, have signed a public statement opposing overlay products.
• Screen reader users report that overlays interfere with the assistive technology they already have configured, sometimes making sites worse than before.
• Sites running overlays have still been sued for inaccessibility. Buying one does not buy immunity.
• In 2025 the Federal Trade Commission finalized an order against overlay vendor accessiBe including a $1 million payment, over claims that its widget made websites WCAG compliant and over deceptive reviews.

If you already have an overlay on your site, removing it is usually a net improvement. Spend the annual subscription on fixing the actual markup instead.

What does real accessibility testing cost?

Rough market ranges, so you can sanity-check a quote.

Type of work	Typical cost	What you get
Automated scan only	$0 to a few hundred	A report listing detectable failures. Useful, incomplete.
Manual audit, small site (10 to 20 templates)	Low thousands	Human testing with screen readers and keyboard, prioritized findings with locations and remediation notes.
Manual audit with disabled user testing	Higher, scales with scope	The above plus task-based testing by people who use assistive technology daily.
Accessibility conformance report / VPAT	Several thousand	The document procurement teams ask for. Needed mainly if you sell to government or education.
Remediation	Hourly	Fixing what the audit found. Our published hourly rate is $95 to $150.

For most small organizations, remediation on an existing site lands somewhere between a few hours of contrast and alt text cleanup and a full rebuild. If the template itself has inaccessible navigation, a slideshow you cannot control, and no focus styles, rebuilding is often cheaper than patching. That is when accessibility work merges into a redesign, which for us falls in the $2,500 to $12,000 band on the pricing page.

Do Minnesota grants require an accessible website?

Increasingly, yes, and the requirement usually arrives buried in the agreement rather than announced.

State agency grant agreements often carry accessibility language tied to the State of Minnesota’s own accessibility standard, which tracks WCAG Level AA. Federal pass-through dollars carry Section 504 obligations to the subrecipient. Foundation grants are less consistent, but several Minnesota funders now ask about digital accessibility in the application itself.

The practical advice: search your actual grant agreement for the word “accessib” before you assume anything. If the clause is vague, email the program officer and ask what evidence they expect. Sometimes the answer is a statement of conformance; sometimes it is nothing at all until a complaint arrives.

Charter schools are the group I would watch most closely in Minnesota. They are public entities with public obligations and, usually, a two-person office. When we rebuilt the site for Gateway STEM Academy, a public K-8 charter in Saint Paul, the practical questions were the same ones every school website faces: can a parent on an old Android phone find the enrollment form, and does the calendar work with a screen reader?

When you should not pay anyone for this

Here is the part that costs me work, and I would rather say it than not.

If your site is five pages on Squarespace or Wix and your only failures are contrast, alt text, and heading order, do not hire an agency. Those three things are editable inside the platform’s own editor. Set aside a Saturday, run WAVE, fix what it flags, and you are done. You would be paying someone $95 an hour to do data entry you can do yourself.

If you are facing an actual demand letter or complaint, hire a lawyer first. A web studio cannot assess your legal exposure, and the sequence matters. Counsel tells you what you need to remediate and on what timeline; then you hire someone to do it. Doing it backwards means paying twice.

If you need a legally defensible conformance audit with a VPAT, hire a dedicated accessibility firm, not a general web studio. That includes us. Specialist firms employ testers who use screen readers every day and write the documentation procurement teams accept. We build and remediate accessible sites; we do not sell ourselves as an audit house, and you should be skeptical of any generalist agency that does.

Where an agency genuinely earns its fee is the middle case: your site has structural problems in its templates, your team cannot fix the code, and the work needs to happen across every page at once rather than one edit at a time.

Where accessibility fits in a normal project

Retrofitting costs several times what building it in correctly does. That is the whole argument for handling it up front. Semantic HTML, real labels, contrast-checked color tokens, and visible focus states cost essentially nothing at build time and are painful to add later.

It also overlaps heavily with things you already want. Proper heading structure helps search engines. Fast, lightweight pages help everyone, which is worth reading about separately in why your website is slow. Descriptive link text improves click-through. Captions get your videos indexed. Accessibility is rarely a trade-off against anything except a designer’s preference for thin gray text.

If you are about to launch, accessibility checks belong in your pre-launch checklist alongside redirects and analytics, not in a follow-up phase that never happens. And if you are evaluating firms, “how do you handle accessibility” belongs on your list of questions to ask a web designer. The answer tells you a lot. A studio that says “we run Lighthouse” is telling you they have not thought about it.

Getting help

We build accessible sites as the default for nonprofits, schools, mosques, clinics, and care providers across the Twin Cities and greater Minnesota, and we remediate existing ones. If you want a straight read on where your current site stands and what it would take to get to WCAG 2.1 AA, get in touch or call (612) 293-0636. If the honest answer is that you can fix it yourself in an afternoon, I will tell you that instead.