Description:
my QA tasks are getting repetitive and I keep seeing accessibility roles pop up 👀. how do i break into accessibility testing without making my resume look like a random jump?
2 Answers
A lot of QA work already maps cleanly to accessibility, so I’d reframe your resume instead of “pivoting” hard. Add a small section for a11y checks you’ve done - keyboard-only pass, focus order bugs, contrast issues, alt text gaps. In my old team, 3 solid bullets beat 12 vague ones.
Build one mini portfolio piece from a real app or demo site and show 2 fixes plus the test method. Use tools like Axe and NVDA, then mention WCAG 2.1 AA by name. Apply to hybrid QA/a11y roles first - pure accessibility jobs were weirdly picky until I had at least 1 story with impact metrics and screenshots
qA teams I worked with kept treating accessibility like a side quest, then got surprised when it turned into a real hiring lane. People say to just “add WCAG” to your reesume and wait, but that reads thin. Put 2 or 3 concrete examples on there - keyboard testing, screen reader checks, color contrast failures you caught, and maybe one audit on a 50-page app - so the move looks like specialization, not a detour.
Join the conversation and help others by sharing your insights.
Log in to your account or create a new one — it only takes a minute and gives you the ability to post answers, vote, and build your expert profile.