Beyond WCAG: Experiences in Implementing BS 8878
•Télécharger en tant que PPTX, PDF•
0 j'aime•448 vues
This document discusses implementing the British Standard BS 8878 on web accessibility. It outlines the stakeholders involved, including site owners, editors, university staff and students. It describes the requirements gathering process, including filling out requirement forms to analyze needs and allocate work. It discusses strategic decisions around feasibility, who will develop the site, and using an agile user-centered design process with customer evaluation. It also recommends what an accessibility statement should contain.
Recommandé
Contenu connexe
Tendances
Similaire à Beyond WCAG: Experiences in Implementing BS 8878
Similaire à Beyond WCAG: Experiences in Implementing BS 8878 (20)
Plus de E.A. Draffan
Plus de E.A. Draffan (20)
Dernier
Dernier (20)
Beyond WCAG: Experiences in Implementing BS 8878
- 1. Beyond WCAG: Experiences in Implementing BS 8878 E.A. Draffan with thanks to Ronise Nepomuceno
- 4. Stakeholders • Who will be involved from the customer / user side? • - Site owners and editors; university staff and students when operating as an end user of a site • Who are the other stakeholders? – Student Union representatives; – Staff Representatives; – Head of Student Services and Student Admin; – Head of Professional Services; – Head of Faculties
- 5. Requirements Gathering Content Manager Allocation to the fills requirement Analyse correct team – form - this refers Production Requirements work through to Steps 1 to 6 of Steps 7 to 12 BS 8878:2010
- 7. Products relationship with target audience and their needs http://flic.kr/p/4tgef9
- 8. Steps 4-6 No guarantee this is a smooth pathway – prepare to revisit steps.
- 9. Strategic Decisions • Feasibility –pre-configuration or procurement –Who will develop? How? When? User Centred Design process – Agile at all times! Evaluation by customer. Development – testing
- 11. Accessibility Statements Nomensa suggest they contain: • An open commitment to providing an accessible website; • An outline of key guidelines and standards the website follows; • Any known exceptions to the intended level of web accessibility; • Contact information for reporting difficulties with the website.
- 14. Thank you Dr Mike Wald, E.A. Draffan plus the Access Technologies Team, ECS University of Southampton http://access.ecs.soton.ac.uk Ronise Nepomuceno, Project manager WAU, iSolutions, University of Southampton http://www.southampton.ac.uk/web4all/abo ut_wau/
Notes de l'éditeur
- Web Accessibility and Usability Implementation projectA project designed to implement policies across a whole institution is not always going to have an easy ride. This is particularly true when it is linked to the usability and accessibility of online resources because there are so many individuals involved in a wide ranging collection of web products.
- Project Sponsor:Diversity Office Manager Executive:HR Policy ManagerHR Diversity Officer Director of CommunicationsDirector of IsolutionsUniversity Legal Team Senior Suppliers:Web Applications ManagerCoaching and Training Services ManagerDigital Media Manager Senior Users: Student RepresentativeStaff RepresentativeDDA Group Representative Project Manager: iSolutions Project Team (to be confirmed):Test ManagerComms (Designer?)TrainingInformation AnalystInformation AnalystDeveloper
- 1- Content manager fills requirement form - this refers to Steps 1 to 6 of BS 8878:2010Content Manager triggers the process when logging into Web4All Sharepoint site from the 'Request a Web Product* section of the Web4All main site. There they also find an array of resources to help them to understand and engage with the process of accessible and usable web products.2. step 1 is analysed and allocated to the relevant team.3. Once allocated to the correct team, then we work through steps 7 to 124. Production
- Define the purpose.Define the target audience.Analyse the needs of the target audience.Note any platform or technology preferences.Define the relationship the product will have with its target audience.Define the user goals and tasks.Consider the degree of user experience the web product will aim to provide.Consider inclusive design & user-personalised approaches to accessibility.
- lead by the Information Analyst, Business Analyst or Web Developer with the customer.ISO 13407 taken from http://www.usabilitynet.org/tools/13407stds.htmHuman centred design processes for interactive systemsISO 13407 provides guidance on achieving quality in use by incorporating user centred design activities throughout the life cycle of interactive computer-based systems. It describes user centred design as a multi-disciplinary activity, which incorporates human factors and ergonomics knowledge and techniques with the objective of enhancing effectiveness and productivity, improving human working conditions, and counteracting the possible adverse effects of use on human health, safety and performance.There are four user centred design activities that need to start at the earliest stages of a project. These are to:understand and specify the context of usespecify the user and organisational requirementsproduce design solutionsevaluate designs against requirements.The process involves iterating until the objectives are satisfied.The sequence in which these are performed and the level of effort and detail that is appropriate varies depending on the design environment and the stage of the design process.
- The provision of information which is easier to find and absorb and has a measurable quality through compliance with WCAG 2.0 level AA, BS 8878 and ISO 13407 Delivering inclusive websites http://coi.gov.uk/guidance.php?page=131 The minimum standard of accessibility for all public sector websites is Level Double-A of the W3C Web Content Accessibility Guidelines. All new websites must conform to these guidelines from the point of publication.