2 thoughts on “Keeping it Legal – The Complementary Approach to Accessibility

  1. Sharon – you’re right that the lack of definition leaves flexability for those who feel informed, supported and able to make decision about what is or isn’t accessible, what is an alternative and whether or not the provision is equitable, unfortunately though most content providers and many (if not most) practitioners aren’t fortunate enough to be in that position so some pointers as to technical conformance is very useful. One of the things we aim to do in “making accessible software, a guide for content providers”, the sister publication to “making software accessible, a guide for Schools” is point to the Standards specs and guidelines which are applicable to environments other than the Web. Working on the premise that that which is documented / standardised is more ‘reasonable’ than that which is not. By following the URL given in the back of the publication www.Becta.org.uk/industry/content/accessibility you can see a list of essential and desirable access requirements for all digital learning resources and links to guidance on implementing these in a range of development environments. It is reasonable to expect a content provider to implement a given function if you can point to guidance on how to do so. It may not be reasonable if a methodology can’t be identified.

  2. Hi Adrian

    Thanks for the link to the resources – there’s a lot of useful information there.

    I agree that guidelines and specifications are necessary to inform and aid technical development, but content developers also need to think “out of the box” when those guidelines don’t help to provide the solutions required. However, this holisitic approach should complement the foundation of technical guidelines and standards.

Leave a Reply to Sharon Cancel reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>