Web Accessibility Checklist
The Web Accessibility Checklist is a how-to guide for creating accessibility compliant web pages. By following all parts of the checklist as outlined, your department webpages will be better processed by screen readers and other assistive devices.
Each document needs to have a unique and meaningful name that distinguishes it from other documents on the website. For example, “Department Guidelines and Procedures for Student Employees” versus “10817234137.docx”
To add a Title and Description to your webpage.
- Navigate to your page within OmniUpdate.
- Click the light bulb to Check Out the page.
- Click Properties.
- Enter a descriptive and unique page Title.*
- Enter a Description and Keywords.
- Save and Publish.
*Make your page title unique by adding your department or program at the beginning of your page title (e.g., "Financial Aid Frequently Asked Questions | Mt. SAC" is much better than just "Frequently Asked Questions").
Images must have alternative text to provide the purpose of the image for people using screen readers.
To add Alternative Text to Images.
- Navigate to your page in OmniUpdate
- Click the light bulb to Check out the page
- Click the Edit button for regions with images
- Click the image to select it
- Click the Insert/Edit button
- Enter a meaningful Image Description
- Save and Publish
Hyperlinks need to use names that are unique and meaningful that clearly describe where the link will take the viewer. For example, “Annual Report to the Community” versus the generic “click here.”
- Make link names that are unique and meaningful.
- Make sure the words you link clearly describe where the will go.
- Avoid phrases like "Click Here."
- Test links to make sure they go to the desired place.
Make sure audio files have transcriptions and videos have captions.
To test videos for captions:
- Click the CC button to confirm the video is captioned
Webpage users must be able to logically navigate electronic media without the use of a mouse.
- Make sure you can navigate your page using the tab key.
- Make sure the navigation is logical and sequential.
Users must be able to logically navigate forms without the use of a mouse.
Confirm a press of the Tab key takes you to the next logical entry spot on the form
If a form label is clicked, confirm the cursor appears in the form field.
Headings and subheadings must be in logical, top-down, sequential order.
- There should be one Heading 1 at the top of the page followed by Heading 2 and so on.
If possible, avoid the use of tables.
- Do not use tables for formatting only.
- Do not use nested tables or nested columns.
- Keep each table to one page if possible.
Color must not be the sole method for providing information or emphasis. For example, changing the color of text to green or red to designate if the item is active or inactive is not compliant.
- Colors should not be used to communicate information. Instead, use bold or italics to emphasize information.
- If you use color, it must be high contrast (i.e., dark text on light background or vice-versa).
- Check for a color contrast of at least 4/5:1 between the text and background by using a color contrast analyzer such as the WebAIM Color Contrast Checker.