Accessibility Testing with WCAG 2.2
Test a local synthetic workshop journey against WCAG 2.2: scope and criteria, keyboard and focus, semantic names, form recovery, contrast and reflow, screen-reader protocols, native modal behaviour, bounded automation, defect evidence and retest. Includes complete local HTML and focused Python Playwright checks; evidence notes are not a compliance certification. A practical path from a keyboard walkthrough to a bounded accessibility evidence portfolio.
- 24
- Lessons
- 8
- Sections
- 8
- Practice labs
- ~12h
- Of content
Sign in to save progress and earn a verified achievement.
1<label for="email">Email address</label>2<input id="email" type="email"3 aria-describedby="email-hint email-error">4<p id="email-error"></p>5<p role="status"></p>
The method
Built like real QA work, not a video playlist.
Learn
24 focused lessons, each a few minutes long.
Practice
8 hands-on labs in a browser workspace.
Test yourself
8 section assessments plus a final exam.
Prove it
A public, verifiable achievement for recruiters.
What you will learn
- Scope, users and WCAG 2.2: Define a journey-based accessibility test scope, Run an isolated repeatable fixture, Translate criteria into observable expectations
- Keyboard and focus: Inspect keyboard order without positive tabindex, Separate visible focus from focus obscuration, Test escape routes instead of disabling focus containment
- Semantic structure and names: Check headings, landmarks and a bypass path, Verify computed names rather than trusting placeholders, Prefer native semantics and avoid redundant ARIA
- Forms, errors and status: Make error identification and recovery specific, Announce confirmation without moving focus to every update, Check instructions, autocomplete and redundant entry
- Contrast, reflow and pointer access: Calculate contrast and classify the content, Test zoom and narrow reflow as different observations, Evaluate target size, dragging and motion without blanket claims
- Screen readers and modal review: Plan real screen-reader combinations, Verify dialog name, opening focus and focus return, Write an assistive-technology transcript without fake certainty
Where you will be at the end
- Complete 8 hands-on practice challenges, one per section (from Scope, users and WCAG 2.2 to Defects, retest and portfolio)
- Pass 8 section assessments
- Pass the Accessibility Testing with WCAG 2.2 final assessment and add the result to your Skill Passport
Who this course is for
- Beginners and manual testers starting this skill from scratch
- Working testers who want to apply it on real projects
- Anyone preparing for QA interviews that ask about this skill
- Best if you already have: Basic browser and HTML familiarity; Python 3 and a browser for the local fixture; an available screen reader for manual protocols
Curriculum
9 sections, one clear path.
- Define a journey-based accessibility test scope
- Knowledge check
- Run an isolated repeatable fixture
- Knowledge check
- Translate criteria into observable expectations
- Knowledge check
- Evidence checkpoint: Scope, users and WCAG 2.2
- Section assessment
Members-only toolkit
Take the course with you
Made from this course's own lessons, quizzes and labs — ready to revise before interviews or use at work.
Course cheat sheet
Loading…
Interview Q&A pack
Loading…
Lab solutions & hints
Loading…
- Auto-checked labs
- Capstone portfolio project
- Timed final exam
Why paid courses
More than a free course: practice, proof and a portfolio
| What you get | Free | Academy |
|---|---|---|
| Short lessons with examples | ||
| Quick checks and certificate | ||
| Hands-on labs checked automatically | ||
| Section tests and a timed final exam | ||
| Portfolio capstone project with milestones | ||
| Cheat sheet, interview pack and lab answers to download | ||
| Verified skills on your profile and Skill Passport |
What Students Are Saying
Sign in and complete 20% of the course to leave a review.
Share your experience on Trustpilot (optional)
Honest feedback is welcome, whatever your experience. A Trustpilot review is not required for your certificate.
Accessibility Testing with WCAG 2.2: common questions
1.Do I need experience before starting Accessibility Testing with WCAG 2.2?
2.What can I try for free, and what needs payment?
3.How long does the course take?
4.What do I get when I finish?
Finish with proof, not just a certificate PDF.
Pass the final assessment and get a public verification page showing your score, completion date and the skills you demonstrated — ready to share on LinkedIn.
About this Accessibility Testing course
A booking form can look finished while someone cannot identify its email field, escape a review window or hear a confirmation. This course follows one local synthetic workshop journey through initial entry, invalid email, correction, review, cancel and confirmation. Twenty-four lessons in eight sections connect observable behaviour to WCAG 2.2 criteria. Eight written evidence checkpoints and eight assessments accompany the lessons. The aim is a reproducible test record with honest limits, not a scanner score or an assertion that a small fixture proves an entire website conforms.
Start by writing a scope that names complete journeys and their states. A WCAG 2.2 AA target includes applicable A and AA criteria. The course separates keyboard operation from focus visibility, visible focus from obscuration, and a control name from its description. Understanding documents interpret requirements; implementation techniques are examples, not mandatory recipes. Criteria such as Accessible Authentication require a real applicable login process. The fixture has no login, so it cannot supply evidence for the authenticated parts of another site.
The reference source-map lesson provides a complete HTML page, setup notes and a Python Playwright check script. Serve the page on your own loopback interface with Python. No actual workshop is booked, no data is stored, and reload resets the example. A native email field has a persistent associated label and a format hint. Invalid submission sets an invalid state, associates a specific correction and moves focus to a summary. Corrected input opens a named native dialog. All inputs used in portfolio screenshots should be synthetic rather than personal email addresses.
Keyboard protocols begin with the skip link, follow meaningful focus order, reverse with Shift+Tab, and activate controls without a pointer. The review dialog places initial focus on Confirm, cycles between its controls, supports Escape and Cancel, and returns focus to the opener on close. Native modal inertness and explicit boundary cycling are used together, because browser behaviour still needs observation. A focus indicator must remain visible and not be completely hidden by an overlay. Focus Appearance is a WCAG 2.2 AAA criterion; it must not be misrepresented as a universal AA obligation.
Visual checks distinguish ordinary text contrast, large text contrast and relevant nontext contrast. Record unrounded measured ratios and the actual adjacent backgrounds rather than relying on colour names. Text resizing to two hundred percent, narrow reflow at three hundred and twenty CSS pixels, and actual browser zoom are separate observations. A narrow screenshot alone is not evidence that real four-hundred-percent browser zoom was operated. Target-size minimum and enhanced requirements have different levels and exceptions. The fixture has no drag interaction or animation; absent features must not generate invented passing results.
Screen-reader lessons provide an execution protocol for supported combinations such as NVDA with Firefox or Chrome on Windows and VoiceOver with Safari on macOS or iOS. Record actual versions, navigation mode, action and announcement. Browser accessibility-tree inspection can reveal names and roles but does not simulate speech, braille or reader modes. Where an environment cannot run a chosen reader, leave the check explicitly not executed. The course does not claim that all screen-reader combinations were tested during preparation. A real transcript is evidence; guessed words are not.
The supplied browser checks cover selected label, focus, invalid-state, modal-exit, confirmation, reflow and reset contracts. A missing-label mutation should make a label-based check fail, followed by a passing run after restoration. These scripts execute independently on the learner machine, never on the Academy server. Optional axe-core scans should name the tool version, selected rule tags and each scanned state, preserving incomplete items alongside violations. Zero detected violations means that configuration found none in those states; it does not certify complete WCAG conformance.
The final portfolio includes a scope, criterion matrix, keyboard observations, contrast measurements, reflow evidence, reader protocol or actual transcript, automated execution record, synthetic defect and retest matrix. Preserve unexecuted work as a named limitation. Retest the repaired boundary and sibling states using comparable environments instead of deleting a finding because one scanner becomes green. Academy completion is not an official W3C or legal compliance credential. The free companion is a shorter orientation, while the premium course supplies the full local reference and deeper evidence workflow; neither requires live instruction or a human-review purchase.
Who this course is for
- QA engineers adding accessibility to existing test work
- Beginners learning WCAG-based observations
- Automation testers separating machine checks from manual evidence
What you need
- Basic browser and HTML familiarity
- Python 3 and a browser for the local reference
- An available screen reader for the manual protocol; unavailable combinations remain unexecuted
What you will be able to do
- Scope complete accessibility journeys and criterion-specific checks
- Test keyboard, names, form recovery and native modal transitions
- Execute the local browser reference and detect a missing-label regression
- Build an honest evidence portfolio with reader and zoom gaps visible
