Address accessibility early to avoid costly delays
Building a site in Drupal and then addressing any accessibility concerns can be a costly mistake. Especially if there is a lot of rich media and different controls available to the end user.
Addressing accessibility issues before or even during the build process can be extremely valuable in terms of saved developer and front ender time as well as significantly reducing time to launch.
Things to consider during the design phase in terms of accessibility can be especially handy for the Project Manager and even the product owner. Getting on top of these concerns quickly is very important.
Providing both the back and front end developers with the skills to identify and address some basic accessibility concerns is easy and its what I intend to go through.
Comments
+1 This is something that is important to me as I've been working with some non-profit and community projects. I feel like I have a decent handle on the topic, but it'd be great to hear it from someone with a greater depth of knowledge so I can assess my understanding and compare notes.