Web accessibility workshop 1

transcript

Design for ALL 1

Web Accessibility WorkshopSession One

Vladimir Tomberg, PhDTallinn University

03.03.2016

2Web Accessibility Workshop

Using Mac Lab

Login: kasutajaPassword: apple

Introduction

https://www.youtube.com

Course Evaluation Criteria

• Work in class gives 20% of final grade;• There will be four different home assignments;• Fulfillment of each gives 20% of the final grade

Today Workshop

1. Target user groups – Who benefits from accessible Web design?

2. Empathy exercise: using Web with limited abilities

3. Framework for Accessible Web4. WCAG 2.0 – preparing for testing

TARGET USER GROUPS Who benefits from accessible Web design?

Design for ALL

What does Accessibility mean?

The goal of Accessibility is that:

• Users with disabilities have access to and use of information and data that is comparable to that of users without disabilities

(Section 508)

• Disabled users should be able to use a system In the usual way like other users; Without particular difficulties; Without help of others

Who are concerned? (1/3)• People with a physical or cognitive

disability, e.g.: Blind or visually impaired; Deaf or hard of hearing; Mobility or dexterity impaired; Reduced cognitive abilities

Most disabled people became disabled as adults, it can happen to all of us

Who is concerned? (2/3)

• Elderly people often develop disabilities, e.g. Reduced vision, reduced hearing; Reduced mobility or dexterity; Reduced tactile and fine motor abilities; Reduced short-term memory; Dyspraxia (difficulties to plan a task); Dyslexia; Etc.

A book: I Wonder what it's Like to be Dyslexic

• This book aims to provide the reader with design led experience of what it feels like to struggle with reading

Design for ALLSource: http://www.reedeeng.com/

Who is concerned? (3/3)

• It is individually very different, which types of disability a person develops, when it starts, and how severe the disability becomes

• In most cases it is a combination of several disabilities;

• The probability that a person becomes disabled raises with age

Example: UK Disability Statistics

• Almost 1 in 5 people in the UK have a disability;

• There are 5.1 million males with disabilities;• There are 5.8 million females with disabilities;• Only 17% of disabled people were born with

impairments. The majority of disabled people acquire their impairments during their working lives

Source: http://www.mph-uk.com

The impact of ageHow many people have less than “Full ability”?

Source: 1996/97 Disability follow-up survey

Who is concerned?

Most of us will be concerned at some point in our lives

Who else would benefit?

• People with temporary disabilities (e.g., after an accident or stroke)

• Users in a context causing a temporary reduction of abilities (handicapping situation), such as Noisy environment (similar to reduced hearing) Hands engaged in other tasks (similar to reduced mobility) Eyes engaged in other task (similar to reduced vision) Attention on more important task (reduced cognitive

capacity) Limited hardware features of mobile devices, etc. (similar to

various physical handicaps)

Design for All

Is Web accessibility relevant for disabled? (1)

• Internet usage of disabled is higher than average!”The Web is not a barrier to people with disabilities, it is the solution“ (WebAIM);

• Overall, 60% of EU citizens frequently use the Internet; this means that more than 60% of disabled people (>30 Mln) actually use the Internet

• People who already use the Internet will continue to use it when becoming older, as long as it is accessible for them

• eAccessibility is important for a large, increasing number of people!

Is Web accessibility relevant for disabled? (2)

Frequent Internet usage 2008

Overall Female

Age 16-24

Age 25-54

Age 55-74

EU 27 60% 53% 83% 63% 29%

eInclusion Policy and Legislation Worldwide

These are examples; similar regulations exist in most countries.Legislation usually is based on the WCAG by W3C-WAI

eInclusion in Europe

• Initiative eEurope (2000);• Ministerial Declaration “ICT for an Inclusive Society”,

Riga, 2005;• i2010-Strategy – A European information society for

growth and employment (2008);

• eAccessibility is a legal obligation in all European countries;

• All regulations refer to “Web Content Accessibility Guidelines (WCAG)” by W3C-WAI consortium

European Parliament urges stronger public website access law

Two years ago (26.02.2014) European Parliament backed a move by 593 votes to 40, with 13 abstentions, to require EU member states to ensure all public websites are fully accessible, not just those in 12 categories proposed by the European Commission such as social security benefits and enrolment in higher education

