ADA Title II Accessibility Roadmap

Table of Contents

Introduction

The purpose of this roadmap is to give you a step-by-step plan for how to get your organization ready for compliance with the new Americans with Disabilities Act (ADA) Title II digital accessibility requirements. But these are just our recommendations. The new rule does not provide instructions on how to meet the requirements, only that you must. Feel free to change things to fit your situation and organizational needs. 

Step 1: Learn about the new requirements and digital accessibility 

It may seem obvious, but your first step should be to learn everything you can about what the new ADA Title II Rule is and what it says you need to do. Our Understanding the New ADA Title II Rule article is a good place to start. We also recommend reading the Department of Justice’s (DOJ) ADA Title II Fact Sheet. But there are lots of other resources available online, too. This is an important topic that has lots of attention right now.

Before moving on to other Steps of the Roadmap, now is the time to make sure that your organization’s leadership and legal teams are aware of the new Rule. They need to be involved in this process from the very beginning.

Beyond the Rule itself, you will want to start learning all you can about digital accessibility as soon as possible, too. But don’t worry too much about specifics yet. Accessibility is a process, not a destination. Learning the basics will be enough to move on to the next steps of the roadmap, and your knowledge will continue to grow from there.

Our free self-paced accessibility courses cover everything you need to get started in a few hours or less. We recommend starting with the Intro to Digital Accessibility track before moving on to more advanced topics. You should also check out trainings and resources offered by other accessibility experts like:

Step 2: Assign responsibilities 

Now that you know what is expected of you and your organization, it’s time to figure out who is going to be in charge of what. Setting clear responsibilities now will make the rest of the process easier for everyone. 

Because each role in your organization will have different responsibilities, they will need different types of training throughout this process. You may also find that some people fit into multiple roles at the same time. The following sections give examples for how the responsibilities of some roles could look, but you will likely need to adapt or add to these responsibilities to fit your organization’s needs. 

All Roles

Everyone in your organization has a responsibility to create accessible content, so everyone needs basic accessibility training at a minimum. 

Minimum Training 

  • Basic overview of accessibility laws, guidelines, and policies 
  • Disability awareness and digital accessibility principles 
  • Platform-specific accessibility training based on the types of content they create 

Recommended Certifications 

Responsibilities 

  • Making all digital content they create accessible 

Administration

Additional Training 

  • None 

Responsibilities 

  • Make accessibility an organizational priority 
  • Provide sufficient funding, resources, and support for the organization’s accessibility initiatives 
  • Work with all other roles to write and implement organization-wide accessibility policies  
  • Enforce accessibility policies 

Legal Team

Additional Training 

  • In-depth knowledge of accessibility laws, guidelines, and policies 

Responsibilities 

  • Advise all other roles on current and future accessibility laws, guidelines, and policies 
  • Work with all other roles to write organization-wide accessibility policies 

Human Resources (HR) Team

Additional Training 

  • None 

Responsibilities 

  • Revise all job descriptions to include creating accessible content as a basic job requirement 
  • Develop and implement accessible hiring practices 

Web Team

Additional Training 

  • Advanced web accessibility (HTML, ARIA, CSS, etc.) 
  • How to meet the Web Content Accessibility Guidelines (WCAG) standards 

Responsibilities 

  • Maintain the accessibility of the organization’s web content 
  • Provide support to all other roles when making web content 

Recommended Certifications 

Purchasing Team

Additional Training 

Responsibilities 

  • Ensure all products and services the organization purchases are accessible 
  • Work with Administration and Legal Team to develop accessible contract language and purchasing procedures 
  • Work with vendors to comply with the organization’s Accessibility Policy and applicable laws 

Team Accessibility Expert 

Each team should have at least one person designated as the accessibility expert for that team. They should receive more in-depth training than their peers and should be the first point of contact for any accessibility issues their team encounters. 

Additional Training 

Recommended Certifications 

Optional Certifications 

