Keyboard Archives - Dennis Deacon

Testing Methods: Keyboard

October 19, 2025November 27, 2025

Reading Time: 3 minutesAchieving true compliance with WCAG 2.1.1 Keyboard requires more than one testing method. A hybrid approach blends automation, AI, and manual testing to balance speed, intelligence, and depth, ensuring both compliance and usability.

Read more Testing Methods: Keyboard

Global Accessibility Awareness Day, One Month OutApril 23, 2026
Reading Time: 5 minutesGlobal Accessibility Awareness Day is more than a calendar event, it's a call to build better. Explore the origins of GAAD, real stories from the field, and 20 practical ideas to help your team celebrate, take action, and sustain an inclusive digital culture all year long.
Don’t Waste Money on an Accessibility AuditApril 15, 2026
Reading Time: 2 minutesA VPAT documents accessibility conformance, but too many organizations treat it as the finish line. With audits costing up to $50K annually, ignoring remediation guidance wastes 50-60% of that investment. Prioritizing critical findings can resolve the majority of real barriers for users with disabilities.
When is a Link not a Link?February 25, 2026
Reading Time: 3 minutesAutomated testing can miss serious accessibility barriers. This article explores how misusing links as buttons breaks keyboard navigation and assistive tech expectations, why semantic HTML matters, and how developers can avoid common pitfalls to create truly accessible user experiences.
When Accessibility Demand Letters Land on Your Desk: A Framework for Strategic ResponseFebruary 18, 2026
Reading Time: 3 minutesAccessibility demand letters reveal organizational readiness and risk management gaps. This article outlines four response pathways, from non-engagement to structured good-faith engagement, showing how strategic response minimizes litigation, contains costs, and builds long-term compliance resilience.
WordPress Plugins, a Love/Hate RelationshipFebruary 14, 2026
Reading Time: 3 minutesWordPress plugins extend functionality but can introduce performance, security, and accessibility risks when overused. This article explores a disciplined, problem-first approach to selecting and managing plugins, emphasizing testing, maintenance, and inclusive user experiences.