Everyone *thinks* they get accessibility. It’s about screen readers, alt text, and maybe some basic color contrast. That’s the common wisdom, right?
None of that is wrong. But it’s incomplete.
The real truth? Accessibility is an operational discipline, not just a design or development add-on. And most agencies are treating it like an afterthought, leading to costly rework and alienated clients.
1. Treating Accessibility as a Final-Stage Checklist
The biggest mistake? Thinking accessibility is something you bolt on at the end. Like a final coat of paint before launch.
This is fundamentally flawed. Accessibility needs to be baked into the entire process, from initial concept to final delivery.
Why this is a problem:
- Rework is expensive. Fixing fundamental structural issues or complex interactions late in the game is a nightmare.
- It leads to compromises. When accessibility is an add-on, creative vision often gets watered down to meet compliance, rather than being *enhanced* by inclusive design principles.
- It misses opportunities. Early integration allows for innovative solutions that benefit *all* users, not just those with disabilities.
The Hard Truth: Accessibility is Design Thinking
True accessibility is about inclusive design. It’s about anticipating the needs of the widest possible audience from the outset.
This means considering:
- User research that includes diverse needs.
- Content strategy that prioritizes clarity and structure.
- User flows that accommodate various input methods.
- Prototyping and testing with accessibility in mind.
When it’s integrated early, accessibility becomes a driver of better design, not a constraint.
2. Over-Reliance on Automated Tools
Those automated accessibility checkers are useful. They catch obvious issues, like missing alt text or insufficient contrast ratios.
But they’re not a silver bullet.
Automated tools can only detect about 20-30% of potential accessibility barriers. They can’t understand context, intent, or complex user interactions.
Think of it like spellcheck. It’s helpful for typos, but it won’t catch a poorly written sentence or a factual error.
The Danger of False Positives and Negatives
- False Positives: Tools might flag something as an error that isn’t, causing unnecessary work or confusion.
- False Negatives: More critically, tools can miss significant issues that manual testing would reveal. For example, a complex custom form or a dynamic content slider might pass automated checks but be completely unusable with a keyboard or screen reader.
Manual testing, including testing with actual assistive technologies and diverse users, is non-negotiable.
3. Neglecting Keyboard Navigation and Focus States
This is a huge one. Many designers and developers assume everyone uses a mouse.
They don’t.
A significant portion of users navigate websites and applications using only a keyboard. This includes people with motor impairments, visual impairments, and even power users who simply prefer it.
If your site isn’t keyboard navigable, it’s not accessible. Period.
What to Look For:
- Logical Tab Order: Can users tab through interactive elements in a predictable and intuitive sequence?
- Visible Focus Indicators: Is it clear which element currently has keyboard focus? A subtle or absent focus outline makes it impossible to know where you are on the page.
- No Keyboard Traps: Can users get stuck in a loop, unable to navigate away from a specific element or section using the keyboard? This is common with modals or complex widgets.
- Keyboard Operability: Can all interactive elements (buttons, links, form fields, custom widgets) be activated and operated using standard keyboard commands?
This isn’t just about tabbing. It’s about ensuring every function available with a mouse is also available via keyboard.
4. Poorly Implemented ARIA
Accessible Rich Internet Applications (ARIA) is a powerful set of attributes that can make dynamic content and advanced user interface controls accessible to assistive technologies.
When used correctly, ARIA is a game-changer.
But it’s often misused, misunderstood, or overused.
Common ARIA Pitfalls:
- Adding ARIA to Native HTML: Don’t add `role=
Frequently asked questions
What is the biggest mistake agencies make with accessibility?
The biggest mistake is treating accessibility as a final-stage checklist rather than integrating it into the entire design and development process from the start. This leads to costly rework and compromises.
How important is keyboard navigation for accessibility?
Keyboard navigation is critical. A significant portion of users rely solely on keyboard input due to motor impairments, visual impairments, or preference. If a site isn't fully navigable and operable via keyboard, it's not truly accessible.
Can automated tools guarantee accessibility?
No. Automated tools are helpful for catching basic issues but can only detect a fraction of potential barriers. Manual testing with assistive technologies and diverse users is essential for comprehensive accessibility.
What is ARIA and why is it often misused?
ARIA (Accessible Rich Internet Applications) provides attributes to make dynamic content accessible. It's often misused by adding it unnecessarily to native HTML elements or by incorrectly defining roles and states, which can actually harm accessibility.