Website accessibility compliance for organizations in Manitoba Mon–Fri, 9:00–5:00 CT · (431) 816-6210
Prairie AccessibilityAccessibility compliance · Manitoba, home Book a consultation

WCAG 2.1 AA in plain language: all 50 success criteria

A plain-language guide to the four WCAG principles and every one of the 50 Level A and AA success criteria in WCAG 2.1.

Published October 2026 · 9 min read · Prairie Accessibility

The Web Content Accessibility Guidelines (WCAG) 2.1 are the technical benchmark named in Manitoba's Accessible Information and Communication Standard Regulation. Level AA is made up of 50 success criteria: 30 at Level A and 20 at Level AA. This guide explains the four principles behind them and then sets out every criterion in one table, with a short description of what each means in practice.

Why WCAG 2.1 AA matters in Manitoba

Under s. 7(1) (opens in a new tab) of Man. Reg. 47/2022, web content must meet WCAG 2.1 Level AA if it was published on or after the applicable date or is needed to access an organization's goods or services. For organizations with one or more employees in Manitoba, that date was May 1, 2025. Our page on the Manitoba standard covers the regulation in more detail.

Meeting Level AA means meeting every Level A criterion and every Level AA criterion. There is no partial score.

The four principles

WCAG organizes its criteria under four principles. If a site fails one of them, some people cannot use it at all.

Perceivable

People must be able to take in the information, whatever senses they use. Images need text alternatives, videos need captions, text needs enough contrast, and content must still work when it is enlarged or viewed on a narrow screen.

Operable

People must be able to use every control. Everything must work with a keyboard, people need enough time, nothing should flash in a way that can trigger seizures, and it should be easy to find your way around.

Understandable

People must be able to understand the content and how the site behaves. Language is identified, pages behave predictably, and forms help people avoid and correct mistakes.

Robust

Content must work reliably with browsers and assistive technology such as screen readers. In practice, that means using standard code correctly so that every control exposes its name, role and state.

Each criterion number tells you where it sits. The first digit is the principle (1 Perceivable, 2 Operable, 3 Understandable, 4 Robust), the second is the guideline, and the third is the specific criterion.

All 50 success criteria

The table lists the 30 Level A criteria first, then the 20 Level AA criteria. The descriptions are simplified; the official text from the W3C remains the authority.

