THE PRINCIPLES OF WCAG 2 Website Accessibility Overview

THE PRINCIPLES OF WCAG 2 Website Accessibility

Overview • • What is Accessibility? Guidelines Conformance Planning

Accessibility • More than just for blind people • More than for disabled people • Accessibility is for everyone • Old devices • Mobile devices • Search engines

The law • Confusion • Lack of clear legislation • Disability Discrimination Act – “provision of services”, which might include websites • Numerous guidelines

WCAG 2 • W 3 C’s Web Content Accessibility Guidelines • Released 2008 to replace 1999’s WCAG 1 • Some controversy • Greatly improved • http: //www. w 3. org/TR/WCAG/

Structure • Three tiers: • • Principles Guidelines – goals to work towards Success criteria – measurable/testable (Techniques – ideas for how to achieve)

Principle 1: Perceivable • Information and user interface components must be presentable to users in ways they can perceive • Text alternatives • Time based media (incl live) – transcript, captions, audio desc, sign lang • Adaptable – e. g. Simpler layout • Distinguishable – colour, contrast, audio, text, layout

Principle 2: Operable • User interface components and navigation must be easy to use whatever disability someone may have • Keyboard access – all functionality, no traps • Enough time – turn off/adjust/extend, pause/stop/hide • Seizures – max 3 flashes per second • Navigable – title, headings, links, labels, bypass, focus

Principle 3: Understandable • Information and operation of the user interface must be understandable • Readable – language, abbrev, jargon, age • Predictable – navigation, no surprises • Input assistance – errors, instructions, suggestions, help, prevention

Principle 4: Robust • Content must be robust enough that is can be interpreted reliably by a wide variety of user agents, including assistive technologies • Compatible – good, standard, semantic markup

Conformance • • • A, AAA Each success criterion has a level Levels are being played down Users’ needs are more important Page-by-page (processes) Unfeasible to have AAA site-wide?

Start with the basics • Work towards conformance • Start with the “quick wins”, e. g. • • • Alt & title attributes Media alternatives Java. Script (progressive enhancement) Resizable text Standards based Single A

Improve where you can • • Consult with your community Test with real users Identify and deal with major issues first Build to AA and AAA on some pages

Complaints • Complaints need to be addressed quickly and thoroughly • Can you be sued? Yes. • Is there precedent? Sort of.

Planning • • Establish approach with your client/agency Remain pragmatic Have a reason for any non-compliance Think of accessibility from the start

Responsibility • Everybody’s responsibility • Principles • Guidelines • Success criteria • Check everything • Needs to be second nature

More information • oxfordcc. co. uk/accessibility • Slides • Links • Other resources