BS8878 Web Accessibility Code of Practice

BS8878 Web Accessibility Code of Practice

Leonie WatsonChair of the British Computer Association of the Blind (BCAB)

@WeAreBCAB@WeAreBCAB @LeonieWatson@LeonieWatson

What is BS8878?

It’s a UK national standard

• From the British Standards Institution (BSI).

It’s a framework

• For making eAccessibility “business as usual” within an organisation.

It’s not a substitute

• For existing legislation, guidelines or standards.

Why was BS8878 created?

The changing technological landscape

• It could no longer be assumed that people were accessing the web from a desktop.

The changing political landscape

"Promoting digital inclusion is essential for a dynamic modern economy and can help to make government more efficient and effective.“(David Cameron)

The changing legal landscape

• The Equality Act would replace the Disability Act in 2010.

Who wrote BS8878?

Industry professionals

• People with a strong background in accessibility and digital inclusion.

Disability organisations

• People with disabilities, and representatives from disability organisations.

How was BS8878 created?

In 2005...

• Research from the Disability Rights Commission (DRC) revealed that websites were struggling with accessibility.

In 2006...

• PAS 78 (Guide to good practice in commissioning accessible websites) was released.

In January 2008...

• Work began to transform PAS 78 into a British Standard (BS8878)

In November 2008...

• First draft of BS8878 was made available for widespread public consultation.

In May 2010...

• A second draft of BS8878 was made available for public consultation, receiving international comment.

In December 2010...

• BS8878 (Web Accessibility Code of Practice) was officially released.

How does BS8878 work?

Assigning responsibility

• Responsibility for eAccesssibility should be assigned to a role or department;

• That role or department should be empowered to fulfil that responsibility.

Creating an eAccessibility policy

• A document that explains an organisation’s commitment to accessibility, and summarises its approach.

Introducing web products

• Any website, web service or web application delivered over IP.

Creating a web product policy

• A living document that evolves throughout the web product’s entire lifecycle;

• Based on the intentions of the organisational policy, but tailored to a particular web product.

How is a web product policy created?

Document the accessibility journey.

Research and requirements

Step 1: Define the purpose of the web product

• What is the purpose of the web product, and what will people expect to achieve when they use it?

Step 2: Define target audiences

• Is the web product internal or public facing, and is it aimed at a particular group of people?

Step 3: Needs of the target audiences

• What are the general needs of the target audiences, and do they have specific needs in relation to the web product?

Step 4: Platform and technology

• Are the target audiences restricted in their technology, perhaps because of cost, confidence or compatibility?

Step 5: Relationship with target audiences

• Will the web product enable personalised choices through a login or cookie, or will it support more general groups of people.?

Step 6: Tasks and goals

• What are the goals someone will be able to complete, and what are the tasks they will use to achieve those goals?

Strategic Choices

Step 7: Level of user experience.

• Will the web product offer a technically accessible, useably accessible, or enjoyably accessible experience?

Step 8: Accessibility approach

• Will the web product take an inclusive design approach, offer user personalisation, or a combination of both?

Step 9: Delivery platform

• Will the web product be optimised for a particular platform, or be part of a suite of platform specific versions?

Step 10: Target technologies

• Which operating systems, browsers and assistive technologies will the web product support?

Procurement

Step 11: Create or procure

• Will the web product be created in-house or procured externally, and how do you ensure third party solutions are accessible?

Production

Step 12: Web technologies

• Do the technologies used to build the web product support accessibility, and do they expose information to assistive technologies?

Step 13: Web guidelines

• What are the best accessibility standards available for the chosen technologies, and how will the web product conform to them?

Evaluation

Step 14: Assure accessibility

• What is the accessibility test plan, and how will it be evaluated throughout development of the web product?

Step 15: Communicate clearly

• What will the accessibility statement say, and how will it be made available throughout the web product?

Post Launch

Step 16: Maintaining accessibility

• How often will updates be planned, and what is the process for continually reviewing and evaluating the web product?

What else does BS8878 offer?

Lots of helpful guidelines

• Inclusive design guidelines;• Personalisation guidelines;• Guidelines for non computer platforms;• Guidelines for older people.

Useful advice on assuring accessibility

• Gathering requirements;• Creating a test plan;• Testing methods;• Post launch programmes.

Even more helpful annexes

• 15 annexes providing supporting information, guidance and example documentation.

Why is BS8878 a British standard?

Legal and cultural specifics

• BS8878 references UK law, and contains guidance on user requirements that is culturally oriented towards UK citizens.

How can BS8878 be applied internationally?

Core principles

• BS8878 encourages the consideration of accessibility throughout a web product’s lifecycle, and its core principles can be followed in any organisation.

Where can I find out more about BS8878?

BS8Case studies and making BS8878 international

• Jonathan Hassell (Hassell Inclusion);• Friday 1.50pm, Madeleine AB 3rd floor;• http://www.hassellinclusion.com/bs8878/

Any Questions?

Thank you

• Léonie Watson• Email: chair@bcab.org.uk • Twitter: @LeonieWatson• W. bcab.org.uk