Brought to you by

Administrative Track – AccessU 2013

Cultural Shifts and Enterprise Accessibility John Slatin AccessU 2013 Denis Boudreau, Deque Systems Inc. Austin – May 15th, 2013

Brought to you by

BY - Attribution NC - NonCommercial SA - ShareAlike 2.5 Canada

/ 2

2013. Some Rights Reserved.

Brought to you by

Instructor

Denis Boudreau @dboudreau on Twitter Web Accessibility Avenger Consultant, Deque Systems W3C Invited Expert

/ 3

Brought to you by

Summary

1. Enterprise Accessibility 2. Policy, Requirement and Process 3. Crowdsourcing Accessibility 4. Best Practices vs. Violations 5. Cultural Shifts and Changes 6. Implementing Accessibility 7. Role-Based Accessibility 8. Accessibility in the Production Life Cycle 9. Testing for Web Accessibility

/ 4

Brought to you by

/ 5

Not every accessibility story has to end badly. But this one does. Enter Organization ABC.

(sadly based on a true story)

Let me Tell You a Story…

Brought to you by

/ 6

Variations of this happen way too often on way too many projects.

Brought to you by

Who Was To Blame?!

Just Who is Accountable for Accessibility?

Most think it's a technological challenge Fewer think it's a communication concern All are both right AND wrong

Ultimately, who answers for accessibility in the organization?

/ 7

Brought to you by

Top 5 Reasons for Failing

What Were the Top Reasons for Failing at ABC?

1.… 2.… 3.… 4.… 5.…

/ 8

Brought to you by

/ 9

My experience with most organizations has often been that disappointing. Which has led to the question:

"How can I help organizations help me help them?"

Brought to you by

Enterprise Accessibility

Brought to you by

Enterprise Accessibility

The Accessibility Challenge

Organizations deal with many internal & external teams Establish reliable processes amongst all existing teams Build a common framework of requirements Find a way to guarantee organizational coherence Ensure consistency across all Web properties

/ 11

Brought to you by

Enterprise Accessibility

Accessibility is Everyone’s Responsibility

Everyone (IT or COM) has a role to play Existing stakeholders need to play their part Assigning responsibility to various people Sharing the tasks to produce accessible results Needs to be integrated in the existing workflow Can’t be seen as just another expertise to bring in

/ 12

Brought to you by

Most Common Pitfalls

Top 5 Traps Most Organizations Fall In

1. View accessibility as a final step (quality control) 2. Rely on an expert instead of team efforts 3. Care about the checklist and nothing else 4. Expecting automated tools to do the work 5. Underestimate the impacts of technological platforms

/ 13

Brought to you by

We’ve Been Here Before

What Organizations Usually Do with Accessibility

Consider the accessibility requirements Develop the project (hoping for the best) Make sacrifices and concessions all along Call for an audit at the very end of the project Ask for confirmation on the efforts that were made Cross their fingers (again, hoping for the best)

/ 14

Brought to you by

We’ve Been Here Before

What Organizations Usually Get From Accessibility

100+ page reports on the conformance level Countless recommendations for remediation A bitter feeling of general failure despite all efforts Frustration, anger - possibly harsh consequences too

/ 15

Brought to you by

Well, Maybe Not So Much…

What Organizations Should Be Getting

A general sense of: • Confidence that accessibility is within reach • Motivation in creating overall better products • Encouragement as practices and methods improve • Collaboration in working towards a common goal

• Pride for contributing to a more inclusive Web

After all, this is what most of us are usually getting, right?

/ 16

Brought to you by

Accessibility Doesn’t Just Happen

It Needs to be Planned From the Start

There’s only so much you can achieve “by accident” Semantic HTML + CSS can only get you so far But what about:

• Keyboard navigation, user testing, color choices? • Compatibility with various assistive technologies? • The underlying technologies projects are based on?

/ 17

Brought to you by

Accessibility Usually Means

Working on Projects That Were…

Never really meant to be accessible Never planned appropriately Based on flawed assumptions from day one Always looked at from a single perspective Conducted by uninformed people Created using limited technologies

/ 18

Brought to you by

Accessibility Usually Means

Being Asked to Work Against

Organization status quo Stakeholders on the defensive (and rightfully so) Impossible or immutable deadlines Limited or non existent budgets Without any significant internal guidelines

/ 19

Brought to you by

Policies, Requirements and Processes

Brought to you by

/ 21

WCAG 2.0 Section 508

Brought to you by

/ 22

Many public administrations and organizations often decide to

rewrite accessibility standards. This can be bad news for the Web.

Creating Accessibility Policies

Brought to you by

The Canadian Govt. Approach

Turning W3C recommendations into requirements

Make WCAG 2.0 level AA a mandatory standard Providing measurable means to achieve compliance Applying at least one technique per success criteria Generally trying to avoid the common failures Indirectly granting those techniques normative status

This can create limitation effects for some organizations.

/ 23

Brought to you by

The Quebec Govt. Approach

Refute WCAG 2.0 because of its vagueness

Make WCAG 2.0 level AA a mandatory standard Identify techniques and turn them into requirements Breaking down each SC into measurable goals Creating another standard altogether in the process

This definitely creates limitation effects for most organizations.

/ 24

Brought to you by

The Ugly Truth…

What Makes WCAG 2.0 Great Also Makes it Flawed

Being technology agnostic is fantastic Great for sustainability but comes with drawbacks A certain vagueness in success criteria formulation Leaves room for various uneducated interpretations Opens the door to lots of uneven implementations Indirectly contributes to making accessibility hard

/ 25

Brought to you by

Informative or Normative

WCAG 2.0, a Double-Edged Sword?

Vagueness is clarified in the techniques & failures Literally, thousands of pages to go through Techniques are only informative (not required) Not everyone reads them (most don’t take the time) We are all welcomed to cherry pick what we like Or maybe even come up with new techniques

/ 26

Brought to you by

On Fragmentation

How Standards Fragmentation “Hurts the Web”

Slows down potential progress for accessibility Must spend more resources on alternate versions Mainstream authoring tools lack accessibility support Products developed locally can’t compete globally Organizations must track & support differing standards

/ 27

Brought to you by

On Harmonization

How Standards Harmonization “Helps the Web”

All benefit from years of international collaboration Funding is saved by using W3C/WAI resources Software developers benefit from economies of scale Web developers can more easily produce content Organizations take advantage of collaborative resources But that doesn’t mean things can’t be improved

/ 28

Brought to you by

Standards Harmonization

Why Standards Harmonization is Essential to Web Accessibility

Explains key role of harmonization Promotes adoption of a consistent set of international standards Available at http://www.w3.org/WAI/Policy/harmon

/ 29

Brought to you by

Implementation Challenges

The Perfect Example

1.3.1 Info and Relationships Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

What does this success criteria even mean?

When is a success criteria “sufficiently met”?

How can anyone validate if it’s conformant or not?

/ 30

Brought to you by

/ 31

Experience shows that for 25 people in a room, we will get about as many different answers...

How many would we get today?

Brought to you by

/ 32

But that doesn’t mean you can’t adapt those requirements so they better fit with your

organization’s culture.

Brought to you by

Creating Requirements

Cherry Picking Your Standards

Choose your weapon: WCAG 2.0, Section 508, ADA… Considered ISO/IEC 40500 – was it a game changer? Standards made for rather arid readings Got Business Analysts to integrate requirements Achieving conformance – where did they start?

/ 33

Brought to you by

Long and Winding Road

Getting There

Adopting vs. adapting – what suited them best? Defined the scope for Web accessibility Fighting ACS (the Accessibility Checklist Syndrome) Integrated accessibility in the development lifecycle Broke down the requirements for stakeholders

/ 34

Brought to you by

Lessons Learned

What Will the Organization Experience?

Bad – accessibility as last minute QA Good – accessibility in the early stages The Power of Planning Organizational Changes Cultural Shifts – Resistance Pragmatism – Choosing their battles Baby Steps to Greatness

/ 35

Brought to you by

Key Challenges

Part Of The Problem With Accessibility Is…

Developers and designers are reinventing the wheel No one sees the broader picture, no cohesion efforts The organization depends on individuals who come and go Processes are only as strong as those who remain No one benefits from the collective intelligence

/ 36

Brought to you by

Collective Intelligence

Definition: "A phenomenon in sociology that describes a type of shared or group intelligence that emerges from the collaboration and competition of many individuals.”

How can organizations tap into this valuable resource?

How can they reap the benefits of all these brains working together for accessibility?

/ 37

Brought to you by

Crowdsourcing Accessibility

Brought to you by

Putting It To The test

Building a Common Understanding of WCAG 2.0

The range of interpretations greatly varies

Not uncommon at all for experts to disagree

Disagreements often based on culture and background

Within an organization, reaching consensus is key

Consensus is a great way to get stakeholder buy-in

Those who argue the longest usually win

/ 39

Brought to you by

Going Back To This Example

The Perfect Example

1.3.1 Info and Relationships Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

What does this success criteria even mean?

When is a success criteria “sufficiently met”?

How can anyone validate if it’s conformant or not?

/ 40

Brought to you by

/ 41

Let’s find out just how many different answers we can come up with, just

amongst our little group today.

Brought to you by

Comparing Apples to Apples?

SC 1.3.1 Can Be Summarized As…

1.Using proper semantics to structure content 2.Providing proper heading structure 3.Providing proper markup for data tables 4.Associating form control and label explicitly 5.Grouping sets of form controls and labels

