Common pitfalls in accessibility testing include treating automated scans as the final verdict, checking whether images have alt attributes without assessing what the descriptions mean, and ending follow-up after one round of fixes. A more comprehensive approach is to use tools to find issues that can be detected automatically, then verify key interactions through keyboard testing, screen reader testing, and manual review. Test reports should also identify the specific standards requirements behind each issue so that fixes go beyond simply clearing warnings.
A scan with no errors does not mean a site has no accessibility barriers
In its 2025 article, Tenten describes automated scanning as an initial check rather than a final verdict. Tools can quickly identify some issues with contrast, ARIA attributes, and form labels, but they cannot reliably assess the meaning of content or its intended use. Scan results alone therefore cannot determine the usability of an entire website.
When choosing tools, there is no need to seek a single product that handles every check. Automated scans, guided assessments, and manual testing each serve a purpose. The priority is to use these methods to complement one another rather than treat any one report as the complete answer.
Static checks can overlook interactions and how images are used
Manual review is not just about revisiting errors flagged by tools; it should also cover areas that tools cannot reliably assess. Based on Tenten’s overview, further checks on key pages can include:
- Whether users can navigate and operate interactive elements with a keyboard.
- Whether the page works with screen readers and the meaning of its content is understandable.
- Whether dynamic interactions are predictable and labels and navigation are clear and consistent.
Image checks should also go beyond confirming that an alt attribute exists. In its 2022 article, awoo notes that image buttons in forms and image links are easy to overlook. Reviewers should also manually check whether descriptions fit the context in which the images appear. This does not mean that every image must have a description.
An error list alone may not make the next steps clear
Simply writing “there is an accessibility issue here” does not explain the basis for a fix. Tenten recommends mapping each issue to a specific WCAG requirement and consulting W3C’s Understanding guides to help engineering and content teams understand what is required. Reports should tell those taking over the work which requirement an issue relates to, rather than simply pass along a tool warning.
The article uses WCAG 2.1 as its framework. Citing its workflow recommendations does not mean that its chosen version or conformance level can be treated as the legal minimum currently applicable to every project.
Later changes can bring issues back after a round of fixes
Tenten also notes that accessibility involves design, development, and content, so it should not be assigned to a single role alone. Beyond initial scanning and manual verification, the article recommends ongoing monitoring, regular reviews, and clearly assigned responsibilities to track whether new features introduce issues. This is the article’s proposed maintenance strategy, not a guarantee that a one-time fix will keep a site accessible permanently.
Accessibility testing: perspectives from across the web
What might testing only on desktop miss?
It may miss mobile and low-vision use cases. In its discussion of WCAG 2.1, Tenten highlights checks for orientation locking, touch targets, motion actuation, and content reflow. When adjusting text spacing or zooming, reviewers should also confirm that no content or functionality disappears. These aspects should not be assessed solely on a fixed-size desktop screen.
Is cognitive load also part of accessibility testing?
Yes. Beyond code-level checks, guided or manual testing can also help assess cognitive load. Tenten notes that clear labels, consistent navigation, and predictable interactions help reduce the effort needed to understand content and interfaces. These issues depend on the context of use and should not be judged solely by automated scan results.
Do teams of different sizes all need the same set of tools?
Not necessarily. Tenten recommends choosing a mix of tools based on team size and project needs. Small projects can combine quick scans, visual guidance, and assessment features. Medium-sized and large teams can consider adding scans to their continuous integration workflow, followed by in-depth review. This is the article’s advice on tool selection, not a guarantee that any particular combination will find every issue.
References
- HTML Image Alt 全攻略!簡單四原則,讓 Google 輕鬆看懂你的圖片!www.awoo.ai · 2022-12-01T10:58:58+00:00 — Source used in the article above.
- WCAG 2.1 檢測工具完整指南:從基礎到進階實戰應用tenten.co · 2025-09-17T08:24:52.000Z — Discusses: What might testing only on desktop miss?; Is cognitive load also part of accessibility testing?
