Manual accessibility checks should confirm whether users can complete tasks with a keyboard, understand the content through a screen reader, and get appropriate alternative text for each image’s purpose. Captions, heading structure, and interaction flows also need to be checked. Checks should cover core functionality and interactive elements, not just areas flagged by scanners. A PageSpeed Insights accessibility score cannot replace a full WCAG compliance audit. Automation can identify some issues, while manual checks are needed to assess whether content conveys the necessary information and features work in practice.
Complete tasks using a keyboard—don’t stop at checking whether elements can receive focus
Without using a mouse, try completing tasks on the website, such as navigating links, using forms, or checking out on a shopping site. The point is not just whether you can reach a button, but whether core features actually work and the process is clear.
- Record elements that cannot be reached or operated with a keyboard.
- Check that the screen clearly indicates which element has keyboard focus and the actions available next.
- Try dynamic components such as dropdown menus to check whether their options appear and can be selected.
You can also ask team members to try tasks independently and report any barriers they encounter. These records can reveal which processes need fixing more clearly than scan scores alone.
Check reading order and whether the content is easy to understand
Manual checks are needed to assess whether the site works with screen readers and whether its content is easy to understand. Check whether form fields have labels that assistive technologies can interpret, and whether labels are clear, navigation is consistent, and interactions produce predictable results.
For images, checking whether alternative text exists is not enough. Scanners can identify missing alternative text, but cannot reliably judge whether existing text meets users’ needs. During manual checks, consider each image’s purpose and confirm that its description is clear, concise, and provides the necessary information. Headings should also follow the logic of the content, using levels to express the relationship between main sections and subsections rather than simply enlarging the font. This helps users understand the content’s structure, including those reading with a screen reader.
Play media and check contrast beyond text
Play videos to confirm that captions can be enabled, display correctly, and stay synchronized with the audio and video. The presence of a caption option on the platform does not mean the check is complete. Audio-only content should have a complete transcript so that people who cannot hear the audio can still access the content.
Start by measuring contrast with tools, then manually check whether any elements have been missed. Besides text against its background, consider whether links, icons, and other interactive elements have sufficient contrast against their surroundings. Do not apply the same text contrast threshold to every element.
Base the scope on the site’s actual functionality, not just its error list
When planning checks, list the website’s core tasks, content formats, and interactive elements. If it has a checkout, test the entire process with a keyboard; if it has videos, check captions; if it has images, review their alternative text. This is a starting point for planning manual checks, not a complete compliance checklist.
Automated scanning, guided testing, and manual review should complement one another. Continued monitoring and periodic reviews are still needed as the website is updated. Passing a scan once does not mean the site will remain free of accessibility barriers.
Accessibility checks: perspectives from across the web
What contrast ratios can serve as reference points when checking text?
One guide gives these reference values: a contrast ratio of 4.5:1 for regular text and images of text, and at least 3:1 for large text and images of large text. Links, icons, and other elements also need to be checked for contrast against their surroundings, but the same text contrast threshold should not be applied to all of them. These two values do not cover all applicable conditions and exceptions, so they alone cannot determine whether an entire site is compliant.
Must a page have only one H1 heading?
A single H1 should not be treated as a requirement shared by all accessibility standards. One article recommends using one H1 as the page title, with H2 and H3 headings for main sections and subsections; this is the article’s structural recommendation. During manual checks, focus on whether the heading hierarchy follows the logic of the content and helps users understand the article’s structure, including those reading with a screen reader.
Do small projects and large websites need the same testing approach?
Not necessarily. One tool guide suggests that small projects can combine quick scans, visual guidance, and evaluation tools. Medium-sized and large teams can integrate scanning into their development workflow alongside in-depth checks, while enterprise applications can add site-wide crawlers or cloud monitoring. These are suggested tool combinations based on team size and needs, not mandatory setups for each category of website.
References
- 7-Step Ecommerce Website Audit to Boost Conversionswww.semrush.com · 2024-05-14T08:30:00Z — Source used in the article above.
- WCAG 2.1 檢測工具完整指南:從基礎到進階實戰應用tenten.co · 2025-09-17T08:24:52.000Z — Discusses: Do small projects and large websites need the same testing approach?
- Check Website Accessibility: Manual Checks and Tools to Use in 2025www.semrush.com · 2024-02-14T13:51:00Z — Discusses: What contrast ratios can serve as reference points when checking text?; Must a page have only one H1 heading?
