Anton Stewart

Contributor, AccessBell

Anton Stewart contributes to AccessBell’s guides on web accessibility, WCAG and accessibility testing.

Every article Anton Stewart works on follows our editorial process: requirements are checked against the primary source, such as the W3C’s Web Content Accessibility Guidelines, and each article shows a review history so you can see what changed and when.

Spotted an error in one of our guides? Tell us and we will review it.

Articles by Anton Stewart

Author · WCAG Codes Explained

WCAG 1.4.2 Audio Control Explained in Plain English

WCAG 1.4.2 Audio Control explained simply: the 3-second rule for autoplaying sound, the pause, stop and volume controls required, and how to test.

Author · WCAG Codes Explained

WCAG 2.1.1 Keyboard Explained in Plain English

WCAG 2.1.1 Keyboard explained simply: why every feature must work without a mouse, the controls that most often fail, how to fix them and how to test.

Author · WCAG Codes Explained

WCAG 2.1.2 No Keyboard Trap Explained in Plain English

WCAG 2.1.2 No Keyboard Trap explained simply: how keyboard traps happen in widgets and embeds, why modal dialogs are not traps and how to test for them.

Author · WCAG Codes Explained

WCAG 2.4.1 Bypass Blocks Explained in Plain English

WCAG 2.4.1 Bypass Blocks explained simply: skip links, landmarks and headings that let keyboard and screen reader users jump past repeated menus.

Author · WCAG Codes Explained

WCAG 2.4.2 Page Titled Explained in Plain English

WCAG 2.4.2 Page Titled explained simply: how to write unique, descriptive page titles, what to do in single-page apps and how to test your titles.

Author · WCAG Codes Explained

WCAG 2.4.3 Focus Order Explained in Plain English

WCAG 2.4.3 Focus Order explained simply: why keyboard focus must follow a logical order, the tabindex and dialog mistakes that break it and how to test.

Author · WCAG Codes Explained

WCAG 2.5.3 Label in Name Explained in Plain English

WCAG 2.5.3 Label in Name explained simply: why a control’s accessible name must contain its visible text, how voice control relies on it and how to test.

Author · Guides

Keyboard Accessibility Testing

A practical guide to keyboard accessibility testing: what to check, the exact keys to use, and a component-by-component reference table mapped to WCAG.

Author · WCAG Codes Explained

WCAG 1.1.1 Non-text Content Explained in Plain English

WCAG 1.1.1 Non-text Content explained simply: how to write alt text for every kind of image, icon, chart and CAPTCHA, with code examples and a test routine.

Author · WCAG Codes Explained

WCAG 1.2.9 Audio-only (Live) Explained in Plain English

WCAG 1.2.9 Audio-only (Live) explained simply: what counts as live audio, who it helps, how to add real-time captions or transcripts, and how to test it.

Author · WCAG Codes Explained

WCAG 1.4.1 Use of Color Explained in Plain English

WCAG 1.4.1 Use of Color explained simply: why color cannot be the only cue, fixes for links, forms, charts and status icons, and how to test your pages.

Author · WCAG Codes Explained

WCAG 2.2.2 Pause, Stop, Hide Explained in Plain English

WCAG 2.2.2 Pause, Stop, Hide explained simply: what moving and auto-updating content needs, the 5-second rule, carousel fixes and how to test your pages.

Author · WCAG Codes Explained

WCAG 2.2.3 No Timing Explained in Plain English

WCAG 2.2.3 No Timing explained simply: why time limits exclude people, the two exceptions, how it differs from 2.2.1, and how to remove timers from your site.

Author · WCAG Codes Explained

WCAG 3.2.2 On Input Explained in Plain English

WCAG 3.2.2 On Input explained simply: what counts as a change of context, who it helps, how to meet it with examples and code, and how to test your forms.

Author · WCAG Codes Explained

WCAG 4.1.3 Status Messages Explained in Plain English

WCAG 4.1.3 Status Messages explained simply: what counts, how to announce it with role status, alert, progressbar or aria-live, form errors and how to test.

Author · Standards

What You Should Know About WCAG 2.2

Here's what you should know about WCAG 2.2: the nine new success criteria, what changed since WCAG 2.1, whether you must conform, and how to test your site.

Scan a Page, Then Monitor and Fix

The free scan shows the issues on one public page. A 3-day free trial then monitors up to 500 URLs per domain and lets you apply fixes you approve, such as alt text, button names and the page language. Nothing is applied until you approve it.

Pro is a 3-day free trial, then $29 per domain per month or $199 per year. You add a card at checkout and are not charged until the trial ends. Cancel before then and you will not be charged.

Not ready for a subscription? A Page Report is $19 for one page, and a Domain Audit is $79 for up to 500 pages.