Transcript accessU-WCAG@-Why-Ca..

Development Track – AccessU 2012
WCAG 2.0
Why can’t we all just get along?
LOUIS ARMSTRONG
“You say WooCAG and I say WayCAG,
You say Area and I say AH-ria,
WooCAG, WayCAG, Area, AH-ria,
Let's call the whole thing off!”
John Slatin AccessU 2012
Denis Boudreau, AccessibilitéWeb
Austin – May 15th, 2012
Brought
to you by
2012. Some Rights Reserved.
 BY - Attribution
 NC - NonCommercial
 SA - ShareAlike 2.5 Canada
Brought
to you by
/2
Trainer
Denis Boudreau
 Over 11 years in Web Accessibility
 President, AccessibilitéWeb
 Co-editor, SGQRI 008 standards
 Invited Expert, W3C
Brought
to you by
/3
Summary
General overview
1.
2.
3.
4.
Implementation challenges
Deep within the WCAG 2.0 specs
Shedding light into WCAG 2.0
Putting it all together
Brought
to you by
/4
But before we begin...
Come pick the tag(s) that fit you most
What best describes the work you do?
Brought
to you by
/5
Brought
to you by
Implementation
challenges
/6
Implementation challenges
Accessibility becomes a serious business
Accessibility auditing is not a game anymore
• Accessibility audits used to be without consequences
• This is all changing with legal requirements & law suits
• Compliance becomes an increasingly sensitive issue
• People now expect measurable and objective results
• While compliance is objective, accessibility is not
• So when has an organization made “enough” efforts?
Brought
to you by
/7
Implementation challenges
Difficulties of implementing requirements
What makes WCAG 2 great also makes it flawed
• Being technology agnostic is awesome
• 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
Brought
to you by
/8
Implementation challenges
Difficulties of implementing requirements
WCAG 2, a double-edged sword?
• The vagueness is clarified in the techniques & failures
• Litterally, thousands of pages to go through
• But those are only informative (therefore, 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
Brought
to you by
/9
Implementation challenges
Difficulties of implementing requirements
The Canadian government approach
• Turn W3C recommendations into formal 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 creates obvious problems in most organizations
Brought
to you by
/ 10
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 the hell does this mean?
When is such a success criteria “sufficiently met”?
Brought
to you by
/ 11
Implementation challenges
Let’s take the AccessU website...
Brought
to you by
/ 12
Implementation challenges
1.3.1 Info and Relationships
Some of the things to consider...
Categories
Details
Semantics
Use semantic elements to markup structure, text and color cues
Headings
Organize pages using h1-h6 headings
Tables
Use semantic elements to markup data tables, use data table elements and
attributes (summary, caption, th, thead, tbody, id, headers, etc.)
Forms
Associate labels and form controls, use title attributes, provide a description for
groups using fieldset and legend, use optgroup to group option elements inside a
select.
Lists
Use ol, ul and dl for lists or groups of links.
Presentation
Use text to convey info conveyed by variations in presentation of text, use CSS to
control visual presentation, separate information and structure from presentation.
Brought
to you by
/ 13
Implementation challenges
The perfect example...
Experience has shown us that for
25 people in a room, we will get
about 25 different answers...
Brought
to you by
/ 14
Implementation challenges
Difficulties of implementing requirements
The Quebec government 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 creates obvious problems for web accessibility
Brought
to you by
/ 15
Implementation challenges
Going down the fragmentation path
Many public administrations decide
to rewrite accessibility standards.
Though perfectly understandable and
in some cases, even productive,
this is bad news for the Web.
Brought
to you by
/ 16
Implementation challenges
The value of standards harmonization
How standards fragmentation hurts the web
• Slows down potential progress towards increasing a11y
• Govt 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
These are all very true in the Quebec province today
Brought
to you by
/ 17
Implementation challenges
The value of standards harmonization
How standards harmonization actually helps
• All benefit from years of international collaboration
• Govts save funding by using W3C/WAI resources
• Software developers benefit from economies of scale
• Web developers can more easily produce content
• Govts can take advantage of collaborative resources
But that doesn’t mean things can’t be improved
Brought
to you by
/ 18
Implementation challenges
Education & Outreach Working Group
Standards harmonization
• Explains key role of harmonization
• Promotes adoption of a consistent
set of international standards
• Currently being updated
• Available at - http://is.gd/szEDLJ
Brought
to you by
/ 19
Implementation challenges
Filling a gap in WCAG 2.0
Improving on what’s already out there
• Still, the Quebec accessibility standards have values
• Fixing success criteria general vagueness
• Providing the developers with clear guidance
• Reaching out to already existing documents
• Creating a “filter” to apply WCAG 2.0 consistently
• Promoting harmonization through fragmentation?!
Brought
to you by
/ 20
Implementation challenges
Establishing common grounds
Coming to an agreement for accessibility
• Consistency is crucial for overall coherence
• Even more so when an organization has many websites
• Unless a lot of effort is devoted:
• Developers hardly have access to detailed specs
• Sharing a common understanding is a real challenge
• Results are uneven and global coherence suffers
Brought
to you by
/ 21
Implementation challenges
Establishing common grounds
End results are always the same.
Ask any website owner out there.
Brought
to you by
/ 22
WAI-Engage Wiki
Role-based accessibility
Thus came ARB*
(a11y responsibility breakdown)
•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!
•Available at - http://is.gd/5CoJd4
Brought
to you by
/ 23
Brought
to you by
Deep
within WCAG 2.0
/ 24
Deep within WCAG 2.0
WCAG 2.0 documents overview
Resource
The WCAG 2.0
Documents
http://www.w3.org
/WAI/intro/wcag20
Brought
to you by
/ 25
Deep within WCAG 2.0
The accessibility guidelines
Resource
WCAG 2.0 - Web
Content Accessibility
Guidelines
http://www.w3.org/TR/
WCAG/
Brought
to you by
/ 26
Deep within WCAG 2.0
The WCAG 2.0 mindmap
Resource
The WCAG 2.0 Map:
A (totally awesome)
visual guide to
understanding web
accessibility
http://www.stamfordi
nteractive.com.au/the
-wcag-2-0-map/
Brought
to you by
/ 27
Deep within WCAG 2.0
The WCAG 2.0 documents
Resource
How to Meet WCAG 2.0
http://www.w3.org/WA
I/WCAG20/quickref/
Resource
Understanding WCAG 2.0
http://www.w3.org/TR/U
NDERSTANDINGWCAG20/
Brought
to you by
/ 28
Resource
Techniques and
Failures for WCAG 2.0
http://www.w3.org/TR
/WCAG-TECHS/
Brought
to you by
Shedding
light into WCAG 2.0
/ 29
Shedding light into WCAG 2
Nuts and bolts of web accessibility
1st exercise – working with SC 1.1.1
• Organize in groups of two to three people
• In 10 minutes:
• Identify someone responsible for taking notes
• Find as many related best practices as you can
• Try to find related potential accessibility problems
• We’ll then share findings with the rest of the group
Brought
to you by
/ 30
Shedding light into WCAG 2
WCAG 2.0 AccessU ShortList
Laying foundations for a WCAG 2.0 Filter
•Non-Text Content (SC 1.1.1)
•Info and Relationships (SC 1.3.1)
•Meaningful Sequence (SC 1.3.2)
•Use of Color (SC 1.4.1)
•Contrast - Minimum (SC 1.4.3)
•Keyboard (SC 2.1.1)
•Focus Order (SC 2.4.3)
•Link Purpose - In Context (SC 2.4.4)
•Available at - http://is.gd/gsmr2P
Brought
to you by
/ 31
Shedding light into WCAG 2
Nuts and bolts of web accessibility
2nd exercise – working with other SC
• Organize in groups of four to five people
• In 10 minutes (per assigned SC):
• Identify someone responsible for taking notes
• Find as many related best practices as you can
• Try to find related potential accessibility problems
• We’ll then share findings with the rest of the group
Brought
to you by
/ 32
Brought
to you by
Putting
it all together
/ 33
Putting it all together
Adopting an assessment method
Three-step accessibility evaluation
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
And write recommendations people can use!!!
Brought
to you by
/ 34
Putting it all together
1st - Using NVDA to Evaluate Web Accessibility
Resource
Using NVDA to
Evaluate Web
Accessibility
http://webaim.org/
articles/nvda/
Brought
to you by
/ 35
Putting it all together
2nd - Web accessibility checker
Resource
Web Accessibility
Checker
http://achecker.ca/c
hecker/
Brought
to you by
/ 36
Putting it all together
3rd - Roger Hudson’s WCAG 2.0 checklist
Resource
WCAG 2.0 Checklist
http://www.usability.
com.au/resources/wc
ag2checklist.cfm
Brought
to you by
/ 37
Putting it all together
Easy to use tools to get the job done
Mozilla Firefox
Microsoft Internet Explorer
•
•
•
•
•
•
•
•
• Web Accessibility Toolbar
Web Developer Toolbar
Accessibility Evaluator
Juicy Studio a11y Toolbar
FireBug
HeadingsMap
NoSquint
WAI-ARIA Landmarks
Fangs
Other useful tools
• Color Contrast Analyzer
• FireEyes Extension
Brought
to you by
/ 38
Thank You!
Denis Boudreau,
President
Coopérative AccessibilitéWeb
1751 Richardson street, suite 6111
Montreal (Quebec), Canada H3K 1G6
Toll Free: +1 (877) 315-5550
Email: [email protected]
Web: www.accessibiliteweb.com
Twitter : @AccessibiliteWb / @dboudreau
Brought
to you by
/ 39