# Checklist: buying ICT that conforms to the Revised Section 508 Standards, and documenting exceptions

Thirteen steps for federal program, acquisition and accessibility staff: deciding what is covered, which E202 exceptions apply and who signs them, what to ask vendors for, and how to check conformance before and after award.

Checklist · Government · Economics & Procurement. Published November 14, 2026. Last reviewed November 14, 2026.

## What the law and the standards ask

Section 508 of the Rehabilitation Act, 29 U.S.C. 794d, requires each federal department or agency, including the Postal Service, that develops, procures, maintains or uses electronic and information technology to ensure, unless an undue burden would be imposed, that employees and members of the public with disabilities have access to and use of information and data comparable to that of people without disabilities. Where meeting the standards would be an undue burden, the agency must provide an alternative means of access [1]. Section 1194.1 sets out the Section 508 standards in appendices A, C and D to 36 CFR part 1194; the Revised 508 Standards are appendix A with appendix C, and appendix D republishes the original 2000 standards [2]. The Board issued them in a final rule on January 18, 2017 [3], and the standards treat ICT procured, maintained or used on or before January 18, 2018 as existing ICT [2]. Electronic content and software must conform to WCAG 2.0 Level A and AA, with listed exceptions for non-web documents and software [2].

## Using the steps

The steps follow the order of an acquisition: scope and exceptions, requirements, market research and solicitation, evaluation and award, then contract performance. They cite the scoping sections of appendix A (E201 to E208) in the eCFR text current to November 12, 2026 [2], the statute [1] and the guidance on Section508.gov [4] [5], which is guidance rather than regulation. Where a step is our suggestion, it says so. The owner under each step is a typical role, not one the standards name, unless the step says the standards name it. This page explains the standards; it is not legal advice.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Confirm that the purchase includes ICT the standards cover, and list each ICT item in it.** (Program manager, with the agency Section 508 program manager) E201.1 applies the standards to ICT that agencies procure, develop, maintain or use, and E103.4 defines ICT broadly, from computers and kiosks to software and electronic content [2]. Section508.gov’s first acquisition step is to determine whether the ICT is subject to Section 508 [4].
2. **Identify the needs of users with disabilities who will use the ICT, employees and public alike.** (Program manager) E203.1 requires all functionality to be accessible and usable, directly or through assistive technology, with comparable access for employees and members of the public, and E203.2 requires agencies to identify how users with disabilities will perform the functions and how the ICT will be set up to support them [2].
3. **Check each general exception and document any that applies, with who in the agency may grant it.** (Agency Section 508 program manager) E202.2 to E202.5 cover legacy ICT that met the earlier standards and has not been altered on or after January 18, 2018, national security systems, ICT a contractor acquires incidental to a contract, and status indicators and operable parts in spaces used only by service personnel [2]. Section508.gov says exceptions should be documented and justified during requirements development, and that each agency should define who is authorized to grant one [4].
4. **Where conformance would be an undue burden or a fundamental alteration, have the responsible official document the reasons and plan an alternative means.** (Responsible agency official (named in the standards)) E202.6.1 bases undue burden on significant difficulty or expense, considering the resources available to the program or component. E202.6.2 requires the responsible agency official to document in writing why and to what extent conformance would be an undue burden or fundamental alteration, and E202.6.3 requires an alternative means that meets identified needs [2]. The statute sets an alternative means duty where meeting the standards would impose an undue burden [1].
5. **Work out which technical requirements apply to each item: hardware, software, electronic content, and support documentation and services.** (Accessibility specialist, with the contracting officer’s representative) E205.4 and E207.2 require WCAG 2.0 Level A and AA for electronic content and software, E206.1 applies chapter 4 to hardware, E208.1 applies chapter 6 to support documentation and services, and E204.1 applies the functional performance criteria where the technical requirements do not address a function [2]. Section508.gov offers its Accessibility Requirements Tool or the Standards Applicability Checklist and chart for this [4] [5].
6. **Include internal content in scope where the standards require it, as well as public-facing content.** (Content owners, with the Section 508 program manager) E205.2 covers all public-facing content. E205.3 also covers non-public content that is official business in nine categories, including emergency notifications, decisions on administrative claims, policy announcements, notices of benefits or personnel actions, surveys, templates and forms, training materials and intranet content designed as a web page, with an exception for records NARA keeps that are not public facing [2].
7. **Do market research for accessible products, collect existing Accessibility Conformance Reports, and record the results.** (Contracting officer, with the program office) Section508.gov’s market research step suggests looking for existing Accessibility Conformance Reports, often based on the VPAT template, asking colleagues and contracting staff, trying to find at least two possible solutions and documenting the research [4]. This research also supports any later best meets decision [2].
8. **Put the accessibility requirements, clauses and acceptance criteria into the solicitation, and for development work, say how, by whom and when accessibility testing will be done.** (Contracting officer) Section508.gov’s third step covers solicitation language, quality assurance surveillance plans and acceptance criteria, and says contracts for ICT development services should specify the accessibility requirements of the deliverables and the testing expectations [4].
9. **Tell offerors what accessibility information to submit: for each standard product, a complete Accessibility Conformance Report, a Supplemental Accessibility Report and an ACR Issue Detail Supplement; for each customized item, a report on how it will meet the requirements and the evaluation methods the offeror will use to validate conformance.** (Contracting officer) Section508.gov advises agencies to require these items from offerors, and lists further items, such as demonstrations and remediation plans, as recommended rather than required [5]. This is guidance on what to ask for, not regulation.
10. **Evaluate proposals against the stated requirements, and test before award or before deploying custom-built deliverables.** (Accessibility tester, with the evaluation panel) Section508.gov’s fifth step asks evaluators to validate vendor claims, review the conformance reports and conduct accessibility testing before awarding a contract or deploying custom-developed deliverables [4].
11. **If no conforming product is commercially available, buy the one that best meets the standards, and have the responsible official document the market research and the gaps.** (Responsible agency official (named in the standards), with the contracting officer) E202.7 requires procuring the ICT that best meets the standards consistent with business needs. E202.7.1 requires written documentation of the non-availability of conforming ICT, including the market research done and which provisions cannot be met, and the basis for the best meets decision. E202.7.2 requires an alternative means for users with disabilities [2].
12. **During performance, re-test new versions and updates against the contract terms, and treat altered legacy components as needing to meet the Revised Standards.** (Contracting officer’s representative) Section508.gov’s sixth step says ICT must remain accessible throughout the period of performance and that each new version should be re-tested [4]. E202.2 limits the legacy exception to components not altered on or after January 18, 2018 [2].
13. **Keep exception and best meets records where the office that handles accessibility complaints can find them.** (Agency Section 508 program manager, with the civil rights office) The statute lets any individual with a disability file a complaint with the agency, handled under the agency’s section 504 complaint procedures, with the remedies, procedures and rights of 29 U.S.C. 794a(a)(2) and 794a(b) available [1]. Filing the records with the complaint office is our suggestion.

## Sources

1. U.S. Government Publishing Office (GovInfo). 29 U.S.C. 794d, Electronic and information technology (United States Code, 2024 edition). <https://www.govinfo.gov/content/pkg/USCODE-2024-title29/html/USCODE-2024-title29-chap16-subchapV-sec794d.htm> Checked November 14, 2026.
2. Electronic Code of Federal Regulations. 36 CFR part 1194, Information and Communication Technology Standards and Guidelines, appendix A (eCFR current to November 12, 2026; checked November 14, 2026). <https://www.ecfr.gov/current/title-36/part-1194> Checked November 14, 2026.
3. U.S. Access Board. Revised 508 Standards and 255 Guidelines (checked November 14, 2026). <https://www.access-board.gov/ict/> Checked November 14, 2026.
4. Section508.gov, General Services Administration. Buy Accessible Products and Services (checked November 14, 2026). <https://www.section508.gov/buy/> Checked November 14, 2026.
5. Section508.gov, General Services Administration. Request Accessibility Information from Vendors & Contractors (checked November 14, 2026). <https://www.section508.gov/buy/request-accessibility-information/> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-section-508-ict-procurement-conformance-e202-exceptions>
Publisher: Moraph Insights