Responsibilities 

  • Be the accessibility expert on their team 
  • Provide technical assistance on accessibility issues 
  • Answer their team’s accessibility questions 
  • Review products for accessibility 

Step 3: Create policies and contract language 

Once everyone knows what their responsibilities regarding accessibility are, the next step is to start implementing official policies and procedures throughout your organization. We recommend starting with these three items: 

  1. Organizational Accessibility Policy 
  2. Public Accessibility Statement 
  3. Accessibility Contract Language 

Before we continue, now is an appropriate time to give this disclaimer: We’re not lawyers! All the examples and recommendations in this Roadmap should be thoroughly vetted by your legal team before putting them into practice. 

Accessibility Policy 

An Accessibility Policy establishes your organization’s commitment to accessibility and puts it front and center. It informs each employee of their responsibilities and helps hold everyone accountable. 

There are many things you could add to your Accessibility Policy. At a minimum, it should include: 

  • The specific accessibility standards that apply to your organization. 
    • The standard set in the new ADA Title II regulations is the Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA.  
    • Optional: We recommend referencing the “newest released version of WCAG Level AA” instead of specifying an exact version. Doing this holds your organization to a higher standard than required by current law, but it also means you don’t have to keep updating your policies every time the law changes. 
  • A commitment to hold vendors accountable to the policy, too. 
  • The responsibilities of each role from Step 2. 

Example Accessibility Policy

The example policy below is adapted from the Policy Template found on the W3C WAI’s Developing Organizational Policies on Web Accessibility page. Parts that you should make specific to your organization are noted in brackets. 

Accessibility Policy

Our organization is committed to ensuring people with disabilities can access our website and digital content. In accordance with state and federal law, all digital content produced by [Organization name] will meet or exceed the newest released version of the Web Content Accessibility Guidelines (WCAG) to a minimum of Level AA, by [compliance date]. 

We are also committed to ensuring the accessibility of products & services we purchase. Products, services, and digital content created or supplied by third-party vendors and subcontractors will also be expected to meet or exceed the standards of this policy. This policy does not apply to user-generated content created by members of the public. 

We will review this policy [review period] on or before the [policy review date]. This policy was last reviewed on [last review date], by [reviewer name]. 

Responsibilities by Role

[List of responsibilities from Step 2]

Accessibility Policy Resources

Accessibility Statement 

It’s important to understand the difference between an Accessibility Policy and an Accessibility Statement. 

  • Accessibility Policy: Internal document that contains specific role responsibilities and other information not relevant to the public. Usually much longer than an Accessibility Statement. 
  • Accessibility Statement: Statement on your website that demonstrates a public commitment to accessibility. 

There are many things you could add to your Accessibility Statement. At a minimum, it should include: 

  • The contact info for the person visitors can reach out to if they encounter accessibility barriers. 
  • The accessibility standard your organization is attempting to achieve. 
    • The standard set in the new ADA Title II regulations is the Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA.  
    • Optional: We recommend referencing the “newest released version of WCAG Level AA” instead of specifying an exact version. Doing this holds your organization to a higher standard than required by law, but it also means you don’t have to keep updating your policies every time the law changes. 

You should put your Accessibility Statement and contact information in an easy to find place on your website, such as a link in the footer. Don’t make it hard for people to get help! 

Example Accessibility Statement

The example statement is adapted from Kris’s Accessibility Statement Template at accessible.org. Parts that you should make specific to your organization are noted in brackets. 

Accessibility Statement

[Organization] is committed to providing an inclusive and accessible experience for everyone, including people with disabilities.  

Our commitment is guided by our accessibility policy to ensure that people with disabilities have full and equal opportunities to access and benefit from the [experiences, content, products, services, information, etc.] offered through [Website.com]. 