Any other suggestions?

/ 42

Brought to you by

Crowdsourcing Accessibility

Drum Roll…. Let’s Play a Game!

Let’s pretend you are tasked with writing accessibility standards for your organization. Knowing the end goal is to make sure all teams (internal or external) can create accessible content.

Would you choose to apply WCAG 2.0? Why? Would you choose to rewrite it partially? Why? Would you choose to rewrite it completely? Why?

/ 43

Brought to you by

Scenario 1 (individually)

Your organization chooses to align to WCAG 2.0 AA. You were designated as the accessibility specialist, and tasked with defining WCAG Success Criteria for your team.

Define what SC 1.1.1 means in layman’s terms Define specific requirements to meet the SC Capture your thoughts on a piece of paper

/ 44

Brought to you by

Scenario 2 (groups of 3-4)

You are part of a small accessibility cell, and tasked with defining WCAG Success Criteria in layman's terms for the rest of the team. You all come to this with your previous experience and need to reach consensus.

Compare SC meanings and create new common answer Compare requirements, agree on common interpretation Document that common interpretation in new version

/ 45

Brought to you by

Scenario 3 (larger group)

You are all representatives of different teams from the same organization, tasked with developing an internal policy for Web accessibility. I am responsible for leading our group of experts.

Discuss your interpretation with other group members Reach agreement on what goes into the internal policy Come up with a final global interpretation for the group Write user stories for each disabilities (one per requirement)

/ 46

Brought to you by

Resulting Requirements

Using Collective Intelligence over SC 1.1.1

Requirements include: 1. … 2. … 3. ... 4. … 5. … 6. … 7. …

/ 47

Brought to you by

Comparing Apples to Apples?

My Take on SC 1.1.1 Would Be:

1.Alt Text (Active Images) 2.Alt Text (Informational Images) 3.Alt Text (Complex Images) 4.Alt Text (Decorative Images) 5.Alt Text (Input Type Images) 6.Alt Text (Embedded Multimedia)

Is there really a better answer? What’s our goal here?

/ 48

Brought to you by

/ 49

What really matters is not how your requirements are written, but that your team actually understands the intent behind them.

User experience over conformance.

Brought to you by

Back To Basics

Pragmatica11y

Understanding the essence of the principles Trust developers and designers to find solutions Build a solid understanding of the guidelines Foster innovation by allowing creative thinking Focus on awareness, not requirements and checklists

/ 50

Brought to you by

Best Practices vs. Violations

Brought to you by

People Will Disagree

Where Do You Draw The Line?

What constitutes a real violation? What constitutes a simple best practice? All about culture and backgrounds clashes Goes back to how people learned and who taught them There is a limit to the answers WCAG 2.0 can provide

/ 52

Brought to you by

Best Practice or Violation?

Success Criterion 1.1.1 (Level A) “The alternative text value of informative images

should be 150 characters or less”.

/ 53

Brought to you by

Best Practice or Violation?

Success Criterion 1.3.1 (Level A) “There can never be more than one first level heading

(h1) per page”.

/ 54

Brought to you by

Best Practice or Violation?

Success Criterion 1.3.1 (Level A) “There needs to always be at least one first level

heading (h1) per page”.

/ 55

Brought to you by

Best Practice or Violation?

Success Criterion 1.3.1 (Level A) “Headings must be organized hierarchically and

heading levels can never be skipped”.

/ 56

Brought to you by

Best Practice or Violation?

Success Criterion 1.3.1 (Level A) “Tables used only for layout need to be avoided at all

times”.

/ 57

Brought to you by

Best Practice or Violation?

Success Criterion 1.3.2 (Level A) “The reading order of content must always match the

visual order displayed on the page”.

/ 58

Brought to you by

Best Practice or Violation?

Success Criterion 2.4.1 (Level A) “Skip links are always required and must be the first

element encountered on the page”.

/ 59

Brought to you by

Keep In Mind…

Use of WCAG Techniques and Failures

Sufficient Techniques – not the only solution and should never be required as the only way to meet WCAG 2.0. Advisory Techniques – can always be considered, but are not sufficient when used alone. Failures – designed to always indicate failure, but their number is more limited than it should. There could be more. There will be more with time.

/ 60

Brought to you by

/ 61

Taking techniques and turning them in requirements to meet specific Success Criteria

should always be avoided.

Brought to you by

Cultural Shifts and Changes

Brought to you by

Cultural Shifts and Changes

Let’s Face It - Accessibility is Disruptive

Accessibility disrupts development habits Organizations aren’t used to the extra costs People aren’t used to have theirs skills questioned Unbalancing the ecosystem creates resistance

/ 63

Brought to you by

Cultural Shifts and Changes

The 5 stages of Accessibility

Denial » “PWD aren’t our target audience!”

Anger » “This is a barrier to my creativity!”

Bargaining » “Isn’t level A enough?”

Depression » “It’s never good enough!”

Acceptance » “We can do this!”

/ 64

Brought to you by

/ 65

“The only way we’re going to get accessibility into the DNA of an organization is for them to

have ownership of it.”

- Lainey Feingold, attorney extraordinaire, 2013

Brought to you by

Change Management 101

So, How Do We Do That?

Change Management – The process of aligning how people work and behave to fit specific changes in the business strategy, systems or organizational structure.

/ 66

Current State

(status quo)

New State

(improved)

Transition

Increasing comfort,

control and confidence

Brought to you by

Change Management 101

/ 67

Key Elements

Strategy Organize Motivate Teamwork Improve Measure

Brought to you by

But there’s a problem…

People are very Resistant to Change

1.Confrontation – direct inadmissibility of the change 2.Rejection – fear of losing, anxiety towards change 3.Avoidance – lack of motivation towards change 4.Faking – seemingly adopting without implementing

/ 68

Brought to you by

What Have YOU Experienced?

What Kind of Resistance Have You Encountered?

1.… 2.… 3.… 4.… 5.… 6.… 7.…

/ 69

Brought to you by

/ 70

Web accessibility challenges the status quo and forces organizations into adopting profound change

strategies as well as significant cultural shifts.

Brought to you by

Typical Answers to Change

Who are you Dealing With?

The critic – who opposes the change The victim – who panics in front of the change The bystander – who ignores the change The navigator – who is empowered by the change

/ 71

Brought to you by

Accessibility Ownership

How Can We Help People Become Navigators?

1.… 2.… 3.… 4.… 5.… 6.… 7.…

/ 72

Brought to you by

Accessibility Ownership

Helping People Become Navigators

Communicate the threat of not changing Keep explaining the reasons for changing Involve team in decision making Be as transparent as possible Minimize uncertainties Celebrate successes

/ 73

Brought to you by

/ 74

For people to willingly go on with the

change, they must first understand what’s in it for them.

Brought to you by

People Management 101

/ 75

Key Elements

Attract Educate Train Motivate Empower Reward

Brought to you by

/ 76

Training is expensive, but incompetence due to lack of

training is more expensive even!

Don’t Ever Forget!

Brought to you by

Accessibility Ownership

Learning to View Change as an Opportunity

Involve your team early in the process Create opportunities for people to rise up Communicate constantly on milestones Plan properly from the very start Don’t ever let up – always keep with the pace

/ 77

Brought to you by

/ 78

Organizations who fail to do this make

change become a burden for all.

Organizations who succeed use change as a catalyst to greatness.

Brought to you by

Organizational Change Portfolio

/ 79

Streams of Change

Communication

Learning

Organization

Performance

Credit: Luc Galoppin, 2008

Brought to you by

Organizational Change Portfolio

/ 80

Communication Stream

Not change propaganda

Manage expectations and support change

Stay in touch with the team

Answer simple questions: “who are we” and “what are we here for”?

Brought to you by

Organizational Change Portfolio

/ 81

Learning Stream

Upgrade the knowledge and skillsets of the organization in terms of context, content and action (why, what, how)

Aim for learning rather than just training – address basic questions like motivation, knowledge and skills

Brought to you by

Organizational Change Portfolio

/ 82

Organization Stream

Define and implement a new organization structure that reflects the changes at hand

Define and establish new work responsibilities in order to make the change happen

Provide concrete support (winning conditions)

Brought to you by

Organizational Change Portfolio

/ 83

Performance Stream

Translate the principles of accessibility into concrete new ways of working

Include detailed instructions for expected changes

Establish meaningful and measurable goals

Brought to you by

/ 84

Part of the secret resides in being transparent and maintaining an open and direct discussion with your team

members.

Brought to you by

Implementing Accessibility

Brought to you by

/ 86

Making a commitment to make its website accessible is one thing, planning for

implementation of accessibility is another.

Implementing Accessibility

Brought to you by

So Where Do We Begin?

Considerations for the Planning Process

1. Establishing Responsibilities 2. Conducting Initial Assessment 3. Developing Organizational Policy 4. Selecting Appropriate Software 5. Providing Proper Training 6. Developing Accessible Website 7. Promoting Organizational Awareness 8. Monitoring Website Accessibility

/ 87

Brought to you by

Implementation - Step One

Establishing Responsibilities

A coordination team with a coordination plan • Involve key players from key departments • Designate a dedicated team leader

A high-level champion to reinforce commitment • Ideally, someone from upper management • Track implementation progresses

/ 88

Brought to you by

Implementation - Step Two

Conducting Initial Assessments

