1 / 11

A Holistic Framework For Web Accessibility

http://www.ukoln.ac.uk/web-focus/events/meetings/bsi-accessibility-2006-01/. A Holistic Framework For Web Accessibility. About This Talk

mab
Download Presentation

A Holistic Framework For Web Accessibility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. http://www.ukoln.ac.uk/web-focus/events/meetings/bsi-accessibility-2006-01/http://www.ukoln.ac.uk/web-focus/events/meetings/bsi-accessibility-2006-01/ A Holistic Framework For Web Accessibility About This Talk This talk describes a holistic framework to Web accessibility which provides a user-focused approach to accessibility which provides a context for use of WAI WCAG guidelines which recognises embraces diversity rather than mandates conformity Brian Kelly UKOLN University of Bath Bath Email B.Kelly@ukoln.ac.uk UKOLN is supported by:

  2. Contents • Shared Assumptions • WAI Limitations • Holistic Framework • Tangram Model • Questions

  3. Common Assumptions (1) • Things we should have in common: • A desire to see widely-accessible and interoperable services • Use of open standards to provide platform and application-independent services • A recognition of the challenges faced in achieving these aims (funding, time scales, expertise, user requirements, …) • A desire to provide advice on how to achieve the aims whilst acknowledging the challenges Slide used at Accessibility Summit, TechDis, in Feb 2002

  4. Common Assumptions (2) • We also recognise that: • The W3C is the authoritative body which is driving the development of Web standards • W3C WAI has driven the agenda for Web accessibility • W3C WAI has been successful in raising awareness globally that: • Digital resources can be made accessible • Digital resources should be made accessible Slide used at Accessibility Summit, TechDis, in Feb 2002

  5. Problems • Guidelines • WAI model is flawed (see [1]) • WCAG guidelines have flaws • Problems with change control (WCAG  1.0 2.0) • Other Developments • Accessibility issues being addressed elsewhere (formats, applications, OSs, metadata, …) • Context • Need to address diversity and seek wider participation rather than impose universal solutions 1 Further information provided in "Forcing Standardization or Accommodating Diversity? A Framework for Applying the WCAG in the Real World ", W4A, Japan, 2005

  6. UsersNeeds Importance of blended learning Solutions • Holistic framework for e-learning accessibility published in CJLT (2004): • Focuses on the user • and recognises importance of: • External pressures e.g. funders, QAA, … • Technical infrastructure • Resource implications • Learning & teaching outcomes • and requires quality assurance based on documented policies and systematic checking Follow-up work awarded prize for Best Research Paper at ALT-C 2005 E-learning conference

  7. Building On This Work • Current work: • Develop general framework for addressing Web accessibility • Build on existing best practices • Allows for diversity: • User environments • Technical developments (within W3C, other IT developments, other technologies e.g. Podcasting, mobile phones, …) • Context of use (information, learning, culture, …) • Blended accessibility • Personalised solutions

  8. Usability • Jigsaw model implies single solution WCAG OS … • Tangram model encourages diversity of solutions Flash Tangram Model (1) • Generic model: • W3C model has severe limitations • This approach: • Encourages diversity of solutions • Focus on 'pleasure' it provides to user

  9. Tangram Model (2) • Model allows us to: • Focuses on end solution rather than individual components • Provided solutions tailored for end user • Doesn't limit scope (can you do better than WAI AAA?) • Make use of automated checking – but ensures emphasis is on user satisfaction • Guidelines/standards for/from: • WAI • Usability • Organisational • Dyslexic • Learning difficulties • Legal • Management (resources, …) • Interoperability • Accessibility metadata

  10. Relevance To Accessibility Metadata • This approach: • Based on principle of "widening participation" rather than "universal accessibility" • Acknowledges that there may be tensions and conflicts • Provides a bigger picture for user and developer communities • Puts WAI guidelines within the context of a bigger picture • Shows how accessibility metadata relates to a bigger picture • Is itself an example of a personalised / blended solution

  11. Discussion • Questions., comments, etc. welcome

More Related