We strive to meet the requirements of the newest released version of the Web Content Accessibility Guidelines (WCAG) to a minimum of Level AA in accordance with state and federal accessibility laws including, but not limited to: 

  • Section [504, 508, etc.] of the Federal Rehabilitation Act 
  • Title [I, II, III, IV, or V] of the Americans with Disabilities Act (ADA) 
  • [Other Applicable Federal Accessibility Laws] 
  • [Applicable State Accessibility Laws] 
Support & Feedback

Please let us know if you encounter an accessibility barrier or find something on our website that isn’t working. We’re here to help! 

  • Name: [Contact Name] 
  • Title: [Contact Title] 
  • Email: [Contact Email address] 
  • Phone: [Contact Phone Number] 

We try to respond to accessibility barriers as quickly as possible and to other concerns within 5 business days. Thank you! 

Accessibility Statement Resources

Accessibility Contract Language 

Everything is on the internet these days. As a result, people with disabilities are encountering more accessibility barriers on the web than ever before. This has understandably led to an increase in accessibility lawsuits. Adding accessibility language to your contracts is one of the easiest ways to help protect your organization and increase the overall accessibility of your digital content and services. Without it, you will have a hard time holding vendors accountable for the accessibility of their products! 

There are many clauses you could add to your Accessibility Contract Language. At a minimum, it should: 

  • Specify the accessibility standard that will apply to the Vendor’s products and services. 
    • The standard set in the new ADA Title II regulations is the Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA. 
    • Optional: We recommend referencing the “newest released version of WCAG Level AA” instead of specifying an exact version. Doing this holds your organization to a higher standard than required by law, but it also means you don’t have to keep updating your contracts every time the law changes. 
  • Require an Accessibility Conformance Report (ACR), Voluntary Product Accessibility Template (VPAT®), or similar accessibility evaluation for each product included in the contract. If a vendor doesn’t know what an ACR or VPAT is, that’s a big red flag! 

Example Accessibility Contract Language

You should always ask your legal team before adding anything to your contracts., but the example below shows how just a few sentences about accessibility can help protect your organization. Parts that you should make specific to your organization are noted in brackets. Our full Sample Accessibility Contract Language document (.docx) contains a longer version of this example. Use it as inspiration for updating your own contracts!  

Accessibility Standard

[Vendor Name] (hereafter “Vendor”) and all Subcontractors will ensure [Product Name] (hereafter “Product”) conforms with the newest released version of the Web Content Accessibility Guidelines (hereafter “WCAG”) to a minimum of Level AA, in compliance with Title II of the Americans with Disabilities Act (ADA) and Section 508 of the Federal Rehabilitation Act. 

Vendor Responsibilities

The Vendor will make all efforts to ensure that all work performed, products created, designs suggested, templates used, and functionality developed by the Vendor and all Subcontractors meets or exceeds the WCAG Standard specified above and passes all relevant WCAG Success Criteria, at no additional cost to [Client Name] (hereafter “Client”) beyond the price agreed upon in this contract.

Accessibility Contract Language Resources

Step 4: Inventory and audit your current content 

Now that you have your policies in place, you’re ready for the next step: gathering an inventory of your current digital content. Then you’ll be able to evaluate whether you need to keep, update, archive, or remove that content. This step is important because you’ll need to know exactly what content you have so you can know how to prioritize fixing it in the next step. 

Before diving in, you’ll want to familiarize yourself with the 5 exceptions listed in the Rule. The overall purpose of the exceptions is to allow you to focus your remediation efforts on the content that matters most instead of wasting a bunch of time, effort, and money fixing things that people aren’t even using. Work smarter, not harder! 

This is another good time to remind you that we’re still not lawyers! You should take our interpretation of the exceptions with a mountain of salt. Please have your legal teams review the full text of the Rule before moving forward with this step of the Roadmap. 

What are the exceptions? 

The DOJ’s Fact Sheet does a good job of summarizing the 5 exceptions listed in the Rule, but unfortunately it leaves out some helpful context. Each “What this means for you” section below contains additional clarifications of the exceptions. 