Identify external accessibility requirements Quickly assess the current level of accessibility Measure current accessibility awareness level Assess current accessibility expertise level Determine suitability of current software Analyze software procurement practices Estimate resources required to address the needs

/ 89

Brought to you by

Implementation - Step Three

Developing Organizational Policy

Identify existing accessibility policies Establish an organizational accessibility policy Announce the new policy - make it a core value Organize promotional events around the policy Create promotion plans to increase awareness Make it inspiring and about the people

/ 90

Brought to you by

Implementation - Step Four

Selecting Appropriate Software

Review procurement requirements Benchmark different options for accessibility Select most conforming authoring software Engage vendors into an accessibility roadmap Develop a web publishing process Counter shortcomings of selected software

/ 91

Brought to you by

Implementation - Step Five

Providing Proper Training

Plan a range of accessibility training options Meet the needs of people with different roles Plan internal and external documentation Arrange for various training strategies Offer repeated training opportunities

/ 92

Brought to you by

Implementation - Step Six

Developing an Accessible Website

Identify accessibility as a core priority Integrate accessibility requirements on day one Verify accessibility at key stages in the process Provide robust tools to ensure accessibility Develop accessibility checklists for each role Supply each team with a validation process

/ 93

Brought to you by

Implementation - Step Seven

Promoting Organizational Awareness

Incorporate policy into key documents Regularly reinforce the accessibility policy Establish forums for exchange Communicate about the clientele Organize accessibility events with experts Provide updates and briefings on the progress

/ 94

Brought to you by

Implementation - Step Eight

Monitoring Website Accessibility

Specify the accessibility evaluation process Ensure quality of the evaluation process Conduct ongoing monitoring of website Invite and respond to user feedback Escalate to champion policy as needed Periodically review all aspects for effectiveness

/ 95

Brought to you by

Digging Deeper

Implementation Plan for Accessibility

•Dated back from 2002 •Being revisited right now •Come join the fun!

http://www.w3.org/WAI/impl/

/ 96

Brought to you by

/ 97

Whenever you fail to plan for accessibility your plan becomes to fail at accessibility.

Simple Math

Brought to you by

Accessibility in the Production Lifecycle

Brought to you by

Accessibility in the Life Cycle

Moving Forward with Accessibility

Ventilate requirements across the whole team Prevent clueless errors and expensive omissions Provide clear, defined patterns and strategies Accessibility is about teamwork and workflows Collective ownership of accessibility requirements

/ 99

Brought to you by

/ 100

Efficiently integrating accessibility within the development lifecycle is all about being able to plan the right intervention, at the

right time, by the right people.

Brought to you by

Ventilating Requirements

Making the Accessibility Goal a Team Effort

Getting involvement from the whole team Make this goal a positive pursuit of quality Break down the requirements into existing roles Benefiting from the already available expertise The best resources are already on board

/ 101

Brought to you by

Prevention is Better Than Cure

Much Cheaper to Get it Right the First Time

More efficient use of everyone's time Significant reductions in terms of costs Significant benefits in production Significant gains in customer relations Significant gains in internal relations

/ 102

Brought to you by

A Culture of Digital Equality

Building Accessibility in the Organization’s DNA

Integrating accessibility as a core value Document processes and methodologies Build around your accessibility expertise Capture the knowledge before it goes away Make it an integral part of your processes

/ 103

Brought to you by

/ 104

An effective way to do that is to understand how accessibility impacts the responsibilities of

every stakeholder in a project.

Brought to you by

Role-Based Accessibility

Brought to you by

The WCAG 2.0 Mind Map

WCAG 2.0 Map: A visual guide to understanding web accessibility

http://stamfordinteractive.com.au/conversations/the-wcag-2-0-map/

/ 106

Brought to you by

Role-Based Accessibility

Generic Model Overview

AN - Analysis PR - HTML/CSS prototyping AR - Architecture FE - Front end development ID - Interaction design BE - Back end development GD - Graphics design QA - Quality control CS - Content strategy MA - Maintenance SE - Search engine optimization

/ 107

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Brought to you by

Putting it All Together

A Few Questions to Ask Ourselves

How do various stakeholders relate to accessibility? Who “owns” a specific accessibility requirement? How can accessibility requirements be shared? How can I adapt a generic model to my organization?

/ 108

Brought to you by

Putting it All Together

Accessibility and Analysis

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with capturing the project’s requirements, analysis of the project’s strategic orientations, analysis of the options for technology platforms, functional analysis of Web interfaces.

/ 109

Brought to you by

Putting it All Together

Accessibility and Analysis

/ 110

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable -- -- --

Operable -- -- 2.2.3, 2.2.4, 2.2.5

Understanding 3.2.1, 3.3.1 3.3.3, 3.3.4 3.3.5, 3.3.6

Robust -- -- --

Total (9) 2 2 5

Brought to you by

Putting it All Together

Accessibility and Architecture

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with the architecture of the information (web content) and the architecture of the data.

/ 111

Brought to you by

Putting it All Together

Accessibility and Architecture

/ 112

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.3.1 -- --

Operable 2.4.2 2.4.5, 2.4.6 2.4.8, 2.4.10

Understanding -- 3.1.2 3.1.3, 3.1.4

Robust -- -- --

Total (9) 2 3 4

Brought to you by

Putting it All Together

Accessibility and Interaction Design

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with the planning of web interfaces, content changes, interactivity and other interface-related contents of the pages.

/ 113

Brought to you by

Putting it All Together

Accessibility and Interaction Design

/ 114

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.3.1, 1.3.3, 1.4.1, 1.4.2 1.4.4 1.4.7, 1.4.8

Operable 2.1.1, 2.1.2, 2.2.1, 2.2.2, 2.3.1, 2.4.4

2.4.5, 2.4.6 2.1.3, 2.2.3, 2.2.4, 2.2.5, 2.3.2, 2.4.8, 2.4.9

Understanding 3.2.1, 3.2.2, 3.3.1, 3.3.2 3.2.3, 3.2.4, 3.3.3, 3.3.4 3.1.3, 3.1.5, 3.2.5, 3.3.5, 3.3.6

Robust 4.1.2 -- --

Total (36) 15 7 14

Brought to you by

Putting it All Together

Accessibility and Graphic Design

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with the graphic design of interfaces, the related graphic declinations, the specific design of navigation elements, context changes and other general design of the main content of the pages.

/ 115

Brought to you by

Putting it All Together

Accessibility and Graphic Design

/ 116

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.3.1, 1.3.3, 1.4.1, 1.4.2 1.4.3, 1.4.4, 1.4.5 1.4.6, 1.4.7, 1.4.8, 1.4.9

Operable 2.1.1, 2.1.2, 2.2.2, 2.3.1, 2.4.1

2.4.5, 2.4.6, 2.4.7 2.2.3, 2.2.4, 2.3.2, 2.4.8

Understanding 3.2.1, 3.3.1, 3.3.2 3.2.3, 3.2.4, 3.3.3 3.2.5, 3.3.5, 3.3.6

Robust -- -- --

Total (32) 12 9 11

Brought to you by

Putting it All Together

Accessibility and Content Strategy

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with producing the site’s text contents, equivalent alternative for non-text content and other general text elements presented in the pages.

/ 117

Brought to you by

Putting it All Together

Accessibility and Content Strategy

/ 118

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3.1, 1.3.3

1.2.5 1.2.7, 1.2.8

Operable 2.1.1, 2.1.2, 2.4.2, 2.4.4 2.4.6 2.4.9

Understanding 3.3.1 3.1.2 3.1.3, 3.1.4, 3.1.5, 3.1.6

Robust -- -- --

Total (21) 11 3 7

Brought to you by

Putting it All Together

Accessibility and Search Engine Optimization

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with providing text equivalents for non-text contents and making contents on a web page more easily indexable/crawlable by search engines.

/ 119

Brought to you by

Putting it All Together

Accessibility and Search Engine Optimization

/ 120

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3.1

1.2.4, 1.2.5, 1.4.5 1.2.6, 1.2.7, 1.2.8, 1.2.9

Operable 2.1.1, 2.1.2, 2.2.1, 2.2.2, 2.4.1, 2.4.2, 2.4.3, 2.4.4

2.4.5, 2.4.6, 2.4.7 2.1.3, 2.2.3, 2.4.8, 2.4.9, 2.4.10

Understanding -- -- --

Robust -- -- --

Total (28) 14 6 9

Brought to you by

Putting it All Together

Accessibility and HTML/CSS Prototyping

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with the production of all web site master templates (HTML and CSS).

/ 121

Brought to you by

Putting it All Together

Accessibility and HTML/CSS Prototyping

/ 122

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.1.1, 1.3.1, 1.3.2 1.4.3, 1.4.4, 1.4.5 1.4.6

Operable 2.1.1, 2.1.2, 2.4.1, 2.4.2, 2.4.3

2.4.5, 2.4.6, 2.4.7 2.1.3, 2.4.8, 2.4.10

Understanding 3.1.1, 3.3.2 3.2.4 3.1.3, 3.2.5

Robust 4.1.1, 4.1.2 -- --

Total (25) 12 7 6

Brought to you by

Putting it All Together

Accessibility and Front-End Development

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with the development of contribution tools, HTML and CSS integration, and the programming of proposed scripts and applications on the web site.

/ 123

Brought to you by

Putting it All Together

Accessibility and Front-End Development

/ 124

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3.1, 1.3.2, 1.3.3, 1.4.1, 1.4.2

