Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

BS8878 Web Accessibility Code of Practice

11,040 views

Published on

Published in: Design, Technology

BS8878 Web Accessibility Code of Practice

  1. 1. BS8878 Web Accessibility Code of Practice Leonie Watson Chair of the British Computer Association of the Blind (BCAB) @WeAreBCAB @LeonieWatson
  2. 2. What is BS8878?
  3. 3. It’s a UK national standard <ul><li>From the British Standards Institution (BSI). </li></ul>
  4. 4. It’s a framework <ul><li>For making eAccessibility “business as usual” within an organisation. </li></ul>
  5. 5. It’s not a substitute <ul><li>For existing legislation, guidelines or standards. </li></ul>
  6. 6. Why was BS8878 created?
  7. 7. The changing technological landscape <ul><li>It could no longer be assumed that people were accessing the web from a desktop. </li></ul>
  8. 8. The changing political landscape <ul><li>&quot;Promoting digital inclusion is essential for a dynamic modern economy and can help to make government more efficient and effective.“ </li></ul><ul><li>(David Cameron) </li></ul>
  9. 9. The changing legal landscape <ul><li>The Equality Act would replace the Disability Act in 2010. </li></ul>
  10. 10. Who wrote BS8878?
  11. 11. Industry professionals <ul><li>People with a strong background in accessibility and digital inclusion. </li></ul>
  12. 12. Disability organisations <ul><li>People with disabilities, and representatives from disability organisations. </li></ul>
  13. 13. How was BS8878 created?
  14. 14. In 2005... <ul><li>Research from the Disability Rights Commission (DRC) revealed that websites were struggling with accessibility. </li></ul>
  15. 15. In 2006... <ul><li>PAS 78 (Guide to good practice in commissioning accessible websites) was released. </li></ul>
  16. 16. In January 2008... <ul><li>Work began to transform PAS 78 into a British Standard (BS8878) </li></ul>
  17. 17. In November 2008... <ul><li>First draft of BS8878 was made available for widespread public consultation. </li></ul>
  18. 18. In May 2010... <ul><li>A second draft of BS8878 was made available for public consultation, receiving international comment. </li></ul>
  19. 19. In December 2010... <ul><li>BS8878 (Web Accessibility Code of Practice) was officially released. </li></ul>
  20. 20. How does BS8878 work?
  21. 21. Assigning responsibility <ul><li>Responsibility for eAccesssibility should be assigned to a role or department; </li></ul><ul><li>That role or department should be empowered to fulfil that responsibility. </li></ul>
  22. 22. Creating an eAccessibility policy <ul><li>A document that explains an organisation’s commitment to accessibility, and summarises its approach. </li></ul>
  23. 23. Introducing web products <ul><li>Any website, web service or web application delivered over IP. </li></ul>
  24. 24. Creating a web product policy <ul><li>A living document that evolves throughout the web product’s entire lifecycle; </li></ul><ul><li>Based on the intentions of the organisational policy, but tailored to a particular web product. </li></ul>
  25. 25. How is a web product policy created?
  26. 26. Document the accessibility journey.
  27. 27. Research and requirements
  28. 28. Step 1: Define the purpose of the web product <ul><li>What is the purpose of the web product, and what will people expect to achieve when they use it? </li></ul>
  29. 29. Step 2: Define target audiences <ul><li>Is the web product internal or public facing, and is it aimed at a particular group of people? </li></ul>
  30. 30. Step 3: Needs of the target audiences <ul><li>What are the general needs of the target audiences, and do they have specific needs in relation to the web product? </li></ul>
  31. 31. Step 4: Platform and technology <ul><li>Are the target audiences restricted in their technology, perhaps because of cost, confidence or compatibility? </li></ul>
  32. 32. Step 5: Relationship with target audiences <ul><li>Will the web product enable personalised choices through a login or cookie, or will it support more general groups of people.? </li></ul>
  33. 33. Step 6: Tasks and goals <ul><li>What are the goals someone will be able to complete, and what are the tasks they will use to achieve those goals? </li></ul>
  34. 34. Strategic Choices
  35. 35. Step 7: Level of user experience. <ul><li>Will the web product offer a technically accessible, useably accessible, or enjoyably accessible experience? </li></ul>
  36. 36. Step 8: Accessibility approach <ul><li>Will the web product take an inclusive design approach, offer user personalisation, or a combination of both? </li></ul>
  37. 37. Step 9: Delivery platform <ul><li>Will the web product be optimised for a particular platform, or be part of a suite of platform specific versions? </li></ul>
  38. 38. Step 10: Target technologies <ul><li>Which operating systems, browsers and assistive technologies will the web product support? </li></ul>
  39. 39. Procurement
  40. 40. Step 11: Create or procure <ul><li>Will the web product be created in-house or procured externally, and how do you ensure third party solutions are accessible? </li></ul>
  41. 41. Production
  42. 42. Step 12: Web technologies <ul><li>Do the technologies used to build the web product support accessibility, and do they expose information to assistive technologies? </li></ul>
  43. 43. Step 13: Web guidelines <ul><li>What are the best accessibility standards available for the chosen technologies, and how will the web product conform to them? </li></ul>
  44. 44. Evaluation
  45. 45. Step 14: Assure accessibility <ul><li>What is the accessibility test plan, and how will it be evaluated throughout development of the web product? </li></ul>
  46. 46. Step 15: Communicate clearly <ul><li>What will the accessibility statement say, and how will it be made available throughout the web product? </li></ul>
  47. 47. Post Launch
  48. 48. Step 16: Maintaining accessibility <ul><li>How often will updates be planned, and what is the process for continually reviewing and evaluating the web product? </li></ul>
  49. 49. What else does BS8878 offer?
  50. 50. Lots of helpful guidelines <ul><li>Inclusive design guidelines; </li></ul><ul><li>Personalisation guidelines; </li></ul><ul><li>Guidelines for non computer platforms; </li></ul><ul><li>Guidelines for older people. </li></ul>
  51. 51. Useful advice on assuring accessibility <ul><li>Gathering requirements; </li></ul><ul><li>Creating a test plan; </li></ul><ul><li>Testing methods; </li></ul><ul><li>Post launch programmes. </li></ul>
  52. 52. Even more helpful annexes <ul><li>15 annexes providing supporting information, guidance and example documentation. </li></ul>
  53. 53. Why is BS8878 a British standard?
  54. 54. Legal and cultural specifics <ul><li>BS8878 references UK law, and contains guidance on user requirements that is culturally oriented towards UK citizens. </li></ul>
  55. 55. How can BS8878 be applied internationally?
  56. 56. Core principles <ul><li>BS8878 encourages the consideration of accessibility throughout a web product’s lifecycle, and its core principles can be followed in any organisation. </li></ul>
  57. 57. Where can I find out more about BS8878?
  58. 58. BS8Case studies and making BS8878 international <ul><li>Jonathan Hassell (Hassell Inclusion); </li></ul><ul><li>Friday 1.50pm, Madeleine AB 3rd floor; </li></ul><ul><li>http://www.hassellinclusion.com/bs8878/ </li></ul>
  59. 59. Any Questions?
  60. 60. Thank you <ul><li>Léonie Watson </li></ul><ul><li>Email: chair@bcab.org.uk </li></ul><ul><li>Twitter: @LeonieWatson </li></ul><ul><li>W. bcab.org.uk </li></ul>

×