What I test
Perceivable and Understandable
Evaluates how effectively screen reader users can navigate and comprehend web content. I focus on ensuring that all information is programmatically accessible and logically structured for a seamless, intuitive experience.
Focus management
When a modal opens, does focus move into it? When it closes, does focus return correctly? Blind users navigate by keyboard — broken focus means getting lost.
Live updates & announcements
Dynamic content — alerts, errors, confirmations, loading states — must be announced. If it only appears on screen, blind users never know it happened.
Full task flow
Can a blind user complete the entire task — sign up, fill a form, submit, get feedback — without getting confused or stuck? I test end-to-end, not just components.
Attributes & markup
Missing alt text, incorrect roles, broken labels, improper heading hierarchy — the structural layer that screen readers depend on.
The silent failures automated tools miss
- A modal opens but focus stays on the button that triggered it — the user has no idea a dialog appeared
- An error message displays visually but is never announced — the user resubmits a broken form, confused
- A page update happens after clicking a button, but nothing is communicated — the user thinks nothing worked
- A loading spinner appears — but there's no ARIA live region to say "loading" or "done"
- A success toast notification appears on screen and fades away before a screen reader gets to announce it
- Navigation skips or menu items that work visually but trap or disorient keyboard users
Services
Manual screen reader audit
Real-world testing with an actual screen reader. I document every failure — broken attributes, silent interactions, confusing flows — with clear explanations and steps to reproduce.
Root cause & fix advice
As a developer, I trace every issue to its source — missing ARIA labels, incorrect live region setup, broken focus management — and explain exactly what code needs to change.
Monthly monitoring
Your app changes constantly. I check in monthly, update a living report with newest findings on top, and flag any regressions before your users notice them.
WCAG review
Structured audit mapped to WCAG guidelines, delivered as a prioritised, actionable report your developers can work from directly.
Technical background
I'm a full stack web developer with deep knowledge of the front-end layer where accessibility problems actually live. I understand your code, which means my reports are never vague — every finding comes with a technical explanation and a concrete fix.
Audit samples
Real audits of live websites — updated regularly with the latest findings.
Audit reports coming soon — check back shortly.
Articles
My articles related to web audits and best practices for screen reader
-
Screen Reader Experience Analysis on Claude
Analysis on how well Claude AI works with screen reader (NVDA).>
-
Screen Reader Experience Mitigation on Claude AI
Article about how to mitigate the inaccessibility items found on Claude AI.
-
Screen Reader Experience Analysis on Grok
Analysis on how well Grok web UI works with screen reader (NVDA).
-
Screen Reader Experience Mitigation on Grok
Article on how to mitigate the inaccessibility factors in Grok web UI.
- note
Screen Reader Experience Analysis on Gemini
Analysis on how well Gemini web works with screen reader (NVDA).
-
Screen Reader Experience Mitigation on Gemini
Article on how to mitigate inaccessibility factors on Gemini web.