Introduction: visual user view

image with no alt text

image with no alt text

image with no alt textimage with no alt text

Marja-Riitta Koivunen
Research Scientist

MIT/LCS

a user with vision and big screen

Slides available at:
http://www.w3.org/2002/Talks/swandwai/

Introduction: nonvisual user view

greyed image with no alt text

greyed image with no alt text

greyed image with no alt textgreyed image with no alt text

Marja-Riitta Koivunen
Research Scientist

MIT/LCS

a blind user screena user with phone driving a car

Why important?

vision, hearing, physical diffi

Introduction: nonvisual user view with alt text

Model of a building W3C is going to move to next year. The building looks like it has just gone through an earthquake. There are no straight walls.

W3C icon

semantic webweb accessibility

Marja-Riitta Koivunen
Research Scientist

MIT/LCS

a blind user screena user with phone driving a car

Introduction: machine view with or without alt text

greyed image

greyed image

greyed imagegreyed image

greyed text (name)

greyed text (affiliation)

a machine as a user

Why important?

"The bane of my existence is doing things that I know the computer could do for me." -- Dan Connolly, The XML Revolution

Introduction: machine view with metadata

the slide with nodes and arcs a machine can understand

a machine as a user

Contents

Web Accessibility Initiative (WAI)

WCAG theme 1: Graceful transformation

brailledevice, cellphone, palm, radio

WCAG Guidelines 1-11

  1. Provide equivalent alternatives to auditory and visual content.
  2. Don't rely on color alone.
  3. Use markup and style sheets and do so properly.
  4. Clarify natural language usage.
  5. Create tables that transform gracefully.
  6. Ensure that pages featuring new technologies transform gracefully.
  7. Ensure user control of time-sensitive content changes.
  8. Ensure direct accessibility of embedded user interfaces.
  9. Design for device-independence.
  10. Use interim solutions.
  11. Use W3C technologies and guidelines.

WCAG theme 2: Understandable and navigable content

street signs, warning signs, he

WCAG Guidelines 12-14

  1. Provide context and orientation information.
  2. Provide clear navigation mechanisms.
  3. Ensure that documents are clear and simple.

Homework 1: Validate content

people checking a document

Homework 2: Check accessibility

people checking a document

Semantic Web (SW) Activity

a bed time story...

Semantic Web - Layers

architectural layers

Main SW principles

Anything can have a URI:

documents, organizations, people, buildings

Resources and links have types:

current web with two greyed resources and a generic href linksemantic web with typed resources as nodes and typed links as arcs

SWELL example: Chain of trust

example of trust processing

Zakim: meeting bot

bot that keeps track of meeting participants, speaker queue and agenda items on irc channel

http://www.w3.org/2001/12/zakim-irc-bot

Annotea: shared annotations

browser integrates HTTP information from web server and annotea servers so that annotations are presented to user in the document's context

http://www.w3.org/2001/Annotea

Annotea: sample UI

pencils mark annotations in the document and open into annotation windows, replies to annotations open into reply windows

Homework 3: Use metadata

The END

stick man waving goodbye