Website accessibility checker with fixes your developer can act on
Accessibility issues lock out people who use screen readers, keyboards or zoom, and many sites are now expected to meet WCAG. This prompt has your todo.is agent test your key pages in a browser, check the most common WCAG 2.2 AA problems and write each issue with who it affects and the exact fix.
The prompt
- Check these pages for accessibility: [PAGE LINKS]. Test against WCAG 2.2 level AA. Check: color contrast of text and buttons, alt text on images, heading order, link and button names, form labels and error messages, keyboard navigation and visible focus, skip link, page language, zoom to 200% and reflow at 320 px wide, captions on videos, and automatic motion. For each issue give: the page, the element, the WCAG criterion, who it affects, severity and the exact fix (with a code example where helpful). Our site is built with [PLATFORM]. Write a Word report with a summary for [AUDIENCE] and an Excel list of all issues. Note what needs a manual test with a real screen reader.
What to change
- [PAGE LINKS]: 3 to 10 key pages, e.g. homepage, a product page, the contact form and checkout.
- [PLATFORM]: e.g. "WordPress with the Astra theme", "Shopify" or "custom React". Helps tailor the fixes.
- [AUDIENCE]: Who reads the summary, e.g. "the owner, non-technical" or "our front-end developer".
Example result
- Accessibility report · Fernway Books (example)
- Standard: WCAG 2.2 AA · Pages: 5 · Checked Oct 8
- Summary
- The site reads well with a screen reader on most pages, but the checkout form is hard to use without a mouse and several buttons have low contrast. 4 high-severity issues should be fixed first.
- High severity
- • Form fields without labels (checkout, 1.3.1 and 3.3.2). The "Postcode" and "Card name" fields only use placeholder text, which disappears when typing and isn't read reliably. Fix: add a visible <label for="postcode">Postcode</label>.
- • No visible focus (all pages, 2.4.7). Keyboard users can't see where they are. Fix: remove "outline: none" and add a clear focus style, e.g. a 2 px outline in a dark color.
- • Keyboard trap in the cookie dialog (all pages, 2.1.2). Tab can't leave the dialog. Fix: make the close button reachable and return focus to the page.
- • Low contrast "Add to basket" button (product page, 1.4.3). Light grey text on white measures about 2.8:1. Normal text needs 4.5:1.
- Medium severity
- • 12 images without alt text, mostly book covers. Fix: alt="Cover of The Salt Road by M. Okafor".
- • Icon-only search button has no name (4.1.2). Fix: aria-label="Search".
- • Heading levels skip from H1 to H4 on the homepage (1.3.1).
- • Error message only in red on the newsletter form (1.4.1). Add text such as "Enter a valid email".
- Passed
- • Page language set, pages reflow at 320 px, zoom to 200% works
- Needs a manual test
- • Full checkout with NVDA or VoiceOver
- • Captions accuracy on the author video
- Automated and browser checks can't prove full compliance. Use this as a fix list, then test with real assistive technology.
How to do it with todo.is
- Copy the prompt and list the pages your visitors use most.
- Paste it into todo.is or send it to your agent by email or Slack.
- Your agent opens each page, checks contrast, structure and keyboard use, and maps each issue to WCAG.
- Hand the Excel list to your developer, then ask your agent to re-check the same pages after the fixes.
Tips for a better result
- Start with the pages people must complete: sign-up, checkout, booking and contact forms.
- Fix shared parts first. A header, footer or cookie banner issue repeats on every page.
- Alt text should describe what matters in the image. Decorative images should have empty alt text (alt="") instead.
- Ask for an accessibility statement draft once the main fixes are done.
website accessibility checker: FAQ
- What is WCAG 2.2 AA? The Web Content Accessibility Guidelines are the common standard for accessible websites. Level AA is the level most laws and policies point to.
- Can an automated checker make my site fully compliant? No. Tools catch many issues, but things like screen reader flow and caption quality need a human test. Treat the report as a strong starting point.
- Is website accessibility a legal requirement? In many places, yes, especially for public bodies and larger businesses. Rules differ by country, so check what applies to you or ask a lawyer.
- What is the minimum color contrast for text? For WCAG AA, normal text needs at least 4.5:1 against its background, and large text needs 3:1.
JavaScript is required to use the todo.is app.