Section_508_Revised_ART_Checklist.xlsx
XLSX spreadsheet 84 KB Posted
- Attached to
- NIH IRP Project, Program, and Portfolio (P3) Support Services Federal contract opportunity
- Solicitation number
- 75N98022R00003
About this file
This federal solicitation seeks proposals for NIH IRP Project, Program, and Portfolio Support Services. The selected contractor shall provide non-R&D, specialized project, program, and portfolio services to support NIH's Intramural Research Program across three task areas: enterprise management system support; project, program and portfolio solutions; and transition planning. The contractor must be highly qualified and experienced in these domains. Questions are due by the date specified in the solicitation, which shall be answered only in writing by the Contracting Officer or Contract Specialist. Offerors must meet applicable Women-Owned Small Business or Economically Disadvantaged Women-Owned Small Business status requirements. The agency is the Department of Health and Human Services National Institutes of Health Office of Logistics and Acquisition Operations.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| RFP_75N98022R00003_ Questions_Responses.pdf | ||
| 75N98022R00003_SF33v1.pdf | ||
| P3_Price_Schedule.xlsx | XLSX spreadsheet | |
| 75N98022R00003_P3_SF33.pdf | ||
| Att1_P3_Labor_Categories_Table.pdf | ||
| RFP_Proposal_ Intent_ Response_Form.pdf | ||
| Att2_P3_ Labor_Hours_Table.pdf | ||
| RepresentationsandCertifications.pdf | ||
| RFP_Question_Template.xlsx | XLSX spreadsheet | |
| P3_Assignment_of_Work_Products.docx | DOCX document | |
| P3_Statement_of_Work.pdf |
Show all 11
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Table-of-Contents HHS Checklist Template and Refs (Table of Contents -ToC)
| This file contains several worksheets in an effort to consolidate related resources into a single file for easier access. |
| Below is a list of the worksheets/tabs as they appear in the file. |
| 1 | Table of Contents |
| 2 | HHS HTML 508 Compliance Checklist |
| 3 | HHS General Office Document File 508 Compliance Checklist |
| 4 | HHS PDF File 508 Checklist |
| 5 | Audio/Video (AV) 508 Checklist |
| 6 | Email 508 Checklist |
| 7 | VPAT Requirements – WCAG A & AA Summary |
| 8 | VPAT Requirements – Revised 508 Report Requirements |
HTML-ChkList
| HHS HTML 508 Compliance Checklist |
| https://www.hhs.gov/web/section-508/making-files-accessible/checklist/html/index.html |
| This checklist is based on the new WCAG 2.0 requirements that will be in effect starting on January 18, 2018. The checklist below, a series of tables, is based on the content of the Web page/Site. If ‘No’ is answered to any item, then the Site is not 508 compliant. |
| "AppInfo" must be completed |
| Date Application Tested: |
| URL Link: Tested: |
| Page Title: |
| Application Name: |
| Page number, name or identifier: |
| PageURL/ location: |
| Names of accessibility tester(s): |
| Operating platform |
(e.g. Windows; OS, Linux, etc.):
| RDMS (e.g. SQL Server, Oracle) |
| Browser version(s): |
| Types of Development/Software Platform (e.g. Drupal, Java, Flash, Bootstrap, Font Awesome, etc.) |
| Note: Recommend completing a separate checklist for each web page, a representive sample of pages should be selected which contain varied levels of complexity should be selected. |
| The best practice recommendation is to test web application pages with multiple browsers. |
| Summary of 11 Compliance Categories by Testing Technique | Revised 508 Standards & Guidelines | |||
| 1 | Section A: General Visual Checks | 100 | Application and Administration | Appendix A: Part 1194 – Section 508 Rehabilitation Act |
Appendix B: Section 255
| 2 | Section B: General Code Inspection | 200 | Scoping Requirements | Both Appendix A & B apply to: Application and Scoping Requirements | |||
| 3 | Section C: Keyboard Navigation | https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-b | |||||
| 4 | Section D: Sites containing Color | Comparable 'Original 508 Standards' | |||||
| 5 | Section E: Sites containing Links | 1194.31 | *300 | Functional Performance Requirements | Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements | ||
| 6 | Section F: Sites containing Images | 1194.23, | |||||
| 24, 25 & 26 | 400 | Hardware Standards | |||||
| 7 | Section G: Sites containing Audio/Video | 1194.21 | |||||
| 1194.22 | 500 | Software Standards | |||||
| 8 | Section H: Sites containing Tables | 1194.41 | *600 | Support Services & Documentation Standards | |||
| 9 | Section i: Sites containing semantic structure | WCAG (IBR) | 700 | Referenced Standards (IBR - incorporated by reference) | |||
| 10 | Section J: Sites containing Forms | *Always applicable | |||||
| 11 | Section K: Sites containing common elements / dynamic content | ||||||
| Note: The 300, 500 & 600's from the Revised 508 Standards are incorporated into the checklist |
**508 Test Methods Utilized (testing recommendations refer to Sample Test Cases - ref by keywords & requirements worksheet and utilize the comparable original 508 standards referenced above). Define which test tool or processes were utilized to validate compliance level (e.g. keyboard, AXE, WAT, WAVE, code review/validation, visual inspection, Color Analyzer, Screen reader, etc.)
| 1 | Section A: General Visual Checks | ||||
| ID | Requirements | Traceability back to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 1 | A1 | Is the site free from content that flashes more than 3 times per second? | A | WCAG 2.0 Success Criterion 2.3.1 |
| 2 | A2 | Can all text be resized up to 200% without degrading quality/understandability? | AA | WCAG 2.0 Success Criterion 1.4.4 |
| 3 | A3 | Is there more than one way to locate a web page? (Site Search, Site Map, etc.) | AA | WCAG 2.0 Success Criterion 2.4.5 |
| 4 | A4 | Is the order of navigational elements consistent across the site? | AA | WCAG 2.0 Success Criterion 3.2.3 |
| 5 | A5 | Can auto updating, moving, blinking, and scrolling content be paused or adjusted? | A | WCAG 2.0 Success Criterion 2.2.2 |
| 6 | A6 | Are all site controlled documents (PDF, Word, etc.) fully accessible or have a conforming alternate version? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 7 | A7 | If there are any time limits on interacting with content, can they be turned off, adjusted, or extended? | A | WCAG 2.0 Success Criterion 2.2.1 |
| 8 | A8 | Are operational instructions that rely on sensory characteristics avoided? (Ex. Click the square, blue button to continue) | A | WCAG 2.0 Success Criterion 1.3.3 |
| 9 | A9 | Is the site free from pages that re-direct after a timeout? | A | WCAG 2.0 Success Criterion 2.2.1 |
| 10 | A10 | Are elements with the same functionality consistently identified across pages? | AA | WCAG 2.0 Success Criterion 3.2.4 |
| 11 | A11 | Do headings accurately describe the content they visually define? | AA | WCAG 2.0 Success Criterion 2.4.6 |
| 2 | Section B: General Code Inspection | ||||
| ID | Requirements | Traceability back to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 12 | B1 | Is the default language of the page set? | A | WCAG 2.0 Success Criterion 3.1.1 |
| 13 | B2 | Has the language been properly set for foreign words or phrases? | AA | WCAG 2.0 Success Criterion 3.1.2 |
| 14 | B3 | Is the page free from major errors defined in W3 Failure #70 when run against an HTML validator? | A | WCAG 2.0 Success Criterion 4.1.1 |
| 15 | B4 | Are duplicate ID values on the same page avoided? | A | WCAG 2.0 Success Criterion 4.1.1 |
| 16 | B5 | With styles disabled, is the reading order of the content logical? | A | WCAG 2.0 Success Criterion 1.3.2 |
| 17 | B6 | Do all frames have a title attribute that accurately defines the content? | A | WCAG 2.0 Success Criterion 4.1.2 |
| 18 | B7 | Does the page have a title attribute that accurately defines the content? | A | WCAG 2.0 Success Criterion 2.4.2 |
| 19 | B8 | Does content intended to be accessible by assistive technology refrain from using display: none or aria-hidden=true? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 20 | B9 | If ARIA is present, does the ARIA coding both meet ARIA specifications and give an accurate representation of the content? | A | WCAG 2.0 Success Criterion 4.1.2 |
| 21 | B10 | Are Fieldset tags only used for form fields? (Not to make a box around a piece of content)? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 3 | Section C: Keyboard Navigation | ||||
| ID | Requirements | Traceability back to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 22 | C1 | Are all elements that can be operated by a mouse also able to be operated by keyboard? | A | WCAG 2.0 Success Criterion 2.1.1 |
| 23 | C2 | When tabbing through the page, do all elements have a clear visual indication that they have focus? | AA | WCAG 2.0 Success Criterion 2.4.7 |
| 24 | C3 | When tabbing the page, are keyboard traps avoided? | A | WCAG 2.0 Success Criterion 2.1.2 |
| 25 | C4 | Is the tab order of the page logical? | A | WCAG 2.0 Success Criterion 2.4.3 |
| 26 | C5 | When tabbing through the page, are changes of context avoided when an element receives focus? | A | WCAG 2.0 Success Criterion 3.2.1 |
27 C6 Is there a method to bypass blocks of repetitive content (such as navigation)? A WCAG 2.0 Success Criterion 2.4.1
| 4 | Section D: Sites containing Color | ||||
| ID | Requirements | Traceability back to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 28 | D1 | Is information conveyed by methods other than color alone? | A | WCAG 2.0 Success Criterion 1.4.1 |
| 29 | D2 | Does all text (with the exception of logos) have a contrast ratio of 4.5:1 or greater no matter the font size? | AA | WCAG 2.0 Success Criterion 1.4.3 (Size stipulation not considered by HHS) |
| 5 | Section E: Sites containing Links | ||||
| ID | Requirements | Traceability to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 30 | E1 | Are links distinguished by a method other than color? | A | WCAG 2.0 Success Criterion 1.4.1 |
| 31 | E2 | Can all link text be understood out of context? If not, does generic link have sufficient content? | A | WCAG 2.0 Success Criterion 2.4.4, |
| 32 | E3 | Do linked images either have an empty alt tag and link text, or no link text and appropriate alt text? | A | WCAG 2.0 Success Criterion 1.1.1 |
| 6 | Section F: Sites containing Images | ||||
| ID | Requirements | Traceability to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 33 | F1 | Do all images have an alt attribute? | A | WCAG 2.0 Success Criterion 1.1.1 |
| 34 | F2 | Do all images conveying information have alt text that provides the same level of understanding a visual user would gain? | A | WCAG 2.0 Success Criterion 1.1.1 |
| 35 | F3 | Do all decorative images have an empty alt tag (alt=””) or are included via the CSS? | A | WCAG 2.0 Success Criterion 1.1.1 |
| 36 | F4 | Is the CSS free from any images conveying information that do not have a text alternative? | A | WCAG 2.0 Success Criterion 1.1.1 |
| 37 | F5 | Do complex images have an alternate accessible means of understanding? | A | WCAG 2.0 Success Criterion 1.1.1 |
| 38 | F6 | Is the page free from images of text? (Picture of an informational table, screenshot of text from another source, etc.) | AA | WCAG 2.0 Success Criterion 1.4.5 |
| 7 | Section G: Sites containing Audio/Video | ||||
| ID | Requirements | Traceability to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 39 | G1 | Do all audio only or video only (video without any sound) files have an accurate transcript? | A | WCAG 2.0 Success Criterion 1.2.1 |
| 40 | G2 | Do all videos have accurate and synchronized captions? | A | WCAG 2.0 Success Criterion 1.2.2 |
| 41 | G3 | 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 | AA | WCAG 2.0 Success Criterion 1.2.5 |
| 42 | G4 | Is there a way to turn off sound that automatically plays for more than 3 seconds? | A | WCAG 2.0 Success Criterion 1.4.2 |
| 8 | Section H: Sites containing Tables | ||||
| ID | Requirements | Traceability to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 43 | H1 | If layout tables are used, is data table markup (Summary, TH, ID, Headers) avoided? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 44 | H2 | If layout tables are used, is the intended order of the content intact? | A | WCAG 2.0 Success Criterion 1.3.2 |
| 45 | H3 | Are data tables implemented with data table coding? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 46 | H4 | Do all header cells utilize the TH tag? Do all data cells utilize the TD tag? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 47 | H5 | Do all Header cells contain text? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 48 | H6 | Do data tables with 1 set of both column and row headers appropriately use scope to associate to data cells? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 49 | H7 | Do data tables with more than 1 set of column and/or row headers appropriately use id/headers to associate to data cells? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 9 | Section i: Sites containing semantic structure | ||||
| ID | Requirements | Traceability to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 50 | i1 | Are all visual bulleted and numbered lists correctly coded with HTML list tags? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 51 | i2 | Are visual headings correctly coded with HTML heading tags? (<h1>, <h2>, etc.) | A | WCAG 2.0 Success Criterion 1.3.1 |
| 52 | i3 | Do heading tags follow a logical hierarchical progression? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 53 | i4 | Are heading tags only used on text that defines a section of content? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 54 | i5 | Is emphasized or special text correctly coded with HTML heading tags? (<em>, <strong>, <sup>, etc.) | A | WCAG 2.0 Success Criterion 1.3.1 |
| 10 | Section J: Sites containing Forms | ||||
| ID | Requirements | Traceability to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 55 | J1 | Are all form fields correctly coded with descriptive and accurate labels? | A | WCAG 2.0 Success Criterion 3.3.2 |
| 56 | J2 | Do grouped form fields have correctly coded fieldset and legend tags? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 57 | J3 | Are form validation errors clear and accurately identified in text? | A | WCAG 2.0 Success Criterion 3.3.1 |
| 58 | J4 | Is the form free of making a selection when attempting to navigate the options? (only submits when user makes a selection) | A | WCAG 2.0 Success Criterion 3.2.2 |
| 59 | J5 | Are Orphan label tags avoided? | A | WCAG 2.0 Success Criterion 1.3.1 |
| 11 | Section K: Sites containing common elements / dynamic content | ||||
| ID | Requirements | Traceability to 508 | **Test Methods Utilized | Result |
(Pass, Fail, Accommodation In-progress)
| 60 | K1 | Is the role of an element (e.g. Button) properly defined , accurate, and communicated to assistive technology? | A | WCAG 2.0 Success Criterion 4.1.2 |
| 61 | K2 | Is the state of an element (expanded or collapsed) properly defined , accurate, and communicated to assistive technology? | A | WCAG 2.0 Success Criterion 4.1.2 |
| 62 | K3 | Are modal dialogues able to be used with keyboard alone and assistive technology? Focus management, hiding underlying content, etc. | Multiple WCAG 2.0 Criterion | |
| 63 | K4 | Are carousels able to be used with keyboard alone and assistive technology? Ability to pause, navigate to individual items, etc. | Multiple WCAG 2.0 Criterion | |
| 64 | K5 | Are menus able to be used with keyboard alone and assistive technology? Ability to expand and navigate subitems | Multiple WCAG 2.0 Criterion | |
| 65 | K6 | Are expandable/collapsible accordion elements able to be used with keyboard alone and assistive technology? Ability to expand and navigate subitems | Multiple WCAG 2.0 Criterion | |
| 66 | K7 | Are Tabbed Interfaces able to be used with keyboard alone and assistive technology? Ability to tell active tab and navigate to appropriate content | Multiple WCAG 2.0 Criterion | |
| 67 | K8 | Are CAPTCHA interfaces able to be used with keyboard alone and assistive technology? Ability to tell the clue and successfully enter and authenticate | Multiple WCAG 2.0 Criterion | |
| 68 | K9 | If a user selection creates an unexpected change on the page, was the change communicated to the user? | A | WCAG 2.0 Success Criterion 3.2.2 |
| Total requirement for web applications | ||||
| **508 Test Methods Utilized (testing recommendations refer to Sample Test Cases - ref by keywords & requirements worksheet and utilize the comparable original 508 standards referenced above). Define which test tool or processes were utilized to validate compliance level (e.g. keyboard, AXE, WAT, WAVE, code review/validation, visual inspection, Color Analyzer, Screen reader, etc.) |
| Missing | ||
| A | 1.2.4 | Captions (Live) |
| A | 3.3.3 | Error suggestion |
| A | 3.3.4 | Error Prevention |
&"-,Bold"File name:&"-,Regular" &F
&P of &N http://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-does-not-violate.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-required-behaviors.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-consistent-functionality.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-descriptive.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-other-lang-id.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-parses.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-parses.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-sequence.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-trapping.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-receive-focus.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-mult-loc.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-without-color.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-without-color.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-consistent-locations.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-presentation.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-av-only-alt.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-captions.htmlhttps://www.hhs.gov/web/section-508/making-files-accessible/hhs-guidance-audio-description.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-audio-desc-only.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-dis-audio.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-sequence.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-pause.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-identified.htmlhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.htmlhttps://www.w3.org/TR/wai-aria-practices-1.1/http://www.w3.org/TR/WCAG20/https://www.w3.org/WAI/tutorials/carousels/http://www.w3.org/TR/WCAG20/https://www.w3.org/WAI/tutorials/menus/http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.htmlhttp://www.w3.org/TR/WCAG20/https://www.w3.org/TR/wai-aria-practices-1.1/http://www.w3.org/TR/WCAG20/https://www.w3.org/TR/wai-aria-practices-1.1/http://www.w3.org/TR/WCAG20/https://www.w3.org/WAI/GL/wiki/Captcha_Alternatives_and_thoughtshttp://www.w3.org/TR/WCAG20/http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.htmlhttps://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelineshttps://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelineshttps://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-required-behaviors.htmlhttps://www.hhs.gov/web/section-508/making-files-accessible/checklist/html/index.htmlhttps://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-understanding.html MSOfficeDocs-ChkList
| ASPA/DCD General Office Document File 508 Compliance Checklist |
| https://www.hhs.gov/web/section-508/making-files-accessible/checklist/aspa-dcd-general-office-document-file-508-checklist/index.html |
| Section A: All Office Documents | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| A1 | Is the title in the Document Properties filled out properly? | WCAG 2.0 Success criterion 2.4.2 |
A2 Is the language of the document properly set? WCAG 2.0 Success criterion 3.1.1
A3 Did the document fully pass the Accessibility Checker? WCAG 2.0 Success Criterion 4.1.1
A4 Is the document free from content that flashes more than 3 times per second? WCAG 2.0 Success Criterion 2.3.1
A5 Is the document free from content carried over from Office such as comments, track changes, etc? WCAG 2.0 Success Criterion 1.3.1
| A6 | Is the order of the content accurate and logical? | WCAG 2.0 Success Criterion 1.3.2 |
| A7 | Can text be resized and considered readable when magnified to 200%? | WCAG 2.0 Success Criterion 1.4.4 |
A8 Is the document free from electronically fillable forms? WCAG 2.0 Success Criterion 3.3.2
| Section B: All Office Documents containing Color | |||
| ID | Requirement | Traceability back to 508 | Testing Methods & Results |
| B1 | Does any information conveyed with color have a non-color method for understanding? | WCAG 2.0 Success Criterion 1.4.1 |
B2 Does all text (with the exception of logos) have a contrast ratio of 4.5:1 or greater no matter the font size? WCAG 2.0 Success Criterion 1.4.3
(Size stipulation not considered by HHS)
| Section C: All Office Documents containing Links | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| C1 | Are links distinguished by a method other than color? | WCAG 2.0 Success Criterion 1.4.1 |
C2 Can all link text be understood out of context? (If generic text is used, see next item) WCAG 2.0 Success Criterion 2.4.4
C3 Does generic link text have sufficient context? WCAG 2.0 Success Criterion 2.4.4
| Section D: All Office Documents containing Images | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| D1 | Do all informational images have alt text that provides the same level of understanding a visual user would gain? | WCAG 2.0 Success Criterion 1.1.1 |
D2 Do all decorative images have “ “ in the alt text field? WCAG 2.0 Success Criterion 1.1.1
D3 Have all multilayered objects been flattened into one image and does that image use one alternative text description for the image? WCAG 2.0 Success Criterion 1.1.1
D4 Do complex informational images have an alternate accessible means of understanding? WCAG 2.0 Success Criterion 1.1.1
D5 Is the document free from any content that should not be included as an image? (Picture of an informational table, text) WCAG 2.0 Success Criterion 1.4.5
| Section E: All Office Documents containing Tables | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| E1 | Was the table created with the built in table styles? | WCAG 2.0 Success Criterion 1.3.1 |
E2 Does the table structure in the tag tree match the visual table layout? WCAG 2.0 Success Criterion 1.3.1
E3 Do all Header cells contain text? WCAG 2.0 Success Criterion 1.3.1
E4 Is the document free from table styles for any content that is not a data table? WCAG 2.0 Success Criterion 1.3.1
E5 Is the document free from data tables with merged cells, both column and row header cells, and multiple column or row cells? WCAG 2.0 Success Criterion 1.3.1
| Section F: All Office Documents containing Lists | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| F1 | Are all visual lists created with the built in list styles? | WCAG 2.0 Success Criterion 1.3.1 |
F2 Are multiple lists in the same document properly grouped / separated? WCAG 2.0 Success Criterion 1.3.1
| Section G: All Office Documents containing Headings | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| G1 | Is text intended to act as a visual heading styled with the built in heading tags (H1 through H6)? | WCAG 2.0 Success Criterion 1.3.1 |
G2 Do heading styles follow a logical hierarchical progression? (Do not skip) WCAG 2.0 Success Criterion 1.3.1
G3 Are heading styles refrained from being used on text that has been visually altered purely for decoration? WCAG 2.0 Success Criterion 1.3.1
G4 Does the Heading text accurately describe the sectional content? WCAG 2.0 Success Criterion 2.4.6
| Section H: All Office Documents containing other common elements | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| H1 | Is the table of contents created with the built in office styles? (TOC, TOC Item) | WCAG 2.0 Success Criterion 1.3.1 |
H2 Are citations and footnotes/endnotes created with the built in office styles? WCAG 2.0 Success Criterion 1.3.1
H3 Is the language properly set for foreign words or phrases? WCAG 2.0 Success Criterion 3.1.2
H4 Is information in the header, footer, watermark, speaker notes, etc. available in the main body of the document? WCAG 2.0 Success Criterion 1.3.1 https://tracker.cloud.hhs.gov/issues/?jql=project%20%3D%20ST%20AND%20resolution%20%3D%20Unresolved%20AND%20issuetype%20%3D%20Accommodation%20ORDER%20BY%20priority%20DESChttps://www.hhs.gov/web/section-508/making-files-accessible/checklist/aspa-dcd-general-office-document-file-508-checklist/index.html PDF-Checklist
| PDF File 508 Checklist (WCAG 2.0 Refresh) | |||
| https://www.hhs.gov/web/section-508/making-files-accessible/checklist/pdf/index.html | |||
| Section A: All PDFs | |||
| These checks should be performed on all PDFs no matter of what is present in the actual content: | |||
| ID | Requirements | Traceability to 508 | Testing Methods & Results |
| A1 | Is the PDF tagged? | WCAG 2.0 Success Criterion 1.3.1 |
A2 Is the Document Title filled out in the Document Properties? WCAG 2.0 Success criterion 2.4.2
A3 Is the correct language of the document set? WCAG 2.0 Success criterion 3.1.1
A4 Did the PDF fully pass the Adobe Accessibility Checker? WCAG 2.0 Success Criterion 4.1.1
A5 Is the document free from content that flashes more than 3 times per second? WCAG 2.0 Success Criterion 2.3.1.
A6 Are accurate bookmarks provided for documents greater than 9 pages? WCAG 2.0 Success Criterion 2.4.5.
A7 Is the document free from review-related content carried over from Office or other editing tools such as comments, track changes, embedded Speaker Notes? WCAG 2.0 Success Criterion 1.3.1
A8 Is the order in the tag structure accurate and logical? Do the tags match the order they should be read in? WCAG 2.0 Success Criterion 1.3.2.
A9 Is all informational content contained in the tag structure? WCAG 2.0 Success Criterion 1.3.1
A10 Are all non-standard tags appropriately mapped to standard Adobe tags? WCAG 2.0 Success Criterion 4.1.2
A11 Is all the text within the tags correctly formatted? (Free from line breaks and split words) Learn more about finding and fixing backend text errors. WCAG 2.0 Success Criterion 4.1.1
A12 Do paragraph tags accurately represent visual paragraphs? WCAG 2.0 Success Criterion 1.3.1
| A13 | Can text be resized and considered readable when magnified to 200%? | WCAG 2.0 Success Criterion 1.4.4 |
| . |
| Section B: PDFs containing Color | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| B1 | Is information conveyed by methods other than color alone? | WCAG 2.0 Success Criterion 1.4.1 | |
| . | |||
| B2 | Does all text (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) |
| Section C: PDFs containing Links | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| C1 | Are links tagged correctly in the tag structure? (Contain visual link text and link OBJR within the Link tag) | WCAG 2.0 Success Criterion 1.3.1 | |
| . | |||
| C2 | Are links distinguished by a method other than color? | WCAG 2.0 Success Criterion 1.4.1, |
| C3 | Can all link text be understood out of context? If not, does generic link have sufficient context? | WCAG 2.0 Success Criterion 2.4.4 |
| , |
| Section D: PDFs containing Images | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| D1 | Are all images conveying information tagged as figures and included in the tag structure? | WCAG 2.0 Success Criterion 1.3.1 | |
| . | |||
| D2 | Do all images conveying information have alt text that provides the same level of understanding a visual user would gain? | WCAG 2.0 Success Criterion 1.1.1 | |
| . | |||
| D3 | Are all decorative images tagged as artifact/background? | WCAG 2.0 Success Criterion 1.1.1 | |
| . | |||
| D4 | Do complex images have an alternate accessible means of understanding? | WCAG 2.0 Success Criterion 1.1.1 | |
| . | |||
| D5 | Is the document free from images of text? (Picture of an informational table, screenshot of text from another source, etc.) | WCAG 2.0 Success Criterion 1.4.5 |
| D6 | Are groups of related images tagged in a way assistive technology users would understand? | WCAG 2.0 Success Criterion 1.1.1 |
| . |
| Section E: PDFs containing Tables | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| E1 | Does the document use table tags only for data tables? | WCAG 2.0 Success Criterion 1.3.1. |
E2 Does the table structure in the tag tree match the visual table layout? WCAG 2.0 Success Criterion 1.3.1.
E3 Are all header cells tagged with the TH tag? Are all data cells tagged with the TD tag? WCAG 2.0 Success Criterion 1.3.1.
E4 Do all Header cells contain text? WCAG 2.0 Success Criterion 1.3.1.
E5 Are merged cells correctly spanned with Colspan and/or Rowspan? WCAG 2.0 Success Criterion 1.3.1.
E6 Do data tables with 1 set of both column and row headers appropriately use scope to associate to data cells? WCAG 2.0 Success Criterion 1.3.1.
E7 Do data tables with more than 1 set of column and/or row headers appropriately use id/headers to associate to data cells? WCAG 2.0 Success Criterion 1.3.1.
| Section F: PDFs containing Lists | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| F1 | Are all visual lists tagged correctly with the List, List Item (LI), and LBody tags? | WCAG 2.0 Success Criterion 1.3.1. |
F2 Does the number of items in the tag structure match the number of items in the visual list? WCAG 2.0 Success Criterion 1.3.1.
F3 Are nested lists appropriately nested in the tag structure? WCAG 2.0 Success Criterion 1.3.1.
| Section G: PDFs containing Headings | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| G1 | Is text intended to act as a visual heading tagged with the heading tags (H1 through H6)? | WCAG 2.0 Success Criterion 1.3.1. |
G2 Do heading tags follow a logical hierarchical progression? (Do not skip heading levels) WCAG 2.0 Success Criterion 1.3.1.
G3 Are heading tags used only on text that defines a section of content? WCAG 2.0 Success Criterion 1.3.1.
G4 Does the Heading text accurately describe the sectional content? WCAG 2.0 Success Criterion 2.4.6
| Section H: PDFs containing Forms | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| H1 | Are all form fields correctly tagged? | WCAG 2.0 Success Criterion 3.3.2 |
H2 Do all form fields contain understandable labels and tooltips? WCAG 2.0 Success Criterion 3.3.2
H3 Do tooltips contain all formatting requirements that will be automatically flagged as an error? WCAG 2.0 Success Criterion 3.3.2
H4 Are required fields programmatically set? WCAG 2.0 Success Criterion 3.3.1
H5 Is the tab order of the form fields logical? WCAG 2.0 Success Criterion 1.3.2.
| Section i: PDFs containing other common elements | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| i1 | Is any nonstandard text (glyph) tagged in an accessible manner? | WCAG 2.0 Success Criterion 1.1.1 | |
| . | |||
| i2 | Was OCR successfully performed on a scanned image document? | WCAG 2.0 Success Criterion 1.4.5. |
i3 Was the language appropriately set for all foreign words or phrases? WCAG 2.0 Success Criterion 3.1.2 i4 Is the table of contents tagged with appropriate tags? (TOC, TOC Item (TOCI)) WCAG 2.0 Success Criterion 1.3.1.
i5 Are all internal links/TOC entries functioning correctly (if linked)? WCAG 2.0 Success Criterion 2.4.5.
i6 Are citations and footnotes/endnotes tagged with appropriate tags? (Reference, Note) WCAG 2.0 Success Criterion 1.3.1.
https://www.hhs.gov/web/section-508/making-files-accessible/finding-and-fixing-backend-errors.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.html Audio & Video
| Audio/Video (AV) 508 Checklist |
| https://www.hhs.gov/web/section-508/making-files-accessible/checklist/av-508-checklist/index.html |
| Section A: Audio Files | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| A1 | Do all audio only files have an accurate transcript? | WCAG 2.0 Success Criterion 1.2.1 |
A2 Is there a way to turn off sound that automatically plays for more than 3 seconds? WCAG 2.0 Success Criterion 1.4.2
| Section B: Video Files | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| B1 | Do video only files have an accurate transcript? | WCAG 2.0 Success Criterion 1.2.1 |
B2 Is the video free from content that flashes more than 3 times per second? WCAG 2.0 Success Criterion 2.3.1.
B3 Can the video be paused or stopped? WCAG 2.0 Success Criterion 2.2.2
| B4 | Does any information conveyed with color have a non-color method for understanding? | WCAG 2.0 Success Criterion 1.4.1 |
| . | ||
| 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? | WCAG 2.0 Success Criterion 1.2.2. |
| 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? | WCAG 2.0 Success Criterion 1.2.5 |
| Section C: AV Players –YouTube/HHS Live | |||
| ID | Requirement | Traceability to 508 | Testing Methods & Results |
| C1 | Are operational instructions that rely on sensory characteristcs avoided? (Ex. Click the square, blue button to continue) | WCAG 2.0 Success Criterion 1.3.3 |
C2 Are all elements that can be operated by a mouse also able to be operated by keyboard? WCAG 2.0 Success Criterion 2.1.1.
C3 When tabbing through, do all elements have a clear visual indication that they have focus? WCAG 2.0 Success Criterion 2.4.7
C4 When tabbing through, is a keyboard trap on a single element or group of elements always avoided? WCAG 2.0 Success Criterion 2.1.2.
C5 Is the tab order logical? WCAG 2.0 Success Criterion 2.4.3
| C6 | When tabbing through, are unexpected changes | WCAG 2.0 Success Criterion 3.2.1 |
| avoided when an element receives focus? | ||
| C7 | Do all frames have a title attribute that accurately defines the content? | WCAG 2.0 Success Criterion 4.1.2 |
C8 If Aria is present, does the Aria coding both meet Aria specifications and give an accurate representation of the content? WCAG 2.0 Success Criterion 4.1.2
C9 Is the role of an element (eg Play Button) properly defined, accurate, and communicated to assistive technology? WCAG 2.0 Success Criterion 4.1.2
C10 Is the state of an element (eg Play or Pause) properly defined , accurate, and communicated to assistive technology? WCAG 2.0 Success Criterion 4.1.2 https://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/web/section-508/making-files-accessible/hhs-guidance-audio-description.htmlhttps://www.hhs.gov/disclaimer.htmlhttps://www.hhs.gov/web/section-508/making-files-accessible/checklist/av-508-checklist/index.html Email-ChkList
| Email 508 Checklist | |||
| https://www.hhs.gov/web/section-508/making-files-accessible/checklist/email-508-checklist/index.html | |||
| Section A: All Email | |||
| ID | Item | Traceability to 508 | Testing Methods & Results |
| A1 | Is the email free from content that flashes more than 3 times per second? | WCAG 2.0 Success Criterion 2.3.1 |
| A2 | Is the order of the content accurate and logical? | WCAG 2.0 Success Criterion 1.3.2 |
| A3 | Can text be resized and considered readable when magnified to 200%? | WCAG 2.0 Success Criterion 1.4.4 |
| Seciton B: Email containing Color | |||
| ID | Item | Traceability to 508 | Testing Methods & Results |
| B1 | Does any information conveyed with color have a non-color method for understanding? | WCAG 2.0 Success Criterion 1.4.1 |
B2 Does all text (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)
| Section: C : Email containing Links | |||
| ID | Item | Traceability to 508 | Testing Methods & Results |
| C1 | Are links distinguished by a method other than color? | WCAG 2.0 Success Criterion 1.4.1 |
C2 Can all link text be understood out of context? If not, does generic link have sufficient content? WCAG 2.0 Success Criterion 2.4.4
| Section D: Email containing Images | |||
| ID | Item | Traceability to 508 | Testing Methods & Results |
| D1 | Do all images conveying information have alt text that provides the same level of understanding a visual user would gain? | WCAG 2.0 Success Criterion 1.1.1 |
D2 Do all decorative images have “ “ in the alt text field? WCAG 2.0 Success Criterion 1.1.1
D3 Have all multilayered objects been flattened into one image and does that image use one alternative text description for the image? WCAG 2.0 Success Criterion 1.1.1
D4 Do complex informational images have an alternate accessible means of understanding e.g text only equivalent? WCAG 2.0 Success Criterion 1.1.1
D5 Is the email free from any content that should not be included as an image? (Picture of an informational table, text) WCAG 2.0 Success Criterion 1.4.5
| Section E: Email containing Tables | |||
| ID | Item | Traceability to 508 | Testing Methods & Results |
| E1 | Is the email free from table styles for any content that is not a data table? Is the email free from table styles for any content that is not a data table? Is the email free from table styles for any content that is not a data table? | WCAG 2.0 Success Criterion 1.3.1 |
E2 Was the table created with the built in table styles? WCAG 2.0 Success Criterion 1.3.1
E3 Does the table structure in the tag tree match the visual table layout? WCAG 2.0 Success Criterion 1.3.1
E4 Do all Header cells contain text? WCAG 2.0 Success Criterion 1.3.1
E5 Is the email free from data tables with merged cells, both column and row header cells, and multiple column or row cells? WCAG 2.0 Success Criterion 1.3.1
| Section F: Email containing Lists | |||
| ID | Item | Traceability to 508 | Testing Methods & Results |
| F1 | Are all visual lists created with the built in list styles? | WCAG 2.0 Success Criterion 1.3.1 |
F2 Are multiple lists in the same email properly grouped / separated? WCAG 2.0 Success Criterion 1.3.1
| Section G: Email containing visual Headings | |||
| ID | Item | Traceability to 508 | Testing Methods & Results |
| G1 | Is text intended to act as a visual heading styled with the built in heading tags (H1 through H6)? | WCAG 2.0 Success Criterion 1.3.1 |
G2 Do heading styles follow a logical hierarchical progression? (Do not skip) WCAG 2.0 Success Criterion 1.3.1
G3 Are heading styles refrained from being used on text that has been visually altered purely for decoration? WCAG 2.0 Success Criterion 1.3.1
G4 Does the Heading text accurately describe the sectional content? WCAG 2.0 Success Criterion 2.4.6
| Section H: Email containing other common elements | |||
| ID | Item | Traceability to 508 | Testing Methods & Results |
| H1 | Is the language properly set for foreign words or phrases? | WCAG 2.0 Success Criterion 3.1.2 |
H2 Are all attachments 508 compliant? Multiple https://tracker.cloud.hhs.gov/issues/?jql=project%20%3D%20ST%20AND%20resolution%20%3D%20Unresolved%20AND%20issuetype%20%3D%20Accommodation%20ORDER%20BY%20priority%20DESChttps://www.hhs.gov/web/section-508/making-files-accessible/checklist/email-508-checklist/index.html VPAT-1 of 2_WCAG
| 2017 Section 508 Report |
| Part 1 of 2 ( Part 2 of 2 - Revised Section 508 Standards) |
| Total 38 "A" & "AA" Guidelines |
| Derived from the Voluntary Product Accessibility Template® (VPAT®) Version 2.1 - March 2018 (refer to link for latest version 2.3 released December 2018; no additional requirements modifications were merely symantec) |
| https://www.itic.org/policy/accessibility/vpat |
| Web Content Accessibility Guidelines (WCAG) 2.0 |
| http://www.w3.org/TR/WCAG20/ |
| ☐ 1.1.1 Non-text Content |
| ☐ 1.2.1 Audio-only and Video-only (Prerecorded) |
| ☐ 1.2.2 Captions (Prerecorded) |
| ☐ 1.2.3 Audio Descriptions or Media Alternative (Prerecorded) |
| ☐ 1.3.1 Info and Relationships |
| ☐ 1.3.2 Meaningful Sequence |
| ☐ 1.3.3 Sensory Characteristics |
| ☐ 1.4.1 Use of Color |
| ☐ 1.4.2 Audio Control |
| ☐ 2.1.1 Keyboard |
| ☐ 2.1.2 No Keyboard Trap |
| ☐ 2.2.1 Timing Adjustable |
| ☐ 2.2.2 Pause, Stop, Hide |
| ☐ 2.3.1 Three Flashes or Below Threshold |
| ☐ 2.4.1 Bypass Blocks (not required for non-web documents and software) |
| ☐ 2.4.2 Page Titled |
| ☐ 2.4.3 Focus Order |
| ☐ 2.4.4 Link Purpose (In Context) |
| ☐ 3.1.1 Language of Page |
| ☐ 3.2.1 On Focus |
| ☐ 3.2.2 On Input |
| ☐ 3.3.1 Error Identification |
| ☐ 3.3.2 Labels or Instructions |
| ☐ 4.1.1 Parsing |
| ☐ 4.1.2 Name, Role, Value |
| Total 25 "A" Guidelines |
| WCAG Level AA Requirements |
| ☐ 1.2.4 Captions (Live) |
| ☐ 1.2.5 Audio Description (Prerecorded) |
| ☐ 1.4.3 Contrast (Minimum) |
| ☐ 1.4.4 Resize Text |
| ☐ 1.4.5 Images of Text |
| ☐ 2.4.5 Multiple Ways (not required for non-web documents and software) |
| ☐ 2.4.6 Headings and Labels |
| ☐ 2.4.7 Focus Visible |
| ☐ 3.1.2 Language of Parts |
| ☐ 3.2.3 Consistent Navigation (not required for non-web documents and software) |
| ☐ 3.2.4 Consistent Identification (not required for non-web documents and software) |
| ☐ 3.3.3 Error Suggestion |
| ☐ 3.3.4 Error Prevention (Legal, Financial, Data) |
| Total 13 "AA" Guidelines |
http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-audio-desc.htmlhttps://www.itic.org/policy/accessibility/vpathttp://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/http://www.w3.org/TR/WCAG20/ VPAT- 2 of 2_R508
| 2017 Section 508 Report | ||
| Part 2 of 2 ( Part 1 of 2 - WCAG 2.0 section) | Derived from the Voluntary Product Accessibility Template® (VPAT®) Version 2.1 - March 2018 (refer to link for latest version 2.3 released December 2018; no additional requirements modifications were merely symantec) | https://www.itic.org/policy/accessibility/vpat |
| Chapter 3: Functional Performance Criteria (FPC) | |||
| Notes: | |||
| Criteria | Conformance Level | Remarks and Explanations | |
| 302.1 Without Vision | |||
| 302.2 With Limited Vision | |||
| 302.3 Without Perception of Color | |||
| 302.4 Without Hearing | |||
| 302.5 With Limited Hearing | 9 | ||
| 302.6 Without Speech | |||
| 302.7 With Limited Manipulation | |||
| 302.8 With Limited Reach and Strength | |||
| 302.9 With Limited Language, Cognitive, and Learning Abilities | |||
| Chapter 4: Hardware | |||
| Notes: | |||
| Criteria | Conformance Level | Remarks and Explanations | |
| 402 Closed Functionality | Heading cell – no response required | Heading cell – no response required | |
| 402.1 General | Heading cell – no response required | Heading cell – no response required | |
| 402.2 Speech-Output Enabled | Heading cell – no response required | Heading cell – no response required | |
| 402.2.1 Information Displayed On-Screen | |||
| 402.2.2 Transactional Outputs | 5 | ||
| 402.2.3 Speech Delivery Type and Coordination | |||
| 402.2.4 User Control | |||
| 402.2.5 Braille Instructions | |||
| 402.3 Volume | Heading cell – no response required | Heading cell – no response required | |
| 402.3.1 Private Listening | |||
| 402.3.2 Non-private Listening | 4 | ||
| 402.4 Characters on Display Screens | |||
| 402.5 Characters on Variable Message Signs | |||
| 403 Biometrics | Heading cell – no response required | Heading cell – no response required | |
| 403.1 General | |||
| 404 Preservation of Information Provided for Accessibility | Heading cell – no response required | Heading cell – no response required | |
| 404.1 General | |||
| 405 Privacy | Heading cell – no response required | Heading cell – no response required | |
| 405.1 General | 5 | ||
| 406 Standard Connections | Heading cell – no response required | Heading cell – no response required | |
| 406.1 General | |||
| 407 Operable Parts | Heading cell – no response required | Heading cell – no response required | |
| 407.2 Contrast | |||
| 407.3 Input Controls | Heading cell – no response required | Heading cell – no response required | |
| 407.3.1 Tactilely Discernible | |||
| 407.3.2 Alphabetic Keys | |||
| 407.3.3 Numeric Keys | |||
| 407.4 Key Repeat | 7 | ||
| 407.5 Timed Response | |||
| 407.6 Operation | |||
| 407.7 Tickets, Fare Cards, and Keycards | |||
| 407.8 Reach Height and Depth | Heading cell – no response required | Heading cell – no response required | |
| 407.8.1 Vertical Reference Plane | |||
| 407.8.1.1 Vertical Plane for Side Reach | |||
| 407.8.1.2 Vertical Plane for Forward Reach | |||
| 407.8.2 Side Reach | |||
| 407.8.2.1 Unobstructed Side Reach | |||
| 407.8.2.2 Obstructed Side Reach | 11 | ||
| 407.8.3 Forward Reach | |||
| 407.8.3.1 Unobstructed Forward Reach | |||
| 407.8.3.2 Obstructed Forward Reach | |||
| 407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach | |||
| 407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach | |||
| 408 Display Screens | Heading cell – no response required | Heading cell – no response required | |
| 408.2 Visibility | |||
| 408.3 Flashing | 2 | ||
| 409 Status Indicators | Heading cell – no response required | Heading cell – no response required | |
| 409.1 General | |||
| 410 Color Coding | Heading cell – no response required | Heading cell – no response required | |
| 410.1 General | 3 | ||
| 411 Audible Signals | Heading cell – no response required | Heading cell – no response required | |
| 411.1 General | |||
| 412 ICT with Two-Way Voice Communication | Heading cell – no response required | Heading cell – no response required | |
| 412.2 Volume Gain | Heading cell – no response required | Heading cell – no response required | |
| 412.2.1 Volume Gain for Wireline Telephones | |||
| 412.2.2 Volume Gain for Non-Wireline ICT | 2 | ||
| 412.3 Interference Reduction and Magnetic Coupling | Heading cell – no response required | Heading cell – no response required | |
| 412.3.1 Wireless Handsets | |||
| 412.3.2 Wireline Handsets | |||
| 412.4 Digital Encoding of Speech | |||
| 412.5 Real-Time Text Functionality | Reserved for future | Reserved for future | 5 |
| 412.6 Caller ID | |||
| 412.7 Video Communication | |||
| 413 Closed Caption Processing Technologies | Heading cell – no response required | Heading cell – no response required | |
| 413.1.1 Decoding and Display of Closed Captions | |||
| 413.1.2 Pass-Through of Closed Caption Data | 2 | ||
| 414 Audio Description Processing Technologies | Heading cell – no response required | Heading cell – no response required | |
| 414.1.1 Digital Television Tuners | |||
| 414.1.2 Other ICT | 2 | ||
| 415 User Controls for Captions and Audio Descriptions | Heading cell – no response required | Heading cell – no response required | |
| 415.1.1 Caption Controls | |||
| 415.1.2 Audio Description Controls | 2 | ||
| Chapter 5: Software | |||
| Notes: | |||
| Criteria | Conformance Level | Remarks and Explanations | |
| 501.1 Scope – Incorporation of WCAG 2.0 AA | See WCAG 2.0 section | See information in WCAG section | |
| 502 Interoperability with Assistive Technology | Heading cell – no response required | Heading cell – no response required | |
| 502.2.1 User Control of Accessibility Features | |||
| 502.2.2 No Disruption of Accessibility Features | 2 | ||
| 502.3 Accessibility Services | Heading cell – no response required | Heading cell – no response required | |
| 502.3.1 Object Information | |||
| 502.3.2 Modification of Object Information | |||
| 502.3.3 Row, Column, and Headers | |||
| 502.3.4 Values | |||
| 502.3.5 Modification of Values | |||
| 502.3.6 Label Relationships | |||
| 502.3.7 Hierarchical Relationships | |||
| 502.3.8 Text | 15 | ||
| 502.3.9 Modification of Text | |||
| 502.3.10 List of Actions | |||
| 502.3.11 Actions on Objects | |||
| 502.3.12 Focus Cursor | |||
| 502.3.13 Modification of Focus Cursor | |||
| 502.3.14 Event Notification | |||
| 502.4 Platform Accessibility Features | |||
| 503 Applications | Heading cell – no response required | Heading cell – no response required | |
| 503.2 User Preferences | |||
| 503.3 Alternative User Interfaces | 2 | ||
| 503.4 User Controls for Captions and Audio Description | Heading cell – no response required | Heading cell – no response required | |
| 503.4.1 Caption Controls | |||
| 503.4.2 Audio Description Controls | 2 | ||
| 504 Authoring Tools | Heading cell – no response required | Heading cell – no response required | |
| 504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) | See WCAG 2.0 section | See information in WCAG section | |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | |||
| 504.2.2 PDF Export | |||
| 504.3 Prompts | 4 | ||
| 504.4 Templates | |||
| Chapter 6: Support Documentation and Services | |||
| Notes: | |||
| Criteria | Conformance Level | Remarks and Explanations | |
| 601.1 Scope | Heading cell – no response required | Heading cell – no response required | |
| 602 Support Documentation | Heading cell – no response required | Heading cell – no response required | |
| 602.2 Accessibility and Compatibility Features | |||
| 602.3 Electronic Support Documentation | See WCAG 2.0 section | See information in WCAG section | |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | 3 | ||
| 603 Support Services | Heading cell – no response required | Heading cell – no response required |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .