Testing Compliance with Accessibility Guidelines

W6

Special Topics

10/15/2014 11:30:00 AM

Testing Compliance with

Accessibility Guidelines

Presented by:

Anish Krishnan

Hexaware Technologies, Ltd

Brought to you by:

340 Corporate Way, Suite 300, Orange Park, FL 32073 888-268-8770 ∙ 904-278-0524 ∙ [email protected] ∙ www.sqe.com

Anish Krishnan

Hexaware Technologies, Ltd Anish Krishnan is an experienced strategic consultant involved in defining testing strategies and test solutions for large transformational programs. His consulting strengths include process optimization, engagement planning, and estimation strategies for financial clients. With significant experience understanding client’s “as-is” process maturity, Anish helps create tailor-made processes to align with the client’s maturity goals. He brings in strong testing project lifecycle experience with hands-on end-to-end operations. Anish is QAI certified CSQA (Certified Software Quality Analyst) and HP certified HP2-N32 ALM Sales Certified.

http://starwest.techwell.com/sme-profiles/anish-krishnan

Testing Compliance with Accessibility Guidelines

Presented By: Anish Krishnan

Email Id: [email protected]

Organization: Hexaware Technologies 152, Sector -III,

Millennium Business Park, A - Block, TTC Industrial

Area, Mahape, Navi Mumbai - 400 710 (India)

2 © Hexaware Technologies. All rights reserved.

AGENDA

Accessibility Testing

Need for Accessibility

1

Myths about Accessibility

2

Disabilities Coverage

3

Standards and Guidelines Coverage

4

Accessibility Scenarios

5

Accessibility Testing Methodology

6

Accessibility Testing Techniques

7

Web and Mobile Accessibility Testing Tools

8

9


ACCESSIBILITY TESTING

What is Accessibility Testing ?



“ACCESSIBILITY = ACCESS + ABILITY”



A web application is deemed to be “ACCESSIBLE” if it can

be used as effectively by people with disabilities as by those

without.


NEED FOR ACCESSIBILITY

1st Reason - Target Population

27% internet users have special needs

when it comes to accessing the internet

10% of population has some form of

disability



2nd Reason – Accessibility Legislation

The Americans with Disabilities Act

(1990)

Equal Opportunities Right (2004)

Disability act of 2005

Disability Discrimination Act (1992)

Dutch law on Quality of Government

Websites (2006)



3rd Reason – Potential Lawsuits

National Federation for the Blind (NFB)

versus Amazon settlement (2007)

Sexton and NFB versus Target Lawsuit

(2007)

California Council for the Blind versus

Bank of America & Wells Fargo ATM

settlements in Florida and California

(2000)

NFB versus AOL settlement (1999)


MYTHS ABOUT ACCESSIBILITY

Accessibility is “ONLY” for Disabled



Accessibility is “UGLY” and “BORING”



Accessibility is “EXPENSIVE” and “TIME-

CONSUMING”



Automated tools are “ENOUGH”


DISABILITIES COVERAGE

Disabilities

Visual Impairments

Hearing Loss

Motor Impairments

Cognitive Impairments

Color Blindness


GUIDELINES COVERAGE

Standards / Guidelines

WCAG 1.0

14 Guidelines

65 Check Points at 3 levels

WCAG 2.0

12 Guidelines

38 Check Points at 3 levels

Section 508

12 Guidelines

ADA (American with Disabilities Act)

61 Check Points


WEB CONTENT ACCESSIBILITY GUIDELINES (WCAG) 1.0

WCAG consist of a set of guidelines for making content more accessible, primarily for disabled users. The guidelines are part of

the series of Web Accessibility guidelines published by W3C (World Wide Web Consortium)’s Web Accessibility Initiative. The

WCAG 1.0 was published in 1999. It has three priority levels as shown in below table.

Priority Description Conformance

1 Developers must satisfy these requirements A

2 Developers should satisfy these requirements AA

3 Developers may satisfy these requirements AAA

Guideline Description Check

Points

1 Equivalent alternatives to

auditory and visual content.

5 (4A and

1AA)

2 Don't rely on color alone. 2 (A and AA)

3 Use markup and style sheets

and do so properly. 7 (AA)

4 Clarify natural language

usage

3 (1A and

2AAA)

5 Create tables that transform

gracefully.

6 (2A, 2AA

and 2AAA)

6 Ensure that pages featuring

new technologies transform

5 (3A and

2AA)

7 Ensure user control of time-

sensitive content changes.

5 (1A and

4AA)


Points

8 Ensure direct accessibility of

embedded user interfaces. 1 (AA)

9 Design for device-

independence.

5 (1A, 2AA

and 2AAA)

10 Use interim solutions. 5 (2AA and

3AAA)

