Skip to secondary navigation Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.


Revised 508 Standards Roadmap

Follow the Revised 508 Standards to ensure your information and communication technology (ICT) is accessible and usable by individuals with disabilities. This Roadmap, developed by the U.S. Federal Government Revised 508 Standards Transition Workgroup and GSA, shows how to integrate the standards into an existing 508 Program.

Transition Guide

If your agency already has a mature 508 Program, this guide explains how the revisions to the 508 standards impact you.

How to Incorporate the Standards

If your agency does not have a 508 Program, or you are working to improve your 508 Program, you will need to incorporate the standards into the work you are already doing. Here is step-by-step technical assistance on how the standards fit into program maturity. Each step below is organized to show requirements, tools, best practices, testing guidelines, and relevant sections of the technology accessibility playbook.

Image depicting components of a mature 508 Program

Caption: Image of the components of a mature 508 Program

Build Awareness & Support

Get out and talk about what your agency is doing to implement the standards. Collaborate internally, and help employees understand their rights and responsibilities.

  • Familiarize your agency with the Revised 508 Standards. (Updated)
  • Requirement E203.2 - Work with your HR Office to identify user needs of people with disabilities in your organization. (NEW)
  • Assess the maturity of your agency's 508 program, and take steps to improve accessibility of agency technology.
  • Collaborate with your CIO and other stakeholders to align Section 508 compliance with enterprise efforts to:
    • Adopt accessibility and universal design principles;
    • Innovate to transform how users interact with government;
    • Modernize agency technology; and
    • Develop and support a diverse workforce.
  • Use plain language when describing policies and procedures, so employees understand requirements and expectations.

Best Practices

Revised 508 Standards

Webinars

Section 508 Online Training

Technology Accessibility Playbook

Back to top

Practice Universal Design

Use the technical requirements in the standards to drive adoption of accessible, sustainable technology and universal design principles. Provide an environment that can be accessed, understood and used to the greatest extent possible by all people, regardless of their age, size, ability or disability.

  • Requirement E203.2 - Understand how to address the needs of users with disabilities, including: (NEW)
    • Users with visual, hearing, mobility or cognitive disabilities (including disabled veterans, employees, and constituents); and
    • Older adults who are developing impairments that change the way they use technology.
  • Incorporate user needs as key drivers for technology solutions and modernization efforts.
  • Use the updated technical requirements to drive compatibility with the latest technology and increase sustainability.
  • Leverage user needs to improve understanding of how to implement emerging interaction technologies (e.g., voice, gesture, touch, sight).
  • Engage employees with disabilities to understand how to develop and support a diverse workforce and validate solutions.

Tools

Best Practices

Testing Guidelines

Technology Accessibility Playbook

Back to top

Update Agency Policies

Update your agency policies to address new or updated requirements in the standards. If your agency does not have a 508 policy, you should establish one.

  • Requirements E202 - Revised criteria includes addressing new requirements when claiming exceptions. (Updated)
    • Requirements E202.6.3, E202.7.2 - Address requirements for providing an alternative means, when needed, to support inclusion when claiming Undue Burden, Fundamental Alteration, and Best Meets exceptions.
  • Requirement E203.2 - Identify user needs of people with disabilities. (NEW)
  • Requirement E205 - Revised technical standards for web and non-web based electronic content (updated), including public facing electronic content and agency official communications
    • Requirement E205.3 & E205.4 - Ensure categories of electronic content that is not public-facing are accessible. (NEW)
  • Requirement E206 & Chapter 4 - Hardware. (Updated)
  • Requirement E207 & Chapter 5 - Ensure authoring tools support the creation of accessible content. (NEW)
  • Requirement E208 & Chapter 6 - Support services & documentation. (Updated)
  • Chapter 3 Functional Performance Criteria (if Chapters 4 and 5 do not address one or more ICT functions). (Updated)

Tools

Best Practices

Technology Accessibility Playbook

Back to top

Procure & Develop Accessible Technology

Ensure that the technology you buy and build is designed to be accessible from the start.

  • Communicate to key internal stakeholders the benefits of accessible technology for all users.
  • When conducting acquisition planning, manage accessibility risk by requesting and evaluating accessibility information from vendors prior to selection:
    • Determine the applicability of the standards to each item.
    • Identify how the vendor should provide information you need to perform a 508 technical evaluation;
    • Incorporate Section 508 criteria into the evaluation factors; and
    • Add accessibility provisions, clauses, and acceptance criteria, to ensure accessibility support is provided throughout the life of the contract, and to manage your agency's accessibility risk after award.
  • Validate that technology products and services provide full support for accessibility prior to award selection and, where feasible, prior to deployment for custom developed deliverables.
    • Follow the updated testing guidelines, endorsed by the Federal CIO Council, to validate support for the standards for web, software, and electronic document products and services. (Updated)
  • Ensure existing staff and contractors who are “certified” under the Federal CIO Council Accessibility Community of Practice's Trusted Tester Program update their certifications once program updates are complete.
  • Requirement E202.2 - Review existing contracts to determine whether amendments are needed to clarify how the standards apply. (NEW)
  • Requirement E202.7 - When making award selection decisions, choose products and services that best meet all user needs, including users with disabilities. (Updated)
  • Requirement E203 - When reviewing acquisition and development solutions, prioritize how to address all user needs, including users with disabilities. (E203.2 NEW)
  • When procuring or developing ICT items, determine the applicability of the standards to each item. (NEW)

Tools

Best Practices

Testing Guidelines

Technology Accessibility Playbook

Back to top

Create Accessible Documents

Help employees create accessible documents and content.

  • Communicate to key internal stakeholders the benefits of accessible documents for all users.
  • Use the defined electronic content categories to identify the types of documents used by your agency; begin with those most frequently used.
  • Commit to using authoring tools and document converters that help users create accessible documents. Upgrade existing tools (e.g., Microsoft Office, Adobe Acrobat) to the latest version. Benefits:
    • Built-in features that make it easier to create accessible documents;
    • May support agency mandates to transition to the cloud;
    • May protect against security breaches; and
    • Addresses new requirements for authoring tools.
  • Promote the Federal CIO Council's free training resources to help you create and test Microsoft Office and Adobe Acrobat documents for accessibility. (Updated)
  • Requirement E205 - Ensure 508 conformance for all public-facing electronic content, as well as internal-facing official communications that fall under defined categories. (NEW)

Best Practices

Technology Accessibility Playbook

Back to top

Measure & Monitor Progress

Keep track of how your agency is meeting goals; measure your success.

  • As technology is modernized or updated, ensure conformance to the standards.
  • Use automated accessibility scanning tools to conduct preliminary testing for large websites and electronic document libraries.
    • Note that automated scanning tools can only validate conformance to a portion of the standards.
  • Update test scripts in current scanning tools to align with the WCAG 2.0 Guidelines. (Updated)
  • Record automated and manual accessibility test results in a central database. Track:
    • Which features and functionality were tested;
    • Whether original or revised standards were used to perform testing;
    • Feedback from users with disabilities; and
    • Accessibility improvement activities.
  • Monitor and report progress - Reports are due to OMB each February and August.

Technology Accessibility Playbook

Reviewed/Updated: January 2018

Section508.gov

An official website of the General Services Administration

Looking for U.S. government information and services?
Visit USA.gov