Andrew Kirkpatrick Adobe Accessibility 1 Focus on why conforming to WCAG is important 2 People Developers are people too 3 Help authors understand the value of their efforts Help authors understand that the standard is to make their work easier ID: 751421
Download Presentation The PPT/PDF document "How to Explain WCAG 2.0 to Your Web Team" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
How to Explain WCAG 2.0 to Your Web Team
Andrew Kirkpatrick | Adobe Accessibility
1Slide2
Focus on why conforming to WCAG is important
2
PeopleSlide3
Developers are people too
3
Help authors understand the value of their efforts
Help authors understand that the standard is to make their work easierSlide4
Provide the 10,000 foot view
WCAG 2.0 can be
a jumble of words to new readers
4Slide5
Provide the 10,000 foot view
Standards (Normative)WCAG 2.0Related Documentation (Informative)
Techniques for WCAG 2.0Understanding WCAG 2.0How To Meet WCAG 2.0
5Slide6
Provide the 10,000 foot view
6Slide7
Provide the 10,000 foot view
7
WCAG 2.0 is not Section 508 is not the ADA
(but your web team probably doesn’t care about policy)Slide8
Developers are people too
8
New + Unfamiliar = Feels difficult and uncertain
Provide a safety net.Slide9
Simplify
Web teams need simpler adviceKnowing what your team does and doesn’t do helps eliminate items which aren’t applicable.
Web site is entirely in HTML/JS/CSS?Web team doesn’t handle PDF documents?Web team is including a lot of video assets?
The best choice for your web team may be to not show them WCAG 2.0 directly.
But know that if claiming conformance that you are still responsible relative to the success criteria directly.
9Slide10
Clarify Important Concepts
WCAG 2.0 is about HTML. But not just HTMLAccessibility Support
Conformant does not mean fully accessible
10Slide11
Help make sense of the Success Criteria
Which success criteria apply?Determine what can be ignored for each page or site
Involve the part of your brain that can think like a lawyerDon’t expect that WCAG will provide specific technical guidance
The Understanding document provides additional
informative
advice to help interpret the Success Criteria (and Conformance Criteria)
11Slide12
Some terms make Success Criteria confusing
Programmatically Determined
1.3.1: Info and RelationshipsKeyboard Interface2.1.2: No Keyboard TrapProgrammatically Determined Link Text
2.4.4 Link Purpose (In Context)
Change of Context
3.2.1: On Focus and 3.2.2: On Input
Labels
3.3.2: Labels or Instructions
Name
4.1.2: Name, Role, Value
12Slide13
Some terms make Success Criteria confusing
Programmatically Determined1.3.1: Info and Relationships
Are current tools able recognize and use information that is present in the code?Tables, Lists, Headings, quotes, and more.
Technology-specific guidance is easier for web teams to take action
“Make sure that all text or images used to represent a section heading uses HTML heading elements [h1-h6]”
What about role=“heading” aria-level=“2”?
13Slide14
Some terms make Success Criteria confusing
Keyboard Interface2.1.2: No Keyboard
TrapSpeaks to a user agent issueDoes an iPhone have a keyboard interface?
14Slide15
Some terms make Success Criteria confusing
Programmatically Determined Link Text
2.4.4 Link Purpose (In Context)User agent support question. Avoiding the worst “click here” issues.
Can you have many “Read more” links in a list of article titles?
15Slide16
Some terms make Success Criteria confusing
Change of Context
3.2.1: On Focus3.2.2: On Input
Classic issue is an HTML select element which jumps to a different page when the selection is changed.
16Slide17
Some terms make Success Criteria confusing
Labels3.3.2: Labels or Instructions
Label is not always <label>A well-formed control label can meet 3.3.2 and provide the required name for the control.
The web team can define how they want to handle labels and provide that advice in the style guide.
17Slide18
Some terms make Success Criteria confusing
Name4.1.2: Name, Role, Value
Does this control have a name?
<input type=“text” name=“
fn
”>
How about this one?
<input type=“text” name=“ln” aria-label=“name”>
18Slide19
How do we know if we conform?
Conformance CriteriaSpecial Success Criteria
Techniques
Sufficient Techniques
Failures
Advisory Techniques
19Slide20
How do we know if we conform?
20
Techniques may be helpful in addressing Success Criteria
Techniques are not required to conform to Success Criteria
(but you need to be able to back up conformance claims)Slide21
We need more help
Community supportIAAP, WebAIM
, and WAI Interest Group lists have many generous and knowledgeable peopleA11y Slackers groupEncourage question-asking!
Professional help
Many qualified vendors
Accessibility tools get better all the time
21Slide22
Q & A
Thank you!Contact:
akirkpat@adobe.comTwitter: @awkawk (personal-
ish
)
@
adobeaccess
(accessibility team)
22Slide23