11 Use W3C technologies and

guidelines.

4 (2AA, 1A

and 1AAA)

12 Provide context and

orientation information.

4 (1A and

1AA)

13 Provide clear navigation

mechanisms.

10 (4AA and

6AAA)

14 Ensure that documents are

clear and simple.

3 (1A and

2AAA)


WEB CONTENT ACCESSIBILITY GUIDELINES (WCAG) 2.0

WCAG 2.0 was published as a W3C recommendation in 2008 and is the current version. It uses the same three levels of

conformance as WCAG 1.0. WCAG 2.0 works on 4 principles of ‘POUR” .i.e.

P - Perceivable

O - Operable

U - Understandable

R - Robust

The WCAG working group maintains an extensive list of web accessibility techniques, 12 guidelines, 61 success criteria

and failure cases for WCAG 2.0.


Points

1 Provide text alternatives for

non-text content 1 (A)

2 Provide captions and other

alternatives for multimedia

5 (3A and,

2AA)

3

Create content that can be

presented in different ways,

without losing meaning.

3 (A)

4 Make it easier for users to

see and hear content

5 (2A and,

3AA)

5 Make all functionality

available from a keyboard 2 (A)

6 Give users enough time to

read and use content 2 (A)


Points

7 Do not use content that

causes seizures 1 (A)

8 Help users navigate and find

content

7 (4A and

2AA)

9 Make text readable and

understandable

2 (1A and

1AA)

10 Make content appear and

operate in predictable ways

4 (2A and

2AA)

11 Help users avoid and correct

mistakes

4 (2A and

2AA)

12 Maximize compatibility with

current and future user tools 2 (A)


SECTION 508

Principles Description Test Coverage

Perceivable

Information and user interface components

must be presentable to users in ways they

are recognizable by assistive technologies.

4 Guidelines

22 Success Criteria (Level A)

Operable The user must be able to use navigation

and other components of the user interface.

4 Guidelines


Understandable

The user must be able to

comprehend information and how the user

interface works.

3 Guidelines


Robust

The content must be presented so that it

can be interpreted reliably by a wide variety

of user agents, including assistive

technologies.

1 Guideline



ADA (AMERICANS WITH DISABILITIES ACT)

ADA prohibits discrimination against people with disabilities in employment, transportation, public accommodation,

communications, and governmental activities. According to this act which has become law in 1990, any website that is

developed to provide goods, services, and programs to the public such as online shopping sites, educational sites etc. in

United States must meet the accessibility accommodations.

Principles Test Coverage

Perceivable, Operable, Understandable, Robust 12 Guidelines


Test Techniques

Screen Reader

Captioning Software

Keyboard

Disabilities Coverage

Visual Impairments

Hearing Loss

Motor Impairments


ACCESSIBILITY SCENARIO - 1

Scenario Screen Reading Software

Recommended /

Available Tools • Job Access with Speech (JAWS) ,VoiceOver, Speakup

Standards

Supported • WCAG 1.0, WCAG 2.0, Section 508, ADA

Tools -

Supported OS • JAWS – Windows, VoiceOver – MAC OS and Speakup – Linux

Description &

Test Approach • Screen Reader reads information aloud displayed on the screen, or entered on the keyboard.

• Screen Reader uses a Text-To-Speech (TTS) engine to translate on-screen information into

speech, which can be heard through earphones or speakers.

• Standards coverage and tool selection is carried out, once we have the Accessibility requirements

in place.

• Screen Reader Software is mainly used for Visually Impaired users.

• Application is navigated using the short-cut keys and the audio from the tool is verified / tested.



Scenario Voice Recognition Software

Recommended /

Available Tools • Dragon Naturally Speaking, Talking Desktop, Dragon Mobile Assistant

Standards

Supported • WCAG 2.0, Section 508, ADA

Tools -

Supported OS • Dragon Naturally Speaking – Android, MAC OS ,Talking Desktop – Windows

Description &

Test Approach

• Voice Recognition Software is used for users who struggle with writing due to a learning disability,

like Dyslexia, where spelling and typing can be frustrating and difficult.

• Voice recognition software has the capability of streamlining your work flow, allowing you to work

as fast as you can speak instead of as fast as you can type and move the mouse.

• The biggest advantage is speed. Voice is 3x faster than typing. While there is a learning curve

while you master the commands, once you are familiar with the program you can actually

navigate your computer and dictate documents faster than you could with a keyboard and mouse.

• The other advantage is the ability to do hands-free computing.

