Websites are continually evolving and changing. Whether it’s design, content, or functionality, sites rarely remain static. What once was functional and accessible may now have become a barrier with content or code updates. Organizations need to have a long-term accessibility maintenance plan in place at the beginning of any project to account for and adapt to these changes. Keeping accessibility maintenance a fundamental part of your web development strategy is more cost-effective and efficient than trying to retrofit it after updates have been implemented. There are many ways to help your organization standardize the accessibility maintenance process.
Keep your accessibility team involvedInform the accessibility team of when website updates are scheduled and their scope. The team can help prioritize accessibility tasks and minimize effort. Everyone has a responsibility to consider and integrate accessibility standards throughout the process, but your accessibility team will make sure things run smoothly and efficiently. And if you don’t have a dedicated accessibility team, assign someone on your digital marketing, development, QA, or content team to be responsible for accessibility oversight for ongoing updates.
Set up regular accessibility reviewsInclude regular accessibility checks during any publishing process to help reduce the risk of new issues being introduced. Running periodic, automated scans can provide an idea if anything has changed recently. If something new shows up that wasn’t found in previous tests, it’s a good indicator that further investigation (and perhaps some manual testing) should be done to determine its impact on accessibility.
- Use tools like WAVE, Axe, and color contrast analyzers for quick, page-level checks
- Use your keyboard to navigate your organization’s webpage without using your mouse. If you can’t navigate easily, seamlessly or in the same manner you would with the mouse, this is a major barrier
- This includes daily content publishing and maintenance activities, as well as broader redesign and development efforts
Reviews should identify issues and why those issues may be occurring
- Are issues caused by a lack of training or understanding by developers, designers or content authors? If so, revisit accessibility training - not just for new members to your team, but for those who could use a refresher course
- Are issues a result of a change in the content management system (CMS)? If so, connect with your accessibility team (or assigned lead) and tech development team and see if patches exist, or what they recommend for compliance