WCAG 1.1 and 1.2 guidelines cover images, videos, maps, data visualizations and podcasts. Therefore, designers, content creators and marketing folks will benefit a lot from this session.
This session was recorded. Use the video player below to view it.
You will need the documents below in order to complete this part of the audit.
Our social media guide can help you figure out whether your alt-text description is good for your image. The video guide will help you decide whether your captions or audio descriptions are sufficient or not.
This training is aimed at teaching you how to audit your agency’s websites for accessibility. It is broken up into seven instructional sessions followed by a few review sessions. We recommend that you spend two to three weeks digesting and practicing the content from each session.
In each session, the WCAG 2.1 Level AA standards are used to measure the accessibility of websites. There are about Five to ten WCAG criterion covered in each session.
For each criterion, we will teach you:
For this session and many others, you will need to use a screen reader to test webpages. It is recommended to spend some time learning the basics of using one before starting your audit.
Screen readers are an assistive technology that is typically used by people who are blind. It reads aloud the contents of the screen to blind users. Screen reader users also navigate using the keyboard instead of the mouse.
For Windows-based screen readers, the arrow keys along with the tab key are the most basic ways to navigate a webpage. The arrow keys read line by line or letter by letter. The tab key navigates to interactable elements such as links, buttons etc.
For Voiceover users on Mac, navigating webpages is accomplished by holding the control and option keys and pressing one of the arrow keys. For example, to have voice over read the next item, press control + Option + right arrow. Voiceover users can also use tab to navigate to interactable elements.
There are other ways of moving around a webpage that improve the speed of screen reader users. There are keyboard shortcuts for each screen reader that allow a user to navigate to the next link, heading, button, edit field, table, image etc. These shortcuts will help us test different elements for accessibility. Below is a table with these common shortcuts.
Command | JAWS | NVDA | Voiceover (Mac) | Comments |
---|---|---|---|---|
Shortcut to turn on screen reader |
Control, Alt and J |
Control, Alt and N |
Command and F5 or press fingerprint button 3 times on touch bar |
For Jaws and NVDA the shortcuts need to be set in properties |
Navigate up and down |
Up or Down Arrows |
Up or Down Arrows |
Up and down arrows or Control, Option and Left or Right Arrows |
|
Navigate by character |
Left or Right Arrows |
Left or Right Arrows |
Control, Option, Shift and Left or Right Arrows |
|
Go to next image |
G |
G |
Control, Option, Command and G or G with Quick Nav |
Add Shift to move to previous image |
Go to next heading |
H |
H |
Control, Option, Command and H or H with Quick Nav |
Add Shift to go to previous heading |
Go to next table |
T |
T |
Control, Option, Command and T or T with Quick Nav |
Add Shift to go to previous table |
Go to next form field |
F |
F |
F, B or C with quick nav |
Add Shift to go to previous form field. For Voiceover F goes to next Text field, B goes to next button and C goes to next checkbox with Quick Nav on |
Go to next region |
R |
D |
Custom command |
Add Shift to go to previous region |
Keyboard access |
All links, buttons and form fields should be navigable using Tab |
All links, buttons and form fields should be navigable using Tab |
All links, buttons and form fields should be navigable using Tab |
For Mac, some Safari settings might need to be adjusted for this to work |
Image based content needs to have a text alternative. For images, alt-text is commonly used to add a description. For maps, a text list indexed by headings that can be filtered is sufficient. For data visualizations, html table alternatives are accessible. Captchas need an audio alternative.
On all pages with images, maps or data visualizations.
Understanding Success Criterion 1.1.1
Jaws and NVDA: Press the letter “G” on your keyboard to navigate to each image and hear it’s alt-text.
Voiceover: Turn on Quick nav by pressing the right and left arrow keys together. Then press G. (Note: Single key navigation must be turned on in the Voiceover Utility)
WAVE, Axe and other automated tools: Insert the URL of the page and find out how many errors you get that mention “missing alt-text.”
If a page has images and a map/data visualization/captcha, get the average for the images, create a score for the map/data visualization/captcha then do the following. Add the two numbers together and divide by 2 for a number between 1 and 0. If there are multiple maps/data visualizations/captchas, use one score to evaluate all of them.
Videos with no sound should have audio description or a transcript of an audio description. Audio only content such as podcasts should have transcripts.
On pages with video only or audio only content. Video only means videos with no sound. Audio only would be podcasts, music etc.
Understanding Success Criterion 1.2.1
If there are any videos with no sound, there should be a text description of the video. If there is audio content such as a podcast, each episode needs to have a text transcript.
Transcripts for audio content
Captions are provided for pre-recorded videos.
On pages with video content. Video content means a video that has audio as well. Videos without sound are covered in 1.2.1.
Understanding Success Criterion 1.2.2
If there are any videos on the page, watch them and review the captions.
Audio descriptions or text transcripts are provided for pre-recorded video content
On pages with video content. Video content means videos with sound. Videos without sound are covered in success criterion 1.2.1.
Understanding Success Criterion 1.2.3
If there are any videos embedded into the page, are they described using text? This would be a paragraph above or below the video player that informs viewers of what they are seeing in the video.
Captions for live video or audio content.
On pages with live video content. Live video content means videos with audio that is streaming live. Videos that do not have audio are covered in success criterion 1.2.1.
Understanding Success Criterion 1.2.4
Watch any live videos that are streamed on this page.
Audio descriptions are provided for pre-recorded video content. Different from 1.2.3 because there is no option to have a text transcript.
Sometimes a video is not audio described but the dialogue in the video is accidentally descriptive. Videos that are descriptive but do not have official audio description may receive a score of up to .5.
On pages with video content. Video content means videos with audio . Videos that do not have audio are covered by success criterion 1.2.1.
Understanding Success Criterion 1.2.5
Watch the video. It should be audio described or link to an audio described version.
Start testing and fill in WCAG 1.1.1 through 1.2.5 by the next session. For assistance, email Walei at wsabry@doitt.nyc.gov.