W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2012

Agenda: UAWG telecon 6 Sept 2012

From: Jim Allan <jimallan@tsbvi.edu>
Date: Tue, 4 Sep 2012 12:39:32 -0500
Message-ID: <CA+=z1WnkKme1RbpsE1djWn3TSNp=VdBxtPMAkGfxd1jHOj3otg@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
Time: User Agent Working Group will begin  the call at 1 pm Boston
Local Time, (17:00-18:30 UTC/GMT)
http://www.timeanddate.com/worldclock/meeting.html Call-in:

Zakim bridge at: +1-617-761-6200, for UK use SIP phone call zakim via

Code:  82941# (UAWG1#)

IRC: server: irc.w3.org, port: 6665, channel: #ua.

Chair: Jim Allan, Kelly Ford

Latest editor's draft -

Agenda+ Conformance discussion - continued
There is no UA that will meet all of the needs of all users. A user
agent provides a foundation from which to build an accessible user
experience. The user will build on the foundation through the use of
extensions or plug-ins and possibly use assistive technology to meet
their individual needs. Support for accessibility needs exists in
several layers.  First, is the platform or operating system.
Accessibility features of platforms may include keyboard/mouse/touch
navigation, high contrast mode, keyboard enhancements (sticky keys,
bounce keys, etc.), some screen reading functionality, some
magnification or the ability to choose base fonts and sizes. Second,
the base browser, extensions and plugins added to browser functions,
and assistive technology added to the platform. The user agent
generally is an application that runs on the platform. It may provide
additional accessibility features that work in conjunction with the
platform (e.g. pass through high-contrast settings) and some my
override the platform features (e.g. change the default font, size,
and color) in the user agent. Third, are extensions, which are
enhancements that are installed by the user and essentially become
part of the User Agent. Another layer is plug-ins. These are external
applications that render specific content and may use the browser as a
delivery mechanism. Plug-ins essentially become the user agent for
specific content types. Finally, a user may not have their particular
accessibility needs met by the use of the previous layers and add the
use of assistive technology(AT). Assistive technology is an
application that runs on the platform to enhance the user experience
on the platform and its applications (including the browser). The AT
may have specific functionality for browsers.
Conformance to each of SCs of UAAG20 includes
  1 id the platform
  2 id the user agent
  3 id extension(s) necessary if any
  4 id plug-in(s) necessary if any
  5 id Assistive technology necessary for specific classes of users.
Except for a few SCs (e.g. those related to speech output and
synthesizer configuration, need to id others) all SC should be met by
a combination of 1-4.

Using the above, created a conformance claim for 1.1.1. it got pretty
cumbersome. Perhaps breaking out all of the media types is more for
testing? Not sure where this will lead.
Conformance for 1.1.1 Render Alternative Content [was 1.1.3]: For any
content element, the user can choose to render any types of
alternative content that are present. (Level A)
html Images - alt
1. windows 7
2. Generic
3-5. none needed

captions for video
1. OS Lion
2. Generic-Mac
3. none needed
4. media player with captions turned on
5. none needed

longdesc (or whatever)
title for abbr etc. (or all titles?)

comments welcome before meeting.

Agenda+ Level Discussion: drafting criteria for determining levels

Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Tuesday, 4 September 2012 17:40:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:41 UTC