GSA / GSA/openacr

Documentation of accommodation plans in a Supplemental Accessibility Report (SAR)

Open
#247 0 comments 0 reactions 1 assignee Claimed by @danid123 View on GitHub
discovery documentation
Dominant language
JavaScript
Stars
128
Forks
36
PR merge metrics
No merged PRs in 30d

Description

If there are accessibility barriers in the ICT being considered, agencies are supposed to highlight how they are to accommodate need needs. This might be part of a broader Service Design Blueprint or the Supplemental Accessibility Report (SAR).

The mitigation of Section 508 failures can often be addressed through custom JavaScript or workarounds. Many agencies require mitigation plans for non-conformant technology.

Supplemental Accessibility Report (SAR) are defined in the Buy Accessible Products and Services part of the Section 508.gov site:
https://www.section508.gov/buy/request-accessibility-information/#0

> **Supplemental Accessibility Report (SAR) - A written SAR containing:**
>
> - Description of evaluation methods used to produce the ACR, to demonstrate due diligence in supporting conformance claims;
> - Documentation of features that help achieve accessibility and usability for persons with disabilities;
> - Information on core functions that can’t be used by persons with disabilities;
> - Information on how to configure and install the ICT item to support accessibility; and
> - Information on how the ICT item enables the creation of accessible electronic content that conforms to the Revised 508 Standards, including the range of accessible user interface elements the tool can create. (only required for authoring tools that generate content (documents, reports, videos, multimedia, web content, etc.)

This needs to be validated and then included in https://github.com/GSA/openacr/issues/188#issuecomment-995936675

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.