I'm looking for a full-time role in digital accessibility.
My best work is finding barriers with assistive technology, explaining them in language product and engineering teams can use, and verifying that the fix works in the real experience.
Where I fit best
Titles vary. The work matters more than the label.
Accessibility testing and QA
Manual testing of websites, apps, SaaS, and native software with VoiceOver, keyboard navigation, and accessibility inspection tools.
Technical accessibility analysis
Reproducible findings with the user impact, the likely cause in the code, and acceptance criteria your engineers can check against.
Product accessibility and training
Working across product, design, engineering, support, and customers to make accessibility understandable and part of ordinary product decisions.
What I bring
Real user judgment, technical understanding, and five years of Apple experience.
I use VoiceOver every day, not only during a test cycle. At Apple I supported customers across a wide range of technical experience and taught Today at Apple accessibility sessions. That combination taught me how to investigate a problem and explain it without losing the person who needs to act on it.
Working strengths
- VoiceOver, keyboard-only, JAWS, and NVDA testing
- Accessible names, roles, states, focus, and navigation
- HTML, ARIA, DOM, and accessibility-tree inspection
- Clear bug reports and prioritized findings
- Cross-functional communication and live demonstrations
How I work with technical teams
Clear findings, practical direction, and direct validation.
I understand code well enough to read it, follow the logic, and know what the result should be for a screen reader. I don't hand-write production code. What I'm good at is working out how something should behave, directing the build, pushing back when it's wrong, testing every version, and deciding whether it's actually usable.
On a team, I'm strongest as the person who finds the barrier, makes it reproducible, hands engineers a useful path forward, and confirms the fix actually works.
Evidence, not adjectives
Web accessibility finding
A screen reader defect verified in the DOM, with a narrow implementation recommendation and passing criteria.
iOS blocker analysis
A complete VoiceOver failure separated from the partial behavior supplied by Apple's Screen Recognition fallback.
Technical accessibility prototype
A macOS accessibility concept I directed and validated to make otherwise invisible controls reachable by VoiceOver.
If your team needs this combination, I'd like to talk.
Full-time roles are the priority. I also consider well-scoped contract work.