Web Development

Website accessibility: what small organizations actually need

WCAG levels explained, where ADA Title II, Section 504, and Title III apply with current dates, the 12 fixes that solve most problems, and a 20-minute test.

Duraan AliUpdated 16 min read
A blind woman at a desk reading a refreshable braille display in front of her laptop

For almost every small organization, the answer is WCAG 2.1 Level AA. That is the standard in the Department of Justice’s ADA Title II web rule, in the HHS Section 504 rule, in the State of Minnesota’s own accessibility standard, and in the settlement terms of most website accessibility lawsuits. 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. The 2026 WebAIM Million found detectable WCAG 2 failures on 95.9 percent of them. 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 on October 5, 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 success criteria on top of 2.1, including a minimum target size of 24 by 24 CSS pixels, a rule against hiding the focused element behind sticky headers, and a requirement that logins not depend on a memory test like a puzzle. It also removed one obsolete criterion, 4.1.1 Parsing.

Here is the part that confuses people: the regulations 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 different for each one. Read the row that matches you, then verify with a lawyer. The dates below are the ones in force as of November 2026; both federal rules were pushed back a year in spring 2026, and the Title II extension is being challenged in court, so check the agency’s page before you plan around a date.

Your organization What applies Practical read
City, county, public school district, public charter school, library ADA Title II. The DOJ rule published in April 2024 adopts WCAG 2.1 AA. An interim final rule published April 20, 2026 moved the compliance dates to April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for smaller entities and special districts. 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. The HHS rule finalized in 2024 adopts WCAG 2.1 AA for recipients’ web content and mobile apps. An interim final rule published May 11, 2026 moved the dates to May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller ones. 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 and no checklist. UsableNet’s 2025 year-end report counted 5,114 digital accessibility lawsuits in federal court and New York and California state courts, 62 percent of them federal. AA is still the practical benchmark.
Private school or religious organization Depends heavily on funding sources and the religious entity exemption in Title III. 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

The WebAIM numbers show why the list is ordered the way it is. In the 2026 Million report, low-contrast text appeared on 83.9 percent of home pages, images without alt text on 53.1 percent, form inputs without labels on 51 percent, and links with no text on 46.3 percent. Those four failures are fixes 3, 4, 5, and 6, and none of them needs a developer.

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 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 catch a minority of real WCAG issues, because most criteria require human judgment. When the UK Government Digital Service planted 142 known barriers in a test page and ran the available tools against it, in an audit published in 2017 and last updated in 2018, the best tool found 40 percent of them. A page can score a clean WAVE report and still be unusable, and a 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.” The two best-known vendors publish their prices: accessiBe’s pricing page, read in November 2026, lists its Micro plan at $59 a month or $490 a year for sites with up to 5,000 monthly visits and its Growth plan at $179 a month or $1,490 a year, and UserWay’s page lists its Pro widget at $490 a year for up to 100,000 monthly page views and $1,490 for up to a million.

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.

  • The Overlay Fact Sheet, a public statement by accessibility professionals, carried 1,048 signatures when I read it in November 2026 behind the sentence that no overlay product on the market can make a website fully compliant with any existing accessibility standard. Signatories who use screen readers report that sites became less usable for them with an overlay installed.
  • UsableNet’s 2025 year-end lawsuit report states that accessibility widgets did not slow litigation in 2025 and that an increasing number of suits were filed against companies already using them, with 95 to 155 such suits a month.
  • On January 3, 2025 the Federal Trade Commission announced an order requiring accessiBe to pay $1 million over claims that its accessWidget could make any website WCAG compliant, and over articles formatted as impartial reviews that did not disclose the company’s connection to the reviewers.

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?

Here is how the market is structured, so you can read a quote. I am deliberately not inventing dollar ranges for audits, because specialist firms price by the number of unique templates and the depth of testing and almost all of them quote on request.

Type of work How it is priced What you get
Automated scan only Free to a modest subscription A report listing detectable failures. Useful, incomplete, and by the GOV.UK test above, well under half of the real problems.
Manual audit, small site (10 to 20 templates) Quoted per template count Human testing with screen readers and keyboard, prioritized findings with locations and remediation notes.
Manual audit with disabled user testing Scales with scope The above plus task-based testing by people who use assistive technology daily.
Accessibility conformance report / VPAT Quoted per product The document procurement teams ask for. Needed mainly if you sell to government or education.
Remediation Hourly or fixed scope Fixing what the audit found. Clutch’s 2026 data puts agency rates at $100 to $149 an hour. TayoPro quotes remediation as a fixed price against the audit’s findings where the audit allows it.

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, and a redesign is priced like a new site of the same size, plus the migration. The published market bands for new sites, with their sources, are on our pricing explainer.

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 MNIT updated to incorporate WCAG 2.1 Level AA effective July 1, 2024, alongside Section 508. Federal pass-through dollars carry Section 504 obligations to the subrecipient, with the 2027 and 2028 dates above. 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 under Title II with a 2027 or 2028 date and, usually, a two-person office. When we designed and built 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? The state postings a charter school has to keep current are in our charter school website requirements guide.

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 agency rates that Clutch’s 2026 data puts at $100 to $149 an hour for 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 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.