http://www.google.co.in/url?sa=i&source=images&cd=&cad=rja&uact=8&docid=TYBM_KSFTjXqzM&tbnid=r3gM9UEkjFhv8M&ved=0CAgQjRw&url=http://www.techpraveen.com/2011/08/e-speaking-control-your-pc-through-your-voice.html&ei=Q1JRU5OnD8aGrgfkqIHACw&psig=AFQjCNFr8djR-fh557YByYtb8ESwOPjt-Q&ust=1397924803352585



Scenario Screen Magnification Software

Recommended /

Available Tools • Zoom Test , MAGic

Standards

Supported • WCAG 2.0, Section 508, ADA

Tools -

Supported OS

• Zoom Test – Microsoft Windows operating systems 2000, XP, Vista and Windows 7

• MAGic - Windows

Description &

Test Approach

• A screen magnifier is software that interfaces with a computer's graphical output to present

enlarged screen content.

• It is a type of assistive technology suitable for visually impaired people with some functional

vision.

• Screen magnification software programs are loaded into the computer's memory, and remain

active so as to magnify the text and graphics that appear in programs and applications run

thereafter.



Scenario Captioning Software

Recommended /

Available Tools • Bobby

Standards

Supported • WCAG 1.0, WCAG 2.0, Section 508, ADA

Tools -

Supported OS

• Bobby - Windows

Description &

Test Approach • A captioned video contains text that transcribes the narration and provides descriptions of the

sounds and music that are present.

• One of the Myth around this software is that this is for use by people with hearing difficulties, but

captions also benefit people who aren’t native speakers of the language used in the video, for

those unfamiliar with the vocabulary of a discipline, and sometimes to allow interactive searches

within the video.

• Captions can be either closed or open. Closed captions can be turned on or off.

• Captioning Software is mainly used for Hearing Impaired users.

http://www.google.co.in/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&uact=8&docid=r2j1cI01-XIvXM&tbnid=NXkO0BbTl-27lM:&ved=0CAUQjRw&url=http://www.subply.com/&ei=DOtRU7fnG8mJrQfyy4CABw&bvm=bv.65058239,d.bmk&psig=AFQjCNHrg_BZYHAT_4aNdazCcoLZHmdfEA&ust=1397963579581218


ACCESSIBILITY TESTING METHODOLOGY

Entry Criteria

• Non Functional

Requirements

Activities

• Understand user

groups and their

special needs

Deliverables

• Accessibility

testing checklist

(includes

standards)

• List of disability

scenarios

Entry Criteria

• Accessibility

testing checklist

Activities

• Plan how to

involve disable

users (real

users/simulation)

• Identify tools and

assistive

technologies

• Training plan for

accessibility

testers

Deliverables

• List of tools and

assistive

technology

products to be

procured

Entry Criteria

•List of disability

scenarios to be

tested

Activities

•Identify all

probable tasks

which user

would perform

on the site

•Identify all

possible

business flows

for the selected

tasks

•Develop test

cases for every

business flow

Deliverables

•Accessibility

test cases

•Test setup plan

Entry Criteria

•Test execution

results report

Activities

Causal analysis

of defects

Deliverables

Root Cause

Analysis Report

Test Requirements

Elicitation

Test

Strategizing

Test

Environment

Setup

Test

Execution

Defect

Analysis

Entry Criteria

•Accessibility

test setup plan

Activities

•Setup the

machine/s with

appropriate

assistive

technologies

• Install and

configure

necessary

testing tools

Deliverables

•Accessibility

test

environment is

ready

Entry Criteria

•Test Environment

is setup

•Application to

be tested is

available for use

•Accessibility test

cases are ready

Activities

•Executes test

cases and cross

check with

accessibility

checklist

•Use automated

compliance tools to

verify compliance

•Log Accessibility

defects

Deliverables

Accessibility test

results report

Test

Planning


ACCESSIBILITY TESTING TECHNIQUES

Manual

Testing

Manual +

Automated

Automated

Testing

1 2 3


WEB & MOBILE ACCESSIBILITY TOOLS

Tool

License Standards / Guidelines OS

Open

Source

Commerci-

al

WCAG

1.0

WCAG

2.0

Section

508 ADA

Window

s Linux MAC Android

JAWS

VoiceOver

Speakup

Dragon

Naturally

Speaking

Talking Desktop

Zoom Test

Magic

Bobby

A-Checker

WAVE

WebKing


Q&A


www.hexaware.com

© 2013 Hexaware Technologies Limited. All rights reserved. For internal circulation only. Neither this publication nor any

part of it may be reproduced, stored in a retrieval system or transmitted in any form or in any means, electronic,

mechanical, photocopying, recording or otherwise, without prior permission of Hexaware Technologies Limited.

Published by Corporate Marketing & Communications

Thank You

Testing Compliance with Accessibility Guidelines

Technology

Testing Compliance with Accessibility Guidelines