Give yourself a scope that is reasonable. For example, committing to make all new content accessible is more doable than retrofitting hundreds of pages of old articles. Set goals that are both ambitious and reasonable.
Read the Guidelines
Select the compliance level you’re working toward to get a better understanding of what accessibility means. Then it won’t feel so complicated.
Simplify the Language on Your Team
If you decide to meet WCAG 2.1 AA, don’t make people say that. Just call them ‘the guidelines’. Have a shared vocabulary so everyone can participate without having to be overwhelmed by a bunch of new acronyms.
This way, your team is measuring success in the same way. Define when testing should happen in your process and who is doing it. Build in redundancies so you can look out for each other as you go.
Most Importantly, Support Each Other!
We’re learning new things all the time, and it’s just part of the process. You’ve got this! Just take it one step at a time.
Get In Touch
Questions? Comments? We want to know! Drop us a line and let’s start talking.
Related Blog Posts
When working on our longer-term clients’ sites, we’re often asked to add a new field (or fields) to some kind of content, and in the same batch of code to add values to those new fields. This shouldn’t be a problem -- and mostly, it isn’t.
There are already lots of articles out there if you want to get excited about Drupal 9, so we’re going to focus on the more practical questions with an AFAQ (Anticipated Fearfully Asked Questions).
Your accessibility statement is not just another contact form on your website.