Web accessibility, answered plainly

Web accessibility is the practice of building websites, apps, and documents that people with disabilities can use - including people who are blind or have low vision, are deaf or hard of hearing, have motor limitations, or have cognitive disabilities. In practice it means content works with screen readers, can be operated by keyboard alone, has sufficient color contrast, captions, and clear structure. About one in four U.S. adults lives with a disability.

WCAG (Web Content Accessibility Guidelines) is the international standard for web accessibility, published by the W3C. It has three conformance levels - A, AA, and AAA. Level AA is the benchmark referenced by nearly every accessibility law, including the ADA Title II rule and Section 508. See our WCAG overview.

WCAG 2.2, published in October 2023, adds nine success criteria on top of WCAG 2.1 - covering focus visibility, dragging alternatives, minimum target size, and accessible authentication. The DOJ Title II rule legally requires WCAG 2.1 Level AA, but building to 2.2 AA meets that requirement and future-proofs your site. AX4E audits against both.

Yes. ADA Title II requires it for state and local governments (with fixed deadlines), ADA Title III applies to businesses open to the public, and Section 508 covers federal agencies and federally funded technology. Several states add their own laws. See our legislation guide.

Very few. The WebAIM Million study finds detectable WCAG failures on roughly 96% of the top one million homepages, with an average of 56 errors per homepage. The gap between what the law requires and what is actually built remains enormous - which is also why enforcement and litigation keep growing.

People with disabilities and their families control over $13 trillion in annual disposable income globally, and accessible sites serve them better. Accessibility work also overlaps heavily with SEO (semantic structure, alt text, clear headings) and improves usability for everyone - older users, mobile users, and people in noisy or bright environments.

Title II of the Americans with Disabilities Act applies to state and local governments and everything they offer the public. In 2024 the Department of Justice published a final rule setting specific technical requirements for web content and mobile apps, with firm compliance deadlines. Details on our Title II page.

Every state and local public entity: cities, counties, courts, K-12 school districts, public universities and community colleges, transit agencies, libraries, police and fire departments, and special districts (water, utility, park districts). Content a vendor provides on a public entity's behalf is covered too.

April 26, 2027 for public entities serving populations of 50,000 or more, and April 26, 2028 for entities under 50,000 and all special districts. These reflect the DOJ interim final rule of April 2026, which extended the original deadlines by one year. Track your deadline with our free Title II checklist.

WCAG 2.1 Level AA. All web content and mobile apps a public entity provides or makes available must conform, with limited exceptions for archived and certain preexisting content.

Yes. The rule explicitly covers both web content and mobile applications that public entities provide or make available, including apps built or run by contractors on their behalf.

Yes. Conventional electronic documents - PDFs, Word files, spreadsheets, presentations - must meet WCAG 2.1 AA, with an exception for preexisting documents that are not currently used to apply for, access, or participate in services. New and actively used documents must be accessible. AX4E offers batch PDF remediation.

The main exceptions: archived web content, preexisting conventional documents not in active use, third-party content not provided under contract or arrangement, individualized password-protected documents, and preexisting social media posts. The exceptions are narrow - if content is needed to use a service today, it almost certainly must be accessible.

Exposure to DOJ enforcement, private lawsuits, and complaints filed with federal funding agencies. Documented, good-faith progress - scans, remediation logs, an accessibility statement, and a roadmap - is the strongest position if you cannot finish everything in time. AX4E builds that documentation trail automatically.

Yes - by April 26, 2028. The smaller-entity deadline is later, not optional. Small entities also tend to have the most inaccessible legacy content, so starting early matters more, not less.

If you provide it under a contract, license, or other arrangement - payment portals, registration systems, agenda platforms - yes, it is your responsibility under the rule. Build WCAG 2.1 AA conformance into procurement contracts and ask vendors for a current VPAT or accessibility conformance report.

In practice, yes. ADA Title III covers businesses open to the public, and the DOJ and most courts treat websites of those businesses as covered. There is no formal Title III web regulation yet, so WCAG 2.1/2.2 Level AA is the de facto standard courts and settlements reference. See our Title III page.

Over 4,600 ADA web accessibility lawsuits are filed in U.S. courts annually, and pre-suit demand letters are estimated to outnumber filed cases several times over. E-commerce, food service, healthcare, and education sites are the most frequent targets.

The same short list, over and over: missing image alt text, forms and checkout flows that screen readers cannot complete, missing labels and button names, keyboard traps, poor contrast, and inaccessible PDFs. These are exactly what an automated scan surfaces first - run a free scan to see where you stand.

Talk to your attorney first - this page is not legal advice. In parallel, start documented remediation immediately: a full audit, prioritized fixes, an accessibility statement, and a remediation log. Demonstrable progress and evidence are what resolve these matters; an overlay widget alone does not. AX4E provides the audit and evidence package legal teams ask for.

Yes. Hundreds of lawsuits have been filed against sites running overlay widgets, because a widget does not fix the underlying code that screen readers and assistive technology depend on. A widget helps users and shows good faith - defensibility comes from remediation plus documentation.

Section 508 of the Rehabilitation Act requires federal agencies - and technology bought, built, or used by them - to be accessible. It incorporates WCAG 2.0 Level AA, and in practice procurement teams expect current WCAG AA conformance. If you sell to the federal government, you will be asked for a VPAT. See our Section 508 page.