Banks, Energy Providers and Public Bodies Should be Subject to Web Accessibility Rules, Vote MEPs

• Just a third of the 761,000 public sector websites in the EU currently conform to "international web-accessibility standards“;

• Organizations whose websites would be subject to the new rules would have one year from the introduction of the new laws to ensure that new content added to their sites complies with the new rules. They would have three years within which to adapt existing content and five years if that content is "live audio“

28 Feb 2014Source: http://www.out-law.com

EMPATHY EXERCISE

Using Web with Limited Abilities

Design for ALL

The First Task (5 min)

• Write a list containing several typical Web sites you use on every day base;

• Describe a couple of usual routine tasks that you implement on each of these Web sites (looking for weather, news, buying a bus ticket, etc.)

Design for ALL

The Second Task (10 minutes)

• Now I want you to throw away your mouse ;) • Then browse the Web doing what you usually

do, and see how you get on with booking your concert (or whatever you like to do)

• Make short notes on your experience and be ready to share it with others

Design for ALL

Some Useful Shortcuts for Safari (and Other Browsers Searchable by Link)

http://www.shortcutworld.com/en/mac/Safari_5.html

FRAMEWORK FOR ACCESSIBLE WEBPrinciples for Accessible UX

Design for ALL

Principles for Accessible UX as a Framework for Web Accessibility

1. People first2. Clear purpose3. Solid structure4. Easy interaction5. Helpful wayfinding6. Clean presentation7. Plain language8. Accessible media9. Universal usability

Design for ALLhttp://goo.gl/Zl9bL3

1. PEOPLE FIRSTDesigning for Differences

People First

When designing for differences, people are the first consideration, and sites are designed with the needs of everyone in the audience in mind

Design for ALL

4 Additional ‘A’ for Persona

• Ability: Information about their ability (physical, cognitive, language) and any assistive technology (AT) they use

• Aptitude: Their current knowledge and ability to make inferences

• Attitude: Their motivation, emotion, risk tolerance, and persistence

• Assistive Technology: Any technology if used or required

Design for ALL

Emily: I Want to Do Everything for MyselfAbility: Cerebral palsy. Difficult to use hands and has some difficulty speaking clearly; uses a motorized wheel chairAptitude: Uses the computer well, with the right input device; good at finding efficient search termsAttitude: Wants to do everything for herself; can be impatientAssistive Technology: • Communicator (AAC) with

speech generator, • iPad, • power wheelchair

• 24 years old• Graduated from high

school and working on a college degree

• Lives in a small independent living facility

• Works part-time at a local community center

Jacob: The Right Technology Lets me Do Anything

• Ability: Blind since birth with some light perception

• Aptitude: Skilled technology user

• Attitude: Digital native, early adopter, persists until he gets it

• Assistive Technology: Screen reader, audio note-taker, Braille display

• 32 years old• College graduate, legal

training courses• Shares an apartment with a

friend• Paralegal, reviews cases and

writes case summaries• Laptop, Braille display, iPhone

Steven: My only Disability is that Everyone Doesn't Sign

• Ability: Native language is ASL; can speak and read lips; uses SMS/IM, Skype, and video chat

• Aptitude: Good with graphic tools, and prefers visuals to text; poor spelling makes searching more difficult

• Attitude: Can be annoyed about accessibility, like lack of captions

• Assistive Technology: Sign language, CART, captions, video chat

• 38 years old• Art school• Graphic artist in a small ad

agency• iPad, iPhone, MacBook Pro;

good computer at work

2. CLEAR PURPOSEWell-Defined Goals

Clear purpose

• Well-defined goals;• People enjoy products that are designed for the

audience and guided by a defined purpose and goals

• These products are recognizable by their straightforward effectiveness, dedication to users’ goals, a direct path to the task at hand, and freedom from confusing clutter or extraneous elements

• The clarity of the design of the OXO products hides the attention to detail that makes them work so well

Example: Oxo Good Grips

Image courtesy of www.phaidon.com

Clear Purpose

Thinking about accessibility from the beginning — “Accessibility First” — is similar to the approach of thinking “Mobile First” to ensure that the design works as well in a screen reader as it does on a small screen

Three Accessibility Strategies1. Universal (or inclusive)

design—one site;2. Equivalent use—includes

alternatives;3. Accommodation—a

separate “accessible” version

3. SOLID STRUCTUREBuilt to Standards

