WAI Outreach Videos

From W3C Wiki
Jump to: navigation, search

These are being developed with EOWG, the W3C Web Accessibility Initiative (WAI) Education and Outreach Working Group. Comments welcome.

All - other guidelines

Draft script (2 minutes)

style: chatty, friendly, a little clippy

  • visual: WCAG

Maybe you've heard about WCAG - Web Content Accessibility Guidelines from the W3C Web Accessibility Initiative (WAI). That's the web standard that tells you what to do to make your websites and web applications accessible to people with disabilities.

But do you also know about it's friends? Ya, WCAG is not alone. Along with it is ATAG and UAAG, and cousin ARIA.

  • visual: ATAG

ATAG - that's Authoring Tool Accessibility Guidelines, A-T-A-G. ATAG says what to do to make authoring tools accessible so people with disabilities can use them. It also says what the authoring tools should do to make it easier to make websites accessible. ATAG applies to HTML editors, content management systems, blog software, and such.

  • visual: UAAG

Then there's UAAG - User Agent Accessibility Guidelines, U-A-A-G. UAAG covers web browsers, media players, and such. It says what they need to do for accessibility.

  • visual: WAI-ARIA

WAI-ARIA is a technical specification that works along with those guidelines. It provides some details for making things work under the hood, that is, in the markup and code. ARIA stands for Accessible Rich Internet Applications.

When authoring tools, browsers, and websites better meet these standards, the web is more accessible.

  • visual: www.w3.org/WAI/intro/components

Learn more from Essential Components of Web Accessibility at w3.org/WAI/intro/components

Notes & Comments


Developers - ATAG & Involving Users


  • Developers, designers, authors
  • Managers

Secondary audience:

  • Procurers

Draft script (2 minutes)

style: short, clippy, edgy

Hey, I'm Shawn Henry from W3C Web Accessibility Initiative (WAI) - here with a 2 minute message to web developers.

What if I had a silver bullet that would automatically make all your web projects accessible?... Sorry, I don't. But I do have two tips that will help significantly: 1.ATAG{a-tag}, 2.users.

  • visual: 1. ATAG 2. users

First: ATAG{a-tag} - that's Authoring Tool Accessibility Guidelines, A-T-A-G. Authoring tools are the things you use to create websites, such as content management systems, HTML editors, and blog software. There are things these tools can do to make it easier for you to create accessible websites. ATAG defines what these things are. So the more your authoring tool meets ATAG, the more accessible your websites can be with less effort.

Second: Users. Don't just try to follow standards blindly (pun intended). Learn how people use the web in different situations. Watch some videos. Hook up with some real people with disabilities and have them show you the strategies and technologies they use to get around your website. Every heard a screen reader spitting out your web page like a rap song? (background: screen reader rappin') Or someone using your web app all with voice control? It's pretty cool. Know your users and the guidelines will make more sense, and make your web sites better for you, your users, and your organization.

Two tips:

  1. Tell your authoring tool vendor that you want them to meet ATAG.
  2. Learn from users with disabilities how they use your website.


  • (long pause:-)
  • visual: www.w3.org/WAI/intro/atag
  • For more information, see the ATAG Overview at w3.org/WAI/intro/atag
  • visual: www.w3.org/WAI/users/involving
  • and Involving Users in Web Projects for Better, Easier Accessibility at w3.org/WAI/users/involving

Notes & Comments


All - What is ATAG

DRAFT script for basic intro: (2 minutes)

style: clear, friendly, not too fast

visual: talking head

  • Hi, I'm Jeanne and I'd like to tell you about authoring tool accessibility.
  • Authoring tools are software or services that people use to create web pages. For example, content management systems are authoring tools. So are blogs.
  • There are two aspects to authoring tool accessibility:
    • A. the tool itself is accessible so people with disabilities can use it
    • B. the tool helps create accessible content (that is, web pages and web applications)

visual: A. tool itself is accessible

  • The first is essential so that everyone can write to the Web, whether they are technical developers creating a new web application, or casual users commenting on a blog, or anywhere in between.

visual: B. tool helps create accessible content

  • The second is about the tool making it easy for developers, designers, content authors and others to make their web content accessible. visual: alt text dialog box For example, when an author puts a new image on a web page, the tool asks for alternative text and offers help on what makes good alt text.
  • Both of these are covered in "a-tag" - Authoring Tool Accessibility Guidelines - A-T-A-G - "a-tag".

visual: ATAG

  • If the websites you use to add web content (such as social networking sites) meet ATAG, they will be accessible to all. If the software that you use to create websites meet ATAG, it will help you make your websites more accessible at all.
  • Would you do something for me? Tell your authoring tool vendor that you want them to meet ATAG! (long pause:-)

visual: www.w3.org/WAI/intro/atag

  • For more information, see the ATAG Overview at w3.org/WAI/intro/atag

Notes & Comments

  • maybe to a basic intro like above, then do a catchier more advanced, slightly longer one as well?
  • [jb] Ideas:
    • maybe start: in 2 minutes I want to tell you three basic things to keep in mind about au ax.
    • here are the three things you can do now:
      • feedback
      • look for tools
      • contact your vendors

People with disabilities & advocates - contact inaccessible websites

Draft script (2 minutes)

style: clear, encouraging

Hi, I'm Shawn Henry from W3C Web Accessibility Initiative (WAI). WAI develops strategies, guidelines, resources to make the Web accessible to people with disabilities.

Here's a question for you: What do you do when you come across an inaccessible website? (I admit that I often yell at the computer.) What about after that initial outburst of frustration? (I sometimes send an e-mail encouraging them to fix it.)

WAI encourages you to tell organizations how important it is that their websites are accessible. Especially when you come across accessibility barriers, tell the organization about it!

We have some guidance to help make this easier and hopefully more effective. It's in a document called: Contacting Organizations about Inaccessible Websites. It walks through steps, provides lots of tips, and includes sample e-mails.

Just yelling at your computer isn't going to get the accessibility barriers fixed. Just complaining on a blog or other place where the organization won't see it isn't likely to help.

Instead, consider what approach will get the results you want. An encouraging e-mail is often a good first step. Sometimes organizations are not even aware of accessibility issues, and don't know how web accessibility is vital for equal rights, required by law in some cases, and has strong business benefits.

  • visual: www.w3.org/WAI/users/inaccessible

See Contacting Organizations about Inaccessible Websites at www.w3.org/WAI/users/inaccessible that's www.w-the-number-3.o-r-g/WAI/users/i-n-a-c-c-e-s-s-i-b-l-e

Notes & Comments


Standards Harmonization

style: formal, authoritative

Judy Brewer, director of W3C Web Accessibility Initiative (WAI)

Notes & Comments


Document Information

Status: Draft Updated August 2011.

Developed with EOWG, the W3C Web Accessibility Initiative (WAI) Education and Outreach Working Group. Lead Editor: Shawn Lawton Henry.

Copyright © 2011 W3C ® (MIT, ERCIM, Keio) Usage policies apply.

This wiki page is published and licensed under a Creative Commons Attribution 3.0 Unported License.

For attribution requirements, see the Creative Commons License (CC) section of Using WAI Material.