[DRAFT] User Agent Accessibility Guidelines Working Group
Charter
The mission of the User
Agent Accessibility Guidelines Working Group (UAWG), part of the WAI Technical Activity, is
to produce guidelines for the development of accessible user agents
(e.g., browsers, media players, mobile applications, etc.) and their
interoperability with assistive technology: software that retrieves and
renders Web content, including text, graphics, sounds, video, images,
etc. In particular, the UAWG will publish the User
Agent Accessibility Guidelines (UAAG) 2.0 as a W3C Recommendation.
This mission is complementary to the work of other Web
Accessibility Initiative (WAI) groups within the WAI
Technical Activity and the WAI
International Program Office Activity.
End date |
31 December 2017 |
Confidentiality |
Proceedings are Public.
Some communications between editors and/or during the
implementation testing period may be member-confidential. |
Initial Chairs |
Jim Allan |
Initial Team Contacts
(FTE %: 40) |
Jeanne Spellman |
Usual Meeting Schedule |
Teleconferences: Weekly
Face-to-face: 1-2 per year |
Scope
The UAWG's scope of work includes:
- Develop UAAG 2.0 as a
W3C Recommendation.
- Develop UAAG 2.0
Reference as a Note.
- Develop public UAAG
2.0 Test Materials to support the evaluation of UAAG 2.0
implementations and to support ongoing user agent accessibility
testing of their products.
- Document implementation testing experience of UAAG 2.0 to meet
Candidate Recommendation requirements.
- Develop UAAG 2.0 support materials in cooperation with the EOWG.
Where appropriate, the UAWG may link to the resulting documents or
the documents may be hosted by the Working Group as W3C Notes.
- Maintain UAAG 2.0 Reference post-Recommendation with additional
examples and resources for user agents on specific types of devices,
technologies, and industries including mobile, media, webTV, and
digital publishing.
- Review and comment on the work in other W3C Working Groups for
dependencies with the requirements of UAAG 2.0.
- Contribute input where appropriate into WAI 2020 Framework
Consistent with W3C
Process requirements on Task Forces, the UAWG may form task
forces composed of UAWG participants or join other W3C task
forces to carry out assignments when under the chartered scope of
UAWG. Any such task force must have a work statement (including
objectives, communication, participation, and leadership) that has
been announced on the UAWG mailing list, approved by the UAWG, and is
available from the UAWG home page. UAWG task forces should produce
requirements documents that outline the scope and expectations for
work. Task forces may set up separate teleconferences and hold
face-to-face meetings per the W3C process and with the approval of the
UAWG.
Success Criteria
- Publication of Testing Materials to support UAAG 2.0 conformance
during Candidate Recommendation and to support .
- By the end of Candidate Recommendation, there are implementations
of UAAG 2.0 that meet the exit criteria.
- Publication of UAAG 2.0 as a W3C Recommendation.
- Publication of Implementing UAAG 2.0 as a Note.
Deliverables
W3C Technical Reports
Other Deliverables
- UAAG 2.0 Testing Materials, to help support UAAG 2.0 conformance.
- Input into WAI 2020 Framework.
Milestones
Milestones
Note: The group will document
significant changes from this initial schedule on the group home
page. |
Specification |
FPWD |
LC |
CR |
PR |
Rec |
Other publications |
UAAG 2.0 Guidelines |
March 2008 |
Sept 2013 |
Apr 2015 |
Apr 2016 |
Jun 2016 |
|
UAAG 2.0 Reference |
|
|
|
|
|
Jun 2016 |
Testing Materials |
|
|
|
|
|
Dec 2014 |
Guides & support materials |
|
|
|
|
|
Dec 2017 |
Timeline View Summary
- Q3 2013:
- Publish Last Call Working Draft of UAAG 2.0
- Publish updated Working Draft of Implementing UAAG 2.0
- Write tests for UAAG 2.0
- Q4 2013 - Q1 2015:
- Respond to comments on Last Call Working Draft of UAAG 2.0 and
Implementing UAAG 2.0
- Followup with commenters and publish working draft for review
and acceptance of changes
- Publish a second Last Call Working Draft of UAAG 2.0
- Provide regular updates of UAAG 2.0 Test Materials
- Confirm implementers of UAAG 2.0 success criteria
- Write exit criteria for Candidate Recommendation
- Q2 2015 - Q1 2016:
- Publish Candidate Recommendation of UAAG 2.0
- Publish updated Working Draft of Implementing UAAG 2.0
- Provide regular updates of UAAG 2.0 Test Materials
- Respond to public comments on Candidate Recommendation of UAAG
2.0 and Implementing UAAG 2.0
- Test implementations of UAAG 2.0
- Work with UAAG 2.0 implementers to address issues
- Prepare UAAG 2.0 Implementation Report
- Q2 2016:
- Publish Proposed Recommendation of UAAG 2.0
- Publish updated Working Draft of Implementing UAAG 2.0
- Prepare announcements and promotional materials
- Publish UAAG 2.0 as a W3C Recommendation
- Publish Implementing UAAG 2.0 as a Working Group Note
- Publish UAAG 2.0 Test Materials as a Working Group Note
- Q3 2016 - Q4 2017:
- Update public testing materials
- Support best practices and promotion of UAAG 2.0
- Publish guides and support materials for emerging
technologies, devices, specific industries and disabilities
- Process any public comments on UAAG 2.0 and publish Errata if
necessary
- Input into WAI 2020 Framework
Dependencies
W3C Groups
- (WAI) Web Content Accessibility Guidelines WG:
If the user interface of a user agent is web-based (e.g. media
player), UAAG 2.0 relies on the Web Content Accessibility Guidelines
2.0 for conformance for web content.
- (WAI) Indie UI WG:
UAAG 2.0 encourages modality independence, and supports the IndieUI
working group establishing the technological solutions for those
needs.
- (WAI) Authoring Tool Accessibility Guidelines WG:
User agents are commonly involved in web content authoring: preview
tools, checking tools, edit modes, automated content changes, and
providing a platform for web-based authoring tools (e.g. blog, wiki
or social networking). The UAWG cooperates with the AUWG in these
areas.
- (WAI) Protocols and Formats WG (PFWG
public page): The UAWG provides input on accessibility
requirements with regard to W3C technologies for which PFWG manages
dependencies.
- (WAI) Education and Outreach WG: UAWG
provides input to EOWG to assist in promoting awareness and
implementation of UAAG 2.0.
The UAWG may also interact with non-WAI W3C Working Groups (e.g.,
CSS WG, HTML WG, Compound Document Formats WG, WebAPI WG, etc.) either
via the
Protocols and Formats Working Group or directly in the case of
responding to
requests for input on suggested user agent behavior.
Furthermore, UAWG expects to follow this W3C Recommendation where
appropriate:
Participation
To be successful, the UAWG is expected to have 6 or more active
participants
for its duration, with participation where possible including
representation
from industry, disability communities, accessibility research and
government.
Effective participation in UAWG is expected to consume 6 hours per
week for
each participant; one day per week for editors.
Participants are reminded of the Good
Standing
requirements of the W3C Process.
Communication
Proceedings are Public.
Some communications between editors and/or during the implementation
testing period may be member-confidential. This group primarily
conducts its work on the public mailing list
w3c-wai-ua@w3.org (archive).
The public
mailing list public-uaag2-comments@w3.org (archive)
is used for public feedback.
This group participates in the WAI Coordination Group. In the event
that Coordination Groups are discontinued under W3C Process, it will
continue to coordinate directly with other WAI groups.
Information about the group (deliverables, participants, face-to-face
meetings, teleconferences, etc.) is available from the User
Agent Accessibility Guidelines Working
Group home page.
Decision Policy
As explained in the Process Document (section
3.3),
this group will seek to make decisions when there is consensus. When
the Chair
puts a question and observes dissent, after due consideration of
different
opinions, the Chair should record a decision (possibly after a formal
vote) and
any objections, and move on.
- When deciding a substantive technical issue, the Chair may put a
question before the group. The Chair must only do so during a group
meeting, and at least two-thirds of participants in Good Standing
must be in attendance. When the Chair conducts a formal
vote to reach a decision on a substantive technical issue,
eligible voters may vote on a proposal one of three ways: for a
proposal, against a proposal, or abstain. For the proposal to pass
there must be more votes for the proposal than against. In case of a
tie, the Chair will decide the outcome of the proposal.
- This charter is written in accordance with Section
3.4, Votes of the W3C Process Document and includes no voting
procedures beyond what the Process Document requires.
Patent Policy
This Working Group operates under the W3C
Patent Policy
(5 February 2004 Version). To promote the widest adoption of Web
standards, W3C
seeks to issue Recommendations that can be implemented, according to
this
policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group,
please see
the W3C Patent Policy
Implementation.
About this Charter
This charter for the User Agent Accessibility Guidelines Working Group
has
been created according to section
6.2 of the Process
Document. In the event of a conflict between this
document or the provisions of any charter and the W3C Process, the W3C
Process
shall take precedence.
The UAWG was first chartered in December
1997. The UAWG was rechartered on 5
November 1999, 5
May
2000, 18
December
2001, 1
January 2005 and on 23
August 2010 (previous charter). Primary changes in this charter:
- Includes mobile applications to definition of user agents in the
Mission section.
- Adds developing support materials in coordination with EOWG and
commenting on the work in the W3C working groups
- Adds test materials and implementations of UAAG 2.0 during Candidate
Recommendation.
- Adds a dependency with Indie UI WG
- Adds input into WAI 2020 Framework
Jim Allan, Co-Chair
Jeanne Spellman, Staff Contact
Copyright
© 2014 W3C®
(MIT,
ERCIM,
Keio, Beihang),
All Rights Reserved.
$Date: 2015/02/23 22:59:20 $