Web accessibility smoke testing for critical issues

Last updated: 15 October 2026

Longhorn PHP Conference 2026 session – 16 October 2026

Resources

Summary

Developers can catch 90% of critical blocker accessibility issues with just a few quick checks. If each developer agrees to test their work for accessibility issues before committing to the branch or marking an issue as “Done,” they can prevent major accessibility problems from advancing through the development pipeline. We will walk through two tests for a total of 6 checkpoints you can do in a web browser that should uncover critical blockers that will prevent some people from using a webpage.

Learning outcomes

  1. Smoke testing is low effort and anyone can do it.
  2. Spending a few minutes to test for accessibility will lead to savings in effort, efficiency and ultimately, money.
  3. Keyboard accessibility is one of the most important aspects of web accessibility.