WCAG 1.4.5 Avoid Images of Text

Do not use images of text on your website except where absolutely necessary or for branding purposes (e.g. logo). What to do? Resources Plain English Explanation Avoid images of text as much as possible. Logos are fine. If you do have an image that has text inside it, account for that information with alternative text … Read more

WCAG 1.4.4 Text is Resizable to 200%

All text on your website can be resized up to 200% without any loss of content or functionality on your website. What to do? Resources Plain English Explanation You should be able to increase text size on your page by up to 200% without the page display messing up, having text overlap over other text … Read more

WCAG 1.4.3 Color Contrast

Text and images of text should have a color contrast ratio of 4.5:1 against the background. Exceptions: What to do? Resources Plain English Explanation This is one of the easier success criteria to check for and fix. All we’re doing is trying to make sure our text sufficiently stands out from the background. The closer … Read more

WCAG 1.4.1 Color Not Only Way of Conveying Information

Color should not be used as the only visual way to convey information or make an indication. What to do? Resources Plain English Explanation This success criterion attempts to eliminate any circumstances where color alone is used to convey information, make an indication or prompt the user, or distinguish between visual elements. This error is … Read more

WCAG 1.4.2 Audio Control

Users must have a way to pause or stop any audio that automatically plays for more than three seconds. What to do? Resources Plain English Explanation One of the fundamental principles of accessibility is to put the user in control of the page’s content; they choose what they want to access and not the website … Read more

WCAG 1.3.3 Instructions Involve More Than One Sense

Write clear instructions that incorporate multiple senses. No instructions should rely solely on the ability to perceive shape, size, visual location, orientation, or sound. What to do? Remember that some people will not: Resources Plain English Explanation The main point here is to incorporate multiple ways to perceive instructions. I think a best practice is … Read more

WCAG 1.3.2 Correct Reading Order Sequence

Structure your website so that your content is presented in a logical order. What to do? Resources Plain English Explanation All we’re doing here is making sure that our website presents content in a sensical order to screen readers. If you structure your website correctly under 1.3.1, this will probably be taken care of. Where … Read more

WCAG 1.3.1 Structure Semantically with HTML5

Structure your website so that content is read by a screen reader in the same way it is presented visually to sighted users. What to do? Resources Plain English Explanation If you’re not a web developer, you probably don’t understand what 1.3.1 is asking for. Semantics, in this context, means you are giving things on … Read more

WCAG 1.2.5 Audio Description for Video

All prerecorded video must have an audio description. What to do? Resources In previous success criteria (1.2.3), an audio description was an option. 1.2.5 requires it.

WCAG 1.2.4 Live Captions

For any live video broadcasts, real-time closed captions that identify speakers and include relevant sounds are provided. What to do? This success criterion specifically says it is not intended to require two-way calls through web apps to be captioned regardless of the needs of users. This seems to apply to more formal broadcasts and in, … Read more