Despite our best efforts, it’s difficult to future proof our digital assets and open source projects for accessibility standards. Our code and design may follow current standards, but will your careful compliance become obsolete when new guidelines are released? What happens when other contributors add features and documentation? What browsers or assistive technology agents do your consumers use?

We will review a holistic approach for the complete lifecycle of an open source project —including how to iterate on existing content without impacting the hard work you put in during the build phase. Much like SEO...your work is never done. It should be considered in the initial build, then maintenance, complete with sprint regression testing, etc.

Attendees will come away from this session with:

* How to get started on improving accessibility on an existing project
* Tips on what useful combinations of user agents, browsers, devices, etc. to test
* A list of free tools that a site owner/content author can use to be sure their website is compliant before and after a build
* What WCAG and other guidelines are on the horizon

Comments

Comments are closed.