slanted W3C logo
Cover page images (keys)

Accessibility of Emerging Rich Web Technologies

Michael Cooper
Web Accessibility Initiative
cooper@w3.org

Outline:

Introduction

Photo of Michael Cooper

Notes:

Topics

 

Notes:

Semantic Web

 

Notes:

Benefits

Benefits

Notes:

Alternate Interface

Alternate interface to Amazon from Simplest shop.

Notes:

Alternate Interface

Alternate interface to Amazon from Amazon Lite.

Notes:

Automated discovery of Semantics

Notes:

Challenges

Design

Notes:

Reference additional technical challenges raised by Becky: focus changes, content update

Complex, updated information

Yahoo Finance page.

Notes:

Aggregated news portal page

AOL portal page.

Notes:

Microformats

Notes:

Ability to Support

Notes:

Solutions

Components of accessibility

Relationship of components of accessibility

Notes:

Tool support

Notes:

Authoring resources

Notes:

WCAG Technique

H42: Using h1-h6 to identify headings

Applicability

(X)HTML

This technique relates to:

Description

The objective of this technique is to use HTML heading markup to convey the structure of the content. Heading markup can be used:

In HTML 4.01 and XHTML 1.x, heading markup is designed to convey logical hierarchy, and heading elements include numbers (h1 through h6). Skipping levels in the sequence of headings may create the impression that the structure of the document has not been properly thought through or that specific headings have been chosen for their visual rendering rather than their meaning. CSS (Cascading Style Sheets) can be used to change the way headings look or sound.

Since headings indicate the start of important sections of content, it is possible for users with assistive technology to jump directly to the appropriate heading and begin reading the content. This significantly speeds interaction for users who would otherwise access the content slowly.

Using headings merely to change the appearance of text does not convey the organization of the content, and may confuse users who use headings to perceive structure or rely on them for navigation. Conversely, while applying bold format, or even "class=heading", can result in the visual display of a heading, assistive technologies will not recognize such text as headings.

Examples

Example 1: Headings show the overall organization of the content

In this example, heading markup is used to make the navigation and main content sections perceivable.

    <!-- Logo, banner graphic, search form, etc.  -->
    <h2>Navigation</h2>
      <ul>
        <li><a href="about.htm">About us</a></li>
        <li><a href="contact.htm">Contact us</a></li>
         ...
      </ul>
    <h2>All about headings</h2>
    <!-- Text, images, other material making up the main content... -->  

Resources

Resources are for information purposes only, no endorsement implied.

Tests

Procedure

  1. Check that heading markup is used when content is a heading.
  2. Check that heading markup is not used when content is not a heading.

Expected Results

Notes:

Technology Standards

Notes:

XML Accessibility Guidelines

Notes:

Accessible Rich Internet Applications

Notes:

ARIA Details

Notes:

WAI-ARIA Example: Checkbox

Notes:

Convergence

Semantic Web could improve accessibility and interoperability of Web 2.0

Notes:

Navigation Mashup

Ottawa pathways route

Tracing route on mapping program

Data exchanged by API

If Semantic Web technologies used for interchange...

Notes:

Navigation Mashup

...could output to mobility aid

GPS Mobility Aid
GPS receiver

Notes:

Future

New Paradigms

Notes:

Research

Notes:

Professionalization

Notes:

Recap / Discussion

Notes:

Thank you

http://www.w3.org/2007/Talks/0508-W4A-MC/

Accompanying paper

Get involved!

Michael Cooper
cooper@w3.org