A VPAT (Voluntary Product Accessibility Template) is the standardized document that becomes an Accessibility Conformance Report - it states, criterion by criterion, how your product meets WCAG and Section 508. You need one to sell software or digital services to federal agencies and, increasingly, to state, local, and education buyers. AX4E Enterprise includes VPAT preparation.

The EAA has been enforceable since June 28, 2025 and requires accessibility for a broad range of products and services sold in the EU - including e-commerce, banking, and e-books - measured against EN 301 549, which incorporates WCAG. U.S. companies selling into Europe are in scope.

Yes. California's Unruh Act attaches statutory damages to ADA violations (a major driver of lawsuit volume), New York is the other leading filing venue, and states like Colorado have their own accessibility mandates for public entities. Meeting WCAG 2.1 AA addresses the substance of all of them.

No. No widget or overlay alone makes a website compliant, including ours. A widget provides real user-facing accommodations and demonstrates good-faith effort, but WCAG conformance requires fixing the underlying code - verified by people. Any vendor that claims one line of JavaScript equals compliance is misleading you.

One embed adds read-aloud, text resizing, dyslexia-friendly fonts, contrast and color themes, reading aids, motion reduction, and keyboard enhancements to any site. It is a genuine usability layer for visitors and a visible signal of commitment - the first step of the compliance stack, not the whole thing.

Because overlay-only vendors marketed widgets as instant, complete compliance - and that claim is false. In 2025 the FTC finalized a $1 million order against a major overlay vendor for deceptive claims that its AI widget could make any website WCAG-compliant. The criticism targets the overclaiming, and we agree with it: a widget is a layer, not a fix.

We lead with the truth the overlay industry was fined for hiding: the widget alone is not compliance. AX4E pairs the widget with full-site AI audits, code-level fix suggestions, PDF remediation, human-verified expert audits, and the legal documentation that makes your position defensible. Software where software works, certified humans where it doesn't.

No tool can guarantee that. A widget reduces real barriers for visitors and demonstrates good faith, which matters. But legal defensibility comes from remediated code, an accessibility statement, and a documented trail of ongoing work - which is exactly what the Pro and Enterprise plans produce.

Three plans: Free (widget on one site plus a basic scan), Pro at $39/month or $390/year (two months free on annual), and Enterprise with custom pricing for manual audits, VPATs, and consulting. A 3-site Pro bundle is $99/month or $990/year. See full pricing.

The AX4E widget on one site (AX4E-branded), a scan of up to 10 pages, and visibility into your top 5 WCAG issues. It shows you the problem for free; Pro is what fixes it. Start with a free scan - no card required.

Everything you need to make and document real progress on one site: the full widget, a complete WCAG 2.1 AA AI audit of all pages, AI-generated code fix suggestions, compliance badge and accessibility statement, PDF and document remediation, AI alt-text generation, and continuous monitoring with violation alerts - $39/month or $390/year.

Yes - Pro is $390/year, which is two months free versus $39 × 12 ($468). The 3-site bundle is $990/year versus $1,188 paid monthly.

Yes. The 3-site Pro bundle is $99/month or $990/year. For larger portfolios - districts, county families of sites, agencies managing client sites - talk to us about Enterprise pricing.

No. Monthly plans are month to month. Annual plans simply prepay twelve months at the discounted rate. Enterprise engagements are scoped per project.

Entry plans from major overlay vendors start around $490/year, and managed platforms run $199 to $799 per month. AX4E Pro is $390/year - below the market entry point - because the widget and audit are how we earn trust, and we are honest that the deeper remediation work is where real conformance work happens.

Two free steps: run the free scan to see your top WCAG issues, and work through the free Title II checklist to assess your program - it has a plain-language mode for leadership and an IT mode for your web team. Then prioritize fixes by user impact and legal risk.

It depends on site size and how much legacy content you have. A small site can reach WCAG 2.1 AA in weeks; a large government or university web presence typically needs a phased roadmap over several months - which is exactly why the 2027 and 2028 Title II deadlines reward starting now, not the quarter before.

It is a public page describing your commitment, the standard you target (WCAG 2.1 AA), known limitations, and how users can report barriers. You should have one - it is expected by users, referenced in legal matters as evidence of good faith, and included automatically in AX4E Pro.

Yes. We remediate PDFs and conventional documents at scale - tagged reading order, headings, tables, accessible form fields, and alt text - including batch remediation for the large document libraries common on government and education sites. PDF remediation details.

Yes - role-based courses for developers, content authors, and procurement teams through the Title II Center, with certification. Training is how compliance survives staff turnover; the Title II rule era makes it a budget line, not a nice-to-have.

A free interactive self-assessment at TitleIIChecklist.com with two paths: a 5-question plain-language version for leadership and a 10-item technical essentials version for IT. It scores you live, saves progress, and prints - useful as the first artifact in your compliance file.

No - accessibility regresses with every new page, post, and PDF. The Title II rule expects conformance on an ongoing basis, so continuous monitoring with alerts (included in Pro) plus periodic manual audits is the sustainable model. Treat it like security: a practice, not a project.