Beyond WCAG: Experiences in Implementing BS 8878 E.A. Draffan with thanks to Ronise Nepomuceno

Bumpy ride

Project Organisation

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

Requirements Gathering Content Manager fills requirement form - this refers to Steps 1 to 6 of BS 8878:2010 Analyse Requirements Allocation to the correct team – work through Steps 7 to 12 Production

The process Customer /Content manager logins into Web4All site Chooses new product or checks product’s life cycle

Products relationship with target audience and their needs

Steps 4-6 No guarantee this is a smooth pathway – prepare to revisit steps.

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

Usability and Accessibility Assurance In-House evaluations Web2Access public version without test for templates and content evaluation. User testing Exceptions Report

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.

Communication, Maintenance and Training

Progress to date… Maintenance and training in the pipeline Monitoring outcomes of the project still to be achieved.

Thank you Dr Mike Wald, E.A. Draffan plus the Access Technologies Team, ECS University of Southampton Ronise Nepomuceno, iSolutions, University of Southampton ut_wau/