1.2.4, 1.2.5, 1.4.3, 1.4.4, 1.4.5 1.2.6, 1.2.7, 1.2.8, 1.2.9, 1.4.6, 1.4.7, 1.4.8, 1.4.9

Operable 2.1.1, 2.1.2, 2.2.1, 2.2.2, 2.3.1, 2.4.1, 2.4.2, 2.4.3, 2.4.4

2.4.5, 2.4.6, 2.4.7 2.1.3, 2.2.3, 2.2.4, 2.2.5, 2.3.2, 2.4.8, 2.4.9, 2.4.10

Understanding 3.1.1, 3.2.1, 3.2.2, 3.3.1, 3.3.2 3.1.2, 3.2.3, 3.2.4, 3.3.3, 3.3.4 3.1.3, 3.1.4, 3.1.6, 3.2.5, 3.3.5, 3.3.6

Robust 4.1.1, 4.1.2 -- --

Total (60) 25 13 22

Brought to you by

Putting it All Together

Accessibility and Back-End Development

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with the development of server side programming and database management.

/ 125

Brought to you by

Putting it All Together

Accessibility and Back-End Development

/ 126

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.1.1, 1.3.1, 1.3.2 -- --

Operable 2.1.1, 2.1.2, 2.2.1, 2.2.2, 2.4.3, 2.4.4

2.4.5, 2.4.6, 2.4.7 2.1.3, 2.2.3, 2.2.4, 2.2.5, 2.4.9, 2.4.10

Understanding 3.2.1, 3.2.2, 3.3.1, 3.3.2 3.1.2, 3.2.4, 3.3.3, 3.3.4 3.1.3, 3.1.4, 3.2.5, 3.3.6

Robust 4.1.1, 4.1.2 -- --

Total (32) 15 7 10

Brought to you by

Putting it All Together

Accessibility and Quality Control

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Covers tasks normally associated with general validations at the very end of the project, before launching.

/ 127

Brought to you by

Putting it All Together

Accessibility and Quality Control

/ 128

Principles Applicable Success Criteria

Level A Level AA Level AAA

Perceivable 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3.1, 1.3.2, 1.3.3, 1.4.1, 1.4.2

1.2.4, 1.2.5, 1.4.3, 1.4.4, 1.4.5 1.2.6, 1.2.7, 1.2.8, 1.2.9, 1.4.6, 1.4.7, 1.4.8, 1.4.9

Operable 2.1.1, 2.1.2, 2.2.1, 2.2.2, 2.3.1, 2.4.1, 2.4.2, 2.4.3, 2.4.4

2.4.5, 2.4.6, 2.4.7 2.1.3, 2.2.3, 2.2.4, 2.2.5, 2.3.2, 2.4.8, 2.4.9, 2.4.10

Understanding 3.1.1, 3.2.1, 3.2.2, 3.3.1, 3.3.2 3.1.2, 3.2.3, 3.2.4, 3.3.3, 3.3.4 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.2.5, 3.3.5, 3.3.6

Robust 4.1.1, 4.1.2 -- --

Total (61) 25 13 23

Brought to you by

Putting it All Together

Accessibility and Project Management

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Planning accessibility at each step, allocating responsibilities, ensuring criteria are met at every milestone, understanding the difference between accessible and conforming content, being aware of tool limitations and working around them, assessing the impact of technology platforms for the overall project.

/ 129

Brought to you by

Putting it All Together

Accessibility and Maintenance

AN AR ID GD CS SE PR FE BE QA

Project Management MA

Making sure relevant knowledge transfer from the production team is passed on to the maintenance team, so accessibility efforts put into the project don't degrade as soon as content is updated on the website. Adapting the workflow to the reality of the maintenance team, based on the roles defined previously.

/ 130

Brought to you by

WAI-Engage Wiki

Role-Based Accessibility

Looking at WCAG 2.0 SC by roles Get involved in the community: comment, contribute, use Make this your own and bring it into your organization! http://is.gd/5CoJd4

/ 131

Brought to you by

Summing It Up

Get subject matter experts in your lifecycle to integrate accessibility so the right questions are asked at the right time by the right people

Plan accessibility from the very early stages Plan sufficient and consistent support Iterative rounds of accessibility validation to stay on track Recommendations to guide the remediation process Ensure autonomy through knowledge transfer

/ 132

Brought to you by

Testing for Web Accessibility

Brought to you by

Testing for Accessibility

Developing a Methodology

1.Define the Evaluation Scope 2.Explore the Target Website 3.Select a Representative Sample 4.Audit the Selected Sample 5.Report the Evaluation Findings

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

/ 134

Brought to you by

Methodology - Step One

Defining the Evaluation Scope

Define the Scope of the Website Define the Goal of the Evaluation Define the Conformance Target Define the Techniques and Failures to be Used

