Accessible web development: WCAG, ARIA and keyboard navigation
A ready-made course you customise for your organisation, with a live session deck and two surveys. You only add the 7 details that are specific to your organisation.
- Length
- 40 min
- Lessons
- 6 lessons
- Frequency
- At onboarding
- Last reviewed
- 21 Oct 2026
An icon-only button has no text
Try it: this is one of 14 interactive activities in the course.
What's included
Three pieces that work together
Copy once, get everything. Learners prepare on their own, you answer questions live, and the surveys tell you what stuck.
Self-paced course
Short lessons with real workplace scenarios, not walls of text.
- 6 lessons, about 40 minutes
- Scenario, timeline, accordion, sorting activity and quizzes
Live session deck
An AhaSlides presentation to run after the course, in person or online.
- 10 slides
- Quiz, poll, ranking, word cloud slides
- A closing slide for your contacts
Two surveys
Find out what landed, and whether people use it on the job.
- Post-course feedback, about 2 minutes
- 30-day check-in
- Anonymous by default
- Results feed your next refresher
Learning objectives
At the end of this course, learners can
Each objective and the lesson that covers it.
| ID | Objective | Source | Where it's covered |
|---|---|---|---|
| TO 354.0 | Achieve ≥ 80% on the final assessment | - | Whole course |
| SO 354.1 | Use semantic HTML and landmarks so a page can be navigated | WCAG 2.2 [check before build] | Whole course |
| SO 354.2 | Give controls an accessible name and role, and know when ARIA is needed | WCAG 2.2 success criteria 4.1.2 and 1.3.1 [check before build] | Whole course |
| SO 354.3 | Make a page usable by keyboard with visible focus | WCAG 2.2 [check before build] | Whole course |
| SO 354.4 | Test with a keyboard and a screen reader + your info | Best practice | Whole course |
| SO 354.5 | Explain the legal context for your market + your info | EN 301 549 and European Accessibility Act, applicable from 28 June 2025 (check scope before build); ADA and Section 508 in the US [check before build] | Whole course |
Your part: what a template can't do for you
- Your workplace details: fill in the 7 highlighted fields so the course describes your own policies, contacts and locations.
- Records: record completion in your own LMS or record system.
Course outline
6 lessons, about 40 minutes
Minutes per lesson are an estimate, shared out by page count.
1A form no one could submit
3 pages
8 min
A form no one could submit
3 pages
2Semantic HTML and landmarks
3 pages
8 min
Semantic HTML and landmarks
3 pages
3Names, roles and ARIA
3 pages
8 min
Names, roles and ARIA
3 pages
4Keyboard and focus
2 pages
6 min
Keyboard and focus
2 pages
5Testing with a screen reader
2 pages
5 min
Testing with a screen reader
2 pages
6Fixing a page and final assessment
2 pages
5 min
Fixing a page and final assessment
2 pages
Live deck and surveys
10 slides to run live, two surveys to close the loop
Pink slides are interactive. Both surveys are anonymous; pink questions are written for this course.
Post-course feedback: 11 questions, about 2 min
- Overall rating 5 stars
- Relevant, realistic, right length, helpful activities agree/disagree grid
- What was most useful? multi-select
- Confidence before this course, and now 1-5 scale
- Confidence in semantic HTML · names and roles · keyboard · screen reader testing · legal context grid
- Is accessibility part of your definition of done? multiple choice
- Which accessibility topic do you want covered? short text
- I can say ‘I did not test this with assistive technology’ without feeling judged. 1-5 scale
- One thing we should change or add open text
- Would you recommend this course? NPS
30-day check-in
- Have you used what you learned since the course? multiple choice
- How confident are you today? Compare with day 1 1-5 scale
- Do you know where to find the accessibility test flow and standards link? yes / no / not sure
- A moment where the training helped, or where you weren't sure open text
- Which topics should the next refresher focus on? ranking
Results show whether people use the training on the job, not just whether they finished it.
Make it yours
7 fields to fill in, and you're ready
Everything else is done. These are the details only your organisation knows; each one is highlighted inside the course.
- Link to the engineering standards or style guide
{{ENGINEERING_STANDARDS_LINK}} - Who to ask for help or to report a concern
{{HELP_CONTACT}} - Where completion is recorded
{{LMS_OR_RECORD_SYSTEM}} - Link to the post-course and 30-day survey
{{SURVEY_2_URL}} - Link to the self-paced course
{{COURSE_URL}} - Link to the organisation policy referred to in the course
{{POLICY_LINK}}
Show all 7 fields
- Link to the baseline survey
{{SURVEY_1_URL}}
FAQ
Common questions
Can I run accessible web development: WCAG, ARIA and keyboard navigation training online?
Yes. The course is self-paced and online, and the live deck lets you add a live session in the room or online.
How often is this training needed?
At onboarding, and before an accessibility audit or a release that must meet accessibility requirements.
Who needs this training?
Front-end developers, QA engineers and design-system teams; run by engineering managers and accessibility leads with L&D.
What records should I keep?
Record completion in your own LMS or record system, so you can show who finished the course and when.
Can I edit the content?
Yes, everything. Change the wording, swap scenarios for ones from your workplace, add your logo, or remove parts that don't apply.
Related templates
Often taught together
Front-end engineering standards: HTML, CSS, javascript and typescript in practice
Front-end and web developers · Web and mobile
Mobile app development and release standards for android and ios teams
Android and iOS developers and QA engineers · Web and mobile
Ready to run it?
Open the live deck to see how the session runs alongside the course and both surveys.