Why accessibility is a maintenance job, not a launch job

A site that passes an audit in March fails one by September, and nobody changed the code. Somebody uploaded a flyer as an image with no alt text. A new staff member pasted a PDF nobody tagged. A board member asked for the gray text to be lighter. Three videos went up without captions before the gala. The templates are still fine; the content is not.

That is why accessibility belongs inside whatever keeps the site current, not in a one-time project. A care plan that already handles updates, backups, and content changes is the natural place for a quarterly pass: run WAVE on the pages that changed, check new images for alt text, check new PDFs and videos, and re-test the forms with a keyboard. It is an hour or two a quarter when it is routine and a project when it is not. Our maintenance checklist has the accessibility items in the quarterly section, and how much website maintenance costs shows the published Twin Cities bands for plans that include that kind of content time.

Retrofitting costs several times what building it in correctly does, which is the whole argument for handling it up front as well. 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, and who checks it after launch” belongs on your list of questions to ask a web designer. A studio that says “we run Lighthouse” is telling you they have not thought about it.

What to do next

Run the 20-minute test above on your home page, your contact page, and the one page people most need to complete a task on. Write down what you find. If the list is contrast, alt text, and headings on a hosted builder, fix it yourself this weekend. If the list includes the navigation, the forms, or the template itself, or if a date in the table above applies to you, it is a project.

If you want a straight read on where your current site stands and what it would take to get to WCAG 2.1 AA, tell us about it or call (612) 293-0636. TayoPro designs and builds websites to WCAG 2.1 AA as the default for nonprofits, schools, mosques, clinics, and care providers across the Twin Cities and greater Minnesota, and keeps them maintained month to month with accessibility in the quarterly checks, both at a fixed price quoted in writing. If the honest answer is that you can fix it yourself in an afternoon, we will tell you that instead.

FAQ

Questions people ask about this

Does my small business website legally have to be accessible?

It depends on what kind of organization you are, and this is a question for a lawyer, not a web studio. Public entities such as cities, counties, and public schools, including charter schools, are covered by the Department of Justice's ADA Title II web rule, with compliance dates of April 26, 2027 or April 26, 2028 depending on population. Organizations receiving federal health funding are covered by the HHS Section 504 rule, with dates of May 11, 2027 or May 10, 2028 depending on employee count. Private businesses face no federal technical standard for websites but are sued regularly under Title III.

What is the difference between WCAG A, AA, and AAA?

They are conformance levels, not versions. Level A covers the most basic barriers, Level AA adds requirements like 4.5 to 1 text contrast and visible focus indicators, and Level AAA includes criteria that are impossible or inappropriate for some content. AA is the level named in the Title II and Section 504 rules and in nearly every grant agreement. Build to AA.

Will an accessibility widget make my site compliant?

No. Overlay widgets sit on top of your existing code and cannot fix the underlying markup. The Overlay Fact Sheet, signed by 1,048 accessibility professionals as of November 2026, states that no overlay can make a site fully compliant with any accessibility standard, and UsableNet's 2025 year-end lawsuit report found that companies already running widgets kept getting sued. In January 2025 the FTC announced a $1 million order against the vendor accessiBe over its compliance claims.

How much does an accessibility audit cost?

Specialist firms price a manual audit by the number of unique page templates and the depth of testing, and most quote on request rather than publishing a rate, so I will not invent a range. Automated-only scans are cheap or free but catch a minority of real issues; a GOV.UK audit of automated tools, published in 2017 and last updated in 2018, found the best one detected 40 percent of the 142 barriers planted for it. Fixing what the audit finds is separate work, usually billed hourly at agency rates Clutch's 2026 data puts at $100 to $149, or as a fixed scope.

Do Minnesota grants require an accessible website?

Many do, and more do every year. The State of Minnesota's own accessibility standard, administered by MNIT, was updated to WCAG 2.1 Level AA effective July 1, 2024, and state agency grant agreements often point to it. Federal pass-through dollars carry Section 504 obligations. Read the accessibility clause in your actual agreement before you assume, and ask the program officer what evidence they want if the language is vague.

Can I fix accessibility problems on a Squarespace or Wix site?

Most of them, yes. Contrast, alt text, heading order, link text, and captions are all editable inside those platforms without touching code. What you cannot always fix is the accessibility of the template's own navigation or slideshow components. Test first, then decide whether the template itself is the blocker.

Keep reading

Start a project

Ready to take your business to the next level?

Let's work together to create solutions that make a real impact. Tell us about your project and we'll come back with a clear plan.

(612) 293-0636info@tayopro.com