Audio/Video (AV) 508 Checklist
Purpose
This checklist is based on the new WCAG 2.0 requirements that will be in effect starting on January 18, 2018.
Compliance Checklist
Below are a series of tables based on an AV file. If ‘No’ is answered to any item, then the file is not 508 compliant.
Section A: Audio Files
|
ID |
Requirement |
Traceability back to 508 |
Result |
|---|---|---|---|
|
A1 |
Do all audio only files have an accurate transcript? |
|
|
|
A2 |
Is there a way to turn off sound that automatically plays for more than 3 seconds? |
|
Section B: Video Files
|
ID |
Requirement |
Traceability back to 508 |
Result |
|---|---|---|---|
|
B1 |
Do video only files have an accurate transcript? |
|
|
|
B2 |
Is the video free from content that flashes more than 3 times per second? |
|
|
|
B3 |
Can the video be paused or stopped? |
|
|
|
B4 |
Does any information conveyed with color have a non-color method for understanding? |
|
|
|
B5 |
Does all text which is not narrarated (with the exception of logos) have a contrast ratio of 4.5:1 or greater no matter the size? |
WCAG 2.0 Success Criterion 1.4.3. (Size stipulation not considered by HHS) |
|
|
B6 |
Do all videos have accurate and synchronized captions? |
|
|
|
B7 |
Do captions have a contrast ratio of 4.5:1 or greater no matter the size? |
WCAG 2.0 Success Criterion 1.4.3. (Size stipulation not considered by HHS) |
|
|
B8 |
Are there any informational parts of the video that require audio description to be understood by users with limited sight and if so, is a second version with audio description available? |
|
Section C: AV Players –YouTube/HHS Live
|
ID |
Requirement |
Traceability back to 508 |
Result |
|---|---|---|---|
|
C1 |
Are operational instructions that rely on sensory characteristcs avoided? (Ex. Click the square, blue button to continue) |
|
|
|
C2 |
Are all elements that can be operated by a mouse also able to be operated by keyboard? |
|
|
|
C3 |
When tabbing through, do all elements have a clear visual indication that they have focus? |
|
|
|
C4 |
When tabbing through, is a keyboard trap on a single element or group of elements always avoided? |
|
|
|
C5 |
Is the tab order logical? |
|
|
|
C6 |
When tabbing through, are unexpected changes avoided when an element receives focus? |
|
|
|
C7 |
Do all frames have a title attribute that accurately defines the content? |
|
|
|
C8 |
If Aria is present, does the Aria coding both meet Aria specifications and give an accurate representation of the content? |
|
|
|
C9 |
Is the role of an element (eg Play Button) properly defined, accurate, and communicated to assistive technology? |
|
|
|
C10 |
Is the state of an element (eg Play or Pause) properly defined , accurate, and communicated to assistive technology? |
|
