Keyboard Only
Try a pretend sign-up form with only a keyboard. Each card is a step; pick what you'd report.
Keyboard Only
An accessibility specialist makes websites and apps usable by people with disabilities: people using screen readers, keyboards only, magnification or captions. The standard most teams use is WCAG (Web Content Accessibility Guidelines) 2.2 from the W3C. Frontend developers already write the HTML and components where most accessibility problems start, so you're closer than you think.
Try this before reading on
(Takes about a minute; answers stay on your device.)
- Have you used semantic HTML on purpose (buttons, labels, headings)? (yes / no)
- Have you tested a page with only a keyboard? (yes / no)
- Have you fixed a colour-contrast complaint? (yes / no)
- Do you like careful checking work? (yes / no)
- Would you enjoy explaining fixes to other developers? (yes / no)
Four or five yeses: this bridge is short for you. Two or three: still reachable. Fewer: start with the frontend developer role page and come back.
Your audit, step by step
Pick a public website you use (a government service, a college site, a shop). Then:
- Test five key pages with only a keyboard and with a free screen reader.
- Run Lighthouse on each page.
- Write an audit: each issue, the WCAG 2.2 criterion it fails, who it affects, and a suggested fix.
- Rebuild one broken component properly in a public repo, with before and after.
Keep the tone kind. Don't publicly shame the site; share the audit privately or anonymise it.
Frontend skills that already count for accessibility
Built forms and components. In the new role: audit them for labels, focus and errors. Fixed CSS layout bugs. In the new role: fix contrast, zoom and reflow issues. Used Chrome DevTools. In the new role: run Lighthouse and read its accessibility results. Reviewed pull requests. In the new role: review for accessibility before release.
The new parts are testing with a screen reader (NVDA on Windows and VoiceOver on Mac are both free), reading WCAG criteria precisely, and writing reports a non-specialist can act on.
Your realistic 90 days
Every form, button and modal you've built either helps or blocks someone using a keyboard or a screen reader. This move turns that knowledge into a job title. The plan centres on one public audit with fixes you can show.
Assumes 2–3 hours a day alongside job applications, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of a job or income.
What AI changed in your old tasks
| You used to… | Now you… |
|---|---|
| Built forms and components | Audit them for labels, focus and errors |
| Fixed CSS layout bugs | Fix contrast, zoom and reflow issues |
| Used Chrome DevTools | Run Lighthouse and read its accessibility results |
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Read the W3C WAI introduction to accessibility | Notes on 5 ideas |
| 2 | Navigate 3 websites with only a keyboard | 3 lists of problems |
| 3 | Install NVDA or turn on VoiceOver and try one form | One form tried |
| 4 | Run Lighthouse on 3 pages you built before | Results saved |
| 5 | Pick a public site for your audit | Site chosen |
| 6 | Audit two pages against WCAG 2.2 | 10 issues listed |
| 7 | Save 10 accessibility or frontend postings that mention accessibility | 10 links |
Days 1–30: Your first audit
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Finish a 5-page audit and rebuild one component | about 14 hours over 3 weeks | audit + repo | 3 pages. | Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later. |
| Share it with 5 frontend or QA people you know | about 2 hours | 5 messages | Share it with 3 frontend or QA people you know. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: A developer reads your audit and asks about a criterion.
Days 31–60: Fix and explain
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Add a short accessibility checklist for pull requests to your repo | about 6 hours | checklist live | 10 items. | Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later. |
| Apply to 8 roles mentioning accessibility, WCAG or a11y | about 4 hours | 8 logged | Apply to 4 roles mentioning accessibility, WCAG or a11y. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 60: A screening call for an accessibility or frontend role.
Days 61–90: Interview depth for accessibility specialist roles
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Practise a live keyboard and screen-reader test while talking | about 3 hours | rehearsed twice | Once. | Optional. Skip it if the week is full; nothing later depends on it. |
| Post a short write-up on one fix that mattered | about 2 hours | post live | DM 3 people. | Write it as a draft and publish later. A saved draft still counts. |
Signal by day 90: A practical audit task.
Job-hunt moves that matter for this route
- Search 'accessibility', 'WCAG', 'a11y' and 'digital accessibility' on LinkedIn and Naukri.
- Many openings are frontend roles that ask for accessibility skills; they count.
- Lead with the audit link.
One search that fits your background
The full set of search strings for this move is on the route page. They work on LinkedIn, Naukri and foundit; Instahyre and Cutshort are worth a weekly look too. Add your old job title to any of them with AND, so recruiters who want both skills find you first.
The two worries we hear most about this move
Is there real demand in India? Searches are small in India today. The work often comes from global companies and agencies serving the US and EU, where laws require it. Treat it as a skill that strengthens a frontend CV as well as a separate route. Do I need a certification first? No. Certifications such as IAAP's exist, but a clear audit with fixes is a better first proof. Decide on certification after you've seen a few job listings.
Other worries, such as age, a career gap, no degree, English, family pressure and savings, are covered on the route page and the role page.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
What frontend developers ask about accessibility work
Do I need a certification? Not to start. IAAP certifications exist; see the route page. Proof matters more in listings we read. Is there demand in India? Searches are low in India, so expect many roles to be with global teams or GCCs. See the route page.
Hiring scams to avoid
Be careful with "test tasks" that are really unpaid client work, recruiters asking for fees, or anyone asking for OTPs or UPI PINs. Use official domains only. Report: cybercrime.gov.in / 1930 (India), ReportFraud.ftc.gov (US).
Accessibility pay: unverified
We haven't verified pay data for accessibility specialist roles. Rates differ by city, company and contract type.
Next: route page · Frontend Developer role page · Quiz
Quick quiz: does this path fit?
Answer each, then press Check. Every answer explains itself.
Make your Path Card
A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.
Scam check before you apply anywhere
- Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
- Never share an OTP or UPI PIN — no genuine employer needs them.
- Use official domains only; type the address yourself.
- India: report at cybercrime.gov.in or call 1930.
- US: report at ReportFraud.ftc.gov.
Small steps, every day.
Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.
Keep exploring
Sources
Checked 25 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
The other facts here are shared with the route page, where each is listed in full with its link.