I run a small agency and made this required viewing. It is free, it is four evenings, and it removed an entire category of bug from our work. The dialog lesson alone.
Accessible by Default
Semantics, keyboard and ARIA — building interfaces that work for everyone, from the first commit.
- 7 hours of video
- 6 hands-on projects
- An audit checklist
- Lifetime access
- Certificate of completion
37% of the running time is hands-on — projects and quizzes rather than video.
What you'll learn
Reach for the element first
The platform already solved most of this. Learn what the right tag gives you before adding a role.
Test with the keyboard
Operate your own interface without a mouse, and find the trap, the skipped stop and the invisible focus ring.
Use ARIA sparingly
The small number of places it is genuinely needed — live regions, composite widgets — and nowhere else.
Meet WCAG 2.2 AA
Colour contrast, focus appearance and target size, hit without redesigning the product.
Audit into a fix list
Produce something a team can ship this sprint, rather than a score nobody acts on.
What’s inside
Every figure below is summed from the lesson list, not estimated — so the chart and the curriculum can never disagree.
| Content type | Minutes | Share |
|---|---|---|
| Video lessons | 315 | 62.6% |
| Hands-on projects | 165 | 32.8% |
| Quizzes | 23 | 4.6% |
37% of this course is hands-on.
Curriculum
4 sections · 16 lessons · 8h total
The platform already solved a lot of this.
- VideoThe accessibility tree, seen in the inspector
- VideoHeadings, landmarks and a document outline
- VideoNames, roles and values, demonstrated
- QuizSemantics quiz
If it works on a keyboard it usually works everywhere.
- VideoFocus order, focus visible, focus trapped
- VideoBuilding a menu with the real keyboard model
- VideoDialogs: inert, return focus, escape
- ProjectProject: make a component library keyboard-complete
The first rule of ARIA is not to use ARIA.
- VideoWhen a role is the right answer
- VideoLive regions that announce once
- VideoThe patterns people get wrong most often
- QuizARIA quiz
From a report nobody reads to a list somebody ships.
- VideoAutomated tools: what they catch and miss
- VideoA manual pass in twenty minutes
- VideoColour, contrast and WCAG 2.2 target size
- ProjectCapstone: audit a real site and fix the top ten
Inês Marchetti
Design engineer · accessibility specialist
Inês sits between design and engineering and refuses to pick a side. She audits for WCAG by day and rebuilds the offending components by night, which is why her lessons always come with the fixed version next to the broken one.
Design systems at Aurora Health
CompletedA component library used across 60 clinical products.
IAAP CPACC
CompletedCertified Professional in Accessibility Core Competencies.
Public audits
In progressPublished teardowns of 40 popular component libraries.
What learners said
5,518 ratings from people who bought this course.
5,518 ratings
- 5 stars
- 4 stars
- 3 stars
- 2 stars
- 1 star
Inês shows the broken version and the fixed version side by side every single time. That format is why it sticks. I have stopped adding role attributes to things that already had a role.
Really good introduction. I would have liked more on screen reader testing across NVDA, JAWS and VoiceOver — it covers one and mentions the others.
Learners also took
Same category first, then whatever pairs well with it.
CSS Without a Framework
Modern layout, custom properties and container queries — the browser is the framework now.
Ship It: Next.js 16 from Zero to Production
Build and deploy a real application on the App Router — async request APIs, streaming, caching and the deploy that follows.
TypeScript for Teams
Types that catch real bugs and stay out of the way — for codebases with more than one author.
Browse the full course catalogue, or see how this page is put together on Built with VivekUI.