Information
This resource can help local governments figure out what they should do to comply with the DOJ rule on web accessibility.
The Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA is the technical standard for state and local governments’ web content and mobile apps.
“Web content” is defined as the information and experiences available on the web, like text, images, sound, videos, and documents.
Action Step 1: Learn about the rule’s requirements
- If you want a basic introduction to the rule: Check out the Fact Sheet.
Action Step 2: Figure out when you need to fully comply with the rule
- Compliance deadline: April 24, 2026
Action Step 3: Figure out who within your bureau or office will have a role in complying with the rule
- Think broadly about who should be involved
- Set clear expectations for staff
- Think about what resources you will need
Action Step 4: Train your staff
General training for all staff members
- Training for designers and marketing staff on accessibility and visual design.
- Training for web developers and content testers on accessible coding solutions.
- Training for non-technical content authors on writing accessible content.
- Training for procurement staff about how your state or local government plans to make sure it buys web content and mobile apps that comply with the rule.
Action Step 5: Identify what web content and mobile apps your public entity has
- How many websites does my public entity have?
- How many web pages are within those websites?
- What types of content are on those web pages? HTML content? PDFs? Word processor files? Videos? Images?
- Does my public entity post on social media? Which social media platforms does it use? What types of content does it post on social media?
- Are there other places on the web that my public entity posts?
- What mobile apps does my public entity use? Are those apps created and operated in-house, or are they operated by third parties?
- Who posts on my public entity’s website? Are there any places where members of the public can post?
- What third-party vendor content does my state or local government provide or make available?
Action Step 6: Refresh your understanding of the rule’s exceptions
Action Step 7: Determine what accessibility fixes are needed
- The W3C has a page explaining some easy first checks that you might want to perform on your website. These preliminary checks can help you get started and figure out how you might want to approach a more comprehensive review.
- Testing the accessibility of web content and mobile apps can take time and planning, so it’s best not to leave this step until the last minute.
- You won’t be able to use automated testing tools alone, because those tools can’t test for all aspects of accessibility, so you’ll want to use some combination of automated and manual assessments.
Action Step 8: Prioritize which content to fix first
DOJ guidance States that we should be prioritizing the most vital documents. This should help you determine which Content should be prioritized for remediation. We have developed a page to help you determine which content to start with.
- You may want to consider factors like whether the content:
- Enables people to perform key tasks, like registering for programs; searching for things; submitting forms, requests, or reservations; paying bills; or making purchases.
- Is frequently accessed or is important for accessing essential government programs.
- Has been flagged as inaccessible by individuals with disabilities.
- Is newly in development, so that you can avoid creating new barriers.
- Appears across multiple web pages, like navigation menus, search features, and standardized footers.
- Is based on a template, so that you can make sure you are using an accessible template.
You can find more suggestions at the W3C’s page on prioritizing issues and page on interim repairs.