1 / 34

Web Accessibility 101

Web accessibility is crucial for everyone, as it ensures that people of all abilities can access and interact with online content. This guide discusses the importance of creating flexible, perceivable, operable, understandable, and robust websites. Highlighting the Web Content Accessibility Guidelines (WCAG) and the responsibilities of creators, it provides insights into making websites, documents, and rich media accessible. From adding alt text to images to ensuring compliance with accessibility standards, learn how to foster an inclusive digital environment that supports all users.

shadi
Télécharger la présentation

Web Accessibility 101

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Accessibility 101 Terrill Thompson Technology Accessibility Specialist University of Washington tft@uw.edu http://staff.washington.edu/tft

  2. Q: Who is affected by inaccessible web content?

  3. A: Everyone!

  4. Ability on a continuum See Hear Walk Read print Write with pen or pencil Communicate verbally Tune out distraction etc.

  5. Old School Technologies

  6. Today: Technological Diversity

  7. We All Have Choices

  8. The Web Must Be _______. • Flexible

  9. When is the web not flexible?

  10. The Web Must Be _______. • Perceivable • Operable • Understandable • Robust

  11. The Web Must Be Perceivable

  12. The Web Must Be Operable

  13. The Web Must Be Understandable

  14. The Web Must Be Robust “SixthSense” from MIT Media Lab Fluid Interfaces Group: Using any surface as an interface

  15. 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

  16. 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

  17. Who’s Responsible for Web Accessibility on Your Campus?

  18. People Who Create Web Sites • Add alternate text to images • Use headings • Add labels to forms • Become familiar with WCAG 2.0

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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?

  24. What Can You Do?

More Related