Solid Structure

• A solid structure depends on good coding practice. A site coded to standards, with all information written to be machine-readable, supports use of the site by different browsers or devices, including assistive technology.

• Style sheets separate content from presentation, using code to communicate semantic meaning, such as content structure, emphasis, or function, as well as visual style;

Built to Standards

• Web accessibility relies on the software’s ability to read and understand the content and instructions contained in web pages;

• The more “meta” information you can provide, the better the user experience will be

Design for ALL

Organize Code for Clarity and Flow

• The order of the source code makes a difference to: Web browsers generally Screen readers Search engines

• Content that appears “above the fold” in code will be what gets read first by the software

Design for ALL

Organizing Code

• Pages are organized so that when code is read in the order it appears in the file, it not only makes sense, but it puts the most important information first

Unfriendly Structure Example

Standards for the Web• HTML - (Hypertext Markup Language), a language for describing the

structure of a page, including semantic information, for including interactive links and forms, and for embedding media elements such as images and video

• CSS (Cascading Style Sheets) – a language for describing the presentation aspects of a page, including color, type, and layout

• JavaScript - scripting language for providing interaction and dynamic content• WCAG 2.0 - (Web Content Accessibility Guidelines) - guidelines and

techniques for making websites and web applications accessible to people with disabilities.

• WAI-ARIA (Accessible Rich Internet Applications Suite) – a framework for adding attributes to web documents in order to make actionable elements accessible to people using assistive technology

Design for ALL

Standards for the Web (2)

• User Agent Accessibility Guidelines (UAAG) for web browsers and media players;

• Authoring Tool Accessibility Guidelines (ATAG) for software that creates websites

• A new WAI project, IndieUI (Independent User Interface), is working to create a device-independent way to communicate user actions, such as scrolling, to a web application

Design for ALL

People feel confident using the design because it is stable, robust, and secure

Supporting Standards in Templates

A big hat tip to @AccessibleJoe and all the folks working on making WordPress more accessible, and to Sylvia Eggers, author of the accessible child theme shown here.

4. EASY INTERACTIONEverything Works

Easy Interaction (1)•Making the interaction easy for

people with disabilities is an extension

of making interaction easy for everyone;

•Interactive elements are identified

clearly and are designed to be easy to

Easy Interaction (2)

• IF the site supports interaction with a keyboard, it should allow assistive technology to emulate the keyboard;

• This also requires that the keyboard tab order make sense, matching the visual presentation

Some Complicated Practices: Don’t Require Point-and-Click Interaction

• Hover: Some devices do not support hover, such as touchscreens— hover all you want over a touchscreen, and nothing is going to happen;

• Select: Using “select” to trigger actions is problematic for keyboard users;

• Drag and drop: This style of interaction makes direct manipulation of objects easy, but typically requires a pointing device and dexterity

This feature, collecting bookmarks for related items, requires a mouse to drag and drop items into the list. A simple Add button would make this more accessible

User Control• A site with easy interaction

enables users to control the interface, with large enough controls. It avoids taking unexpected actions for users that they can do on their own;

• Easy interaction also includes both preventing and handling errors in an accessible way

Images: Braille, foot pedal, magnifier, Talking Dial, Voiceover, joystick, audio, high contrast keyboard, Glenda Watson Hyatt and her iPad

Everything Works

People can use the product across all modes of interaction and operating with a broad range of devices.

5. HELPFUL WAYFINDINGGuides Users

Helpful Wayfinding

• In the physical world, we rely on maps, street signs, and how spaces are designed to help us get around;

• With helpful wayfinding, people can navigate a site, feature, or page following self-explanatory signposts

Create Consistent Cues for Orientation and Navigation (1)

• Identify the site. (name of the site and the organization);

• Title the page. ( Title appears in the title bar of the browser, in a bookmarks list, in search results, and it is the first thing announced by screen reader software);

• Provide good headings. (describe the main topic of the page, as well as sections of content. The correct markup (<h1–h6>) makes it easier for people who use assistive technology to find them);

Create Consistent Cues for Orientation and Navigation (1)

• Start with an overview. (It’s common for users to leave sites if they don’t see what they are looking for quickly);

