Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Accessibility
Check a design for accessibility barriers and list practical fixes
What you'll learn
POUR principles
Colour contrast
Keyboard focus
Meaningful labels
Practice
Write a developer-ready note for one WCAG failure25 min
Audit a Sign-Up Form for Accessibility Issues10 min
Audit a real app for one accessibility issue15 min
Chapter 2
Accessibility standards
Test a page by keyboard only and record what fails
What you'll learn
Success criteria
Conformance levels
Native HTML first
Audit scope
Practice
Audit a Component and Write a Developer-Ready Remediation Note20 min
Chapter 4
Assistive technology testing
Test a form with a screen reader and log barriers
What you'll learn
Screen reader modes
Keyboard focus
Accessible names
Reader differences
Practice
Test a Form with VoiceOver (or NVDA) and Log What Gets Announced20 min
Chapter 4
Usability testing
Watch a user try a design while you stay quiet
What you'll learn
User task
Think-aloud protocol
User behaviour
Test method
Practice
Run a Think-Aloud Usability Test with a Friend15 min
Chapter 6
Communication
Rewrite an update for two different readers, cutting extra lines
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Write a Six-Line Delay Message10 min
3 more in the plan
Problem solvingTest each possible cause of a problem instead of guessingCh 7
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Separate the Problem from the Symptom10 min
Adapting to changeTry a new tool and describe how you handled changeCh 7
What you'll learn
Change vs your response
The messy in-between
Not there yet
Real change vs a feeling
Practice
Map a Change You've Already Survived15 min
Working with othersContribute to group work, ask for help and credit teammatesCh 8
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Practice
Write a Request That Makes It Easy to Say Yes10 min
Your plan
Chapter by chapter.
12 chapters, in this order. Chapter 1 is free.
1~2 wks
See the work of an Accessibility Specialist
StartFree
2~2 wks
Audit and fix designs for accessibility
Skills
3~2 wks
Audit a public site and propose fixes
Project
4~2 wks
Test with screen readers and real users
Skills
51–2 wks
Talk to two working accessibility specialists
People
6~2 wks
Make your point land the first time
Skills
7~2 wks
Solve problems when plans change
Skills
8~2 wks
Work well with the people around you
Skills
9~2 wks
Capstone: run a usability study with disabled participants
Project
101–2 wks
Answer the questions interviewers ask
Interview
111–2 wks
Decide how you will get in
Decide
12on your timeline
Send your first applications
Apply
The job
What a Accessibility Specialist does
Tests and improves digital products so disabled people can use them fully. Works with standards like the Web Content Accessibility Guidelines (WCAG). Helps teams meet laws such as the European Accessibility Act in the EU and the Americans with Disabilities Act (ADA) in the US.
The work
Audit websites and apps against WCAG (the global accessibility standard)
Test products with assistive technology like screen readers and switch devices (simple buttons for people who cannot use a mouse)
Review designs and code early to catch accessibility problems before launch
Write remediation guidance (clear fix instructions) developers can act on quickly
Run usability sessions with disabled users to find real-world barriers
Teach designers and developers to build accessible products by default
Track legal requirements like the European Accessibility Act, ADA, and Section 508
Judge issues automated checkers miss, like confusing flows or unclear labels
A typical day
Test a new feature with a screen reader and keyboard-only navigation
Log issues with severity ratings, screenshots, and clear suggested fixes
Join a design review to flag contrast, focus order, and labeling problems
Pair with a developer to fix a tricky form or custom component
Run a short training session or answer team questions about WCAG
Update the accessibility checklist and report progress to product leads
How long does it take to become a accessibility specialist with Welica?
The plan is 12 chapters, 4–5 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are bachelor degree in design, HCI (human-computer interaction), computer science, or psychology, certification from the International Association of Accessibility Professionals (IAAP), like CPACC or WAS, short courses in web accessibility, WCAG, and inclusive design, or self-study using free W3C (the web standards body) accessibility courses plus practice audits.
What is free?
Chapter 1, See the work of an Accessibility Specialist, is free for good. Premium unlocks the rest of the plan.