Blog

How to collect accessibility feedback on a website

You don't need to be an accessibility specialist to catch the problems that lock people out of a website. A designer, a project manager or a client can run a handful of checks in under half an hour and write each problem up so a developer can fix it. This guide covers website accessibility feedback from start to finish: what to test, how long each check takes, which WCAG 2.2 guideline it maps to, and how to word the comment.

Accessibility feedback: Quick checks anyone on the team can run.
The short versionPut the mouse away and tab through the page, check text contrast, look for images without descriptions, confirm headings run in order, make sure every link, button and form field has a clear name, zoom to 200%, and check video captions and moving content. Write each problem as one comment on the exact element: where it is, what happens, what should happen, and the WCAG 2.2 success criterion. These checks catch common problems early. They don't replace a full audit or testing with disabled people.

What quick checks can and can't tell you

The checks below come from the most common problems on real websites: things a keyboard user, a screen reader user or someone with low vision runs into on the first page they visit. Each one takes a few minutes and needs no special skill.

They have limits, and it's worth saying them to the client up front. A quick review doesn't cover every WCAG success criterion. It won't tell you how the site works for someone who uses a switch device, voice control or a screen reader every day. If accessibility is a legal or contract requirement, book a full audit before launch and, where you can, test with disabled users. The W3C makes the same point about its own Easy Checks, which are a good companion to this guide: a page can pass quick checks and still have serious barriers.

What the checks do well is find problems early, when many fixes take a line of CSS. Run them on the staging site during the build, alongside the usual design and content review.

The tools you need

Everything here costs nothing for basic use. All of them run in your browser or come with your computer (checked 16 November 2026).

  • Your keyboard. The Tab key, Shift and Enter do most of the work.
  • WAVE from WebAIM. Paste an address on its site, or add the extension for Chrome, Firefox or Edge. It marks problems directly on the page.
  • axe DevTools from Deque. The free Chrome extension runs basic automated tests page by page. Guided tests and user-flow testing are in the paid version.
  • Lighthouse. It's built into Chrome DevTools: open DevTools, choose the Lighthouse panel and run a report with Accessibility ticked. Google notes that the score is a weighted pass or fail across its audits, so a page with one unlabelled button scores zero on that audit.
  • The WebAIM contrast checker, for checking two colours against the WCAG ratios.
  • A screen reader. VoiceOver is built into macOS and iOS (Command-F5 turns it on and off on a Mac). NVDA is a free, open-source screen reader for Windows.

Run one automated scan first for a list of likely problems, then do the manual checks below.

Keyboard navigation and visible focus

Click in the browser's address bar, then press Tab repeatedly and work through the whole page without touching the mouse. Shift and Tab goes backwards. Enter follows links and presses buttons; Space also presses buttons and ticks checkboxes.

Watch for four things:

  • You can always see where you are. Every link, button and field should show a clear outline or highlight when it has focus (2.4.7 Focus Visible).
  • The focused item isn't hidden. A sticky header, chat widget or cookie banner shouldn't cover it completely (2.4.11 Focus Not Obscured, new in WCAG 2.2).
  • You can reach and use everything: menus, tabs, accordions, sliders and the form submit button (2.1.1 Keyboard). You can also get out of every part again, including pop-ups and embedded maps (2.1.2 No Keyboard Trap).
  • The order makes sense. Focus should move through the page in the order you read it, without jumping from the footer back to the header (2.4.3 Focus Order).

A menu that only opens on hover, or a modal you can't close with the keyboard, can stop some people using the site at all.

Colour contrast

Text needs a contrast ratio of at least 4.5:1 against its background. Large text, meaning at least 18 point or 14 point bold, needs at least 3:1 (1.4.3 Contrast Minimum). Buttons, form field borders, icons that carry meaning and focus outlines need at least 3:1 against what's next to them (1.4.11 Non-text Contrast).

WAVE and axe flag most low-contrast text automatically. Look yourself at the places scanners miss: text over photos or gradients, placeholder text inside form fields, light grey captions, and text on buttons in their hover state. When in doubt, pick the two colours and check them in the WebAIM contrast checker. Put the ratio you measured in your comment so the designer doesn't have to measure it again.

Images and alt text

Every image that carries information needs a text alternative that does the same job (1.1.1 Non-text Content). Decorative images should have empty alt text so screen readers skip them.

WAVE shows each image's alt text on the page, which makes this quick to review. Ask of each one: if the image disappeared, would the alt text tell me what I'd miss? A product photo described as "IMG_4021" fails. So does a chart described as "chart", or a linked logo with no text at all, because a screen reader may then read out the file name or address.

