Attachment 26 - Section 508 Requirements.pdf

PDF 125 KB Posted

Attached to
Web-based Jury Management System (JMS)
Solicitation number
USCA24R0030
Issued by

About this file

This document is the Accessibility Requirements Tool ICT Accessibility Requirements Statement per Section 508 of the Rehabilitation Act for a Web-Based Jury Management System (JMS) federal contract opportunity.

The document outlines the accessibility requirements for the ICT (Information and Communication Technology) components of the web-based JMS solution. It specifies that the electronic content, user interface components, and support documentation must conform to the Level A and Level AA Success Criteria and Conformance Requirements of the Web Content Accessibility Guidelines (WCAG) 2.0. The requirements cover areas such as providing alternative text, captions, audio descriptions, keyboard accessibility, and compatibility with assistive technologies. The contract opportunity is being solicited by the Administrative Office of the U.S. Courts (AO) for an Indefinite Delivery, Indefinite Quantity (IDIQ) contract, with responses due by 12:00 P.M. ET on May 31, 2024.

View the file

Other files

File Type Posted
USCA24R0030 Amendment 0004.pdf PDF
USCA24R0030 Amendment 0003.pdf PDF
Attachment 8 - Attendance Functions_rev1.pdf PDF
Attachment 24 - Deliverables_rev1.pdf PDF
Attachment 4 Task Order 0001_rev1.pdf PDF
USCA24R0030 Amendment 0002.pdf PDF
Questions and Answers Spreadsheet USCA24R0030 05222024.xlsx XLSX spreadsheet
Amendment 0001 USCA24R0030.pdf PDF
Attachment 19 JIFMS-JMS Web Service Interface Requirements Specifications REVISED.pdf PDF
Attachment 2 - Demonstration Script.pdf PDF
Attachment 3 - Past Performance Questionnaire.pdf PDF
Attachment 14 - General System Functions.pdf PDF
Attachment 18 - Statistical Reporting Functions.pdf PDF
Attachment 19 - JIFMS-JMS Web Service Interface Requirements Specifications.pdf PDF
Attachment 23(c) - Guide to Implementing the Judiciary Information Security Framework JISF.pdf PDF
Attachment 24 - Deliverables.pdf PDF
Attachment 32 - EOC-SOP-SBO-22-105-Knowledge-Management.pdf PDF
Attachment 9 - Scanning Technology Functions.pdf PDF
Attachment 13 - Glossary of Terms.pdf PDF
Attachment 17 - Wheel Deletion Functions.pdf PDF
Attachment 22 - Web-Based JMS Architecture.pdf PDF
Attachment 23(a) - Judiciary Information Security Framework (JISF).pdf PDF
Attachment 25(a) - Nondisclosure Agreement.pdf PDF
Attachment 29 - EOC-NSD-SOP-SBO-22-103-Request-Fulfillment.pdf PDF
Attachment 7 - Panel Functions.pdf PDF
Attachment 31 - EOC-SOP-SBO-22-102-Problem Management.pdf PDF
JMS RFP USCA24R0030 dated 4.29.2024.pdf PDF
Attachment 4 - Task Order 0001.pdf PDF
Attachment 8 - Attendance Functions.pdf PDF
Attachment 11 - Interactive Voice Response System Functions.pdf PDF
Attachment 15 - Customization Functions.pdf PDF
Attachment 16 - Wheel Loading Functions.pdf PDF
Attachment 25(b) - Sensitive Information Nondisclosure Agreement.pdf PDF
Attachment 30 - EOC-SOP-SBO-20-101-Communications.pdf PDF
Attachment 1 - Web-Based JMS Price Tables.xlsx XLSX spreadsheet
Attachment 5 - Web-Based JMS Traceability Matrix.xlsx XLSX spreadsheet
Attachment 6 - Pool Functions.pdf PDF
Attachment 10 - Online Public Access Juror Management Functions.pdf PDF
Attachment 12 - Proximity Technology Functions.pdf PDF
Attachment 20 - Appear Speech Overview.pdf PDF
Attachment 21 - Current Forms Used by District Courts.pdf PDF
Attachment 27 - EOC Service Desk and Support.pdf PDF
Attachment 28 - EOC-NSD-SOP-SBO-24-102-Incident-Management.pdf PDF
Attachment 33 - Root Cause Analysis Template.pdf PDF
Attachment 34 - OCS Bulletin and ERC Templates.pdf PDF
Show all 45

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

Accessibility Requirements Tool

ICT Accessibility Requirements Statement per Section 508 of the Rehabilitation Act

Web-Based JMS

E201.1 Scope ICT that is procured, developed, maintained, or used by agencies shall conform to the Revised 508 Standards.

E205.1 General Electronic content shall comply with E205.

E205.2 Public Facing Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.

E205.3 Agency Official Communication Electronic content that is not public facing shall conform to the accessibility requirements specified in E205.4 when such content constitutes official business and is communicated by an agency through one or more of the following:

● A. An emergency notification;

● B. An initial or final decision adjudicating an administrative claim or proceeding;

● C. An internal or external program or policy announcement;

● D. A notice of benefits, program eligibility, employment opportunity, or personnel action;

● E. A formal acknowledgement of receipt;

● F. A survey questionnaire;

● G. A template or form;

● H. Educational or training materials; or

● I. Intranet content designed as a Web page.

E205.4 Accessibility Standard (WCAG 2.0) - Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG

2.0 (Incorporated by reference, see 702.10.1).

E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

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

Exception from E207.1 General: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to 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).

Exceptions from E207.2 WCAG Conformance:

● Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.

● Non-web software shall not be required to conform to the following four Success Criteria in WCAG 2.0: 2.4.1 Bypass Blocks; 2.4.5 Multiple Ways;

3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.

● Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

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.

E208.1 General Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E301 General

E301.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.

E302 Functional Performance Criteria

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 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.

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.

Exception from E503.2 User Preferences: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

503.3 Alternative User Interfaces. Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

503.4 User Controls for Captions and Audio Description Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

503.4.1 Caption Controls Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

503.4.2 Audio Description Controls. Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

602.1 General.Documentation that supports the use of ICT shall conform to 602.

602.2 Accessibility and Compatibility Features. Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

602.3 Electronic Support Documentation. Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

602.4 Alternate Formats for Non-Electronic Support Documentation. Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

603.1 General. ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

603.2 Information on Accessibility and Compatibility Features. ICT support services shall include information on the accessibility and compatibility features required by 602.2.

603.3 Accommodation of Communication Needs. Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

Accessibility Requirements Tool
ICT Accessibility Requirements Statement per Section 508 of the Rehabilitation Act
Web-Based JMS

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