Skip to main content

Dennis Deacon

Third-Party Chatbots and Accessibility: What Breaks and How to Test It

Third-party chatbots often trap keyboard focus, omit labels, stay silent when replies arrive, and hide behind launchers keyboards cannot open. This article explains each failure, maps it to WCAG 2.2 Success Criteria, gives tests, and shows how to write a vendor defect report that gets fixed.

Read more about Third-Party Chatbots and Accessibility: What Breaks and How to Test It

Test the Third-Party Stuff Too: Why Accessibility Testing Must Include Vendor Solutions

Skipping accessibility testing on third-party tools because you can’t edit them leaves you blind to real barriers and real legal risk. Testing gives you the knowledge to keep, configure, escalate or replace a vendor product, and builds a good-faith record that protects your users and your business.

Read more about Test the Third-Party Stuff Too: Why Accessibility Testing Must Include Vendor Solutions

Digital Accessibility Lessons: How One Meetup Mistake Led to Better Inclusive Design

When dimming the lights improved screen visibility at a Chicago accessibility meetup, it accidentally excluded a deaf attendee who relied on lip-reading. This story explores how accessibility fixes can create new barriers, and why embracing mistakes is key to inclusive leadership.

Read more about Digital Accessibility Lessons: How One Meetup Mistake Led to Better Inclusive Design

Accessible Design Systems: The Scalability Advantage You’re Missing

Design systems transform accessibility from reactive cleanup into proactive quality engineering. By embedding accessible components, tokens, and governance into a shared system, organizations eliminate repeated failures and scale standards consistently across every product and team.

Read more about Accessible Design Systems: The Scalability Advantage You’re Missing

Why Automated Accessibility Testing Is Not Enough: A Leadership Perspective

Automated accessibility tools catch technical errors efficiently, but they cannot evaluate whether users can actually succeed. True accessibility requires a layered approach combining automation, expert manual review, assistive technology testing, and direct input from users with disabilities.

Read more about Why Automated Accessibility Testing Is Not Enough: A Leadership Perspective

ARIA Done Right: Why Accessibility Starts with Better Decisions, Not More Code

ARIA enhances accessibility when native HTML falls short, but misuse creates real barriers. This article explores the principles behind correct ARIA implementation: prioritizing native elements, understanding what ARIA communicates versus what it creates, avoiding common failures, and testing with real assistive technologies.

Read more about ARIA Done Right: Why Accessibility Starts with Better Decisions, Not More Code