Scanners can find a missing alt attribute, but only a person can say whether the description is right. Clients are good at this check because they know what each image is meant to show.

Headings, links and buttons

Screen reader users often move through a page by its headings, like a table of contents. Check that the page has one main heading, that sections use headings and not just large bold text, and that levels don't skip, for example from h2 straight to h4. Headings should also describe what follows (1.3.1 Info and Relationships, 2.4.6 Headings and Labels). WAVE's structure view lists the headings in order, and the VoiceOver rotor does the same.

Then look at link and button text. "Read more", "Click here" and "Learn more" repeated five times tell a screen reader user nothing when they're read out as a list. A link's purpose should be clear from its text, or from its text together with its surroundings (2.4.4 Link Purpose). Icon-only buttons, such as a magnifying glass for search or a cross to close a menu, need an accessible name (4.1.2 Name, Role, Value). If a button shows text, its accessible name should contain that text, so voice control users can say what they see (2.5.3 Label in Name).

Form labels and error messages

Fill in every form on the site with the keyboard, then submit it with mistakes on purpose: leave required fields empty and type an invalid email address.

  • Each field needs a visible label that stays visible while you type. Placeholder text that disappears doesn't count as a label, and required fields should be marked (3.3.2 Labels or Instructions).
  • When something goes wrong, the form should say which field has the problem and what it is, in text (3.3.1 Error Identification). A red border alone isn't enough.
  • Clicking a label should put the cursor in its field. If it doesn't, the label probably isn't connected to the field in the code, which also means a screen reader won't announce it.

Zoom to 200% and check small screens

Use the browser's zoom (Command and plus on a Mac, Control and plus on Windows) to set the page to 200%. All the text should get bigger, nothing should be cut off or overlap, and every feature should still work (1.4.4 Resize Text). Watch for headers that cover half the screen and buttons whose text spills out.

Go on to 400% on a desktop window about 1280 pixels wide if you have time. Content should then fit in one column without scrolling sideways, apart from things like maps and data tables (1.4.10 Reflow). On phones, check that buttons and links are big enough to tap: at least 24 by 24 CSS pixels, or with enough space around them (2.5.8 Target Size Minimum, also new in 2.2).

Video captions and motion

Play every video with the sound off. Pre-recorded video with speech needs captions (1.2.2 Captions Prerecorded), and live video needs them at AA (1.2.4 Captions Live). Automatic captions are a start, but read them: names, product terms and numbers are where they go wrong.

Then look at anything that moves on its own. Carousels, scrolling logo bands and background videos that run for more than five seconds need a way to pause, stop or hide them (2.2.2 Pause, Stop, Hide). Nothing should flash more than three times a second (2.3.1 Three Flashes). Also turn on Reduce motion in your system's accessibility settings and reload the page. Large parallax and zoom effects should calm down or stop. That last check maps to 2.3.3 Animation from Interactions, which is level AAA, so present it as a recommendation unless your target includes AAA.

How to write an accessibility comment a developer can fix

A comment like "the menu isn't accessible" sends the developer off to repeat your whole test. A good one lets them reproduce the problem in a minute and tells them when it's fixed. Use this template:

Where:    [page], [element], [desktop / tablet / phone]
What happens: [what you did and what you saw or heard]
What should happen: [the expected behaviour]
Guideline: WCAG 2.2 [number] [name] (Level [A / AA])
Tested with: [browser, zoom level, screen reader if used]

Three filled-in examples:

  • "Main menu, desktop. When I tab to Services, the dropdown doesn't open and I can't reach its links. It should open with Enter or Space, and Escape should close it. WCAG 2.2 2.1.1 Keyboard (A). Chrome, keyboard only."
  • "Newsletter button in the footer, all views. The focus outline is removed, so I can't tell when the button has focus. Any visible outline that meets 3:1 against the background would fix it. 2.4.7 Focus Visible (AA)."
  • "Team page, the photo of the office. VoiceOver reads 'team-final-2 dot jpg'. It should describe the image, for example 'Eight people around a table in the Leeds office'. 1.1.1 Non-text Content (A)."

One problem per comment. If the same fault shows up on every page, say so in the first comment and don't repeat it everywhere; the fix usually lives in a shared template. Our guide to giving good website feedback covers the general habits that make any comment easier to act on.

A quick accessibility checklist

Print this or paste it into your review brief. The times are rough, for one page.

