Posted by PeachMAA on September 19, 2010 at 11:23pm
HI All
I work for a not for profit and we are looking to make the change from joomla to drupal.
I am looking for a design and development organisation that as a good understanding of accessibility.
Does anyone have any advice?
Thanks
Comments
Some good accesibility points
PeachMAA, we are a Canberra based company that does a lot of Drupal work and inparticular for government. Have a look at this page for some information on accessibility.
http://www.opc.com.au/blog/308
Drupal, out-of-the-box is pretty damn good in this regard, which is why more and more government departments are seriously looking at it.
It would be interesting to hear how you go making the jump from Joomla to Drupal, a wise move!!
requirements gathering and acceptance testing...
You shouldn't have too much trouble finding an organisation that meet Accessibility requirements.
But you should probably include Accessibility in a list of requirements and look for an organisation who understands stakeholder/business requirements and has a proven track record of building software that meets them.
You'll also need to work out a way of measuring those requirements so you can accept them on delivery. For example: do you require your site to be accessible to more than 1000 users concurrently?
Many good organisations may say "we understand accessibility", but the best ones will say "what do you mean exactly?".
Hope that helps.
Huh???
For example: do you require your site to be accessible to more than 1000 users concurrently?
I think you have mis-understood the original authors question. I gather the question is more to do with WCAG 2.0 guidelines than server/infrastructure capabilities.
Understanding what 'accessibility' is is one thing, but knowing how to properly test and implement the requirments is another.
.
Obviously the question is about Accessibility guidelines. Perhaps I was a little misleading...
Focus on the process of requirements rather than a specific requirement. Find an organisation that is agile enough to deliver your project whatever the requirements may be (because they will change). Think about your requirements and how you are going to measure them (it may be a cursory browse through the site).
It's a good way to avoid this: http://drupalradar.com/when-merde-hits-fan
Accessibility
Hi PeachMAA,
You don't have to jump ship to J! to Drupal. J! could also handle the accessiblity problem you have. All you have to do is to validate your website using the W3C validator (http://validator.w3.org). There are lots of options you can choose to clean up your site.
This can also basically help you in terms of accessibility (http://www.thesitewizard.com/webdesign/improve-accessibility.shtml)
We've done a load of WCAG
We've done a load of WCAG compliance using Drupal for government and non-profit clients. http://www.previousnext.com.au.