Quoting Ian Forrester <[EMAIL PROTECTED]>:


Robin Christopherson Web Services Manager of AbilityNet said “We believe it’s time for the focus to come back onto Accessibility, and that a conference of this kind is what is needed to help developers make their Web 2.0 applications accessible. It promises to be a highly practical day, where delegates come away knowing exactly what they need to do, and where they need to focus to make sure they consider accessibility in their products. With some of the biggest and best names in the industry we are very excited about what this event is going to bring to individuals and the industry as a whole.”


Is one day really enough to do justice to this subject.

What do we mean by accessibility?

Do we mean people with differing levels of computer literacy and the design of sites and services to evolve to be fully inclusive?

Do we mean accessibility for those with presbycusis, protanopia, deuteranopia, photosensitive epilepsy, tinnitus and other "mildly" disabling issues, all of which are specialist use cases. If designers design to be inclusive of all these cases, they are noticeably limited in design schemes and technologies, but normally can create something useful to all. Alternatively, can the data be available in alternative guises, like in BETSIE?

For more debilitating issues, it is often necessary to design in such a way that the data may be accessed in alternative ways, like feed readers, text-to-speech engines? Is there a open-standard method?

Then what are the legal aspects of the design implementation, from the DPA requirements of holding data about end-users abilities, to the potential for legislation like the Broadcasting Act but for the internet with regards to presentation of access services and OFCOM's guidances on photosensitive epilepsy.

--
ST

[EMAIL PROTECTED]



-
Sent via the backstage.bbc.co.uk discussion group.  To unsubscribe, please 
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.  
Unofficial list archive: http://www.mail-archive.com/[email protected]/

Reply via email to