Part four of our new series ‘A Product Leader’s Guide To Accessibility & AODA’. You’ve launched your website, it feels good. All new and glossy, what next? During this chapter, we’re getting to explore these two options for maintaining your AODA compliant website, their pros, and cons, and a couple of common use cases for every.
We’ve worked on dozens of accessibility projects over the years, and have helped nonprofits, associations, businesses, and controlled industries navigate the tricky waters of accessibility compliance.
We are excited to launch our five-part series on Product Leader’s Guide To Accessibility & AODA with Simone Abel – Director of Digital Strategy at Enginess. Over subsequent weeks, we’ll post several articles sharing the simplest practices and key recommendations around implementing accessibility and AODA together with your project.
AODA and Managing Ongoing Maintenance
Now, you’ve launched your new accessible website. It’s compliant, it’s shiny, it’s wonderful.
You’re done, right?
Not such a lot. There are two approaches we see our clients take with reference to ongoing maintenance.
Once and Done: Push everything you’ve got into your launch, then essentially leave your website alone.
Ongoing Retainer / Program: Continuous, regularly care over an extended period of your time (ideally the lifespan of your site).
In this chapter, we’re getting to explore these two options, their pros and cons, and a couple of common use cases for every .
