Providing better scaffolding - how BS8878 affects people designing inclusive user experiences


Published on

Presentation given by Jonathan Hassell (Director of Hassell Inclusion and lead author of BS8878) at UK-UPA 'Call to action: Designing inclusive user experiences' event London, Sept 2011.

Covers: what accessibility is really all about (inclusive UX); how BS8878 helps organisations understand the business case for accessibility; how to embed accessibility in their business-as-usual; how different job roles each contribute to whether a product includes or excludes disabled and elderly people; how policies can facilitate or inhibit accessibility; now to make good decisions about accessibility; how to ensure you have the right user-research so your decisions are made on facts not assumptions; what BS8878 enables UX staff to do more easily; how hassell inclusion can help you move forwards in implementing BS8878

Published in: Technology, Design
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Providing better scaffolding - how BS8878 affects people designing inclusive user experiences

  1. 1. Providing better scaffolding - how BS8878 affects people designing inclusive user experiences <br />Prof Jonathan Hassell<br />Director, Hassell Inclusion ltd.<br />Chair, BSI IST/45<br />UK-UPA Call to action: Designing inclusive user experiences<br />16th September 2011<br />
  2. 2. IST/45 view: what accessibility really should be…<br /><ul><li>all about disabled people
  3. 3. aim shouldn’t be accessibility… or even usability… but a great user experience for disabled and elderly people
  4. 4. whether they can get the right value out of what you create
  5. 5. exactly what you aim for, for every other audience
  6. 6. you don’t want to exclude 10m+ people from using your products…
  7. 7. so why don’t more organisations do it?</li></li></ul><li>How does BS8878 help?<br /><ul><li>presents the business-case for accessibility and digital inclusion
  8. 8. gives advice for how to embed accessibility strategically within an organisation
  9. 9. shows a process which identifies the key decisions which are taken in a web product’s lifecycle which impact accessibility
  10. 10. recommends an informed way of making these decisions…
  11. 11. and a way of documenting all of this to ensure best practice</li></ul>Organizational Web Accessibility Policy<br />WebProduct Accessibility Policy<br />WebProduct Accessibility Statement<br />
  12. 12. The accessibility of your web productsis in all these people’s hands…<br />SnrMgrs<br />Legal<br />Finance<br />Marketing<br />Strategy<br />Project Mgrs<br />Product Mgrs<br />Developers<br />Designers<br />Research & Testers<br />Writers<br />
  13. 13. Embedding motivation<br /><ul><li>Need to motivate each group…
  14. 14. Or just use a business case for the top level and set policy top to bottom…
  15. 15. check out OneVoice business cases…</li></ul>SnrMgrs<br />Legal<br />Finance<br />Marketing<br />Strategy<br />Project Mgrs<br />Product Mgrs<br />Developers<br />Designers<br />Research & Testers<br />Writers<br />
  16. 16. Embedding responsibility<br /><ul><li>Work out whose responsibility accessibility should ultimately be…
  17. 17. Make sure they delegate (and monitor results) well
  18. 18. Make sure those delegated to are trained in their responsibilities</li></ul>SnrMgrs<br />Legal<br />Finance<br />Marketing<br />Strategy<br />Project Mgrs<br />Product Mgrs<br />Developers<br />Designers<br />Research & Testers<br />Writers<br />
  19. 19. Embedding through strategic policies<br />SnrMgrs<br />Legal<br />Finance<br />Marketing<br />Strategy<br /><ul><li>create an Organizational Web Accessibility Policy to strategically embed accessibility into the organization’s business as usual
  20. 20. including where accessibility is embedded in:
  21. 21. web procurement policy
  22. 22. web technology policy
  23. 23. marketing guidelines
  24. 24. web production standards (e.g. compliance with WCAG, browser support, AT support)</li></ul>Project Mgrs<br />Product Mgrs<br />Developers<br />Designers<br />Testers<br />Writers<br />
  25. 25. Harmonising accessibility with user-centred/inclusive design processes<br /><ul><li>relating web accessibility to wider human-centred and inclusive design practices
  26. 26. and bringing in concepts of user-personalised approaches…</li></ul>From: ISO/FDIS 9241-210<br />Human-centred design for interactive systems<br />
  27. 27. Yes,there are16steps(sorry…)<br />
  28. 28. An informed way of making good decisions<br /><ul><li>every decision taken could affect whether the product will include or exclude disabled and elderly people
  29. 29. so every decision should be:
  30. 30. recognised as a decision
  31. 31. have all options and implications considered
  32. 32. made based on justifiable reasoning
  33. 33. noted in the Web Product’s Accessibility Policy for transparency
  34. 34. at every step of the process</li></li></ul><li>BS8878 Product process - 1st stage: doing the right research & thought before you start…<br />
  35. 35. 2. Define its target audiences<br />can you predict/control who will use it?<br />e.g. an Intranet<br />or an extranet<br /><ul><li>or will be used by a range of audiences?
  36. 36. is it designed for a particular audience?</li></li></ul><li>4. Note any platform or technology preferences& restrictions<br /><ul><li>for example:
  37. 37. lack of ability to download & install plug-ins or browser updates
  38. 38. IT policy restrictions in offices, colleges preventing use of browser preferences, installation of assistive technologies
  39. 39. strong platform preferences due to worries of cost/complexity/security
  40. 40. will impact on technology choice, platform choice, reliance on ATs to mediate website experiences
  41. 41. cf. rich-media technologies like Flash and ‘alternative versions’
  42. 42. accessibility isn’t about luddite-ism; it is about understanding what your audience really need…</li></li></ul><li>BS8878 Product process - 2nd stage: making strategic choices based on that research<br />
  43. 43. 7. Consider the degree of user-experience the product will aim to provide<br /><ul><li>degrees:
  44. 44. technically accessible
  45. 45. usable
  46. 46. satisfying/enjoyable
  47. 47. an example for online Pacman:
  48. 48. Technically accessible = can control Pacman using a switch
  49. 49. Usable = have a chance of winning as the ghosts adapt to the speed of interaction of my switch
  50. 50. Satisfying = have the right level of challenge (not too easy or too hard)
  51. 51. define the aim for each combination of user group and user goal
  52. 52. BS8878 doesn’t tell you what level you should pick, just lets you know what the options are, and asks you to choose a level you feel you can justify</li></li></ul><li>9. Consider the delivery platforms you will support(and their accessibility implications)<br /><ul><li>which platforms are you going to support, and what degree of accessibility will you aim to achieve?
  53. 53. useful research to have:
  54. 54. are you in control of which platforms your users will use your product on?
  55. 55. no, if it’s available publicly via a browser
  56. 56. yes, if it’s an intranet or only available as an app
  57. 57. are your users likely to have a preference on the platforms on which to use your product?
  58. 58. options for degree of accessibility to aim for across different platforms?</li></ul>one accessible product for desktop, hope standards will make it work on other platforms<br />as (1) but with UI tweaks (device detection) and accessibility testing on other platforms<br />versions optimised for each platform, including appropriate UI and functionality subset, fully tested<br />
  59. 59. BS8878 Product process -3rd stage: production, launch and maintenance<br />
  60. 60. Quality of data<br />User testing<br />Remote testing<br />User reviews / interviews<br />Expert walkthrough<br />Heuristics<br />Testing with assistive technologies<br />Automated testing<br />14.Assure the product’s accessibility through production<br /><ul><li>creating an accessibility test plan
  61. 61. which testing methods will be used…
  62. 62. at what points of the production process…
  63. 63. sticking to the plan
  64. 64. finding out whether you are achieving your target degree of UX
  65. 65. when the ideal isn’t possible… </li></ul>Cost<br />
  66. 66. 15. Communicate accessibility decisions at launch<br /><ul><li>working out which compromises you can launch with… and which you can’t…
  67. 67. achieving the minimal viable product and managing accessibility risk
  68. 68. communicating all those decisions & compromises to your audiences…
  69. 69. in an easily found accessibility statement on your website
  70. 70. which your audiences can understand…</li></ul>Confusing help text: A number of sites accessed by participants provided help pages which were so technical that they were practically useless. Mention of plugins and cookies resulted in complete confusion by the users and apprehension about whether they were able to follow the instructions given.<br />
  71. 71. Summary: in a team/organisation that follows BS8878<br /><ul><li>you’ll be expected to take accessibility seriously by product managers
  72. 72. you’ll be in a team where each member knows what accessibility expects from them
  73. 73. they’ll ask you to follow a user-centred design process(like I guess you want anyway)
  74. 74. they’ll ask you for/give you real-world user-research to help good decision making
  75. 75. you’ll be empowered to make decisions re accessibility, as long as you can justify them, and write them down
  76. 76. you’ll have the freedom to create product variations where users’ needs diverge
  77. 77. you’ll have a place to find best practice help for accessible design beyond the web
  78. 78. you’ll be asked to test products for accessibility, alongside usability, to the level the budget will allow (and they’ll be aware of the limited benefits of cheap options)
  79. 79. you’ll be freed from the impossibility of doing everything you could possibly do for v1.0, as long as you tell your audience why and when they’ll get what they need</li></li></ul><li>Innovation<br />Embedding<br />Standards<br />Strategy & research<br /><br />
  80. 80. Standards for the next generation of accessibility - BS8878<br />Jonathan HassellChair, BSI IST/45Head of Usability & Accessibility, BBC Future Media<br />BTAT Technical Swapshop<br />11th February 2011<br />e: jonathan@hassellinclusion.comt: @jonhassellw:<br />