web for all

Web For All

Digital Inclusion Divison

March 2012

Office of the Government Chief Information Officer

Agenda • Digital 21 Strategy and Inclusive Society

• What is Web Accessibility?

• Why Web Accessibility?

• Major Concerns from Persons with Disabilities with Recommendations

• International Standard

• International & Government practices

• Web Accessibility Campaign

• Start your Web Accessibility Project

Digital 21 Strategy & Inclusive Society

One of five key areas of 2008 Digital 21 Strategy

• Building an inclusive, knowledge-based society

• bring the benefit of ICT to disadvantaged groups

• enhance their quality of life

• strengthen their capacity in engaging with the development of information society

What is Web Accessibility?

• Making website content available for ALL

• Including persons with disabilities

What is Web Accessibility?

• An accessible website －

•Adjustable

font size

•Sufficient

colour

contrast

•Audio

control

•Screen reader

•Input devices

for persons

with disabilities

•Voice control

software

•Text

transcript for

multi-media

contents

•Some people

have

difficulties

using the

mouse

Can be used with assistive device

Provides additional

descriptions

Reduces impediments

Is perceivable

• Equal opportunities • for persons with disabilities, elderly, etc.

• Social responsibility

• Widest possible reach-out

• Lower costs in the long term

Why Web Accessibility?

• Engage rehabilitation organisations

• Receive surveys from over 300 persons with disabilities

• Understand major problems in accessing websites

Major concerns from persons with disabilities with recommendations

1. Unable to skip Adobe Flash and moving objects


2. Small font sizes or insufficient colour contrast


• Example 1 – Resize Text

All text can be resized up to 200%


Cannot resize text Can resize text

• Example 2 – Colour Contrast

Contrast ratio of at least 1: 4.5


Poor background contrast Easier to read with higher contrast

3. No alternatives for non-text information

• Descriptive text alternative

for image

• Text transcripts for audio

and video

Web Accessibility

Management

Handbook


• Example 3 – Avoid Non-text Content

Text alternative for all content


Screen reader can not read the picture

Description of the picture can be read by screen reader

Major concerns from persons with disabilities with recommendations 4. Complicated website structure

Simpler and ordered website structure Complicated website structure

Major concerns from persons with disabilities with recommendations 5. Missing heading structure

• Provide appropriate heading structure for screen readers

Missing heading structure Appropriate heading structure

Major concerns from persons with disabilities with recommendations 6. Images of text

• Do NOT use images to display text as screen readers cannot read text inside an image

An image of text heading Text heading

Major concerns from persons with disabilities with recommendations 7. Content and functions inaccessible by

keyboard

• Ensure all content and functions can be accessed via a keyboard, e.g. through Tab key and the Enter key

Major concerns from persons with disabilities with recommendations 8. Websites with background audio

Major concerns from persons with disabilities with recommendations 9. Difficulties in accessing PDF documents

PDF documents not accessible Text-based accessible PDF

Major concerns from persons with disabilities with recommendations 10. Outdated text versions

• Keep the text-only versions updated

• Prevent asymmetrical contents with the graphical versions

• When graphical version is verified to be accessible, text-only version may be considered to remove

International Standard

• World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG)

• International widely adopted standard

• Latest version is 2.0

International Standard

• W3C WCAG 2.0 consist of four parts

4 Principles

12 Guidelines

61 Success Criteria

Many Techniques

Guidelines for Perceivable

1.1 Provide text alternatives for any non-text content so that it can be changed into other forms people need.

1.2 Provide alternatives for time-based media.

1.3 Create content that can be presented in different ways without losing information or structure.

1.4 Make it easier for users to see and hear content including separating foreground from background.

2.1 Make all functionality available from a keyboard.

2.2 Provide users enough time to read and use content.

2.3 Do not design content in a way that is known to cause seizures.

2.4 Provide ways to help users navigate, find content, and determine where they are.

Guidelines for Operable

3.1 Make text content readable and understandable.

3.2 Make Web pages appear and operate in predictable ways.

3.3 Help users avoid and correct mistakes.

4.1 Maximize compatibility with current and future user agents, including assistive technologies.

Guidelines for Understandable & Robust

International and Government Practices

Countries Standard Timeline to achieve standard

New Zealand WCAG 2.0 Level AA June 2010

United Kingdom WCAG 1.0 Level AA March 2011

Canada WCAG 2.0 Level AA July 2013

Singapore WCAG 1.0 and key aspects of WCAG 2.0

December 2013

Australia WCAG 2.0 Level A & Level AA

December 2014

• Some governments are adopting W3C WCAG 2.0 for public facing websites


• In latest version (Version 2.0) there are three Levels of conformance -

Level A 25 success criteria

Level AA +13 success criteria

Level AAA +23 success criteria

Basic Recommended Ideal

Level AA Conformance

• HK Government has been implementing web accessibility guidelines since 1999, based on a version of W3C WCAG

• HK Government websites, except archive materials, are required to conform to W3C WCAG 2.0 Level AA by 2013

• Encourage quasi-government and public service organisations to take corresponding action


Web Accessibility Campaign

Launched in 2011 -

• Focus group discussion

• Survey with persons with disabilities

• Management handbook

• Portal with Illustration webpages

(www.webforall.gov.hk)

• Awareness building seminars

Web Accessibility Campaign

Upcoming events

• Experience sharing sessions &

Technical workshops

• Ethics building in tertiary education institutions

• Recognition scheme

Start Your Web Accessibility Project

Assess the Whole Website

• Consider rearranging the structure

• Simplify content

• Use simple HTML code can help a lot • Alternative text for image, alt= • Keyboard input, onkeypass= • Define language, lang=

• Testing

Testing Techniques

1. Code Scanning

• Many accessibility issues can be detected automatically using specialist software and tools.

Example Tools - AChecker WAVE Web Accessibility Checker

Testing Techniques

2. Manual Screen Reader Testing

Example Tools - Jaws VoiceOver Window Light

• Navigate your website and determine just how much information you’re able to access through the screen reading software.

Testing Techniques

3. Human Testing – preferably by persons with disabilities

• Many organisations that support persons with disabilities can help by providing free or affordable human testing services.

• Website owners are encouraged to contact these organisations for assistance.

Questions and Answers

Web For All At the time building fast application

and using modern technology

Adopt accessibility design

Join hands to make Hong Kong a caring and inclusive IT hub

Thank you

web for all

Technology