APPENDIX I - WCAG SuccessCriteriaCkl.docx

DOCX document 18 KB Posted

Attached to
VA Enterprise Learning Management Solution (ELMS)
Solicitation number
36C10B24R0004
Issued by

About this file

This document appears to be an Appendix I - WCAG Success Criteria Checklist related to a federal contract opportunity. It outlines various Web Content Accessibility Guidelines (WCAG) success criteria, including requirements for non-text content, information and relationships, sensory characteristics, use of color, images of text, keyboard functionality, focus visibility, error prevention, and name/role/value of user interface components. The related federal contract opportunity is for a VA Enterprise Learning Management Solution (ELMS), solicitation number 36C10B24R0004. The solicitation is a Request for Proposal, with a proposal due date as noted on the Standard Form 1449. The contract will be awarded using NAICS code 541519 with a $34M business size standard. The Performance Work Statement describes the requirements for the items to be acquired, and the Basis for Award provision outlines the evaluation criteria.

View the file

Other files

File Type Posted
Questions and Answers Amendment 0013.docx DOCX document
36C10B24R0004 Amendment 0013.docx DOCX document
36C10B24R0004 Amendment 0012.docx DOCX document
36C10B24R0004 Amendment 0011.docx DOCX document
Questions and Answers Amendment 0011.docx DOCX document
36C10B24R0004 0010 SOL Extension Posted.pdf PDF
36C10B24R0004 0009 Posted.pdf PDF
36C10B24R0004 Amendment 0008 Posted.docx DOCX document
Questions and Answers Amendment 0008 Posted.docx DOCX document
36C10B24R0004 Amendment 0007 Extension.pdf PDF
36C10B24R0004 Amendment 0006 Extension.docx DOCX document
36C10B24R0004 Amendment 0005.docx DOCX document
Question and Answers Amendment 0005.docx DOCX document
36C10B24R0004 0004 Sol Extension.pdf PDF
36C10B24R0004 Amendment 0003 - Posted.docx DOCX document
36C10B24R0004 ELMS - Amendment 00002 - Posted.docx DOCX document
36C10B24R0004 Amendment 0001_Posted.docx DOCX document
APPENDIX F - Past Performance Questionnaire.docx DOCX document
APPENDIX J - VPAT EXAMPLE.docx DOCX document
36C10B24R0004 ELMS - Posted to SAM.gov.docx DOCX document
APPENDIX G - TASK DEMONSTRATION.docx DOCX document
Show all 21

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

APPENDIX I – WCAG SUCCESS CRITERIA CHECKLIST

REFERENCE #
SEVERITY LEVEL
WCAG SUCCUESS CRITERIA
YES/NO/NOT PRESENT
WCAG 1.1.1
CRITICAL
Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A). Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.) Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.) Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content. Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content. CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities. Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.

• Do all non-decorative graphics have a textual equivalent that expresses the meaning of the element?

• Do all buttons, checkboxes, and other form fields have a label or text alternative?

• Do all tables have a text equivalent describing the purpose of the table?

• Do all other non-text objects (graphs, charts, audio players, etc) have a textual equivalent?

WCAG 1.3.1
CRITICAL
Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A).

• If there is a visible structure that is necessary to understand the data on the page is that structure available to the screen reader?

WCAG 1.3.3
CRITICAL
Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A) • Is information portrayed by color, shape, size visual location, orientation or sound also portrayed in some other form?
WCAG 1.4.1
CRITICAL
Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A) • Is any information portrayed by color also portrayed in some other manner?
WCAG 1.4.5
CRITICAL
Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA) Customizable: The image of text can be visually customized to the user's requirements Essential: A particular presentation of text is essential to the information being conveyed • Is there valid justification for all uses of text in an image?
WCAG 2.1.1
CRITICAL
2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A) • When tabbing through the application can all content and functionality be accessed? If not, can the actionable item be reached via a hot key? • If hot keys are used, do the hot keys have instructions to guide the user on how to use them? Do the instructions work with screen reader software?
WCAG 2.1.2
CRITICAL
No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A) • If the user can move the cursor focus into a control or section of a page, can the user move the cursor focus away from that control or section? • If the user cannot tab away from the control or section, is there a documented method for the user to ‘un-trap’ the keyboard?
WCAG 2.2.2
CRITICAL
Pause, Stop, Hide: For moving, blinking, scrolling, or auto- updating information, all of the following are true: (Level A) Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. • If the text movement is not essential to understanding the content, can the user pause, stop or hide the movement? • If the text is auto updating, can the user pause stop or hide the auto update or control the frequency of the update?
WCAG 2.3.1
CRITICAL
Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A) • Does any component on the screen flash for more than three times per second?
WCAG 2.4.7
CRITICAL
Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) • Does each user interface element have a visible focus?
WCAG 3.2.1
CRITICAL
On Focus: When any component receives focus, it does not initiate a change of context. (Level A) • Is the context of the document changed when a component receives focus?
WCAG 3.3.1
CRITICAL
If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) • When an error occurs while entering data into a component is the error message placed in text on the form so the AT can read the error?? • When an error occurs when submitting a form, is the generated error message placed in text when the form is reloaded so AT can read the error? Note: It is not required but we highly encourage focus be placed on the error message when the form is reloaded.
WCAG 3.3.2
CRITICAL
Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) • Are required fields clearly identified to the assistive technology? • Are examples provided of expected data formats to ensure information is entered correctly? • Are field labels in close proximity to the associated fields? • Is the label spoken by screen readers when the field receives focus? • Is each label on the page unique?
WCAG 3.3.4
CRITICAL
Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA) 1. Reversible: Submissions are reversible. 2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. 3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. • If the page is submitting information that causes a legal or financial transaction, or modifies or deletes user controllable data, or submits user test responses is at least one of the following true? o The submission is reversible, o Data entered by the user is checked for input errors and the user is provided an opportunity to correct them or o A mechanism is available for reviewing, confirming and correcting information before finalizing the submission.
WCAG 4.1.2
CRITICAL
Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A) • Is the name, role and value of each user interface component programmatically determinable?

File details come from the government source that posted it. Updated .