A website accessibility checklist is most useful when it helps a team reproduce a barrier, assign a fix and verify the result. A scanner score alone does not show whether someone can complete a booking, understand an error or navigate a menu without a mouse.
For US businesses, accessibility work should be part of normal website quality assurance. This guide offers a practical first-pass workflow, not a legal opinion, certification or guarantee of conformance. W3C’s Easy Checks guidance explicitly warns that a page can pass simple checks and still contain significant barriers. Comprehensive evaluation requires a broader scope and appropriate expertise.
Scope the website accessibility checklist around real tasks
Select representative templates and complete journeys: homepage navigation, service discovery, enquiry submission, account access and checkout if relevant. Include shared components such as cookie notices, menus and dialogs. An issue in a common header may affect much more than the single page where it was discovered.
Write down the test environment, including browser, device and any assistive technology used. Keep the URL, page state and steps needed to reproduce each observation. Use non-sensitive test data and an authorized test environment where transactions or messages could otherwise reach real customers.
Agree an evaluation target with the appropriate project owner or specialist. WCAG provides technical criteria, but a short checklist does not establish that all relevant criteria, pages or legal duties have been addressed. Keep the scope and limitations visible in the report.
Navigate the important journeys using a keyboard
Start at the beginning of the page and use Tab and Shift+Tab to move through controls. Check that focus is visible, follows a sensible order and reaches links, buttons and form fields. Use the expected activation keys for each control rather than assuming every widget behaves like a link.
Open navigation menus, cookie settings and modal dialogs. Confirm that the focused item is not hidden behind a sticky header or overlay. Try closing an opened dialog and check where focus returns. If you cannot continue without picking up a mouse, record the exact stopping point.
Do not remove focus outlines because they look unfamiliar. W3C’s guidance highlights keyboard access, logical focus order and visible focus as important checks. A redesign should preserve those interaction cues while improving appearance.
Inspect headings, links and image alternatives
Check that the page title identifies the page and that headings describe the content in a useful hierarchy. Visually large text is not necessarily a heading in the document structure. Look for repeated navigation and ensure users have a practical way to reach the main content.
Read links outside their surrounding paragraph. Labels such as “view installation requirements” are usually clearer than several identical “click here” links. Check icon-only controls for an understandable accessible name rather than assuming the icon’s meaning is universal.
Evaluate image alternatives in context. Informative images need a useful equivalent; purely decorative images generally need an empty alt attribute. A scanner can find a missing attribute, but it cannot reliably judge whether the wording conveys the right meaning. Do not insert keywords into every image description at the expense of its actual purpose.
Test forms in success and error states
Check that each control has an associated label and that instructions remain available while entering information. Placeholders alone can disappear and should not be the only source of essential instructions. Required formats should be explained before a visitor makes an avoidable mistake.
Submit an incomplete form, an invalid value and a valid test submission. Errors should identify the problem in words rather than color alone. Verify that users can find the error, correct it and retain information already entered where appropriate.
For ecommerce journeys, inspect address entry, shipping choices and payment-provider transitions within the agreed testing scope. The Shopify launch scope checklist helps identify customer tasks and third-party boundaries that should not disappear from the test plan simply because another provider renders them.
Review contrast, zoom and changing content
Measure text contrast using a suitable tool, including muted labels and text over imagery. W3C’s preliminary guidance identifies a minimum ratio of 4.5:1 for normal-size text. Different criteria and exceptions apply to other content, so do not treat one ratio as a complete evaluation of every interface element.
Increase text size and browser zoom, then inspect whether content and controls remain usable. Look for clipped labels, overlapping navigation and dialogs whose close button moves off screen. Test narrow layouts separately rather than assuming a responsive preview proves accessibility.
Review moving content and media. Check relevant pause controls, captions and alternatives, with a specialist where necessary. Automated tools can identify some issues, but manual review and assistive-technology testing remain important. Include users with disabilities in research when feasible and appropriately supported.
Turn findings into verified improvements
For each issue, record the affected task, observed barrier, expected behavior, evidence, owner and retest status. Prioritize barriers that block essential tasks, while preserving lower-priority findings in the backlog. Shared-component fixes should be retested across the templates that use them.
If platform limitations are preventing maintainable fixes, revisit the platform ownership and publishing decision guide. For a larger rebuild, include accessibility review time in the US website budget plan rather than leaving it as unspecified final polish.
Close an issue only after reproducing the original steps on the changed version and checking for regressions. Repeat checks after new templates, content and integrations ship. A credible report states what was tested, what remains unresolved and where a more comprehensive assessment is still needed.
