Website accessibility guides
Answers for the people who run websites: what the rules ask of a business, how to check a site, what common problems look like and how to fix them. When you want to see your own pages, run a free scan.
Law and compliance
What the ADA, WCAG, the European Accessibility Act and Section 508 mean for a website, in plain language.
- ADA website compliance: a practical checklist for small businesses
The ADA does not name a technical standard for private-business websites, but WCAG is the benchmark most often used in practice.
- Received an ADA website demand letter or lawsuit? What to do first
Do not ignore it, and do not pay or admit anything before speaking with an attorney who handles accessibility claims.
- The ADA Title II web rule: who it covers, deadlines and what to test
The DOJ's Title II rule requires state and local government web content and mobile apps to meet WCAG 2.1 Level AA.
- WCAG compliance levels and versions explained: A, AA, AAA and 2.0, 2.1, 2.2
WCAG is the W3C's set of web accessibility success criteria, organized into levels A, AA and AAA.
- The European Accessibility Act and online stores: what sellers need to know
The European Accessibility Act has applied since 28 June 2025.
- Section 508 website requirements: who they apply to and what to test
Section 508 applies to U.S.
Testing and tools
How to check a site yourself, which free tools are worth using, and what automated scanners can and cannot find.
- How to check if a website is accessible: a free 15-minute test
Run a free automated scan, then spend ten minutes using the page with only a keyboard, zoomed to 200 percent.
- Free website accessibility checkers compared: WAVE, axe, Lighthouse, Pa11y and more
WAVE is the friendliest visual checker, axe DevTools and Lighthouse suit people comfortable with browser developer tools, Pa11y suits automation, and Accessibility Insights adds guided manual tests.
- What automated accessibility scanners can and cannot find
Scanners reliably catch rule-based problems such as missing form labels, low text contrast, empty buttons and invalid ARIA.
Audits, reports and buying decisions
What audits cost, how overlays differ from fixing the code, and the documents buyers and regulators ask for.
- How much does a website accessibility audit cost? What you are paying for
Costs range from free automated scans to quoted manual audits, and the price depends on how many pages and templates are tested, how deep the testing goes and whether fix guidance and retesting are included.
- Accessibility overlays explained: what they do, what critics say and what to do instead
An overlay is a script that adds a toolbar and automatic adjustments to a site without changing its underlying code.
- How to write a website accessibility statement (with a template)
A good accessibility statement says which standard you aim for, what you have tested, what you know is not yet fixed, how to reach a person and when you last reviewed it.
- VPATs and accessibility conformance reports (ACRs) explained
A VPAT is the Voluntary Product Accessibility Template; an Accessibility Conformance Report (ACR) is the completed document that describes how a product meets accessibility standards.
Shopify, Wix, WordPress and Squarespace
What each platform handles for you, and what stays with the site owner.
- Shopify accessibility: what your theme and apps handle, what you do, and how to test
Shopify provides accessibility requirements for themes and publishes a conformance report for its checkout, but accessibility of your store depends on the theme you choose, the apps you add and the content you publish.
- Wix accessibility: what the Accessibility Wizard does, what it misses and what you still do
Wix's Accessibility Wizard scans your site from the editor, lists detected issues and manual tasks, and a Monitor rechecks the published site.
- Squarespace accessibility: built-in tools and what stays with the site owner
Squarespace gives you tools such as alt-text fields and color controls, but meeting accessibility goals is up to the site owner: choose high-contrast colors, describe images, use real heading levels, write clear link text and label forms.
- WordPress and WooCommerce accessibility: themes, plugins and checkout
A WordPress theme tagged accessibility-ready has passed a manual review against the theme team's minimum standards, but the tag does not guarantee conformance with WCAG AA.
Common problems and how to fix them
The issues that show up most on real pages, with before-and-after code.
- Color contrast and WCAG: the ratios you need and how to fix low contrast
Normal text needs a contrast ratio of at least 4.5 to 1 against its background, large text needs 3 to 1, and interface parts such as input borders and icons need 3 to 1.
- Alt text best practices: how to write image descriptions that work
Write alt text that gives the same information or function as the image, in a short phrase, and use an empty alt (alt="") for purely decorative images.
- Accessible forms: labels, placeholders and error messages that work
Give every field a visible label that is programmatically tied to it with for and id, do not use a placeholder as the only label, mark required fields in text, and show errors in words next to the field and in a summary.
- Keyboard focus: how to make sure people can see where they are (WCAG 2.4.7)
Anyone using a keyboard needs a visible indicator of where focus is.
- Fixing links and buttons with no accessible name
Every link and button needs a name that says what it does, in its visible text or in an accessible label.
- Heading structure for accessibility: how to use H1 to H6 correctly
Use one H1 for the page's main title, follow with H2s for major sections and H3s inside them without skipping levels, and use real heading tags rather than bold or large text.
- Target size (WCAG 2.5.8): the 24 by 24 pixel rule and how to meet it
WCAG 2.5.8, new in WCAG 2.2 at Level AA, asks that pointer targets are at least 24 by 24 CSS pixels, unless enough spacing separates them or another exception applies.
- Zoom and reflow: making pages work at 200 percent and 400 percent zoom
At 400 percent zoom (a 320 pixel wide view) content should reflow into a single column without horizontal scrolling, text should resize to 200 percent without loss, and the page must never disable pinch zoom.
Stores, launches and agencies
Checklists for online stores, redesigns and upkeep, how accessibility relates to SEO, and a workflow for agency client work.
- E-commerce accessibility checklist: from product page to checkout
Test the whole path a customer takes: find a product, choose options, add to cart, check out and manage an account.
- Website redesign, launch and maintenance: an accessibility checklist
Decide on WCAG 2.2 Level AA before design starts, check colors and components early, test templates as they are built, scan and hand-test before launch, and recheck after every release.
- Accessibility and SEO: where the work overlaps and where it does not
Many accessibility fixes (descriptive alt text, clear headings, meaningful link text, page titles, a stated page language) also give search engines clearer information.
- Small business website compliance checklist: accessibility, privacy, cookies and email
A small business website generally needs accessible pages, a privacy policy if it collects personal information, cookie notices for visitors in places that require them, email that follows CAN-SPAM, and a secure payment setup.
- Accessibility QA for agencies and freelancers: a repeatable workflow for client sites
Scope by template instead of by page, scan each template, fix the findings, hand-test the key flows, recheck and give the client a dated record.