Xuru Technologies

Tag: ADA compliance

  • Restaurant Website Accessibility: Menus, Online Ordering and Reservations

    Skip to main content
    Blog · Accessibility · 7 min read

    Restaurant website accessibility: menus, ordering and reservations

    For a restaurant, three things on the website matter most: the menu, the order button and the booking form. Here is how to make sure every guest can use all three, including people who browse with a screen reader, a keyboard or zoom.

    By the Xuru Technologies team · 21 October 2026

    Key takeaways

    • Food service is consistently one of the most targeted industries in US digital accessibility lawsuits, second only to e-commerce in recent reports.
    • The biggest barriers on restaurant sites are predictable: image or PDF menus, ordering flows that can't be used with a keyboard, unlabeled form fields and low-contrast text.
    • Third-party ordering and reservation widgets are part of your guest's journey, so test them as if they were your own code.
    • Accessibility is not a one-time project: menus, specials and hours change weekly, and every change can introduce a new barrier.
    • This is practical guidance, not legal advice. For questions about your legal obligations, talk to a lawyer.

    Why restaurants keep showing up in accessibility claims

    Restaurants update their websites constantly, rely heavily on photos, and often bolt on ordering and booking tools from several different vendors. That combination makes accessibility barriers common, and easy for anyone to spot.

    The numbers reflect it. UsableNet's review of 2025 filings, published in January 2026, counted more than 5,000 digital accessibility lawsuits in the US last year, with e-commerce making up nearly 70% and food service roughly 21%. The same report found that a large share of federal cases were filed against companies that had already been sued before, which tells you that a quick fix after a first complaint often doesn't hold.

    There is also a well-known court decision in this space. In Robles v. Domino's Pizza, the Ninth Circuit held in 2019 that the ADA applied to Domino's website and app because of their connection to its physical restaurants, and the US Supreme Court declined to review the case in October 2019. Courts in different parts of the country still disagree on some of the details, which is one more reason to get advice from a lawyer about your specific situation.

    The US Department of Justice's guidance on web accessibility (March 2022) points businesses to the Web Content Accessibility Guidelines (WCAG) and lists exactly the kinds of barriers that are common on restaurant sites: missing alt text, poor color contrast, videos without captions and mouse-only navigation.

    The menu is usually the most visited page on a restaurant site, and the most likely to be inaccessible. The three classic problems are:

    • Menus as images. A photo of your printed menu is invisible to a screen reader and turns into a blur when someone zooms in on a phone.
    • Menus as untagged PDFs. Most PDFs exported from design tools have no reading order, headings or text alternatives, so assistive technology reads them as a jumble or not at all.
    • Prices and dietary icons that carry meaning only visually. A tiny leaf icon for "vegan" or a chili for "spicy" means nothing to a screen reader unless it has a text equivalent.

    The fix is a real HTML menu page: section headings for starters, mains and desserts; each dish as text with its price; and dietary or allergen information written out (or icons with proper text labels). It is better for search engines too, which is why we recommend it even before accessibility comes up. We cover the business case in why PDF menus lose customers.

    If you must keep a downloadable PDF for printing, keep it as a secondary option and make sure the HTML version has the same content and is updated at the same time.

    Online ordering: where the money is

    An ordering flow has more moving parts than any other page on your site: item options, quantity steppers, modals, a cart, a pickup or delivery time picker and a payment form. Each one can break for a keyboard or screen reader user. Common failures include:

    • "Add to order" buttons built from plain div elements that can't be reached with the Tab key.
    • Item pop-ups (modals) that don't move focus into the dialog, or trap the user inside with no way to close it.
    • Options such as size, sides or spice level shown as styled boxes with no labels, so a screen reader announces "button, button, button".
    • Cart updates that happen silently, with no announcement that an item was added.
    • Time-slot pickers that only work with a mouse, and checkout fields that rely on placeholder text instead of real labels.
    • Error messages shown only in red, with no text explaining what went wrong.

    Many restaurants use a hosted ordering platform rather than custom code. That is fine, but it doesn't take the issue off your plate: your guest experiences it as your website. Ask the vendor for their accessibility documentation or conformance report, and test the flow yourself (see the checklist below). If you are choosing a platform now, put accessibility on the comparison list alongside fees. Our guide to commission-free online ordering explains the setup options.

    Reservations and booking widgets

    Reservation tools are usually embedded widgets from OpenTable, Resy, SevenRooms or similar providers. Before you embed one, check:

    • Can you choose a date, party size and time using only the keyboard?
    • Does the calendar announce dates properly to a screen reader, or is it a grid of unlabeled numbers?
    • Does the widget have a meaningful title if it sits inside an iframe?
    • Is there an obvious alternative, such as a phone number or email link right next to it, for anyone the widget fails?
    • Do confirmation and error messages appear as text, not just a color change?

    Also think about what guests need to know before they arrive: step-free access, accessible restrooms, space for wheelchairs, and whether you can accommodate service animals and allergies. A short, honest "Accessibility at our restaurant" section on your contact or FAQ page answers questions that people otherwise have to phone to ask.

    A 20-minute restaurant accessibility check

    You don't need special software to find the biggest problems. Work through this on your home page, menu, ordering flow and reservations page.

    CheckHow to testWhat "good" looks like
    Keyboard onlyUnplug the mouse; use Tab, Shift+Tab, Enter and SpaceYou can browse the menu, add an item, check out and book a table, and you can always see where focus is
    Menu as textTry to select a dish name with your cursor; zoom to 200%Text selects and reflows; nothing is an image of text
    ImagesCheck food photos and logos for alt textMeaningful photos are described briefly; decorative images are skipped
    ContrastUse a contrast checker on prices, buttons and text over photosText meets WCAG AA contrast (4.5:1 for normal text)
    FormsClick each field label in checkout and booking formsEvery field has a visible label; errors are explained in words
    Pop-upsOpen an item modal or cookie banner with the keyboardFocus moves in, Escape closes it, and focus returns to where you were
    VideoPlay any promo or chef videoCaptions are available; nothing autoplays with sound
    AlternativesLook near the order and booking buttonsA phone number or email is easy to find for guests who prefer it

    Automated tools help, but they only catch part of the picture. The WebAIM Million 2026 study found detectable WCAG failures on 95.9% of the top one million home pages, with low-contrast text (83.9%), missing alt text (53.1%) and missing form labels (51%) the most common, and WebAIM notes that automated testing understates the real number of barriers. For a deeper list, see our WCAG 2.2 AA checklist for small business websites.

    A note on widgets that promise instant compliance

    It is tempting to add a one-line accessibility toolbar and move on. Those tools don't fix the underlying code of your menu or ordering flow, and UsableNet's data shows lawsuits continue to be filed against sites that use them. We explain why in why accessibility overlays don't make your website compliant.

    Keep it accessible as the menu changes

    Restaurants change their sites more often than most businesses: weekly specials, seasonal menus, new photos, holiday hours, a new ordering partner. Every update is a chance for a new image without alt text or a new button that only works with a mouse. That is why we treat accessibility as an ongoing service rather than a one-off audit. Our website accessibility plans include monthly monitoring (Monitor, US$99/month), hands-on fixes (Care, US$249/month, or Care Plus, US$499/month), and a full audit from US$690 if you want a detailed starting point. No service can promise you will never receive a complaint, but steady, documented improvement makes your site work for more guests.

    Frequently asked questions

    Does the ADA apply to my restaurant's website?

    Restaurants are public accommodations under the ADA, and the Department of Justice has said its requirements apply to goods and services offered on the web. How that applies to your specific business depends on your circumstances and location, so please consult a lawyer for advice on your obligations.

    Is a PDF menu enough if I also have it printed in the restaurant?

    A printed menu doesn't help someone deciding where to eat from home. An HTML menu page is the most reliable way to make your menu usable with screen readers and zoom, and it helps search engines understand what you serve.

    Our ordering system is run by a third party. Is that our problem?

    From your guest's point of view, it is your website. Ask the vendor for accessibility documentation, test the flow with a keyboard, and keep a phone or email alternative visible. If the platform has serious barriers, it may be worth comparing alternatives.

    How often should we check accessibility?

    At least monthly, and after any significant change such as a new menu layout, ordering partner or theme. Automated monitoring catches regressions early; periodic manual testing catches what tools miss.

    Website accessibility

    Is your menu usable by every guest?

    Take our 2-minute self-check to see where your restaurant website stands, then choose a monthly plan that keeps it accessible as your menu changes.

    Take the 2-minute self-checkSee monthly plans
    Keep reading
    Accessibility

    Hotel Website Accessibility: ADA Requirements for Booking Sites

    Restaurants

    Restaurant Reservation Systems: OpenTable vs Resy vs SevenRooms vs Direct Booking

    Have a project in mind?

    Let’s build
    what’s next.

    info@xurutechnologies.com +91 87992 91881 WhatsApp

    Websites, payments, digital marketing, AI automation, consultancy and practical technology training — for businesses and aspiring professionals worldwide.

    Monday – Friday: open 24 hours
    Saturday – Sunday: closed
    © 2026 Xuru Technologies Private Limited. All rights reserved. Serving clients worldwide · Mon – Fri, 24 hours

  • Hotel Website Accessibility: ADA Requirements for Booking Sites

    Skip to main content
    Blog · Accessibility · 7 min read

    Hotel website accessibility: ADA requirements for booking sites

    Hotels have an extra layer of ADA obligations that most businesses don't: the reservations rule. Here is what it asks your booking website to say and do, and how to make the booking journey itself usable for every guest.

    By the Xuru Technologies team · 20 October 2026

    Key takeaways

    • US hotels are subject to a specific ADA regulation on reservations, 28 C.F.R. § 36.302(e), which has applied to reservations made since March 15, 2012.
    • Your booking channels must identify and describe accessible features in enough detail for a guest with a disability to judge, independently, whether a room meets their needs.
    • Accessible rooms must be bookable during the same hours and in the same way as other rooms, and a reserved accessible room must be blocked and held for that guest.
    • Describing rooms is only half the job. The website and booking engine also need to work with a keyboard, screen reader and zoom, which is where WCAG 2.2 AA comes in.
    • This is general information, not legal advice. Talk to a lawyer about your property's specific obligations.

    What does the ADA require of a hotel booking website? In short, two things. First, under the Department of Justice's reservations rule, the site must let guests with disabilities reserve accessible rooms the same way as everyone else, and it must describe your accessible rooms and common areas in enough detail for them to decide for themselves. Second, the site itself has to be usable by people who rely on assistive technology, or the first requirement is meaningless. Most hotel accessibility complaints we see in published cases touch on one or both.

    The ADA reservations rule in plain English

    The rule sits in the Title III regulations at 28 C.F.R. § 36.302(e). The text, reproduced by the ILRU research center, covers reservations made by phone, in person or through a third party, and applies to reservations made on or after March 15, 2012. It requires a place of lodging to:

    1. Offer equal access to booking. Guests needing accessible rooms must be able to reserve them during the same hours and in the same manner as other guests.
    2. Identify and describe accessible features of the hotel and its guest rooms "in enough detail to reasonably permit individuals with disabilities to assess independently" whether a room meets their needs.
    3. Hold accessible rooms for people who need them until all other rooms of that type have been rented.
    4. Reserve and block a requested accessible room so it is removed from all reservation systems.
    5. Guarantee that the specific accessible room booked is held for that guest.

    The last three points don't apply to individual units that the operator doesn't own or substantially control, which matters for some condo-hotel and rental-pool arrangements. Your lawyer can confirm how that applies to you.

    How much detail your website needs

    The rule doesn't list exact fields, which is why it has been litigated. In Love v. Marriott Hotel Services (9th Cir. 2022), the Ninth Circuit found the rule ambiguous on detail and deferred to the Department of Justice's guidance. It held that the hotel's website was compliant because it stated the hotel was accessible, listed accessible room types, beds, bathing facilities and communication features, described accessible routes and areas, and gave a phone number for more information. The court also said a site doesn't need to repeat the technical specifications behind the word "accessible" where that term is defined in the ADA Standards.

    A summary of that guidance by attorneys at K&L Gates, published on Today's Hotelier, suggests that older properties built before the 1991 Standards should go further, describing the accessible entrance and route to check-in, the route to accessible rooms, and any features that fall short (for example, a narrower door with its measured width).

    Accessible-room information checklist

    InformationWhere it belongsExample
    Accessible room types availableRoom pages and booking engine"Deluxe King, accessible with roll-in shower"
    Bed size and numberRoom pages and booking engineOne king bed
    Type of bathing facilityRoom pages and booking engineRoll-in shower with fold-down seat, or tub with grab bars
    Communication featuresRoom pagesVisual alarms, notification devices, TTY or text options
    Accessible routes and common areasAccessibility pageStep-free entrance, route to check-in, pool lift, restaurant access
    Parking and arrivalAccessibility page, directionsLocation of accessible parking, valet availability
    Known limitations (older properties)Accessibility page and room pages"Bathroom door is 30 inches wide"
    A direct contactEvery room pagePhone and email for accessibility questions

    Make sure the same details appear on the OTAs and channel managers you use. The rule covers reservations made "through a third party", so it is worth keeping one master description and syncing it everywhere.

    Make the booking journey itself accessible

    A perfect room description doesn't help a blind guest who can't operate your date picker. Booking flows are where hotel sites tend to fail, because they combine calendars, pop-ups, room selectors and payment forms. Test these against WCAG 2.2 AA:

    • Date pickers work with the keyboard, announce the selected dates and allow typing dates directly.
    • "Accessible room" filters are labeled clearly and are not hidden behind an icon with no text alternative.
    • Room cards have descriptive alt text on photos and headings that a screen reader can jump between.
    • Guest and payment forms have visible labels, clear error messages and no time-outs that can't be extended.
    • Pop-ups and cookie banners can be closed with Escape and never trap keyboard focus or hide the focused item.
    • Confirmation pages and emails state the accessible features of the room booked, so the guest has a record.

    If your booking engine is a third-party product, ask the vendor for its accessibility conformance report and roadmap. Guests experience it as your website, whoever built it. Our guide to boutique hotel website design covers how to keep the booking path short, which helps every guest.

    Why hotels are frequent targets

    Hotel reservation pages are easy to review remotely, which made them a focus for "tester" lawsuits. The issue reached the US Supreme Court in Acheson Hotels v. Laufer, but, as Consumer Finance Monitor reported, the Court dismissed the case as moot on December 5, 2023 without deciding whether testers have standing. The practical lesson is that the question remains open, so publishing clear, accurate accessibility information is the sensible baseline. For the wider picture, see our article on ADA website lawsuits in 2026.

    A practical plan for your property

    1. Walk the property with a tape measure and record accessible features, routes and any limitations room by room.
    2. Write one master accessibility description and a dedicated accessibility page, then add the room-level details to each room page.
    3. Sync the details to your booking engine, channel manager and OTA listings.
    4. Check inventory rules so accessible rooms are held and blocked correctly when reserved.
    5. Audit the site and booking flow against WCAG 2.2 AA, fixing issues in the code rather than adding an overlay widget.
    6. Re-check after every change, including renovations, new room types and booking engine updates.

    Our website accessibility service can take the website side off your hands: an audit from US$690, then ongoing monitoring and fixes through Monitor (US$99/month), Care (US$249/month) or Care Plus (US$499/month). No service can promise you will never receive a complaint, but a tested, maintained site serves guests far better and puts you in a stronger position.

    This article is general information, not legal advice. Please consult a lawyer about your obligations under the ADA and any state or local law.

    Frequently asked questions

    Does the ADA reservations rule apply to small hotels and B&Bs?

    The rule applies to places of lodging covered by Title III. Very small owner-occupied properties may be treated differently under the ADA, so ask a lawyer to confirm where your property stands.

    Is it enough to say "accessible rooms available, call us"?

    Courts have looked for more than that. The guidance discussed in Love v. Marriott points to room type, beds, bathing facility, communication features and accessible areas, plus a contact for questions.

    Do OTA listings count?

    The rule covers reservations made through third parties, so keep your accessibility details consistent across your website, booking engine and the OTAs you use.

    Will an accessibility widget make our booking site compliant?

    No widget can describe your rooms or fix a broken date picker. Fix the underlying code and content, then monitor it as the site changes.

    Website accessibility

    Is your booking site ready for every guest?

    Take a two-minute self-check to see your likely risk areas, then choose an audit or a monthly plan that fixes issues in your code.

    Take the 2-minute self-checkSee monthly plans
    Keep reading
    Accessibility

    The WCAG 2.2 AA checklist for small business websites

    Hospitality

    Hotel website direct bookings in 2026: how to cut OTA commission

    Have a project in mind?

    Let’s build
    what’s next.

    info@xurutechnologies.com +91 87992 91881 WhatsApp

    Websites, payments, digital marketing, AI automation, consultancy and practical technology training — for businesses and aspiring professionals worldwide.

    Monday – Friday: open 24 hours
    Saturday – Sunday: closed
    © 2026 Xuru Technologies Private Limited. All rights reserved. Serving clients worldwide · Mon – Fri, 24 hours

  • WCAG 2.2 AA Checklist for Small Business Websites

    Skip to main content
    Blog · Accessibility · 7 min read

    The WCAG 2.2 AA checklist for small business websites

    WCAG is long and technical. Most small business sites only need to get a few dozen things right, on a handful of pages that matter. Here is a plain-English checklist you can work through, starting with the failures that turn up most often.

    By the Xuru Technologies team · 19 October 2026

    Key takeaways

    • WCAG 2.2 became a W3C Recommendation on October 5, 2023. It adds nine success criteria, six of them at Level A or AA, and removes 4.1.1 Parsing.
    • The WebAIM Million 2026 found detectable WCAG failures on 95.9% of the top one million home pages, with low-contrast text on 83.9% of them.
    • Six issues (contrast, alt text, form labels, empty links, empty buttons and page language) account for most automatically detected errors, so they are the best place to start.
    • Automated scanners only catch part of the picture. Keyboard and screen-reader checks on your key journeys are essential.
    • This is general information, not legal advice. Consult a lawyer about your obligations under the ADA, the European Accessibility Act or other laws.

    What does a WCAG 2.2 AA checklist look like for a small business? In practice it comes down to five groups of checks: text and color, images and media, navigation and keyboard use, forms and checkout, and the six criteria that are new in WCAG 2.2. Work through them on your highest-value pages first (home, services or products, booking or checkout, and contact) and you will cover the problems most likely to block a real customer.

    Why WCAG 2.2 AA is the sensible target

    The W3C's summary of what's new in WCAG 2.2 explains that the 2.2 version builds on 2.0 and 2.1, which remain essentially the same apart from the removal of the obsolete 4.1.1 Parsing criterion. Meeting 2.2 AA therefore also covers 2.1 AA, the level many laws and contracts still refer to. In the US, for example, the Department of Justice's 2024 rule for state and local governments adopts WCAG 2.1 Level AA. That rule does not directly cover private businesses, but it shows which standard regulators and courts tend to treat as the benchmark. If you sell to EU customers, our guide to the European Accessibility Act for non-EU businesses explains how the standard applies there.

    Start with the failures that show up most

    The WebAIM Million 2026 scanned the home pages of the top one million websites and found an average of 56.1 detectable errors per page. The same six problems top the list every year, and most of them are quick to fix:

    FailureShare of home pages (2026)Typical fix
    Low-contrast text83.9%Darken text or lighten backgrounds to at least 4.5:1 for body text
    Missing image alt text53.1%Describe what each meaningful image communicates; mark decorative images as empty
    Missing form input labels51%Give every field a visible, programmatically linked label
    Empty links46.3%Add text or an accessible name to icon-only links (social icons, logos)
    Empty buttons30.6%Name icon buttons such as search, menu, close and cart
    Missing document language13.5%Set the page language in your theme (for example, lang="en")

    Because these problems usually live in your theme, header and footer, one fix often repairs every page at once.

    The WCAG 2.2 AA checklist

    1. Text, color and layout

    • Body text has a contrast ratio of at least 4.5:1; large text and key interface elements (buttons, form borders, icons) at least 3:1.
    • Color is never the only way information is shown, such as red-only error messages or "required" fields marked only by color.
    • Text can be zoomed to 200% and the page reflows on a narrow screen without horizontal scrolling or overlapping content.
    • Headings follow a logical order (one H1, then H2s and H3s) that matches how the page looks.

    2. Images, video and documents

    • Meaningful images have alt text that conveys their purpose; product and room photos describe what matters to the buyer.
    • Videos have accurate captions; audio-only content has a transcript.
    • Nothing auto-plays sound, and moving carousels can be paused.
    • Key PDFs (menus, brochures, price lists) are accessible or also available as a web page.

    3. Navigation and keyboard

    • Every link, menu, button, filter and modal works with the keyboard alone (Tab, Shift+Tab, Enter, Space, Escape, arrow keys).
    • A visible focus indicator shows where you are at all times.
    • Focus never gets trapped in a pop-up, chat widget or cookie banner.
    • A "skip to content" link lets keyboard users bypass the menu.
    • Link text makes sense on its own ("View room rates", not "Click here").

    4. Forms, booking and checkout

    • Every field has a visible label; placeholders are not used as labels.
    • Errors are described in text, linked to the field and announced to screen readers.
    • Required fields and input formats (dates, phone numbers) are explained before submission.
    • Time limits can be extended, and date pickers can be operated with the keyboard or bypassed by typing.

    The six new Level A and AA criteria in WCAG 2.2

    These are the additions most older audits miss. Each one maps to a common pattern on small business sites.

    CriterionLevelWhat to check on your site
    2.4.11 Focus Not Obscured (Minimum)AASticky headers, cookie banners and chat bubbles don't completely hide the item that has keyboard focus
    2.5.7 Dragging MovementsAASliders, maps and drag-to-reorder features also work with simple taps or clicks
    2.5.8 Target Size (Minimum)AAButtons and links are at least 24×24 CSS pixels or have enough space around them
    3.2.6 Consistent HelpAPhone, chat or contact links appear in the same place on every page
    3.3.7 Redundant EntryAMulti-step forms don't ask for the same details twice (for example, billing address auto-filled from shipping)
    3.3.8 Accessible Authentication (Minimum)AALog-ins allow password managers and paste, and don't rely on puzzles without an alternative

    How to test without a big budget

    1. Pick your critical journeys. For a hotel, that is finding a room and booking; for a shop, finding a product and checking out; for a service business, reading a service page and sending an enquiry.
    2. Run an automated scan on those pages to catch contrast, labels, alt text and naming issues. WebAIM notes that not all conformance failures can be detected automatically, so treat a clean scan as a starting point.
    3. Unplug your mouse. Complete each journey with the keyboard alone and note anything you can't reach, see or close.
    4. Try a screen reader such as VoiceOver (Mac and iPhone) or NVDA (Windows) on your main form.
    5. Zoom to 200% and check on a phone in both orientations.
    6. Fix at the source in your theme and components, not with an overlay. Our article on why accessibility overlays don't make a site compliant explains why.
    7. Re-test after changes. New plugins, pages and campaigns reintroduce issues.

    If you'd rather hand this over, our website accessibility service starts with an audit from US$690, then keeps your site in shape through the Monitor plan (US$99/month), Care (US$249/month) or Care Plus (US$499/month). No provider can promise you will never receive a complaint or demand letter, but a tested, maintained site is far better for your customers and your position.

    This article is general information, not legal advice. Please consult a lawyer about your legal obligations under the ADA, the European Accessibility Act, the UK Equality Act or any other law.

    Frequently asked questions

    Is WCAG 2.2 AA legally required for my business?

    It depends on where you operate, who your customers are and what you sell. Many laws and contracts point to WCAG 2.1 AA, and 2.2 AA covers it. A lawyer can tell you what applies to you.

    How long does it take to meet WCAG 2.2 AA?

    It varies with the size and age of the site. Template-level issues such as contrast, labels and button names are often fixed quickly; custom booking engines or checkouts can take longer. An audit gives you a realistic plan.

    Can I just use an automated checker?

    Use one, but not on its own. Automated tools miss keyboard traps, confusing focus order, poor alt text and many form problems that only manual testing reveals.

    Do third-party booking or ordering widgets count?

    Customers experience them as part of your site, so test them too. If a vendor's widget fails, ask the vendor for their accessibility conformance information and roadmap.

    Website accessibility

    Not sure where your site stands? Check it in two minutes.

    Answer a few quick questions to see your likely risk areas, then choose an audit or a monthly plan that fixes issues in your code.

    Take the 2-minute self-checkSee monthly plans
    Keep reading
    Accessibility

    ADA website lawsuits in 2026: what small businesses need to know

    Accessibility

    Why accessibility overlays don't make your website compliant

    Have a project in mind?

    Let’s build
    what’s next.

    info@xurutechnologies.com +91 87992 91881 WhatsApp

    Websites, payments, digital marketing, AI automation, consultancy and practical technology training — for businesses and aspiring professionals worldwide.

    Monday – Friday: open 24 hours
    Saturday – Sunday: closed
    © 2026 Xuru Technologies Private Limited. All rights reserved. Serving clients worldwide · Mon – Fri, 24 hours

  • Why Accessibility Overlays Don’t Make Your Website Compliant

    Skip to main content
    Blog · Accessibility · 8 min read

    Why accessibility overlays don't make your website compliant

    A one-line script that promises instant accessibility is an appealing idea. Here is what overlays technically do, what regulators and experts have found, and the approach that actually fixes your site.

    By the Xuru Technologies team · 18 October 2026

    Key takeaways

    • Accessibility overlays run in the browser on top of your existing code. They can change some things on the page, but they can't reliably fix the underlying HTML, content and interaction problems that WCAG covers.
    • In 2025 the US Federal Trade Commission finalized an order requiring accessiBe to pay US$1 million over claims that its widget could make any website WCAG-compliant.
    • More than 1,000 accessibility professionals have signed the Overlay Fact Sheet, which states that no overlay can make a site fully compliant.
    • UsableNet's 2025 year-end report, which reviewed more than 5,000 digital accessibility lawsuits, found that widgets "did not slow litigation".
    • The approach that holds up is an audit, fixes in your templates and content, and ongoing monitoring. This is general information, not legal advice.

    Do accessibility overlays work? Not as a route to compliance. An overlay can adjust colors, enlarge text and patch a handful of predictable issues, but it can't rewrite how your site is built. Missing form labels, broken keyboard navigation, inaccessible checkouts and images described by guesswork all stay in your source code. If you want a site that people with disabilities can actually use, and a stronger position under the ADA, the European Accessibility Act or the UK Equality Act, the fix has to happen in the code and content itself.

    What an accessibility overlay actually is

    An overlay is a third-party JavaScript snippet you paste into your site. When a visitor loads a page, the script runs in their browser and tries to modify what they see. Most products combine two things:

    • A toolbar or widget. The familiar floating icon that opens controls for contrast, text size, cursor size, reading guides and similar settings.
    • Automated "repair". Scripts, often marketed as AI, that scan the page and inject attributes such as image descriptions, ARIA labels or heading roles after the page has loaded.

    Nothing changes on your server: your theme, templates and content stay exactly as they were. The overlay is a layer of guesses applied to each page view, and if the guess is wrong, or the script loads late or conflicts with a visitor's own software, the original barrier is still there.

    What overlays can and can't do

    Where they can help a little

    The Overlay Fact Sheet, written and signed by accessibility practitioners, accepts that some fixes can be applied when the page loads. Overlays may improve conformance with a few individual WCAG provisions.

    What they can't reliably fix

    The same fact sheet identifies the areas where automated repair is unreliable, and they are exactly the ones that tend to block real customers:

    • Image text alternatives. Software can describe a photo but can't know what it should communicate in context.
    • Form labels and error handling in checkout, booking and contact forms.
    • Keyboard access. Menus, filters, modals and date pickers built without keyboard support can't simply be patched from outside.
    • Modern dynamic interfaces. Sites built with frameworks such as React, Angular or Vue change content in ways overlays struggle to keep up with.
    • Non-HTML content. PDFs, canvas, SVG and media files are out of reach entirely.

    The toolbar side has its own problem. The fact sheet calls overlay widgets "unnecessary and are poorly placed in the technology stack", because people who need larger text or higher contrast usually already have those settings in their operating system, browser or assistive technology. The joint statement by the European Disability Forum and IAAP adds that overlays can interfere with assistive technology, override users' own settings, and raise privacy concerns when they detect that a visitor uses a screen reader, which can reveal a disability.

    What the evidence says

    The FTC's accessiBe order

    On January 3, 2025, the FTC announced a proposed order against accessiBe, alleging that claims its accessWidget tool could make any website WCAG-compliant were "false, misleading, or unsubstantiated." The agency also alleged that accessiBe formatted third-party articles and reviews so they looked like independent opinions. The Commission voted 5–0, and on April 22, 2025, it approved the final order. It requires a US$1 million payment and bars the company from claiming its automated products can make a website WCAG-compliant, or keep it compliant, without evidence. Announcing the case, Samuel Levine of the FTC's Bureau of Consumer Protection said: "Overstating a product's AI or other capabilities without adequate evidence is deceptive."

    What accessibility professionals think

    The Overlay Fact Sheet lists 1,048 named signatories, including WCAG and HTML contributors, assistive technology developers, lawyers and disabled users. It concludes: "No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard." In WebAIM's third survey of accessibility practitioners, with 758 responses, 67% rated overlays, plugins or widgets as not at all or not very effective. Among respondents with disabilities, that rose to 72%, and only 2.4% called them very effective. The EDF and IAAP statement puts it plainly: "Overlays do not make the website accessible or compliant with European accessibility legislation."

    What regulators and lawsuit data show

    The US Department of Justice's guidance on web accessibility and the ADA says automated checkers and overlays "can be helpful tools" but "need to be used carefully", and recommends pairing them with manual checks. Lawsuit data does not suggest widgets keep owners out of court either. The UsableNet 2025 year-end report reviewed more than 5,000 ADA-related digital accessibility lawsuits and concluded that "accessibility widgets did not slow litigation in 2025". For more on the US picture, see our guide to ADA website lawsuits in 2026.

    Overlay vs real remediation: a side-by-side comparison

    QuestionAccessibility overlaySource-code remediation
    Where the change happensIn each visitor's browser, after the page loadsIn your theme, templates, components and content
    Form labels and errorsGuessed and injected; unreliableLabels and messages built into the form
    Keyboard navigationLimited ability to repair custom widgetsMenus, modals and checkout rebuilt to work by keyboard
    Image descriptionsAutomated guesses without contextWritten by people who know what the image is for
    Assistive technology usersMay conflict with screen readers and personal settingsWorks with the tools visitors already use
    Can it achieve full WCAG conformance?No, according to the Overlay Fact SheetYes, when audited and maintained
    Evidence you can showA vendor's marketing claimsAudit report, fix log and accessibility statement
    If you cancelThe patches disappear with the scriptThe fixes stay in your site

    What to do instead

    Real remediation follows a steady pattern:

    1. Audit against WCAG 2.2 AA. Combine automated scanning with manual keyboard and screen-reader testing on your most important journeys: home, product or service pages, forms, booking and checkout. The WebAIM Million 2026 found detectable WCAG failures on 95.9% of the top one million home pages and warns that "not all conformance failures can be automatically detected".
    2. Fix at the source. Start with template and component fixes that repair many pages at once, such as navigation, buttons and form fields. Then work through content: alt text, link wording, headings and color contrast.
    3. Remove or reconsider the overlay. Once the code is fixed, test with the toolbar switched off; it may add little and can get in the way of assistive technology.
    4. Publish an accessibility statement. Explain your standard, known limitations and how people can report a problem. For EU sales this is expected; our post on the European Accessibility Act for non-EU businesses explains why.
    5. Monitor continuously. New pages, plugins and theme updates reintroduce issues. Regular re-testing keeps the gains you paid for.

    This is the work our website accessibility team does every month: an audit from US$690, then monitoring and fixes through the Monitor plan at US$99/month, Care at US$249/month or Care Plus at US$499/month. No provider can promise that you will never receive a complaint or demand letter, and anyone who does is repeating the mistake the FTC acted on. What we can do is help you build a site that genuinely works for disabled visitors and keep it that way.

    This article is general information, not legal advice. Please consult a lawyer about your legal obligations under the ADA, the European Accessibility Act, the UK Equality Act or any other law.

    Frequently asked questions

    Do accessibility overlays work at all?

    They can make limited visual adjustments and patch a few predictable issues. They can't reliably fix form labels, keyboard access, meaningful image descriptions or dynamic components, which is why experts and the FTC have rejected claims that they deliver compliance.

    Will an overlay protect us from an ADA lawsuit?

    There is no evidence that it will. UsableNet's 2025 year-end report found that accessibility widgets did not slow litigation, and it continued to record lawsuits against companies that had one installed. Talk to a lawyer about your own risk.

    Should we remove our overlay straight away?

    Removing it alone fixes nothing. Start with an audit, fix the underlying issues, then test the site without the overlay and decide whether it still adds anything for your visitors.

    Is automated scanning enough on its own?

    No. WebAIM and the US Department of Justice both note that automated tools miss some problems. A clean scan should be paired with manual keyboard and screen-reader testing.

    Website accessibility

    Relying on a widget? See what it's missing.

    Answer 11 quick questions to see your likely risk areas, then choose an audit or a monthly plan that fixes issues in your code, not on top of it.

    Take the 2-minute self-checkSee monthly plans
    Keep reading
    Accessibility

    ADA website lawsuits in 2026: what small businesses need to know

    Accessibility

    The European Accessibility Act for non-EU businesses selling online

    Have a project in mind?

    Let’s build
    what’s next.

    info@xurutechnologies.com +91 87992 91881 WhatsApp

    Websites, payments, digital marketing, AI automation, consultancy and practical technology training — for businesses and aspiring professionals worldwide.

    Monday – Friday: open 24 hours
    Saturday – Sunday: closed
    © 2026 Xuru Technologies Private Limited. All rights reserved. Serving clients worldwide · Mon – Fri, 24 hours

  • ADA Website Lawsuits in 2026: What Small Businesses Need to Know

    Skip to main content
    Blog · Accessibility · 8 min read

    ADA website lawsuits in 2026: what small businesses need to know

    Website accessibility claims are not slowing down. Here is what the latest filing data shows, why small businesses are frequent targets, and the practical steps that make your site genuinely usable — and harder to fault.

    By the Xuru Technologies team · 16 October 2026

    Key takeaways

    • Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, up 27% on 2024 — and filings kept climbing into 2026.
    • The US Justice Department says the ADA applies to what businesses offer online, and points to WCAG as helpful guidance.
    • The most common barriers are well known and fixable: low contrast, missing alt text, unlabeled forms, empty links and buttons.
    • Overlays and widgets are not a compliance shortcut. Real fixes in the code, plus ongoing monitoring, are what hold up.
    • This article is general information, not legal advice. Talk to a lawyer about your specific obligations.

    The numbers: website lawsuits are rising again

    After two years of decline, federal website accessibility filings bounced back. According to law firm Seyfarth Shaw's ADA Title III blog, plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025 — 665 more than in 2024, a 27% increase. Website cases made up 36% of all ADA Title III federal filings, up from 28% the year before.

    The trend continued in 2026. Seyfarth's mid-year review counted 5,006 federal ADA Title III lawsuits of all kinds in the first half of 2026, up 9% on the same period of 2025. Accessibility vendor UsableNet, whose research was summarized by Equidox in July 2026, projected that digital accessibility lawsuits (including state court cases) were on track to exceed 6,000 in 2026, nearly 20% more than in 2025.

    These figures don't include demand letters, which never reach a court and are not publicly counted. Seyfarth notes that demand letters and state-court suits are common, particularly against businesses with physical locations.

    Where the cases are filed

    Federal website cases cluster in a few states. In 2025, Seyfarth recorded 1,021 in New York, 961 in Florida (nearly double its 2024 total) and 585 in Illinois, followed by Minnesota and Pennsylvania. Where a case is filed doesn't always match where a business is based, so online sellers outside those states shouldn't assume the trend doesn't affect them — ask your lawyer how it applies to you.

    What the law actually says (in plain English)

    Title III of the Americans with Disabilities Act covers "public accommodations" — hotels, restaurants, shops, clinics and many other businesses open to the public. The Justice Department's guidance on web accessibility states that the ADA's requirements apply to all the goods and services businesses offer, "including those offered on the web." It gives businesses flexibility in how they comply, and names the Web Content Accessibility Guidelines (WCAG) as a helpful technical standard.

    There is still no detailed federal technical rule for private-sector websites, which is why WCAG 2.1 or 2.2 Level AA is the benchmark most audits and remediation plans use. A separate rule for state and local governments (Title II) had its deadlines pushed back by an interim final rule in April 2026, to April 2027 and April 2028 depending on population. That delay applies to public bodies, not to private businesses.

    Whether and how the ADA applies to your business — especially an online-only one — can depend on where you operate and which courts are involved. Please consult a qualified lawyer about your legal obligations.

    Why small businesses get targeted

    • Common barriers are easy to detect. The WebAIM Million 2026 report found detectable WCAG failures on 95.9% of the top one million home pages, with an average of 56.1 errors per page.
    • Online sales and bookings. Checkout, booking and reservation flows that can't be completed with a keyboard or screen reader block customers from buying at all.
    • Template sites. Off-the-shelf themes and page builders often ship with low contrast, empty buttons and unlabeled forms.
    • Limited resources. Small teams rarely have an accessibility specialist, so issues go unnoticed until someone complains.

    The barriers that show up again and again

    WebAIM found six issue types accounted for 96% of all detected errors in 2026:

    IssueShare of home pages (2026)What it means for visitors
    Low-contrast text83.9%Hard to read for people with low vision, or anyone on a phone in sunlight
    Missing image alt text53.1%Screen reader users can't tell what an image shows or what a linked image does
    Missing form labels51%Booking, contact and checkout fields aren't announced properly
    Empty links46.3%Icons or links with no text give no clue where they go
    Empty buttons30.6%"Menu", "Search" or "Add to cart" buttons are silent to assistive tech
    Missing page language13.5%Screen readers may pronounce content incorrectly

    Source: WebAIM Million 2026. Automated tools only catch part of the picture; manual testing with a keyboard and screen reader finds issues such as focus traps and confusing error messages.

    A word on overlays and widgets

    Plug-ins that promise "instant compliance" are tempting, but they don't fix the underlying code. In April 2025 the US Federal Trade Commission approved a final order requiring accessiBe to pay US$1 million, alleging its widget did not make all websites WCAG-compliant as advertised. Fixing your theme, content and forms at the source is the approach that actually helps users.

    A practical risk-reduction checklist

    StepWhy it matters
    1. Run an audit against WCAG 2.2 AA (automated plus manual)Gives you a prioritized list of real barriers
    2. Fix key journeys first: home, menu or product pages, booking, checkout, contactThese are the pages customers rely on most
    3. Fix the theme and templates, not just single pagesOne template fix can repair hundreds of pages
    4. Train whoever adds content (alt text, headings, link text)New content is a common way issues return
    5. Publish an accessibility statement with a contact routeLets users report problems directly to you
    6. Monitor monthly and re-test after changesPlug-in updates and new pages can reintroduce barriers
    7. Keep records of audits and fixesDocuments your ongoing effort; your lawyer can advise how this helps

    Not sure where you stand? Our 2-minute accessibility self-check flags likely problem areas. We also offer a full audit from US$690 and monthly plans — Monitor at US$99/month, Care at US$249/month and Care Plus at US$499/month. No service can promise you won't be sued, but a usable, well-maintained site is the strongest position to be in.

    Frequently asked questions

    Does the ADA apply to my website if I'm a small business?

    Title III doesn't set a minimum business size for public accommodations, and the Justice Department says its requirements extend to services offered online. How it applies to your situation depends on your business and location, so please consult a lawyer.

    Which WCAG version should I aim for?

    Most businesses target WCAG 2.2 Level AA, the current W3C recommendation. It includes everything in WCAG 2.1 AA plus a few extra criteria, such as minimum target sizes and focus that isn't hidden.

    We received a demand letter. What should we do?

    Don't ignore it, and don't install a quick-fix widget in a panic. Contact a lawyer promptly, keep a copy of your site as it is, and get a proper audit so you understand the real issues.

    Is a one-time fix enough?

    Rarely. New pages, products, plug-in updates and design changes regularly reintroduce issues, which is why monthly monitoring matters.

    Website accessibility

    Find your accessibility gaps before someone else does.

    Answer 11 quick questions and see your likely risk areas, then choose an audit or a monthly plan.

    Take the 2-minute self-checkSee monthly plans
    Keep reading
    Website revamp

    9 signs your website needs a redesign

    Restaurants

    Restaurant website must-haves for 2026

    Have a project in mind?

    Let’s build
    what’s next.

    info@xurutechnologies.com +91 87992 91881 WhatsApp

    Websites, payments, digital marketing, AI automation, consultancy and practical technology training — for businesses and aspiring professionals worldwide.

    Monday – Friday: open 24 hours
    Saturday – Sunday: closed
    © 2026 Xuru Technologies Private Limited. All rights reserved. Serving clients worldwide · Mon – Fri, 24 hours