Web Accessibility 101

34

description

Web Accessibility 101. Terrill Thompson Technology Accessibility Specialist University of Washington [email protected] http:// staff.washington.edu / tft. Q: Who is affected by inaccessible web content?. A: Everyone!. Ability on a continuum. See Hear Walk Read print Write with pen or pencil - PowerPoint PPT Presentation

Transcript of Web Accessibility 101

Page 1: Web Accessibility 101
Page 2: Web Accessibility 101

Web Accessibility 101Terrill Thompson

Technology Accessibility SpecialistUniversity of Washington

[email protected]://staff.washington.edu/tft

Page 3: Web Accessibility 101

Q: Who is affected by inaccessible web

content?

Page 4: Web Accessibility 101

A: Everyone!

Page 5: Web Accessibility 101

Ability on a continuum

SeeHearWalk

Read printWrite with pen or pencilCommunicate verbally

Tune out distractionetc.

Page 6: Web Accessibility 101

Old School Technologies

Page 7: Web Accessibility 101

Today: Technological Diversity

Page 8: Web Accessibility 101

We All Have Choices

Page 9: Web Accessibility 101

The Web Must Be _______.

• Flexible

Page 10: Web Accessibility 101

When is the web not flexible?

Page 11: Web Accessibility 101
Page 12: Web Accessibility 101
Page 13: Web Accessibility 101
Page 14: Web Accessibility 101
Page 15: Web Accessibility 101
Page 16: Web Accessibility 101
Page 17: Web Accessibility 101
Page 18: Web Accessibility 101
Page 19: Web Accessibility 101
Page 20: Web Accessibility 101

The Web Must Be _______.

• Perceivable• Operable• Understandable• Robust

Page 21: Web Accessibility 101

The Web Must Be Perceivable

Page 22: Web Accessibility 101

The Web Must Be Operable

Page 23: Web Accessibility 101

The Web Must Be Understandable

Page 24: Web Accessibility 101

The Web Must Be Robust

“SixthSense” from MIT Media Lab Fluid Interfaces Group: Using any surface as an interface

Page 25: Web Accessibility 101

World Wide Web Consortium (W3C)

• HTML, CSS, XML, SMIL• Web Content Accessibility Guidelines (WCAG)

– 1.0 became a “standard” in 1999– 2.0 became a “standard” in 2008– Three levels of success criteria

• 26 “Level A” success criteria – the most important• 13 “Level AA” success criteria – also important• 23 “Level AAA” success criteria – maximum accessibility

Page 26: Web Accessibility 101

Other W3C Standards & Specifications

• User Agent Accessibility Guidelines (UAAG)• Authoring Tool Accessibility Guidelines (ATAG)• Accessible Rich Internet Applications (ARIA)

– Provides markup that makes it possible to make complex interactive web applications accessible

Page 27: Web Accessibility 101

Who’s Responsible for Web Accessibility on Your Campus?

Page 28: Web Accessibility 101

People Who Create Web Sites

• Add alternate text to images• Use headings• Add labels to forms • Become familiar with WCAG 2.0

Page 29: Web Accessibility 101

People Who Create and/or Distribute Electronic Documents

• Add alternate text to images• Use headings• Add labels to forms • Become familiar with document

accessibility issues and techniques– PDF– Word– PowerPoint

Page 30: Web Accessibility 101

People Who Create Rich Interactive Web Applications

• Learn and apply WCAG 2.0• Learn and apply ARIA • Choose and use widgets, plug-ins,

modules and themes that are accessible

Page 31: Web Accessibility 101

People Who Produce and/or Distribute Audio or Video

• Develop a workflow for making media accessible– Captions – Audio description

• Choose accessible media players• Explore ways to maximize the benefit of

accessible media– Captions make video searchable – Captions make video translatable – Transcripts can be interactive

Page 32: Web Accessibility 101

People Who Procure Web Tools

• Ask vendors specific questions about accessibility

• Demand accessibility – We’re liable and at risk if your product

discriminates against any of our students– Only by demanding accessibility do we

create a market for it

Page 33: Web Accessibility 101

Questions to Always Ask When Procuring Product

• Is it accessible?• Can users perform all functions without a

mouse?• Has it been tested using assistive technologies

such as screen readers? • Is accessibility documentation available (e.g.,

Voluntary Product Accessibility Template)? • If an authoring tool, how does one create

accessible content with it?

Page 34: Web Accessibility 101

What Can You Do?