WCAG 2.0 - How Will Compliance Testing

Change?Barry Johnson

Senior Accessibility EngineerDeque Systems

Friday March 2, 2012 – 1:50pm

First Happy Birthday

Theodore Geisel, a.k.a Dr. Seuss (108)And

Jon Bon Jovi (50)

Learning Objectives:

• Participants will learn about the new testing techniques to comply with WCAG 2.0.

• Participants will understand how the new standards will affect them.

• Participants will explore how WCAG 2.0 will provide a more accessible result than the current 508 standards.

What do I know?

• Programmer/Developer for 20 years• Working on web & software accessibility since

1990• Worked at FAA & DoT, HHS, DHS and now ED• Assisted DoT in implementing A11y policies as

well as AccVerify/Repair across all dot.gov properties

• Assisted HHS ASPA/WCD with Compliance and Remediation Guidelines.

Where Are We?

• For the past decade we have all been working to ensure our websites are Section 508 compliant to the current 1194.22 & .21 standards. Now, as the 508 refresh approaches, we are going to be faced with some new challenges as some of the features we have been "passing" on our tests are not acceptable under the 2.0 Guidelines.

The Challenge

• The challenge for the US Federal Government Agencies as the new standards are released is going to be changing the way they validate compliance. Specifically for web accessibility they will need to re-train their accessibility testers, edit their testing methodologies, update their testing tools, and retrain their developers.

What are we doing now?

• General “Automated” testing…• WAVE Toolbar

More of what we are doing…

• Then we use the some of the other tools/tool bars to test individual items.

• WAVE or Web Developers Toolbar or WAT

Other Tools

WAT

Firebug

Automated Tools

• Deque Worldspace• HiSoft AccVerify– Compliance Sheriff

• SSB Bart AMP

• All automated tools require manual verification.

Current Section 508

• Most of us know “The 16” by heart and the Software Standards…– 1194.22 (a) – (p)– 1194.21 (a) – (l)

• The current tools / toolbars help with 1194.22

What should we be getting ready to do?

• The “refresh” and WCAG 2.0• What is added / What are the differences • What is the difference between “A”, “AA” &

“AAA”?– Easy– Harder– Hardest

• Refresh is mapping to “A” & “AA”• How should this change our testing approach?

What is Added?

• Keyboard Accessibility• “More” links• Form Errors• Live Captions• CAPTCHA

WCAG 2.0

• 1 Perceivable• 2 Operable• 3 Understandable• 4 Robust

Principle 1 – Perceivable

– 1.1 Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

– 1.2 Provide alternatives for time-based media.– 1.3

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

– 1.4 Make it easier for users to see and hear content including separating foreground from background.

Principle 2 - Operable

– 2.1 Make all functionality available from a keyboard.

– 2.2 Provide users enough time to read and use content.

– 2.3 Do not design content in a way that is known to cause seizures.

– 2.4 Provide ways to help users navigate, find content, and determine where they are.

Principle 3 - Understandable

– 3.1 Make text content readable and understandable.

– 3.2 Make Web pages appear and operate in predictable ways.

– 3.3 Help users avoid and correct mistakes.

Principle 4 – Robust

• 4.1 Maximize compatibility with current and future user agents, including assistive technologies.

Changes in testing

• KEYBOARD• KEYBOARD• KEYBOARD• Add a Screen reader– The JAWS “Links List” (Insert + F7) – Does it read error messages &/or Required fields?

Changes in Testing Tools

• Upgrade all of your tools– WAT 2011– Latest WAVE– Latest Web Developer– Firebug• Fireeyes

WAT 2011

Firebug / Fireeyes

Firebug / Fireeyes

Firebug / Fireeyes

New from Deque

• New Worldspace Sync• Updates Fireeyes for Firebug

• 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)

New from Deque

• Demo of new Fireeyes features

Changes in testing

• Screen Reader Simulator

References

• http://www.section508.gov/index.cfm?fuseAction=stdsdoc• http://www.w3.org/TR/WCAG/ • http://www.w3.org/WAI/WCAG20/from10/comparison/• http://webaim.org/standards/wcag/checklist • http://

www.usability.com.au/resources/wcag2checklist.cfm• http://www.icdri.org/Kynn/disability-comp.html • http://www.tomjewett.com/accessibility/508-WCAG2.html • http://uiaccess.com/drafts/WCAG2n508.html • http://www.deque.com/deque-fireeyes

Thank you

• Thank you for coming today.– By that I mean staying until Friday afternoon ;-)

• Stay tuned for changes – uh, I mean “Updates” - as the government moves to the refresh and WCAG 2.0 Guidelines.

• Follow the A11y Tribe on Twitter – Search #a11y – Follow the speakers here at CSUN

Connecting with Deque

Twitter LinkedIn Web Email @dequesystems Deque Systems deque.com info@deque.com