/ 135

Brought to you by

Methodology - Step Two

Explore the Target Website

Identify Common Web Pages of the Website Identify Common Functionality of the Website Identify the Variety of Web Page Types Identify Web Technologies Relied Upon

/ 136

Brought to you by

Methodology - Step Three

Select a Representative Sample

Include Common Web Pages of the Website Include Exemplar Instances of Web Pages Include Other Relevant Web Pages Include Complete Processes in the Sample Include a Randomly Selected Sample Eliminate Redundancies in the Sample

/ 137

Brought to you by

Methodology - Step Four

Audit the Selected Sample

Check for the Broadest Variety of Use Cases Assess Accessibility Support for Features Use Techniques and Failures Where Possible Archive Web Pages for Reference Record Software Tools and Methods Used

/ 138

Brought to you by

Methodology - Step Five

Report the Evaluation Findings

Provide Documentation for Each Step Provide a Conformance Evaluation Statement Provide a Performance Score Provide Machine-Readable Reports

/ 139

Brought to you by

Approach to Testing

Adopting an Assessment Method

Usually, a three step process 1. Testing the web page with a screen reader 2. Using an automatic checker for basic problems 3. Running manual testing to complete the audit

/ 140

Brought to you by

Accessibility Testing

1st - Using NVDA to Evaluate User Experience

Using NVDA to Evaluate Web Accessibility http://www.webaim.org/articles/nvda/

/ 141

Brought to you by

Accessibility Testing

2nd - Using FireEyes to Evaluate Accessibility

Worldspace FireEyes Quick Start Tutorial http://www.deque.com/tutorial

/ 142

Brought to you by

Accessibility Testing

3rd – Complete with Manual Testing

WebAIM's WCAG 2.0 Checklist for HTML documents http://webaim.org/standards/ wcag/checklist

Or actually create your own, based on WCAG 2.0!

/ 143

Brought to you by

Building Your Own Checklist

What Does the Team Really Need?

Clear guidance as to what constitutes a requirement A reference to some normative framework (WCAG 2.0)

• A referral to a specific requirement • An identifying short name for easy reference • A prescriptive checklist explanation item • A commonly approved method for testing • An appreciation of requirement impacts

/ 144

Brought to you by

More Tools for Everyone!

Mozilla Firefox

Web Developer Toolbar Accessibility Evaluator Juicy Studio Toolbar FireBug HeadingsMap NoSquint Fangs

/ 145

Internet Explorer

Web Accessibility Toolbar

Other Useful Tools

Color Contrast Analyzer FireEyes Extension WAVE Toolbar

Brought to you by

Example

Using Success Criterion 2.4.7

Focus Visible (level AA) 1. Checklist: It is visually apparent which page element has

the current keyboard focus (i.e., as you tab through the page, you can see where you are).

2. Testing Method: Manually set focus on the user interface elements using the Tab key. Confirm that when an element receives focus, the background color or border is changed to make it visually distinct.

/ 146

Brought to you by

Example Using SC 1.1.1

Other Rich Examples…

Non-Text Content (level A) • Alt Text (Active Images) • Alt Text (Informational Images) • Alt Text (Complex Images) • Alt Text (Decorative Images) • Alt Text (Input Type Image) • Alt Text (Embedded Multimedia)

/ 147

Brought to you by

Example Using SC 1.3.1

Other Rich Examples…

Info and Relationships (level A) • Semantics • Heading Structure • Data Tables • Explicit Forms Association • Fieldset and Legends

/ 148

Brought to you by

Beware of Opinions!

Interpretations vs. Opinions vs. Facts

Value opinions, but only consider documented facts Distinguish normative from informative Recognize techniques as what they are Differentiate sufficient techniques from advisory Acknowledge the importance of failures

/ 149

Brought to you by

/ 150

A simple eXcel spreadsheet can get you a very long way… and generate endless debates!

{{{ Be ready }}}

Start Small

Brought to you by

/ 151

After all, accessibility is an art,

not an exact science.

Remember…

Brought to you by

Involving Users in Testing

Getting Feedback Where it Matters Most

Developers can only do so well when testing Real users can provide truly valuable feedback Building an appropriate testing environment Validating user testing results with users Using results as another catalyst to greatness

/ 152

Brought to you by

Summing It Up

The answer to Enterprise Accessibility?

1. Defining policy, requirement and process 2. Managing cultural shifts and changes 3. Implementing accessibility successfully 4. Breaking down roles and responsibilities 5. Integrating in the production life cycle 6. Building a test suite for web accessibility

/ 153

Brought to you by

// Denis Boudreau, // Senior Subject Matter Expert // Web Accessibility Avenger // Deque Systems, Inc. // +1 (514) 730-9168 // db@deque.com // www.deque.com // @dboudreau

Thank You!