Accessibility is often treated as a final step in the design process - something to "check" before launch. In reality, accessibility issues usually reveal deeper product and system-level problems that affect far more users than we expect.
During a recent accessibility audit, I evaluated a public-facing nonprofit website that supports time-sensitive, mission-critical services. Because users often interact with the site in urgent situations, accessibility plays a key role in ensuring information can be found, understood, and acted on quickly.
The audit focused on three high-traffic pages and applied WCAG 2.2 Level AA criteria and the POUR principles (Perceivable, Operable, Understandable, Robust). What stood out wasn't just the number of issues - but how consistently they appeared across the product.
When "Nothing Looks Broken," But Everything Is
On the surface, the interface looked clean and functional. But once tested with accessibility in mind, critical barriers emerged:
- Screen reader users couldn't understand content due to missing alternative text and broken heading hierarchy
- Keyboard-only users were blocked by hover-only navigation, invisible focus states, and keyboard traps inside modals
- Low-vision users struggled with insufficient text and non-text contrast
- Motor-impaired users faced difficulty interacting with small tap targets
These issues didn't just reduce usability - they prevented users from completing essential tasks.
Accessibility Issues Are Rarely Isolated
One of the biggest insights from this project was that accessibility failures were systemic, not page-specific. Missing labels, inaccessible navigation patterns, and reliance on color alone appeared repeatedly. This pointed to gaps in design standards and component decisions rather than isolated implementation mistakes.
This is where accessibility becomes a design system and product thinking problem, not just a QA task.
Accessibility Is a Risk and Trust Consideration
For public-facing organizations, accessibility gaps can create avoidable operational and reputational challenges while limiting the ability to serve their communities effectively. Addressing accessibility early helps reduce downstream rework, supports inclusive access, and builds long-term trust with users.
Inclusive Design Improves UX for Everyone
Accessibility improvements don't only benefit users with disabilities. Clear focus states, logical structure, keyboard support, and sufficient contrast improve usability for all users -especially in high-stress, task-driven scenarios.
Accessibility is not about designing for edge cases. It's about designing for reality.
For example, improving keyboard navigation and visible focus states helps users complete important tasks more efficiently, while clearer structure and sufficient contrast make it easier to scan and understand information under pressure. These changes support accessibility needs while also improving speed, clarity, and confidence for all users.
From Findings to Action
Rather than stopping at problem identification, this audit produced a prioritized remediation roadmap, separating critical blockers from moderate improvements. The goal was to make accessibility actionable for designers, developers, and stakeholders alike.
Final Thought
Accessibility work has taught me that some of the most important UX problems are invisible until you look for them. When accessibility is treated as a core product responsibility instead of a compliance checkbox, it leads to better systems, clearer experiences, and more resilient products.
I'm always interested in working on teams where accessibility is treated as a first-class requirement - not an afterthought.
This accessibility audit was conducted as part of an academic project, with guidance and instruction from Prof. Deborah Prewitt. I'm grateful for her mentorship and emphasis on thoughtful, standards-driven accessibility practice.
#Accessibility #InclusiveDesign #UXDesign #ProductDesign #WCAG #DesignSystems #UserCenteredDesign