Exception 1: Archived web content 

What the rule says 

“Web content that meets all four of the following points would not need to meet WCAG 2.1, Level AA:

  1. The content was created before the date the state or local government must comply with this rule, or reproduces paper documents or the contents of other physical media (audiotapes, film negatives, and CD-ROMs for example) that were created before the government must comply with this rule, AND 
  2. The content is kept only for reference, research, or recordkeeping, AND 
  3. The content is kept in a special area for archived content, AND 
  4. The content has not been changed since it was archived.” 
What this means for you 
  1. If you want to use this exception, you must create and clearly label a section of your website as “Archived”. You can’t just label the content itself as archived. It must be kept in a separate place that is easy to identify. 
  2. Content doesn’t qualify as “archived” just because you put it in the Archived section of your website. All four of the points above must apply to the content for it to qualify for this exception. 
  3. After your compliance date, any content you want to use this exception on can never be updated. As soon as you change it in any way, it no longer qualifies for this exception and would need to be made accessible at that time. 
  4. Any content created after your compliance date can never qualify for this exception. This is because all content created after your compliance date must be accessible from the beginning. You can still put that new content in the Archived section of your website, but it will already be accessible by that point, so the exception would be useless. 
  5. Even if content qualifies for this exception, if someone requests an accessible version of it, you still have to make it accessible for them. This is a requirement found in the rest of Title II. 

Exception 2: Preexisting conventional electronic documents 

What the rule says 

“Documents that meet both of the following points usually do not need to meet WCAG 2.1, Level AA, except in some situations: 

  1. The documents are word processing, presentation, PDF, or spreadsheet files; AND 
  2. They were available on the state or local government’s website or mobile app before the date the state or local government must comply with this rule.” 
What this means for you 
  1. You don’t have to make all your old documents accessible. 
  2. You do have to make any old documents that people are still using “to apply for, access, or participate in services, programs, or activities” accessible. 
  3. After your compliance date, any content you want to use this exception on can never be updated. As soon as you change it in any way, it no longer qualifies for this exception and would need to be made accessible at that time. 
  4. Any documents created after your compliance date can never qualify for this exception. This is because all content created after your compliance date must be made accessible from the beginning, so the exception is useless at that point. 
  5. Even if a document qualifies for this exception, if someone requests an accessible version of it, you still have to make it accessible for them. This is a requirement found in the rest of Title II. 

Exception 3: Content posted by a third party 

What the rule says 

“Content that is posted by third parties on a state or local government’s website or mobile app would not need to meet WCAG 2.1, Level AA.” 

What this means for you 
  1. This exception does not apply to content posted by your vendors! In this case, “third parties” means “members of the public.” 
  2. Any of the tools and platforms that allow members of the public to post content onto your website do need to be accessible. However, the content that the public posts using those tools does not. Basically, you can’t force a member of the public to create accessible content, so that means you’re not responsible for it. For example: 
    1. If you have a message board on your website, the message board itself must be accessible. Any posts you or any of your vendors make on your message board must also be accessible. But any posts that members of the public make on your message board do not need to be accessible. 
  3. Even if content qualifies for this exception, if someone requests an accessible version of it, you still have to make it accessible for them. This is a requirement found in the rest of Title II. 

Exception 4: Individualized documents that are password-protected 

What the rule says 

“Documents that meet all three of the following points do not need to meet WCAG 2.1, Level AA: 

  1. The documents are word processing, presentation, PDF, or spreadsheet files, AND 
  2. The documents are about a specific person, property, or account, AND 
  3. The documents are password-protected or otherwise secured.” 
What this means for you 
  1. This exception does not apply to documents just because they are behind a password. 
  2. This exception can never apply to documents that are distributed for public use. 
  3. This exception only applies to the 4 specific types of documents listed. If you provide documents to people in other formats, such as HTML, those documents do need to be accessible.  
  4. Even if a document qualifies for this exception, if someone requests an accessible version of it, you still have to make it accessible for them. This is a requirement found in the rest of Title II. 

