A retail-shop owner in Nob Hill in Albuquerque got a demand letter last spring: her website’s color contrast was too low for a screen reader user, and unless she fixed it in thirty days, she was looking at a federal ADA claim. She had eight employees. Her site had been designed by a local freelancer in 2019 and hadn’t been touched since. This is what website accessibility enforcement looks like for small businesses now — not government audits, not fines from a regulator, but plaintiffs’ attorneys sending demand letters and filing complaints.
The good news: the legal standard is knowable, most of the fixes are straightforward, and the same work that reduces legal exposure also makes your site work better for every visitor. Here is what small-business owners in New Mexico (and everywhere else) actually need to know about website accessibility in 2026.
The short version of the law
Title III of the Americans with Disabilities Act applies to “places of public accommodation” — a category federal courts have consistently ruled includes commercial websites. There is no federal regulation spelling out exactly what an accessible commercial website looks like. Instead, courts and plaintiffs’ attorneys have converged on a technical standard: the Web Content Accessibility Guidelines, currently at version 2.2, at conformance Level AA.
WCAG 2.1 Level AA is what most consent decrees, settlement agreements, and demand letters cite today. WCAG 2.2, published by the W3C in October 2023, adds nine new success criteria on top of 2.1 — most of them concerned with cognitive accessibility and touch-target size. Building to WCAG 2.2 AA now is the sensible target, because you get 2.1 AA for free and stay ahead of the next round of enforcement.
Title II of the ADA — which covers state and local government sites — got a hard rulemaking in 2024, with compliance dates of April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for smaller ones. That deadline does not apply to your business directly, but it is a big part of why “ADA accessibility” is suddenly in the news.
Why 2026 is different
Digital-accessibility litigation is not slowing down. In 2025, plaintiffs filed 3,117 website-accessibility lawsuits in U.S. federal court alone — a 27% increase over 2024 — and total filings including state courts exceeded 5,000 cases. Nearly eight in ten of those are now filed in state courts, where the procedural defenses available to defendants are weaker than in federal court.
The distribution matters more than the total. Roughly 64% of these lawsuits targeted companies with annual revenue under $25 million. E-commerce and retail businesses were named in about 70% of cases; food and beverage in another 21%. If you run a shop, a restaurant, a bar, a spa, or an online store, the risk is real, and it is not concentrated on the giants.
What “accessible” actually means in practice
Automated scanners find six categories of failures that account for roughly 96% of everything they catch. They are also the six that plaintiffs’ attorneys screen for first. In descending order of prevalence:
- Low color contrast. Present on 83.9% of homepages tested by WebAIM in 2026. Body text must have a 4.5:1 contrast ratio against its background; large text and UI components need 3:1.
- Missing alternative text on images. Every meaningful image needs an
altattribute describing what it conveys. Decorative images should havealt="", not be skipped. - Empty links and buttons. A link with no text, or an image link with no alt text, is a dead end for a screen reader.
- Missing form labels. Every input needs a programmatically associated
<label>. Placeholder text does not count. - Missing document language. The
<html lang="en">attribute tells assistive tech what language to read the page in. - Missing or out-of-order headings. Screen-reader users navigate by heading. Skipping from H1 straight to H4 breaks the outline.
Fix those six categories and you have removed most of your legal exposure. You have also made your site substantially better for every user — better contrast for anyone reading in bright sunlight, cleaner headings for anyone skimming, real labels for anyone filling out a form on a phone.
Does my small business website legally have to be accessible?
Yes, if your business is a “place of public accommodation” — which effectively means any business open to the general public: retail, restaurants, hotels, health providers, professional services, entertainment venues, and most online-only businesses. The ADA does not include a small-business exemption for accessibility the way it does for physical construction. A five-person shop in Las Cruces is subject to the same legal standard as a national chain. What differs is your exposure and the practical steps that make sense at your scale.
A realistic starting checklist
No small business fixes accessibility in one sprint. But you can knock down the biggest risks in a week of focused work:
- Run a free automated scan. WAVE (from WebAIM) and axe DevTools are the two most-cited free tools. They will surface the six categories above and give you a triage list.
- Fix contrast first. It is the most common failure and usually a matter of tweaking a few color values in your theme.
- Audit every image. Add
alttext to meaningful images; usealt=""for purely decorative ones. - Fix your forms. Every field labeled, every error explained in words, every required field marked.
- Check your headings. One H1 per page; no skipping levels.
- Test with a keyboard. Unplug your mouse and try to navigate your site with Tab, Shift+Tab, and Enter. If you get stuck, so does someone using assistive tech.
That is the 80/20. It will not get you to full WCAG 2.2 AA — real conformance also requires a manual audit — but it will move you from “sitting duck” to “reasonably defensible.”
What automated tools actually catch (and what they don’t)
Automated tools, including the AI-powered “accessibility overlays” that pop up on many small-business sites, catch 30–40% of WCAG failures. The rest — screen-reader compatibility, cognitive load, keyboard traps in interactive components, meaningful reading order in complex layouts — require a human evaluator using real assistive technologies. Overlays in particular have been named in an increasing share of lawsuits, because they can create their own accessibility problems while giving owners false confidence.
Treat automated tools as triage, not certification. If your risk profile is high — an e-commerce store, a healthcare site, a booking system — budget for a manual audit from a specialist who tests with a screen reader and a keyboard.
What good sites build in from the start
The cheapest accessible site is one that was accessible from day one. A well-built WordPress site should ship with correct heading structure, semantic HTML, keyboard-navigable menus, sufficient contrast, and labeled forms — not because of a lawsuit but because those are the same choices that produce a faster, better-organized site. When I rebuilt the St. Elizabeth Shelter site in Santa Fe, mobile-first responsive design, keyboard-accessible navigation, and full Spanish translation were not line items added at the end. They were the design brief.
If you are planning a rebuild anyway, put WCAG 2.2 AA in the scope as a stated requirement, and ask the developer how they will verify it. If your current site is holding up otherwise, a targeted remediation pass is usually the cheaper path — and a good developer can quote it honestly once they have seen a scan report and spent an hour with a keyboard.
The bottom line
Website accessibility is one of those areas where doing the right thing and doing the safe thing point in the same direction. Patrick Iverson builds custom WordPress websites for Santa Fe, Albuquerque, and small businesses across New Mexico with accessibility built in from the first line of markup — not bolted on later with an overlay. If your site was built before WCAG 2.2 was on anyone’s radar and you would like a straight read on where you stand, get in touch.