Web Accessibility (WCAG)
Welcome, champion! 🔥
You've mastered 0 of 74 lessons. Start your first lesson free — no signup needed.
About this course
An email field with no label looks fine on screen, yet a screen reader has no name to announce for it. Many accessibility failures are like this: small, invisible to the person who built the page, and fixed with a line or two of HTML once you know what to look for. This online web accessibility course on Abekus starts by fixing that one unlabelled input and builds up to how WCAG 2.2 is organised, semantic HTML, perceivable content, keyboard operation, understandable forms, WAI-ARIA and accessibility testing, in short reading-card lessons each followed by an MCQ quiz.
Who this web accessibility course is for
It is written for front-end developers, testers and designers who build or check web pages and forms. You should be able to read basic HTML; the code examples are HTML with a little CSS and plain JavaScript, and no framework is used. By the end you can read a WCAG 2.2 success criterion and apply it, fix common failures in HTML and ARIA, test a page with a keyboard, a screen reader and automated tools, and write an honest conformance report.
The course follows WCAG 2.2, the current W3C Recommendation, with level AA as the default target, along with WAI-ARIA 1.2. Success criteria are cited by number and short name, such as 1.4.3 Contrast (Minimum), and thresholds are given as the standard states them. Screen readers such as NVDA, JAWS, VoiceOver and TalkBack are named as examples, without key-by-key tutorials. For the Indian context the course refers to GIGW 3.0 and the Rights of Persons with Disabilities Act, 2016. It leaves out native mobile app accessibility APIs, PDF and document accessibility, comparisons of paid audit tools, and WCAG 3 beyond its status as a draft. It is an independent course and is not affiliated with or endorsed by the W3C.
How the lessons work
Each lesson is a short set of reading cards on one success criterion, element or pattern, usually with a few lines of markup and a note on what assistive technology announces, followed by a quiz of multiple-choice questions that often ask whether a snippet passes, what a screen reader will announce or which fix is correct. Lessons go from basics up: one form field fixed and who benefits, how WCAG is organised, semantic HTML, perceivable content, operable interfaces, understandable forms, WAI-ARIA, testing and reporting, and finally comparisons and worked cases. You move at your own pace, and every lesson works from markup shown as text, with no screenshots of screen readers or audit tools.
MCQ practice vs video courses for web accessibility
Video courses on Udemy, Coursera or YouTube are a good choice if you want to watch a screen reader being used on a live site or an audit tool being run. This course is built for a different job: a short explanation followed straight away by questions about real markup, such as whether a label is linked to its input, whether a colour pair meets 4.5 to 1, where focus should go when a dialog opens, or whether an ARIA attribute helps or harms. WCAG is specific, with exact thresholds and exceptions, and checking snippets against it question by question builds the eye for failures that an audit depends on. Many learners use both: a video to see assistive technology in use, and questions to make the criteria stick.
Common accessibility mistakes
The course corrects these directly:
- Using a placeholder as the label. Placeholder text disappears when the user starts typing and does not replace a label linked to the input.
- Adding a role to a div and calling it a button. ARIA changes semantics only; keyboard behaviour must be added, or a native button used.
- Treating a passing automated scan as conformance. Automated tools miss a large share of barriers, so keyboard and screen reader checks are still needed.
- Quoting 44 by 44 pixels as the AA target size. 2.5.8 Target Size (Minimum) at AA is 24 by 24 CSS pixels; 44 by 44 belongs to the AAA criterion.
- Reading large text as 18 pixels. Large text is at least 18 point, about 24 CSS pixels, or 14 point bold.
- Still testing 4.1.1 Parsing. It was removed in WCAG 2.2 as obsolete.
- Relying on an overlay widget. Conformance depends on the page's own content and code.
Best way to learn web accessibility
Start with native HTML and a keyboard. Take a page you have built, put the mouse aside and try to reach and operate every control from the keyboard, then check that every control has an accessible name and every image a suitable text alternative. Learn the criteria by the failures they prevent rather than by number alone, and reach for ARIA only when no native element does the job. The last part of the course is built around these choices: native HTML versus an ARIA widget, AA versus AAA targets, overlay widgets versus fixing the source code, and when to use ARIA or a live region, applied to an accessible login form, a modal dialog, a data table and a checkout flow.