Testing Compliance with Accessibility Guidelines

  • View
    195

  • Download
    6

Embed Size (px)

Text of 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 sqeinfo@sqe.com 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 clients as-is process maturity, Anish helps create tailor-made processes to align with the clients 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.

  • Testing Compliance with Accessibility Guidelines

    Presented By: Anish Krishnan

    Email Id: AnishK@hexaware.com

    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

  • 3 Hexaware Technologies. All rights reserved.

    ACCESSIBILITY TESTING

    What is Accessibility Testing ?

  • 4 Hexaware Technologies. All rights reserved.

    ACCESSIBILITY TESTING

    ACCESSIBILITY = ACCESS + ABILITY

  • 5 Hexaware Technologies. All rights reserved.

    ACCESSIBILITY TESTING

    A web application is deemed to be ACCESSIBLE if it can be used as effectively by people with disabilities as by those

    without.

  • 6 Hexaware Technologies. All rights reserved.

    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

  • 7 Hexaware Technologies. All rights reserved.

    NEED FOR ACCESSIBILITY

    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)

  • 8 Hexaware Technologies. All rights reserved.

    NEED FOR ACCESSIBILITY

    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)

  • 9 Hexaware Technologies. All rights reserved.

    MYTHS ABOUT ACCESSIBILITY

    Accessibility is ONLY for Disabled

  • 10 Hexaware Technologies. All rights reserved.

    MYTHS ABOUT ACCESSIBILITY

    Accessibility is UGLY and BORING

  • 11 Hexaware Technologies. All rights reserved.

    MYTHS ABOUT ACCESSIBILITY

    Accessibility is EXPENSIVE and TIME-CONSUMING

  • 12 Hexaware Technologies. All rights reserved.

    MYTHS ABOUT ACCESSIBILITY

    Automated tools are ENOUGH

  • 13 Hexaware Technologies. All rights reserved.

    DISABILITIES COVERAGE

    Disabilities

    Visual Impairments

    Hearing Loss

    Motor Impairments

    Cognitive Impairments

    Color Blindness

  • 14 Hexaware Technologies. All rights reserved.

    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

  • 15 Hexaware Technologies. All rights reserved.

    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)

    Guideline Description Check

    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)

  • 16 Hexaware Technologies. All rights reserved.

    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.

    Guideline Description Check

    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)

    Guideline Description Check

    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)

  • 17 Hexaware Technologies. All rights reserved.

    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

    20 Success Criteria (Level A)

    Understandable

    The user must be able to

    comprehend information and how the user

    interface works.

    3 Guidelines

    17 Success Criteria (Level A)

    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

    2 Success Criteria (Level A)

  • 18 Hexaware Technologies. All rights reserved.

    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

    61 Success Criteria (Level A)

    Test Techniques

    Screen Reader

    Captioning Software

    Keyboard

    Disabilities Coverage

    Vi