Many times a client will specify that their site must be "508 Compliant", or, in the UK, be "Compliant with the DDA". Many times the client may never really know what that means, or if in the end the finished project is "compliant". It's always best to educate clients on what it means to meet this requirement. However, to enlighten a client that the WAI by the W3C has the WCAG and that'll help meet the requirements of Section 508 of the Rehabilitation Act of 1973 or the Disability Discrimination Act 1995 will often make their heads pop, or make them call another shoppe. Irregardless of what language is used to the client to convey confidence, we, as Drupal code monkeys, have to assure our teams, and the clients, that whatever guidelines or checklists we use will not only meet the customer's needs, but hopefully ensure a truly accessible and more usable product. This round table discussion is meant to showcase the little things in our Drupal workflow that aid us in creating accessible websites.
vê, vé, ℣, vituperāvī, vitriolic, vrijeđati, all stand for veeliam. And, he stands for accessibility. bio from Twitter
Sign in to add slides, notes or videos to this session