Accessible Design for Screen Reader Users
Role: UX designer, Accessibility Lead
Duration: Jan 2025 - May 2025
Device: Desktop
Keywords: Accessibility Design, Screen reader, Keyboard navigation, Search experience
Confidential information and deliverables are omitted due to a nondisclosure agreement.
Starting with a thank you!
I appreciate you taking the time to review this case study. I chose this example because I feel it demonstrates:
My ability to conduct platform-wide accessibility audits
My ability to apply accessibility best practices in a design system
My ability to influence team culture and mentor UX practices
Brief
As part of a strategic pilot project with the New Mexico government, I led several initiatives to enhance the accessibility of our platform for screen reader users. This work not only improved the user experience for individuals with visual impairments but also laid the foundation for long-term accessibility integration across our product ecosystem.
Through effective collaboration, we made the search experience accessible as a starting point and added other key pages to our accessibility improvement roadmap.
Goal
Improve screen reader accessibility across the platform.
My Path to Accessibility Design
My journey into accessibility started as a teaching assistant, but I didn’t get to apply those skills until this project in 2025. With no accessibility standards in place at work, I led the charge to build education, audits, and design guidelines from the ground up.
In 2025, I finally got the chance I had been waiting for: to lead accessibility efforts in a pilot project with the New Mexico government. However, the platform had been built without accessibility in mind, and there was a long list of issues to address. This became a turning point where I could finally turn my passion into meaningful, practical impact.
Problem
Our platform lacked support for screen reader users, resulting in poor usability. There was no internal standard or awareness of how to design and implement accessible components, including the following issues.
Lack of landmarks and proper heading structure
Missing or incorrect reading order
No accessibility annotations provided
Not accessible via keyboard navigation
Inability to test due to lack of screen reader knowledge
Solution Overview
After identifying the key challenges, we developed a phased solution strategy to address them, from building internal awareness to collaborating with developers for implementation.
Built internal knowledge and awareness
Conducted Platform-Wide Accessibility Audit
Created Accessibility Annotation Standards
Defined the navigational structure
Collaborated with Developers
Process 1) Built internal knowledge and awareness
I independently researched screen reader behavior (NVDA, JAWS, VoiceOver), created a comprehensive manual, and led company-wide training sessions for 100+ employees to improve accessibility practices.
Process 2) Conducted Platform-Wide Accessibility Audit
I audited key platform pages using WCAG 2.2 guidelines and identified several accessibility gaps, including:
Missing landmarks and heading structures
Missing alt text for icons
Disorganized focus order
Dropdowns are not operable via keyboard
These issues were prioritized based on their impact and implementation complexity, and then communicated to the engineering team for resolution.
Process 3) Created Accessibility Annotation Standards
I facilitated a workshop on annotation styles, where designers explored three different options. After an in-depth discussion, we selected the most effective option, the CVS annotation kit. I also provided training to ensure consistent application across the design team.
Process 4) Defined the navigational structure
(Images are intentionally blurred for NDA compliance)
I established consistent landmark and heading structures across the platform pages, and hand them off to the engineers for implementation.
Process 5) Collaborated with Developers
I created the accessibility tickets and handed them over to the developers. This included reviewing ARIA attributes, keyboard navigation support, and testing interactive elements with screen readers.
Outcome
Search domains are now fully accessible via screen readers.
Completion of 21 out of 54 accessibility tickets in Q1 and Q2.
Accessibility is prioritized in the engineering roadmap.
Raised company-wide accessibility awareness through a training session attended by 100+ staff members.
Positive feedback from cross-functional teammates, highlighting the value of collaboration and accessibility advocacy.
“Bomi worked tirelessly in the background, helping deliver a great final product. The client even provided tips on how we could further showcase our commitment to accessibility.”
- Katie Keating, VP of Sales Engineering
“It’s been a joy to work with Bomi on the accessibility audit. Her willingness to learn and drive solutions shows her incredible collaboration and tenacity.”
- Max Holcomb, Product Manager
“Bomi has been leading the conversation on accessibility annotations. I appreciate her thoughtful research and cross-functional collaboration.”
- Emma Rubinowitz, Senior UX Designer
Reflections
Accessibility as a Foundation, Not a Feature
This project deepened my understanding that accessibility isn’t an add-on, it’s a fundamental part of product design. Ensuring screen reader compatibility required thinking about structure, hierarchy, and user flow at a deeper level than usual.
Empowering Teams Through Education
One key takeaway was how crucial internal education is. Many teammates had never used a screen reader, so I created manuals and led training sessions. This showed me that designers can influence not just interfaces, but team culture and awareness.
Looking Ahead
If I were to approach this project again, I’d involve users with disabilities earlier in the process and push for accessibility testing throughout the product lifecycle. This experience made me a more thoughtful and inclusive designer.