Section 508 - ICT Requirements.pdf
PDF 59 KB Posted
- Attached to
- INTENT TO SOLE SOURCE: UltraArchive Software License Subscription Federal contract opportunity
- Solicitation number
- W911QX21Q0213
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Section 508 - Contract Language Template.docx | DOCX document |
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
ICT Accessibility Requirements Statement per the Revised Section 508 of the Rehabilitation Act
UltraARCHIVE Software Renewal
Department of Defense - Dept of the Army alexander.k.cheatham.ctr@mail.mil
General Exceptions
Electronic Content
UltraARCHIVE Software
Technical Criteria:
E205.1 General - Electronic content shall comply with E205.
Software
UltraARCHIVE Software
Technical Criteria:
E207.1 General - Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5 E207.2 WCAG Conformance - User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).
E207.2.1 Word Substitution - When Applying WCAG to Non-Web Software For non-Web software, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “software” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in software” shall be substituted for the phrase “on a Web page.”
E207.3 Complete Process for Non-Web Software - Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in E207.2.
E501.1 Scope - Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).
E502.1 General - Software shall interoperate with assistive technology and shall conform to 502.
http://section508.gov/ict-accessibility#e205_1_general http://section508.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 http://section508.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 http://section508.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 http://section508.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 http://section508.gov/ict-accessibility#e501_1_scope http://section508.gov/ict-accessibility#e502_1_general
502.2 Documented Accessibility Features - Software with platform features defined in platform documentation as accessibility features shall conform to 502.2.
502.2.2 No Disruption of Accessibility Features - Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.
502.3.1 Object Information - The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.
502.3.2 Modification of Object Information - States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.
502.3.3 Row, Column, and Headers - If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.
502.3.4 - Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.
502.3.5 Modification of Values - Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.
502.3.6 Label Relationships - Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.
502.3.7 Hierarchical Relationships - Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.
502.3.8 Text - The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.
502.3.9 Modification of Text - Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.
502.3.10 List of Action -
502.3.11 Actions on Objects - Applications shall allow assistive technology to programmatically execute available actions on objects.
502.3.12 Focus Cursor - Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.
502.3.13 Modification of Focus Cursor - Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.
502.3.14 Event Notification - Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.
503.1 General - Applications shall conform to 503.
503.2 User Preferences - Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.
Functional Performance Criteria:
301.1 Scope - The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.
302.1 Without Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.
302.2 With Limited Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.
302.3 Without Perception of Color - Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.
302.4 Without Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.
302.5 With Limited Hearing - Where an audible mode of operation is provided, ICT shall http://section508.gov/ict-accessibility#e502_2__e502_2_2__e502_3_1 http://section508.gov/ict-accessibility#e502_2__e502_2_2__e502_3_1 http://section508.gov/ict-accessibility#e502_2__e502_2_2__e502_3_1 http://section508.gov/ict-accessibility#502_3_2__502_3_3__502_3_4__502_3_5 http://section508.gov/ict-accessibility#502_3_2__502_3_3__502_3_4__502_3_5 http://section508.gov/ict-accessibility#502_3_2__502_3_3__502_3_4__502_3_5 http://section508.gov/ict-accessibility#502_3_2__502_3_3__502_3_4__502_3_5 http://section508.gov/ict-accessibility#502_3_6__502_3_7__502_3_8__502_3_9__502_3_10 http://section508.gov/ict-accessibility#502_3_6__502_3_7__502_3_8__502_3_9__502_3_10 http://section508.gov/ict-accessibility#502_3_6__502_3_7__502_3_8__502_3_9__502_3_10 http://section508.gov/ict-accessibility#502_3_6__502_3_7__502_3_8__502_3_9__502_3_10 http://section508.gov/ict-accessibility#502_3_6__502_3_7__502_3_8__502_3_9__502_3_10 http://section508.gov/ict-accessibility#502_3_11__502_3_12__502_3_13__502_3_14 http://section508.gov/ict-accessibility#502_3_11__502_3_12__502_3_13__502_3_14 http://section508.gov/ict-accessibility#502_3_11__502_3_12__502_3_13__502_3_14 http://section508.gov/ict-accessibility#502_3_11__502_3_12__502_3_13__502_3_14 http://section508.gov/ict-accessibility#503_1__503_2 http://section508.gov/ict-accessibility#503_1__503_2 https://buyaccessible.gov/ict-accessibility#e301_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 provide at least one mode of operation that enables users to make use of limited hearing.
302.6 Without Speech - Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.
302.7 With Limited Manipulation - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.
302.8 With Limited Reach and Strength - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.
302.9 With Limited Language, Cognitive, and Learning Abilities - ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.
Instructions
If you'd like to start a new procurement, please click here to restart the form.
The Accessibility Requirements Report should be incorporated into the solicitation requirements document (SOO, SOW, PWS, etc.). Please go to the Revised 508 Standards Roadmap (https://section508.gov/manage/program-roadmap) for further information on the procurement process.
https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://buyaccessible.gov/ict-accessibility#e302_1 https://section508.gov/art/accessibility-requirements-tool https://section508.gov/manage/program-roadmap
File details come from the government source that posted it. Updated .