WCAG 2.1 Level A and AA success criteria
CriterionNameLevelWhat it means in practice
1.1.1 (opens in a new tab)Non-text ContentAImages, icons and image buttons have text alternatives that serve the same purpose, or are hidden if decorative.
1.2.1 (opens in a new tab)Audio-only and Video-only (Prerecorded)ARecorded audio has a transcript, and silent video has a text or audio description.
1.2.2 (opens in a new tab)Captions (Prerecorded)ARecorded videos with sound have accurate captions.
1.2.3 (opens in a new tab)Audio Description or Media Alternative (Prerecorded)AImportant visual information in videos is described in audio or in a text alternative.
1.3.1 (opens in a new tab)Info and RelationshipsAHeadings, lists, tables and form labels are marked up in code, not just styled to look that way.
1.3.2 (opens in a new tab)Meaningful SequenceAThe reading order in the code matches the order that makes sense.
1.3.3 (opens in a new tab)Sensory CharacteristicsAInstructions do not rely only on shape, position, size or sound, such as "click the round button on the right".
1.4.1 (opens in a new tab)Use of ColorAColour is never the only way information is shown, such as red text alone marking an error.
1.4.2 (opens in a new tab)Audio ControlAAudio that plays automatically for more than three seconds can be paused, stopped or turned down.
2.1.1 (opens in a new tab)KeyboardAEvery function works using only a keyboard.
2.1.2 (opens in a new tab)No Keyboard TrapAKeyboard users can always move focus away from any component.
2.1.4 (opens in a new tab)Character Key ShortcutsASingle-key shortcuts can be turned off, remapped, or only work when the relevant component has focus.
2.2.1 (opens in a new tab)Timing AdjustableATime limits can be turned off, adjusted or extended, with some exceptions.
2.2.2 (opens in a new tab)Pause, Stop, HideAMoving, scrolling or auto-updating content, such as carousels, can be paused, stopped or hidden.
2.3.1 (opens in a new tab)Three Flashes or Below ThresholdANothing flashes more than three times in any one second.
2.4.1 (opens in a new tab)Bypass BlocksAA skip link or similar lets people jump past repeated navigation to the main content.
2.4.2 (opens in a new tab)Page TitledAEach page has a title that describes its topic or purpose.
2.4.3 (opens in a new tab)Focus OrderAKeyboard focus moves through the page in a logical order.
2.4.4 (opens in a new tab)Link Purpose (In Context)AThe purpose of each link is clear from its text or its surrounding context.
2.5.1 (opens in a new tab)Pointer GesturesAAnything done with a multi-finger or path-based gesture can also be done with a single tap or click.
2.5.2 (opens in a new tab)Pointer CancellationAActions trigger on release rather than on press, so people can slide off to cancel a mistaken tap.
2.5.3 (opens in a new tab)Label in NameAThe accessible name of a control includes its visible label, so voice control users can say what they see.
2.5.4 (opens in a new tab)Motion ActuationAFunctions triggered by shaking or tilting a device also have a regular control and can be turned off.
3.1.1 (opens in a new tab)Language of PageAThe page's main language is set in the code so screen readers pronounce it correctly.
3.2.1 (opens in a new tab)On FocusAMoving focus to an element does not cause an unexpected change, such as opening a new page.
3.2.2 (opens in a new tab)On InputAChanging a setting, such as choosing from a drop-down, does not cause an unexpected change without warning.
3.3.1 (opens in a new tab)Error IdentificationAForm errors are identified and described in text.
3.3.2 (opens in a new tab)Labels or InstructionsAForm fields have visible labels or instructions.
4.1.1 (opens in a new tab)ParsingAThe code is well formed, without errors such as duplicate IDs that confuse assistive technology.
4.1.2 (opens in a new tab)Name, Role, ValueAEvery control exposes its name, what kind of control it is, and its current state to assistive technology.
1.2.4 (opens in a new tab)Captions (Live)AALive video with sound, such as a webinar, has captions.
1.2.5 (opens in a new tab)Audio Description (Prerecorded)AARecorded videos include audio description of important visual information.
1.3.4 (opens in a new tab)OrientationAAContent works in both portrait and landscape unless one orientation is essential.
1.3.5 (opens in a new tab)Identify Input PurposeAAFields asking for personal details, such as name and email, are coded so browsers can autofill them.
1.4.3 (opens in a new tab)Contrast (Minimum)AAText has a contrast ratio of at least 4.5:1, or 3:1 for large text.
1.4.4 (opens in a new tab)Resize TextAAText can be enlarged to 200% without losing content or function.
1.4.5 (opens in a new tab)Images of TextAAReal text is used instead of pictures of text, except for logos and similar cases.
1.4.10 (opens in a new tab)ReflowAAContent fits a 320 CSS pixel wide viewport without scrolling sideways.
1.4.11 (opens in a new tab)Non-text ContrastAAButtons, form field borders, focus indicators and meaningful graphics have at least 3:1 contrast.
1.4.12 (opens in a new tab)Text SpacingAAContent still works when people increase line, letter, word and paragraph spacing.
1.4.13 (opens in a new tab)Content on Hover or FocusAATooltips and pop-ups shown on hover or focus can be dismissed, hovered over and stay visible until dismissed.
2.4.5 (opens in a new tab)Multiple WaysAAThere is more than one way to find a page, such as navigation plus search or a site map.
2.4.6 (opens in a new tab)Headings and LabelsAAHeadings and labels describe the topic or purpose of what follows.
2.4.7 (opens in a new tab)Focus VisibleAAKeyboard users can always see which element has focus.
3.1.2 (opens in a new tab)Language of PartsAAPassages in another language, such as a French paragraph, are marked in the code.
3.2.3 (opens in a new tab)Consistent NavigationAANavigation that repeats across pages appears in the same order each time.
3.2.4 (opens in a new tab)Consistent IdentificationAAElements that do the same thing are labelled the same way throughout the site.
3.3.3 (opens in a new tab)Error SuggestionAAWhen an error is detected and a fix is known, the form suggests how to correct it.
3.3.4 (opens in a new tab)Error Prevention (Legal, Financial, Data)AALegal, financial or data submissions can be reviewed, corrected or reversed before they are final.
4.1.3 (opens in a new tab)Status MessagesAAMessages such as "Added to cart" or "3 results found" are announced by screen readers without moving focus.

A note on 4.1.1 Parsing: the W3C has since clarified that, for content written in HTML or XML, this criterion is treated as always satisfied, because modern browsers and assistive technology handle the issues it was written for. It remains in the WCAG 2.1 list, so it is included here for completeness. Problems such as duplicate IDs can still cause failures under other criteria, especially 1.3.1 and 4.1.2.

Which criteria need a person to test

Automated tools are good at finding some issues, such as missing alt attributes, low contrast in plain text, or a missing page language. Many criteria, however, require judgement: whether alt text is meaningful, whether focus order makes sense, whether error messages help, whether a video's captions are accurate. That is why our method combines automated scans with manual keyboard testing, NVDA and VoiceOver screen readers, 200% zoom and 320 pixel reflow checks.

A clean result from an automated scanner does not mean a page meets WCAG 2.1 AA. It means the scanner did not find the issues it is able to detect.

How to use this list

Not every criterion applies to every site. If you have no video, the media criteria in 1.2 have nothing to test. If you have no time limits, 2.2.1 is not a concern. An audit records which criteria apply, which pass and which fail, and where. You can see how we present that in our sample report, and further reading is listed on our resources page.

Talk to us

If you would like to know how your website measures against all 50 criteria, book a consultation. We will explain what an audit covers and provide a fixed written quote after the audit.

Last reviewed October 2026. General information, not legal advice.

Next step

Find out where your website stands.

Book a 20-minute consultation. We review your website with you, explain what applies to your organization, and follow up with a fixed written quote.