Website Accessibility Checklist – for Website Authors
Posted: Sat Apr 05, 2025 4:30 am
Text equivalents: Success criterion WCAG 1.1.1. Non-textual content (Level A)
Provide text equivalents for all non-text content so that the content can be converted to other necessary formats, such as large text, braille, speech, symbols, or simpler language.
All non-textual content presented to the user is provided with a text equivalent that meets the same need , except for the cases listed below.
The WCAG 1.1.1 requirement means that all non-text content presented to the user on a website, such as images, videos, and sounds, must have a text description that tells the user what that content is. The following are examples of how text descriptions can be used on websites: Image text descriptions: Text descriptions for images should describe the subject, content, and meaning of the image. Video text descriptions: Text descriptions for videos should describe the content and meaning of the video. Audio text descriptions: Text descriptions for audio should describe the content and meaning of the sound.
Understanding Non-text Content (Level A)
How to Meet Non-text Content (Level A)
Forms: Success Criterion 2.4.6 Titles and Labels (Level AA)
Titles and labels describe the topic or meaning.
The WCAG 2.4.6 requirement means that websites must have clear country email list and informative titles and names. This is important so that all users, including those who cannot see or hear, can understand the information on the website.
Here are some key WCAG 2.1 form requirements: All form fields must be clearly identifiable. This means that the names of the form fields must be given clearly and informatively. In addition, the form fields must be easily distinguishable from each other. The form fields must be easily accessible. This means that the form fields must be accessible from the keyboard and easy to fill out. Form error messages must be clear and informative. Error messages must be written in a way that users understand what is wrong.
The following are examples of how WCAG 2.1 criteria can be met in web forms: Form field names: Form field names should be informative and describe the content of the field. For example, a form field name could be “First Name”, “Last Name”, and “Email Address”. Form field accessibility: Form fields should be accessible using the keyboard. This can be done, for example, by ensuring that the fields have clear labels and that users can navigate between fields using the keyboard. Form error messages: Error messages should be written in a way that users understand what is wrong. Error messages should not be too general or vague.
Understanding Headings and Labels (Level AA)
How to Meet Headings and Labels (Level AA)
Titles: Success Criterion 1.3.1 Information and Relationships (Level A)
The information, structure , and relationships conveyed in the presentation can be explained programmatically or are available as text.
Provide text equivalents for all non-text content so that the content can be converted to other necessary formats, such as large text, braille, speech, symbols, or simpler language.
All non-textual content presented to the user is provided with a text equivalent that meets the same need , except for the cases listed below.
The WCAG 1.1.1 requirement means that all non-text content presented to the user on a website, such as images, videos, and sounds, must have a text description that tells the user what that content is. The following are examples of how text descriptions can be used on websites: Image text descriptions: Text descriptions for images should describe the subject, content, and meaning of the image. Video text descriptions: Text descriptions for videos should describe the content and meaning of the video. Audio text descriptions: Text descriptions for audio should describe the content and meaning of the sound.
Understanding Non-text Content (Level A)
How to Meet Non-text Content (Level A)
Forms: Success Criterion 2.4.6 Titles and Labels (Level AA)
Titles and labels describe the topic or meaning.
The WCAG 2.4.6 requirement means that websites must have clear country email list and informative titles and names. This is important so that all users, including those who cannot see or hear, can understand the information on the website.
Here are some key WCAG 2.1 form requirements: All form fields must be clearly identifiable. This means that the names of the form fields must be given clearly and informatively. In addition, the form fields must be easily distinguishable from each other. The form fields must be easily accessible. This means that the form fields must be accessible from the keyboard and easy to fill out. Form error messages must be clear and informative. Error messages must be written in a way that users understand what is wrong.
The following are examples of how WCAG 2.1 criteria can be met in web forms: Form field names: Form field names should be informative and describe the content of the field. For example, a form field name could be “First Name”, “Last Name”, and “Email Address”. Form field accessibility: Form fields should be accessible using the keyboard. This can be done, for example, by ensuring that the fields have clear labels and that users can navigate between fields using the keyboard. Form error messages: Error messages should be written in a way that users understand what is wrong. Error messages should not be too general or vague.
Understanding Headings and Labels (Level AA)
How to Meet Headings and Labels (Level AA)
Titles: Success Criterion 1.3.1 Information and Relationships (Level A)
The information, structure , and relationships conveyed in the presentation can be explained programmatically or are available as text.