UAAG2 at CSUN

Below are my thoughts for the presentation submission. The idea for the
submission is for it to act as a scaffold to build the presentation for
March 2008. We are still in the preliminary stages of development of UAAG2
and I don't want to lock-in the presentation, or write something that cannot
be delivered or changes by March.

I would to have at least one additional name to add as a back-up or
co-presenter.

Title:
Bowser Accessibility: Towards User Agent Accessibility Guidelines 2.0
(UAAG20)

Abstract:
Current status of the development of the W3C User Agent Accessibility
Guidelines version 2 (UAAG2). Learn about the future of browser
accessibility.

Type: Lecture
Length: 60 min
Level: Intermediate (Beginner?)
Track: Internet/WWW

Paper:
Bowser Accessibility: Developing the User Agent Accessibility Guidelines 2.0
(UAAG20)
Authors: W3C User Agent Working Group (UAWG). (Jim Allan, Chair; Jan
Richards; Cathy Laws; Peter Perente; Kelly Ford; and others.)

User Agent Accessibility Guidelines 1.0 (UAAG 1.0) provided guidelines for
designing user agents (browsers) that lower barriers to Web accessibility
for people with disabilities (visual, hearing, physical, cognitive, and
neurological).

Since the release of UAAG 1.0 as a W3C Recommendation in December 2002, the
working group has received feedback about the usability, understandability,
and applicability of the suite of documents. Also, in the intervening years
there have been changes and improvements in

  a.. technologies and techniques used in web content,
  b.. functionality of assistive technology,
  c.. accessibility application programming interfaces (APIs), and
  d.. platforms used to receive content.
The feedback, changes, and information gathered from evaluating user agents
using test suites and implementation reports is driving the development of
UAAG 2.0.

We will discuss:

  1.. How UAAG 2.0 reflects structural changes made in the Authoring Tools
Accessibility Guidelines 2.0 and the Web Content Accessibility Guidelines
2.0 by separating the guidelines into the following areas: perceivable,
operable, understandable, and assistive technology friendly.
  2.. How future accessible browsers may implement Web 2.0, Accessible Rich
Internet Applications (ARIA), HTML 5, other emerging W3C technologies, and
other Web technologies. Or, to put it another way, what features, settings,
and controls are needed by users in their browser to gain full access to
these new information delivery mechanisms?
  3.. The separation of compliance responsibility by the core browser (IE,
Firefox, Safari, etc.) functions from browser extensions/add-ons and
assistive technologies (AT).
  4.. How the use of engineered platform accessibility APIs vs. DOM
(application-specific APIs) vs. off-screen models (OSMs) and heuristics
effect the user's access to information delivered by the browser.
  5.. How to participate in, or communicate with the working group.
References
1.      User Agent Working Group:
http://www.w3.org/wai/ua

2.      UAAG Requirements Document:
http://www.w3.org/WAI/UA/2007/UAAG20-REQUIREMENTS-20071005.html

3.  Issues Tracking Table for User Agent Accessibility Guidelines 1.0
http://www.w3.org/WAI/UA/2007/uaag_issues_11jan2007.html