© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. How to Explain WCAG 2.0 to Your Web Team Andrew Kirkpatrick | Adobe Accessibility.

Slides:



Advertisements
Similar presentations
WCAG 2 Compliance With PDF
Advertisements

Deakin University CRICOS Provider Code: 00113B WEB ACCESSIBILITY Umesh Gupta Consultant – (HRIS)
IMPORTANT: Instructions
Web Accessibility: Mastering the Essentials for Compliance Annie Bélanger Liam Morland May 2013.
NOTE: Much of this presentation is outdated. For new material, see “WCAG 2 Presentations” at presentations/WCAG20/ Overview.
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Adobe Acrobat XI Accessibility Features Matt May | Accessibility Evangelist.
Web Accessibility Web Services Office of Communications.
WCAG 2.0 Web Content Accessibility Guidelines Update Last Updated July 2007.
Introduction to Web Accessibility. What is Web Accessibility Web accessibility means that people with disabilities can use the Web Disabilities including.
CM143 - Web Week 11 Accessibility Priority Checkpoints.
Making The Web Usable By Everyone (Including people with disabilities, people with slow net connections, people with broken mice, etc.) Gregory C. Lowney,
Planning and Designing a Website Session 8. Designing a Website Like all technical artefacts a website needs to be carefully planned and designed to be.
Web Accessibility. Ensuring people of all abilities have equal access to web content Disability Discrimination Act – Web Access Advisory notes 2010 Required.
Accessibility of online instructional tools and documents Terrill Thompson ATUS Technology Accessibility Consultant x 2136
Dhananjay Bhole, Coordinator, Accessibility Research Group, Department of Education and Extension, University of Pune.
Creating and publishing accessible course materials Practical advise you can replicate.
WEBINAR SERIES: ACCESSIBLE INTERACTIVE DOCUMENTS Week 3: Accessible Web Forms Norman Coombs
PDF accessibility Susannah Pike
Creating a Simple Page: HTML Overview
IT Introduction to Website Development Welcome!
CO1552 – Web Application Development Lists, Special Characters, and Tables.
The Internet Writer’s Handbook 2/e Web Accessibility Writing for the Web.
Learning Web Design: Chapter 4. HTML  Hypertext Markup Language (HTML)  Uses tags to tell the browser the start and end of a certain kind of formatting.
Measuring PDF Accessibility PDF a11y Testing for the Rest of a11yBOS 2013 Deque Systems, Inc.
Design and Construction of Accessible Web Sites Michael Burks Chairman Internet Society SIG For Internet Accessibility for People with Disabilities June.
LEARN THE QUICK AND EASY WAY! VISUAL QUICKSTART GUIDE HTML and CSS 8th Edition Chapter 6: Links.
Status as of 9 August 2007  Rough concept draft only, much of it is incomplete  There are Notes for some slides, and none yet for others Note: This document.
Accessibility of online instructional tools and documents Terrill Thompson Technology Accessibility
9 August 2012 Museum of Contemporary Art, Sydney Roger Hudson Web Usability Arts, Media and Technology at the MCA.
Daniel Njuguna – IT Officer/ Adaptive Technology Trainer Kenya Society For The Blind Accessibility in ICT’s.
WEB ACCESSIBILITY. WHAT IS IT? Web accessibility means that people with disabilities can use the Web. Web accessibility encompasses all disabilities that.
Copyright © 2012 W3C (MIT, ERCIM, Keio) BAD: Before and After Demo Shadi Abou-Zahra W3C Web Accessibility Initiative (WAI)
+ A11y assessment Lisa Liskovoi. + WCAG POUR some accessibility sugar on me Perceivable – Can I see it? Hear it? Feel it? Operable – Can I scroll it?
WCAG 2.0 Web Content Accessibility Guidelines Update Last Updated August 2007.
WAC Accessibility Conference Update. Conference details Aiming for Accessibility Conference University of Guelph June 8-9, 2010
Dive into Mobile Guidelines for Testing Native, Hybrid, and Web Apps Susan Hewitt, Accessibility Consultant, Deque Systems Jeanine Lineback, Accessibility.
Creating Accessible PDFs Professional Development Day Fall 2015.
Lab: Making PDF documents truly accessible Mireia Ribera, Universitat de Barcelona Friday, Nov , 2:15 - 4:15 p.m. 12th Annual Accessing Higher.
A centre of expertise in digital information managementwww.ukoln.ac.uk Accessibility and Usability For Web Sites: An Introduction to Web Accessibility.
Section 508 Refresh WCAG 2.0 A and AA Information & Comparison CB Averitt – Deque Systems.
ADA 508 Compliance in Online Classes Presenter: Tahiya Marome.
1 Click to edit Master text styles Second level Third level Fourth level Fifth level AODA Website Accessibility Compliance at York Open Discussions June.
Standard Manual Content and Bookmarked PDF’s Dr. Lam TECM 4250.
Web Accessibility June 2, 2016 Evaluation and Workflow.
Web Accessibility. Why accessibility? "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect."
Unit II – Leadership Skills Chapter 3 - Motivation Section 2 – Coaching and Mentoring.
IMPORTANT Note to Presenters The slides themselves have limited text, in order to avoid participants reading much while you are talking. There are extensive.
Prepared by Sana Maqbool. Objectives After completing this lesson, the you will be able to… Understand about web authoring Name and explain the uses of.
Prepared by Sana Maqbool. Objectives After completing this lesson, the you will be able to… Understand about web authoring Name and explain the uses of.
Accessibility issues: Images and the use of ALT Text
Techniques, Tools and Resources for Making WordPress Website WCAG 2
Accessibility with Lectora Inspire 16
L A B E L Marina Karapetyan.
Creating Accessible PDFs from Word Docs
Introduction to Web Accessibility
Creating Accessible Electronic Content
Content Best Practices
Basics of Accessibility in Adobe PDF
Context Is Everything Meaningful Alternative Text
Web Content Accessibility Beata M. Ofianewska (DG COMM) 7 December 2006 December 2006 COMM C2.
Lakeshore Public Schools
Common Barriers to Accessibility on the Web
Elements of Effective Web Design
Demystifying Web Content Accessibility Guidelines
Site Design & Organization
Accessible Design Top 10 List
Adobe Acrobat DC Accessibility Page Structure
WebAIM Screen Reader Survey Results
Adobe Acrobat DC Accessibility Forms
Presentation transcript:

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. How to Explain WCAG 2.0 to Your Web Team Andrew Kirkpatrick | Adobe Accessibility 1

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Focus on why conforming to WCAG is important 2 People

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 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

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Provide the 10,000 foot view WCAG 2.0 can be a jumble of words to new readers 4

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Provide the 10,000 foot view  Standards (Normative)  WCAG 2.0  Related Documentation (Informative)  Techniques for WCAG 2.0  Understanding WCAG 2.0  How To Meet WCAG 2.0 5

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Provide the 10,000 foot view 6

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 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)

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Developers are people too 8 New + Unfamiliar = Feels difficult and uncertain Provide a safety net.

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Simplify  Web teams need simpler advice  Knowing 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. 9

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Clarify Important Concepts  WCAG 2.0 is about HTML. But not just HTML  Accessibility Support  Conformant does not mean fully accessible 10

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 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 lawyer  Don’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) 11

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Programmatically Determined  1.3.1: Info and Relationships  Keyboard Interface  2.1.2: No Keyboard Trap  Programmatically Determined Link Text  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 12

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Programmatically Determined  1.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”? 13

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Keyboard Interface  2.1.2: No Keyboard Trap  Speaks to a user agent issue  Does an iPhone have a keyboard interface? 14

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Programmatically Determined Link Text  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? 15

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Change of Context  3.2.1: On Focus  3.2.2: On Input  Classic issue is an HTML select element which jumps to a different page when the selection is changed. 16

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Labels  3.3.2: Labels or Instructions  Label is not always  A well-formed control label can meet 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. 17

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Name  4.1.2: Name, Role, Value  Does this control have a name?  How about this one? 18

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. How do we know if we conform?  Conformance Criteria  Special Success Criteria  Techniques  Sufficient Techniques  Failures  Advisory Techniques 19

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 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)

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. We need more help  Community support  IAAP, WebAIM, and WAI Interest Group lists have many generous and knowledgeable people  A11y Slackers group  Encourage question-asking!  Professional help  Many qualified vendors  Accessibility tools get better all the time 21

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Q & A  Thank you!  Contact:   Twitter: (personal-ish) (accessibility team) 22

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.