Exception 5: Preexisting social media posts 

What the rule says 

“Social media posts made by a state or local government before the date the state or local government must comply with this rule do not need to meet WCAG 2.1, Level AA.” 

What this means for you 
  1. Any of your social media posts created before your compliance date do not need to be made accessible. 
  2. Any of your social media posts created after your compliance date do need to be accessible. 
  3. Even if a social media post qualifies for this exception, if someone requests an accessible version of it, you still have to make it accessible for them. This is a requirement found in the rest of Title II. 

Gather your content inventory 

The folks at the Nielsen Norman Group have created a fantastic Content Inventory and Auditing 101 guide that thoroughly details the process for performing a content inventory and audit. Here’s a summary of the topics the guide covers: 

  • Explaining the difference between an inventory and an audit and why you need both 
  • How to get started by choosing the right people, processes, and tools for the job 
  • Choosing the information you need to gather during the inventory process 
  • Choosing the evaluation criteria for the auditing process 
  • Setting up your inventory and audit spreadsheet 
  • Deciding what to do with each piece of content 
  • How to maintain the inventory and audit 

They even include a free Content Inventory and Auditing Template spreadsheet that you can adapt to your needs. Talk about a time saver! 

Sort and evaluate your content 

The Content Inventory and Auditing 101 guide does a good job of explaining the general process of sorting and evaluating your content. The guide recommends assigning each piece of content a status of Keep, Update, or Remove. However, the exceptions to the new Title II rule require us to rethink those categories a bit. We will refer to these categories as “buckets” from this point on. Partly because it makes it easier to visualize, and partly because it’s more fun. 

Each team in your organization should use these four buckets to sort the content they are responsible for: 

Bucket 1: Remove

Any obsolete or redundant content that you can safely remove or delete goes in this bucket. You will want to remember to take your organization’s data retention policies into account, but if you don’t need to keep the piece of content anymore, then why would you? 

The more content you delete now, the less content you have to fix later.

Bucket 2: Ignore

Any content you need to keep that qualifies for Exceptions 2, 3, 4, or 5 goes in this bucket. Since this content qualifies for an exception, you can safely ignore the requirement to make it accessible for now.

But, remember that you still have to make this content accessible if someone asks for it! 

Bucket 3: Archive

Any content you need to keep that qualifies for Exception 1 goes in this bucket. All five of the exceptions remove the need for you to make the content accessible, but Exceptions 2, 3, 4, and 5 don’t have any extra requirements for the content like Exception 1 does. That’s why this content gets its own bucket. 

Bucket 4: Update

Any remaining content that doesn’t belong in the other buckets will end up in this bucket. It should contain any content you need to keep but does not qualify for an Exception.

The content in this bucket is what you will need to make accessible by your compliance deadline! 

Step 5: Work through your content buckets 

Now that your content is sorted into the right buckets, it’s finally time to do something with it! Of all the steps in the roadmap, this is the one that will take the most time and effort to complete. It’s also the step that is most critical to get right.  

The whole roadmap has been leading up to this Step. 

Let’s roll up our sleeves and get to work! 

How to work through Bucket 1: Remove 

This bucket is the “fun” bucket. Simply delete this content and you’re done. Seriously, what are you waiting for? It’s therapeutic! 

But you should probably double check that you don’t need it anymore at least once before you delete it. 

How to work through Bucket 2: Ignore 

This bucket may be less fun than Bucket 1, but it’s easier to deal with because you’re already done. You don’t have to do anything to this content. Moving on! 

How to work through Bucket 3: Archive 

This is where the real work begins.  

To satisfy the conditions of Exception 1, you need to create an “Archived” section on your website. It doesn’t have to have this exact name, but it should be obvious that this content is not currently in use. We recommend clearly explaining what “archived content” means in a prominent place, too. People with disabilities need to be made aware up front that the content in this section of your website will probably not be accessible unless they specifically request it. And you should let them know what the process is for them to be able to make those requests. 