CheckHow to testWCAG 2.2Time
Keyboard and focusTab through the page; watch the outline and the order2.1.1, 2.1.2, 2.4.3, 2.4.7, 2.4.113 min
ContrastRun WAVE or axe, then check text on images by hand1.4.3, 1.4.113 min
Alt textShow alt text with WAVE; listen with a screen reader1.1.13 min
HeadingsList the headings; check order and wording1.3.1, 2.4.62 min
Links and buttonsRead link text out of context; check icon buttons2.4.4, 2.5.3, 4.1.22 min
FormsSubmit with mistakes; click each label3.3.1, 3.3.24 min
Zoom and tap sizeZoom to 200%, then 400%; check buttons on a phone1.4.4, 1.4.10, 2.5.83 min
VideoPlay with sound off; read the captions1.2.2, 1.2.42 min
MotionLook for autoplay and flashing; turn on Reduce motion2.2.2, 2.3.1 (2.3.3 is AAA)2 min

Accessibility checks also belong in the final pass before go-live. Our website launch checklist lists them alongside links, forms, SEO and analytics.

Collecting accessibility feedback in HTMLAnnotate

Run the keyboard, zoom and screen reader tests on the site itself in a normal browser tab. Then record what you found on a review link, so every problem sits in one list the developer can work through. Here is what HTMLAnnotate does for that, and no more.

  • Comments on the exact element. Paste the staging or live address, or upload an HTML file, and send the link. Reviewers click the button, image or heading with the problem and write the comment there, with no account or extension. The developer sees which element you mean without a screenshot.
  • Separate views. Desktop, tablet and phone each keep their own comments, so a tap-size problem on the phone stays on the phone view. You can pick exact device sizes, from iPhone SE to iPad Pro 13".
  • Browser details on every comment. Each one records the browser, system and screen and window size it came from. Still write the zoom level and any screen reader in the comment, because those aren't recorded.
  • Labels, priority and search. Labels are a fixed set: Bug, Copy, Design, Question and Idea. A simple habit is to tag accessibility problems as Bug, set a priority, and start each comment with "Accessibility:" so a search for that word lists them all.
  • Status and resolve. Mark a comment In progress while it's being fixed, then resolve it. Everyone in the thread gets an email, so the reviewer can check the fix with the same test.
  • A page health check. Every new page is checked for broken links, images that don't load or have no description, leftover dummy text and a missing page title, and the owner can pin what it finds as comments. It is not an accessibility checker and doesn't test contrast, keyboard use or anything else in this guide.

You can see the review page on a sample site at the live demo, or start a review link for your own staging site. Plans are on the pricing page; everything above is on the free plan. For the rest of the review process, including who reviews what and how to close a round, see our website feedback guide.

Questions

Can a non-expert give useful accessibility feedback on a website?

Yes. Many common barriers, such as missing focus outlines, low-contrast text, images with no description, unlabelled form fields and pages that break when zoomed, can be spotted by anyone who knows what to look for. What a non-expert can't do is say a site is accessible. That needs a full audit and, ideally, testing with disabled people.

Which WCAG version and level should we test against?

WCAG 2.2 at level AA is the usual target. The current W3C Recommendation is dated 12 December 2024. Check what your contract or local law asks for, since some still name WCAG 2.1. Everything in 2.1 AA is also in 2.2 AA, apart from 4.1.1 Parsing, which 2.2 marks as obsolete.

Do automated checkers like WAVE or Lighthouse find every accessibility problem?

No. WebAIM says on its help page that WAVE can't tell you whether content is accessible and that only a human can judge that. Automated tools are good at spotting missing alt attributes, contrast failures and unlabelled fields. They can't tell whether alt text makes sense, whether focus order is logical or whether an error message is helpful.

What should an accessibility comment include?

Four things: where the problem is (page, element and screen size), what happens now, what should happen, and the WCAG success criterion number and name. Add the browser and any assistive technology you used, such as VoiceOver or NVDA, and how to repeat the problem.

Does HTMLAnnotate check my site for accessibility problems?

No, it has no accessibility checker. Every new page gets a page health check that flags broken links, links that go nowhere, images that don't load or have no description, leftover dummy text and a missing page title. That overlaps with one accessibility check, alt text, and nothing more. Use WAVE, axe DevTools or Lighthouse for automated accessibility testing, and HTMLAnnotate to collect and track what reviewers find.

How long does a quick accessibility review take?

For one page, about 20 to 30 minutes if you run every check in this guide. Test one page of each template: the homepage, a content page, a form, and any page with video. Problems on a template usually repeat across the site, so one comment can cover many pages.

When do we need a professional accessibility audit?

Before launch on any site where accessibility is a legal or contract requirement, after a redesign, and whenever the site includes complex parts such as custom menus, carousels, checkouts or web apps. An auditor tests every relevant success criterion with assistive technology and gives you a report you can act on and keep.

Send your next accessibility round on one link. Reviewers click the element that has the problem and leave a comment, with no account and nothing to install.

Start a free review