A website accessibility audit helps you find barriers before they prevent someone from reading, navigating, completing a form, or buying from your site. Use this repeatable checklist to test keyboard access, focus states, headings, images, contrast, forms, media, zoom, mobile layouts, and basic screen-reader behavior. It is designed for quarterly reviews, redesigns, new campaigns, and important workflow changes.
Overview
Accessibility testing combines automated checks with hands-on use. An automated tool can identify some missing labels, color-contrast concerns, empty links, and structural problems, but it cannot reliably judge whether a form is understandable, whether a keyboard user can tell where they are, or whether an error message helps someone recover. Treat automated results as a starting point rather than a complete accessibility verdict.
Begin with representative pages instead of testing only the homepage. Include a landing page, a content page, a navigation menu, a contact or sign-up form, a search results page, a checkout or booking flow if applicable, and any page that changes after user interaction. Test both the desktop and mobile layouts, and include authenticated areas when they are important to the site experience.
For each issue, record the URL, the affected component, the steps to reproduce it, the user impact, a screenshot or short recording when useful, and the suggested owner. Separating evidence from assumptions makes it easier to verify a fix later.
Checklist by scenario
1. Keyboard navigation and focus
- Use only the keyboard to move through the page with Tab, Shift+Tab, Enter, and the arrow keys where relevant.
- Confirm that every interactive element can be reached and operated without a mouse or touch screen.
- Check that the focus indicator is visible against the surrounding background and is not hidden under a sticky header, cookie banner, or modal.
- Test menus, accordions, carousels, dialogs, date pickers, custom dropdowns, and other components that may require more than a simple link.
- When a modal opens, confirm that focus moves into it, remains within it while open, and returns sensibly when it closes.
- Look for keyboard traps: places where focus enters a component but cannot leave without refreshing the page.
2. Headings, landmarks, and link text
- Check that each page has a clear main heading and that headings follow a meaningful hierarchy.
- Use headings to describe sections, not merely to create larger or bolder text.
- Confirm that navigation, main content, complementary content, and footer regions are identifiable where landmarks are used.
- Read links out of context. Replace vague labels such as “click here” or repeated “read more” with text that explains the destination or action.
- Make sure the page title, heading, and visible navigation label give a consistent description of the page.
3. Images and non-text content
- Give informative images concise alternative text that communicates their purpose in context.
- Use empty alternative text for purely decorative images when the surrounding content already provides the information.
- Do not place essential instructions, prices, or words only inside an image.
- Describe charts, diagrams, and infographics in nearby text or provide an equivalent long description when the visual carries important meaning.
- Check icons used as buttons. An icon-only control needs an accessible name, even if its visual meaning seems obvious.
4. Color, contrast, and visual presentation
- Test body text, headings, placeholder text, labels, buttons, and essential icons for sufficient contrast using a current contrast checker.
- Do not use color alone to show status, required fields, errors, selected options, or differences between chart values.
- Check links in paragraphs for a visual distinction beyond color when their purpose could otherwise be missed.
- Zoom the page and enlarge text. Confirm that content remains readable and controls do not overlap or disappear.
- Inspect high-contrast, reduced-motion, and dark-mode presentations if your site offers them.
5. Forms and error recovery
- Give every field a persistent, programmatically associated label. Do not rely on placeholder text as the only label.
- Identify required fields in text or an accessible name, and keep the required-state treatment consistent.
- Group related controls, such as address fields or radio buttons, with an appropriate visible legend or heading.
- Make instructions available before the user needs them, including formatting rules for dates, passwords, phone numbers, and file uploads.
- Submit incomplete and invalid forms. Confirm that errors are visible, specific, associated with the relevant fields, and announced when appropriate.
- Check that entered information is retained after a validation error and that the user can move directly to the first problem.
- Test success messages as well as failures. A user should be able to tell when an action completed without relying on a visual change alone.
6. Media, motion, and timing
- Check that video and audio controls are keyboard operable and have clear labels.
- Provide captions for spoken video content and a text alternative when the material is important to understanding the page.
- Make sure auto-playing media can be paused or stopped, especially when it produces sound.
- Test animated banners, carousels, and transitions with reduced-motion settings enabled. Avoid motion that is unnecessary, distracting, or difficult to control.
- Check time limits in forms, carts, reservations, and logged-in sessions. Give users adequate warning and a way to extend time when the workflow requires it.
7. Mobile and responsive behavior
- Test common screen widths and both portrait and landscape orientations, not just a single phone model.
- Confirm that controls have enough space to operate without accidentally activating nearby controls.
- Check that menus, filters, tables, cookie notices, and checkout steps remain usable at zoomed text sizes.
- Ensure horizontal scrolling is not required for ordinary text or essential controls unless the content genuinely needs a wide layout.
- Test with touch and keyboard access where mobile users may connect an external keyboard or use assistive technology.
8. Screen-reader spot checks
- Use a screen reader available on your operating system to review the page title, headings, landmarks, links, form labels, buttons, and status messages.
- Navigate by headings and landmarks. If the sequence is confusing, review the document structure and visual order.
- Check dynamic updates such as cart changes, filtering results, validation messages, and modal dialogs.
- Listen to images, icon buttons, and controls with changing states to confirm that their names and states make sense.
What to double-check
Prioritize findings by user impact and reach rather than by the order in which a tool lists them. A blocked checkout, inaccessible sign-in process, keyboard trap, or unlabeled form field usually deserves attention before a minor heading-order issue on a low-traffic page. A useful priority table looks like this:
| Priority | Typical issue | First action |
|---|---|---|
| Urgent | A core task cannot be completed, or users become trapped in a component. | Reproduce the issue, provide a usable path if possible, and assign an immediate fix. |
| High | Important information or errors are unavailable to keyboard or assistive-technology users. | Fix the shared component or template, then retest every page that uses it. |
| Medium | Navigation, labels, contrast, or responsive behavior is confusing but a workaround exists. | Add the issue to the next development cycle and test representative pages. |
| Low | Minor consistency or clarity problem with limited effect on task completion. | Bundle it with related design-system or content improvements. |
Check fixes in the environment where they will be released. A change that works on a staging site can behave differently after a plugin update, template change, third-party widget installation, or CSS optimization. For WordPress sites, a staging site provides a safer place to test theme and plugin changes before publishing them.
Accessibility is also part of normal site operations. A faster page, a new ecommerce feature, a security banner, or a redesigned navigation can introduce new barriers. Coordinate accessibility checks with your website speed audit, release review, and content QA rather than treating accessibility as a one-time project.
Common mistakes
- Relying on one automated scan: automated tools miss many interaction, wording, focus, and user-flow problems.
- Testing only the homepage: accessibility defects often appear in forms, account areas, checkout steps, and reusable widgets.
- Removing visible focus styles: a subtle or absent focus indicator makes keyboard navigation difficult even when the tab order is technically correct.
- Writing alt text for every image the same way: useful alternative text depends on whether an image is informative, decorative, functional, or part of a larger explanation.
- Using placeholders as labels: placeholders disappear during entry and can be difficult to perceive or interpret.
- Fixing contrast without checking states: hover, focus, disabled, selected, error, and visited states can each introduce separate problems.
- Ignoring third-party components: chat tools, payment widgets, cookie interfaces, video players, and embedded forms still affect the experience users receive.
- Closing tickets without regression testing: verify the original steps and test related templates after every shared-component change.
When to revisit
Run a focused accessibility check whenever you publish a new form, checkout flow, navigation system, template, popup, media component, or third-party integration. Repeat a broader audit after a redesign, migration, major CMS or plugin update, or substantial content change. A quarterly review is a practical baseline for an active site, while high-value transaction flows may need checks in every release cycle.
Review your testing tools, browser support assumptions, internal accessibility requirements, and the WCAG version your organization has chosen to follow when your standards or platform requirements change. Tool output can change over time, so preserve the steps and evidence for important findings instead of comparing scan scores alone.
To act on this checklist, select five representative pages and one complete task flow. Test keyboard access first, then review headings, links, images, contrast, forms, zoom, mobile behavior, and a screen-reader path. Log each issue by impact, fix the highest-risk shared components, and repeat the same test after deployment. Keep the checklist with your release documentation so the next audit starts with known coverage rather than from scratch.