W3C home > Mailing lists > Public > www-qa-wg@w3.org > October 2002

Fwd: Request to advance UAAG 1.0 to Proposed Recommendation

From: Lofton Henderson <lofton@rockynet.com>
Date: Fri, 04 Oct 2002 10:54:34 -0600
Message-Id: <5.1.0.14.2.20021004105236.036eaec0@rockynet.com>
To: www-qa-wg@w3.org

QAWG members --

http://lists.w3.org/Archives/Member/chairs/2002OctDec/0006.html

It might be interesting for us to have a quick look at this, and see if 
UAAG has made the same sorts of changes that are reported for WCAG20.

Ref:  http://www.w3.org/QA/WG/qawg-issues-html#x101

-Lofton

>Resent-Date: Fri, 4 Oct 2002 11:20:15 -0400 (EDT)
>Date: Fri, 04 Oct 2002 11:20:05 -0400
>From: "Ian B. Jacobs" <ij@w3.org>
>Organization: W3C
>User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) 
>Gecko/20020623 Debian/1.0.0-0.woody.1
>X-Accept-Language: en-us, fr-fr, it
>To: steve@w3.org
>Cc: webreq@w3.org, chairs@w3.org, w3t-comm@w3.org, w3t-qa@w3.org,
>         timbl@w3.org, Karl Dubost <karl@w3.org>
>Subject: Request to advance UAAG 1.0 to Proposed Recommendation
>Resent-From: chairs@w3.org
>X-Mailing-List: <chairs@w3.org> archive/latest/2161
>X-Loop: chairs@w3.org
>Sender: chairs-request@w3.org
>Resent-Sender: chairs-request@w3.org
>List-Id: <chairs.w3.org>
>List-Help: <http://www.w3.org/Mail/>
>List-Unsubscribe: <mailto:chairs-request@w3.org?subject=unsubscribe>
>X-RCPT-TO: <lofton@rockynet.com>
>
>
>Steve,
>
>This is a request to advance "User Agent Accessibility Guidelines
>(UAAG) 1.0" [1] to Proposed Recommendation. The UAWG resolved to
>make this request at its 26 Sep 2002 teleconference [2]. We would
>like to publish the document on 15 October.
>
>The UAWG has been working actively on UAAG 1.0 since the end of
>1997. In this time, the document has received wide review from
>people in the disability community, developers, and other W3C
>groups.  The UAWG's deliverables history [3] includes evidence
>of wide review.
>
>The UAWG recently closed all issues from the fourth last call
>[4]. The resolutions clarified the document but did not increase
>the scope of its requirements. We incorporated most of the
>reviewers' suggestions into the 3 Oct draft [1]. Where we chose
>not to (see our substantive replies to reviewers [5]), the
>reasons were that we did not want to increase the scope of the
>document, or that we do not have implementation experience for
>the suggested feature.
>
>The fourth last call followed a second Candidate Recommendation
>period (see the announcement to AC [12] for implementation about
>expectations) that lasted approximately one year. During that
>time, the UAWG worked closely with developers to assess
>implementability of the specification and to promote the
>document. Out of the CR experience, the UAWG produced an
>implementation report [6], a form-based tool [7] for performing
>user agent evaluations that may be integrated into the report,
>and a draft HTML test suite [8] for UAAG 1.0.  Our charter [9]
>does not include a test suite as a deliverable, but the UAWG,
>with guidance from the QAWG, has made substantial progress on
>this tool, which we believe will promote the deployment of UAAG
>1.0.
>
>There have been no objections raised or withdrawn since those
>raised prior to the second Candidate Recommendation (before Sep
>2001). The three still in effect from earlier reviews are listed
>here [10].
>
>There are currently no patent disclosures regarding UAAG
>1.0; see the disclosures page [11].
>
>The abstract reads:
>
>   This document provides guidelines for designing user agents
>   that lower barriers to Web accessibility for people with
>   disabilities (visual, hearing, physical, cognitive, and
>   neurological). User agents include HTML browsers and other
>   types of software that retrieve and render Web content. A user
>   agent that conforms to these guidelines will promote
>   accessibility through its own user interface and through other
>   internal facilities, including its ability to communicate with
>   other technologies (especially assistive
>   technologies). Furthermore, all users, not just users with
>   disabilities, are expected to find conforming user agents to be
>   more usable.
>
>   In addition to helping developers of HTML browsers and media
>   players, this document will also benefit developers of
>   assistive technologies because it explains what types of
>   information and control an assistive technology may expect from
>   a conforming user agent. Technologies not addressed directly by
>   this document (e.g., technologies for braille rendering) will
>   be essential to ensuring Web access for some users with
>   disabilities.
>
>In the event that the request to advance is approved, I will
>prepare a Proposed Recommendation version of the
>document for the Webmaster.
>
>Thank you,
>
>  - Ian
>
>P.S. For this request, I am test driving the new draft 'How to
>Organize a PR review' [13].
>
>
>[1] http://www.w3.org/WAI/UA/WD-UAAG10-20021003/
>[2] http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0173
>[3] http://www.w3.org/WAI/UA/Deliverables
>[4] http://www.w3.org/WAI/UA/issues/issues-linear-lc4
>[5] http://www.w3.org/WAI/UA/Deliverables#lc4-reviews
>[6] http://www.w3.org/WAI/UA/impl-pr2
>[7] http://www.w3.org/WAI/UA/2002/08/eval
>[8] http://www.w3.org/WAI/UA/TS/html401/
>[9] http://www.w3.org/WAI/UA/charter-20011218
>[10] http://www.w3.org/WAI/UA/2001/08/lc3-dispo#objections
>[11] http://www.w3.org/WAI/UA/disclosures
>[12] http://lists.w3.org/Archives/Member/w3c-ac-members/2001JulSep/0025
>[13] http://www.w3.org/2000/11/StartReview-20001103
>
>--
>Ian Jacobs (ij@w3.org)   http://www.w3.org/People/Jacobs
>Tel:                     +1 718 260-9447
>
Received on Friday, 4 October 2002 12:53:34 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:11 GMT