Let’s recap: 

  1. Create a new “Archived” section on your website and move all the content in Bucket 3 there. 
  2. Clearly label that the content in this section is “archived” and explain what that means. 
  3. Give people an easy way to ask you to make specific archived content accessible. 
  4. Archived content can never be updated or changed in any way. If you do make any changes to archived content, then that entire piece of content must be made accessible.  

How to work through Bucket 4: Update 

We’ve saved the best and most important bucket for last. Bucket 4 is where you should spend most of your time and effort while working through the roadmap. It contains your most important content, so it’s worth taking the time to get it right. 

To begin, we recommend spending some time to identify and prioritize which content you should make accessible first. This process will help ensure you are impacting the largest groups of people as quickly as possible.  

Important note: You should include people with disabilities throughout this process. Who better to help you identify and correct any accessibility barriers in your content than the people that those barriers directly affect?  

Identify your critical content 

To begin prioritizing what you should fix first, you’ll need to determine which content is the most important for your team or organization. There are two simple steps you can take to do this: 

  1. Think about what processes, web pages, or documents are critical to your organization’s daily operations. Some examples of content you might consider critical are people being able to apply for a job, signing up for a class, registering to vote, or paying a bill. 
  2. If you have access to any analytics on your website (or in your Content Management System, Learning Management System, Web Platform, or other systems like Google Analytics), you can use this data to see what content people are accessing most often.  

Test your critical content for accessibility 

By now, at least a few people in your organization should have a decent grasp on how to test your web content and documents for accessibility. But if not, we have multiple courses in our self-paced online course catalog that can teach you how to get started. The courses cover topics such as how to make Microsoft Word and PowerPoint documents accessible all the way up to how to test the accessibility of a website. 

Good accessibility testing combines automated tools, such as WAVE, axe DevTools, and Accessibility Insights, with manual checks, such as keyboard testing and color contrast. Many enterprise-level automated tools, such as those from Pope Tech, Siteimprove, and Deque, can also check the accessibility of many webpages at once. However, no automated tool can fully judge whether a website or document is accessible on its own, and you should beware of any vendor that claims their product can! But these tools are still very valuable and can help speed up testing significantly.

Important!

During this testing process you may identify that a product you have already purchased, or content created by one of your vendors is inaccessible. If this happens, you will need to work with the vendor to make any necessary changes to improve the accessibility of their products. If they are unwilling to do this, you will need to find a new vendor that offers a more accessible product.  

Unfortunately, this is often easier said than done. This is why adding accessibility language to your contracts sooner rather than later is so important! 

Check out these resources for more information: 

Checklists 

Accessibility testing has a lot of steps, which increases the chances of something being forgotten or overlooked. Because of this, it’s important to use some kind of checklist to make sure that everyone is checking the things they need to every time. There are many accessibility checklists available online, but here are a few to get you started: 

Prioritize by Severity Level 

In-depth testing will also help reveal the content that is the most inaccessible. This will help you prioritize your work even more. We recommend using the following severity levels to categorize content by how severe its accessibility barriers are: 

  • Roadblock: Users cannot complete their desired task or process, there is no workaround available, or it is almost impossible for users to determine the correct way to perform the task without spending significant time and effort, if at all. 
  • High Severity: Users can only perform the task or process by using a workaround, it is unlikely that non-power users will be able to find the workaround, or a crucial page function does not function as intended. 
  • Medium Severity: Users can perform the desired task, but it may take more time than it should or could cause significant frustration. The user may need assistance from someone else to perform the task. 
  • Low Severity: Users can perform the desired task on their own, but doing so causes inconvenience or mild frustration. 

Fix your critical content 

