Featured Post
04.02.2020
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.
Select the compliance level you’re working toward to get a better understanding of what accessibility means. Then it won’t feel so complicated.
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.
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.
Questions? Comments? We want to know! Drop us a line and let’s start talking.
Learn More
01.20.2021
What's the difference between git and GitHub? What's a repo? How is a release different from a deployment? How are tags and releases related?
11.30.2020
We know that balancing the ongoing needs of your website, your team, and your users can be a real challenge. We have developed a clear set of priorities and checkpoints to ensure your digital properties stay secure, up-to-date, and optimized for the long haul, and re-structured our process with those priorities in mind.
11.30.2020
If content changes on your site and there’s a visual change to let users know, you need to make that change clear to folks who can’t see the visual cues. Drupal.announce is a JS method built into Drupal core that can make this easy.