WCAG 3.3.4 Prevent Serious Errors

Make suggestions on how to fix errors on forms. For any web pages that have important implications (legal commitments, rights waivers, spending money, scheduling reservations, etc.), make sure that at least one of the following options is available: What to do? Examples of Big Implications Resources Plain English Explanation All 3.3.4 is getting at is … Read more

WCAG 3.3.3 Error Suggestions

Make suggestions on how to fix errors on forms if an input error is automatically detected. What to do? Resources Plain English Explanation This looks very familiar, right? 3.3.3 is an extension of 3.3.1.  Whereas 3.3.1 requires notification of errors, 3.3.3 takes it a step further by requiring suggestions and instructions to help users correct … Read more

WCAG 3.3.2 Labels and Instructions

For any element that requires user input, concise labels and/or instructions are provided. What to do? Resources Plain English Explanation Every element that allows for user input should have clear, concise, descriptive labels and, where applicable, instructions. A label could be “First Name”. An instruction could be “All fields marked with an * are required.” … Read more

WCAG 3.3.1 Input Errors

When any input error is automatically detected, alert the user, describe the error, and provide instructions on how to correct it. What to do? Resources Plain English Explanation When a user is filling out a form on your website, for any errors they make that are automatically detected, make it easy for them to correct … Read more

WCAG 3.2.4 Consistent Identification

Page components (e.g. links, buttons, icons) that have the same functionality should be identified (with labels, names, and text alternatives) consistently throughout a website. What to do? Examples Resources Plain English Explanation If you read through this success criterion too quickly, you might come away thinking that everything that looks identical needs to have the … Read more

WCAG 3.2.3 Consistent Navigation

Keep your navigation menu placement and order consistent throughout your website. What to do? Resources Plain English Explanation If your page contains a navigation menu (in the header, footer, or both), make sure it is consistent with the menu(s) on other pages of your website. 3.2.3 is getting after predictability.  When it comes to website … Read more

WCAG 3.2.2 No Automatic Change on Input

Nothing on a website should automatically change just because a user inputs text, checks a box, or navigates down a drop down box. What to do? Resources Plain English Explanation This is almost the same as 3.2.1 but this time we’re making sure that adding input doesn’t create an automatic change.  In 3.2.1 we were … Read more

WCAG 3.2.1 No Automatic Change on Focus

Nothing on a website should automatically change just because it receives focus. What to do? Resources Plain English Explanation You always want to put the user in control of your website’s content and functions.  This success criterion speaks to that by requiring that no elements automatically change just because they receive focus. For example, if … Read more

WCAG 3.1.2 Language Change

If the language of a page or on parts of a page is different from the default language of the website, the change needs to be indicated in the HTML code. What to do? Resources Plain English Explanation If there is a language switch for a page, linked page, or paragraph, set the language for … Read more

WCAG 3.1.1 Default Language

The default language for each page of your website is set in the code. What to do? Resources Plain English Explanation Whatever the primary language is for your website, make sure that is the default language set in your website’s HTML code. To check this right now, type: view-source:https://yourwebsite.com into Chrome or Firefox. Look at the very top … Read more