I honestly thought I’d seen every way a WordPress project could fail. Then I audited a “fully accessible” enterprise site last Tuesday that used three different overlay plugins and still failed a basic screen reader test. Most developers treat accessibility like a CSS linting error—something to fix at the very end. But if you aren’t starting with Accessible UX Research, you’re just guessing with your users’ time.
Smashing Magazine just released a new book by Dr. Michele Williams that hits exactly where it hurts: the research phase. As someone who has spent 14+ years refactoring messy themes, I can tell you that “Accessible UX Research” is the roadmap we’ve been missing to stop the cycle of expensive, late-stage accessibility patches.
The Fallacy of the Accessibility Checklist
Specifically, many teams rely on a WCAG checklist and call it a day. However, compliance is not the same as usability. You can have a site that passes automated tests but remains a nightmare for a user with motor impairments or cognitive differences. Furthermore, without Accessible UX Research, you’re building solutions for problems you don’t actually understand.
Dr. Williams’ book, Accessible UX Research, breaks down how to recruit disabled participants and facilitate sessions that actually yield actionable data. It’s not about “getting it right” for the sake of a certificate; it’s about building products that work for more people from day one. I’ve previously discussed real accessibility improvements in WordPress core, but those tools only work if your design intent is inclusive.
Refactoring for Inclusive Results
When you actually do the research, you realize that standard WordPress patterns often need a little extra help. For example, a common research finding is that “hidden” navigation elements are often skipped by assistive technology if the ARIA states aren’t managed correctly. Therefore, we should use hooks to ensure our markup is descriptive.
Here is a common mistake I see in legacy code—treating a menu toggle as a simple link without state management:
<!-- The Bad Way -->
<a href="#" class="menu-toggle">Menu</a>After applying Accessible UX Research principles, we know that a screen reader needs to know if that menu is expanded or collapsed. Here is how I refactor this in a custom theme using a PHP filter:
<?php
/**
* Prefix: bbioon_
* Add accessibility attributes to nav menu links based on research findings.
*/
function bbioon_accessible_nav_attributes( $atts, $item, $args ) {
if ( property_exists( $item, 'classes' ) && in_array( 'menu-item-has-children', $item->classes ) ) {
$atts['aria-haspopup'] = 'true';
$atts['aria-expanded'] = 'false';
}
return $atts;
}
add_filter( 'nav_menu_link_attributes', 'bbioon_accessible_nav_attributes', 10, 3 );
?>Inside the Practical Roadmap
Dr. Michele Williams doesn’t just give you theory. The book is a 324-page deep dive into the real world. You’ll learn how to:
- Plan research that includes disabled participants from the start.
- Recruit participants without falling into the “one-size-fits-all” trap.
- Ask better questions to avoid unintentional bias in your methodology.
- Analyze results with accuracy to create a real impact on your dev cycle.
If you’ve been struggling with implementing CSS contrast or other technical hurdles, this book provides the “Why” that makes the “How” much easier to implement. It even includes a foreword by Jared Smith of WebAIM, which is basically the gold standard in our industry.
Look, if this Accessible UX Research stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Stop Patching, Start Shipping
The biggest takeaway from my decade-plus in the WordPress ecosystem is that technical debt is almost always “accessibility debt” in disguise. We build things fast, we break things, and then we try to fix them with a plugin. Michele’s book is the antidote to that hacky workflow. It challenges you to rethink what inclusion really means in UX research and beyond. If you are a developer, a manager, or a designer, get this book. Your users will thank you.