From here, the process itself is fairly straight-forward: 

  1. Fix any barriers identified as a Roadblock first. 
  2. Continue working through the barriers from most severe to least severe. (High > Medium > Low) 
  3. Repeat this process for all content in Bucket 4. 

Unfortunately, there is no “magic accessibility wand” that can fix your content for you. This part of the process will require a lot of good old-fashioned hard work (or money!) to complete. Depending on the amount of content you have—and let’s be honest, it’s probably A LOT—you might need to consider looking for a vendor to help you fix your content to be able to meet your compliance deadline. 

Remediation Vendors 

We can’t officially endorse any vendor over any other, but we can at least help point you in the right direction. These vendors have a proven track record and are highly respected in the accessibility industry: 

Caution!

Be cautious of any vendor that claims to be able to get you to “100% accessibility”! The nature of accessibility work means that it is not possible to truly reach 100% accessibility. By removing certain barriers, you will necessarily create others. It’s all about being flexible and responsive to your audience. 

We particularly urge you to avoid vendors selling a group of products known as “accessibility overlays”. These vendors often greatly exaggerate the capabilities of their products. And even worse, overlays can often introduce accessibility barriers that you didn’t have to begin with! 

Read the Overlay Fact Sheet for more information. 

Step 6: Maintain the accessibility of your content 

Now that you’ve gotten your current content to a baseline level of accessibility, you’re not done! Accessibility is a continuous process. You’ll need to constantly adapt and grow your methods to ensure any new content you create from here on out is accessible too.  

Below are a few more ways to keep the momentum going. You’ve got this! 

Fully embed accessibility into your organization 

From this point on, any document or web page your organization creates or edits should be fully accessible. Most of this roadmap specifically deals with the new digital accessibility requirements added to Title II of the ADA, but there are other accessibility considerations you should be thinking about too while you’re at it. For example, any event you host should have captioning and sign language available for participants. The policies, practices, and oversight created in the steps above should provide support for ensuring these things are done, too. 

Don’t lose all the progress you’ve made by letting accessibility go to the backburner after the initial remediation is complete! 

Resources for developing an accessibility strategy

Maturity models

Establish patterns for testing content 

Test web content and documents for accessibility on a regular basis. For instance, as mentioned above, there should always be checks when new content is created. But this is only one piece of the puzzle. There are several more times in the lifecycle of your content where checks should be done: 

  • When a new feature for a website is being designed or developed 
  • When new products are being evaluated for purchase or use 
  • When any web or document content is edited or otherwise updated 
  • When any new web or document content is created 

For more information, check out Section508.gov’s Effective Methods and Tools for Incorporating Accessibility Conformance Validation within Development Processes. 

Continue accessibility training 

You and your organization should never stop learning about accessibility, whether from us or from someone else. There is always something new and exciting to learn about!

We have plans to continue creating more self-paced courses on digital accessibility, and we will be rolling out a new workshop training model soon. Stay tuned!

We also host Oklahoma’s premier digital accessibility conference annually, TechAccessOK! This free conference brings in big-name accessibility experts from around the country to talk about a variety of topics related to digital accessibility. We hope to see you there!

There are also lots of other organizations that provide amazing trainings, webinars, and other types of learning, too. Here are a few that you should check out:

Sign up for newsletters 

Did you know that lots of accessibility organizations have newsletters? They’re a great option for staying on top of what’s going on in the accessibility world, and they usually contain lots of tips, tricks, and other resources, too! Here are a few of our favorites: 

Conclusion 

We know that accessibility can seem daunting at first. But with the right plan, the right people, and a lot of hard work, we can all make it easier for people with disabilities to simply live their lives. And that’s the whole point. 

Contact us 

Accessibility compliance is a complicated and ever-evolving topic, so please let us know if you have any questions, comments, or suggestions.  We will continue to update this resource to give you what you need as we receive new information. Thank you!  

The information contained on this website is provided for informational purposes only, and does not, and is not intended to, constitute legal advice on any subject matter.