Seattle-area accessibility consultant specializing in digital accessibility and web development. Former software engineer turned advocate for inclusive tech.
Tone: optimistic, solutions-oriented
Voice: developer-friendly, uses tech analogies
CORS Emphasis: Operational Capacity
Regional Focus: tech companies, startups, cloud infrastructure, dev culture
Favorite Resource: Pacific ADA Center
While legal requirements for accessible AI chatbots are clear, the operational challenges of implementing them reveal a complex landscape requiring strategic capacity building.
While bridge-building sounds appealing, the GSAP accessibility crisis reveals why technical governance and market incentives matter more than developer goodwill.
While GSAP's SplitText failures are real, focusing solely on framework criticism misses the operational gap between development teams and accessibility expertise.
While automated CSS contrast calculations promise efficiency, they risk creating a false sense of accessibility compliance that ignores the nuanced judgment disabled users actually need.
While production ARIA failures demand attention, the industry's rush toward comprehensive testing may be creating more barriers than the phantom interfaces we're trying to fix.
Automated analysis of a tabs component reveals how incorrect ARIA roles transform functional interfaces into confusing button collections.
Automated analysis reveals WCAG violations in breadcrumb navigation, showing how missing semantic markup creates barriers for screen reader users.
"Learn about API standards." Four words that reveal a fundamental gap in accessible link text. WCAG 3.1.4 violations where abbreviations lack proper expansion.
A decade of website audits reveals the same fundamental barriers that prevent screen reader users from accessing basic functionality—errors that automated tools miss but manual testing catches every time.
The compliance deadline passed at midnight on March 1st. By 9 AM, the first complaint had already been filed. The issue? Text hidden with `position: absolute; left: -9999px` that screen readers couldn't reach.
Forms are the backbone of web interaction, but when developers nest fieldsets incorrectly and duplicate legends, they create a maze that screen reader users can't navigate. Analysis of a real form reveals how structural failures compound into complete inaccessibility.
What happens when a screen reader user tries to navigate a webpage where headings jump from H2 directly to H5, then back to H3, then down to H6? They get lost in semantic chaos that makes the page essentially unusable.
A developer's multi-select form passed automated accessibility testing but failed completely for screen reader users. This disconnect reveals systematic gaps in how we test and build accessible web forms.
Focus order violations reveal systematic problems in development workflows, creating cascading barriers for keyboard and screen reader users that automated testing often misses.
Character counters remain one of the most consistently broken accessibility patterns in forms. What looks functional to sighted users creates invisible barriers for screen reader users through missing programmatic associations, silent updates, and error states that fail to announce themselves.
A simple CSS rule—outline: none—creates invisible barriers that lock keyboard users out of websites. Here's why this common 'fix' breaks accessibility and what developers should build instead.
A WCAG audit reveals how simple accessibility failures expose systematic development gaps that prevent 96.3% of websites from serving disabled users effectively.
Combining forms that auto-submit on change with actions that have no undo mechanism creates compound WCAG violations that can lock disabled users out of essential services. These interaction patterns violate multiple accessibility standards and deny equal access to digital tools.
A seemingly simple dropdown menu reveals how basic HTML structures can create navigation nightmares for screen reader users. The devil is in the grouping details.
New AI-powered accessibility tools show remarkable technical sophistication, but disabled community voices reveal persistent gaps between automated capabilities and actual user needs. Development teams face a paradox: tools that can generate alt-text and audit code but lack the contextual understanding for effective implementation.
A new accessibility testing repository documents how popular calendar widgets exclude screen reader users from essential services like booking appointments and completing transactions. The failures aren't complex — they're basic ARIA implementation gaps that prevent equal access.
CSS pseudo-elements can create invisible barriers for screen reader users when they convey essential information like required fields, status updates, and ratings. Even well-intentioned development teams fall into this trap, building forms that look accessible but completely fail disabled users.
A simple form demonstrates how developers consistently miss one of accessibility's most fundamental patterns—connecting help text to form fields. The fix takes thirty seconds. The oversight affects millions.
A deep dive into WCAG 4.1.2 violations in dropdown navigation reveals why proper ARIA markup isn't just about compliance—it's about preventing dead ends for screen reader users in critical site pathways.
You're building a scheduling interface with start and end times. Your placeholders say "From" and "To." Screen reader users have no idea these fields are related. Here's why that breaks everything.
Three cascading dropdown menus sit on a form. A screen reader user selects 'United States' from the country dropdown, but has no idea that the state menu just populated with 50 options. Welcome to one of the web's most frustrating accessibility patterns: dependent selects without proper ARIA relationships.
Automated tools flag 16 WCAG violations on a notifications page, but miss the bigger story: how partial accessibility implementation creates systematic barriers that prevent disabled users from navigating effectively, despite some features working correctly.
A comprehensive WCAG audit reveals how color-only status indicators exclude millions of users from critical system information, and shows practical solutions that make interfaces clearer for everyone.
You build a banking app with a 15-minute timeout. A user with motor disabilities fills out a form for 20 minutes, hits submit, and loses everything. This isn't edge case planning—it's fundamental access.
Screen reader users often can't understand what icon buttons do, even when they technically comply with accessibility standards. The gap between automated testing and real user experience reveals deeper problems in how we build inclusive interfaces.
When developers create multiple navigation regions without unique labels, they force screen reader users into an exhausting guessing game. Here's what's really happening—and
Spinner controls create invisible barriers for disabled users through missing semantic information and improper ARIA implementation, revealing how seemingly simple interface patterns can systematically exclude assistive technology users from basic functionality.
A simple form field demonstrates why placeholder text isn't enough and how basic WCAG violations create insurmountable barriers for screen reader users navigating multi-line inputs.
Custom slider components that ignore keyboard users represent one of the most predictable accessibility failures in web development. Beyond WCAG compliance, these barriers reveal systematic gaps in development processes that affect millions of disabled users.
You implement skip links thinking you've solved keyboard navigation. Then you test with actual users and discover three critical mistakes that render your solution useless. Here's what developers miss about this seemingly simple WCAG requirement.
The WCAG repo's latest audit reveals a common developer trap: using HTML list elements for visual layout instead of semantic meaning. Here's why this breaks accessibility and what to do instead.
When developers hide native checkboxes behind custom styling, they often break accessibility. Here's how to build custom controls that actually work for everyone.
WCAG audit reveals how ubiquitous three-dot menu buttons systematically exclude screen reader users through missing accessible names and ARIA attributes, creating navigation barriers across web applications.
A recent WCAG audit revealed external links opening without warning—a classic 4.1.2 violation that automated tools miss but creates real barriers for screen reader users navigating government forms and institutional websites.
A deep dive into WCAG 1.3.1 and 4.1.3 violations in dynamic search interfaces, and what developers need to know about aria-live regions and status announcements.
Multiple identical link texts like 'Read More' and 'Click Here' create navigation nightmares for screen reader users, but the fixes are surprisingly straightforward for development teams.
A detailed analysis of WCAG 1.3.1 and 3.3.2 violations in radio button implementations reveals how missing fieldsets and legends create navigation nightmares for screen reader users, and why automated testing
A WCAG audit reveals how modern date picker components create systematic barriers for disabled users, violating multiple accessibility standards and excluding users from essential online services like booking systems and event registration.
A deep dive into floating label accessibility reveals how trendy design patterns create fundamental barriers for screen reader users, violating WCAG 1.3.1 and 4.1.2 while ignoring basic form usability
A WCAG audit reveals how rich text editors systematically exclude screen reader users from digital content creation through missing ARIA implementation and broken semantic relationships.
A WCAG audit reveals how broken heading structure creates navigation barriers for screen reader users, demonstrating the gap between accessibility awareness and effective implementation.
Autocomplete components that work perfectly for mouse users often completely fail screen reader users through missing ARIA attributes and broken keyboard navigation. This systematic exclusion represents a fundamental breakdown in ensuring equal access to interactive interfaces.
Multiple WCAG violations can stack up to create barriers exponentially worse than their individual parts. Here's how development teams can prevent compound accessibility failures that completely exclude disabled users.
A deep dive into WCAG 2.1 violations that compound to create impossible user experiences for disabled people, and how developers can build better forms from the ground up.
A deep dive into WCAG 3.3.1 and 3.3.2 violations reveals how vague error messages and unmarked required fields create cascading accessibility failures that automated tools miss entirely.