• Highlight the current location. (In the page title, by highlighting the menu item for the section, by breadcrumb navigation.

• Use multiple cues (E.g., using an icon with color-coding and a strong text label)

Use WAI ARIA for Navigation Roles

HTML5 elements and ARIA roles are complementary. Including both of them in your site provides a solid code structure and good navigation around the page

Web Accessibility Workshop

Principles for Accessible UX to be Continued on the Next Lesson

WCAG 2.0Preparing for Testing

Web Content Accessibility Guidelines (WCAG) 2.0

• WCAG 2.0 defines how to make Web content more accessible to people with disabilities;

• Several layers of guidance are provided including overall principles, general guidelines, testable success criteria and a rich collection of sufficient techniques, advisory techniques, and documented common failures with examples, resource links and code

Integrated Accessibility Guidelines

• WCAG is part of an integrated suite of accessibility guidelines and specifications from the W3C WAI: Web Content Accessibility Guidelines (WCAG) for web content Authoring Tool Accessibility Guidelines (ATAG) for authoring

tools, HTML editors, content management systems (CMS), blogs, wikis, etc.

User Agent Accessibility Guidelines (UAAG) for Web browsers, media players, and other "user agents"

Accessible Rich Internet Applications Suite (WAI-ARIA) for accessible rich Internet applications developed with Ajax and such

Principles

• At the top are four principles (POUR) that provide the foundation for Web accessibility: Perceivable, Operable, Understandable, Robust

Guidelines

• Guidelines are under the principles; • The 12 guidelines provide the basic goals that

authors should work toward in order to make content more accessible to users with different disabilities

Web Accessibility Workshop

68Image: http://www.projectrics.org

Success Criteria

• For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used;

• In order to meet the needs of different groups and different situations, three levels of conformance are defined:

• A (lowest), • AA, and • AAA (highest).

Success Criteria

Image: http://www.michaelgaigg.com

Sufficient and Advisory Techniques

• For each of the guidelines and success criteria in the WCAG 2.0 document itself, the working group has also documented a wide variety of techniques;

• The techniques are informative and fall into two categories: Sufficient for meeting the success criteria; Advisory are optional

WCAG 2.0 Guidelines

http://www.w3.org/TR/WCAG20/#guidelines

Two WCAG versions

• WCAG 1.0 (1999) • WCAG 2.0 (2008)• WCAG 2.0 builds on WCAG 1.0 and

incorporates what we've learned to make WCAG more useful and more effective;

• Most websites that meet ("conform to") WCAG 1.0 should not require significant changes in order to meet WCAG 2.0

How WCAG 2.0 Differs from WCAG 1.0

• The guidelines are organized around four basic principles (POUR), which together constitute the basic philosophy of the guideline;

• The guidelines themselves are under the principles; • Finally, each guideline includes a series of success

criteria which, like the WCAG 1.0 checkpoints, define rules for the accessibility of Web content;

• Unlike WCAG 1.0, criteria are testable. The success criteria are assigned conformance levels (A, AA, AAA), in a similar way as WCAG 1.0 checkpoints

TESTING SITES ON WCAG 2.0 CRITERIA

Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0

Adapted from http://www.w3.org/TR/WCAG-EM/

Example: Generated Site Map

Evaluation Tools

• While Web accessibility evaluation tools can significantly reduce the time and effort to evaluate Web sites, no tool can automatically determine the accessibility of Web sites;

• W3C does not endorse specific vendor products;

• Web Accessibility Evaluation Tools: Overview

Comparison Of The Tools

Source: http://usabilitygeek.com

Homework Assignment 1A. Choose a Web site for testing. It should be a government web site or

the public sector web site (bank, public transportation company, etc.) B. Implement steps from

Conformance Evaluation Methodology WCAG-EM, like define the scope of the Web site, identify common Web pages of the Web site, select a representative sample, audit the selected sample;

C. Select one or two tools link one, link two, and make testing of Selected Sample;

D. Analyze the web site by using these tools and methodology and report results, by uploading it to the course Google Drive folder until March 19th.

E. The link to Google Drive https://goo.gl/0t61Wl (use please your TLU email or make request for access)

References

• A training course “Introduction to eAccessibility” by Fraunhofer FIThttp://www.dfaei.org (developed in a framework of DFA@eInclusion project);

• Sarah Horton , Whitney Quesenbery. A Web for Everyone: Designing Accessible User Experiences, Rosenfeld Media; 1st edition (January 16, 2014)

Design for ALL