W3C logo Web  Accessibility Initiative    (WAI) logo

(DRAFT) WAI Authoring Tool Guidelines Working Group Charter

(WAI-AU)

  1. Mission
  2. Scope
  3. Duration
  4. Deliverables
  5. Dependencies of other groups on this group's deliverables
  6. Dependencies of this group on other groups' deliverables
  7. Intended degree of confidentiality
  8. Relation to other groups
  9. Milestones for work items & deliverables
  10. Meeting mechanisms & schedules
  11. Communication mechanisms
  12. Voting mechanisms
  13. Level of involvement of Team
  14. W3C staff contact
  15. Estimate of time commitment a group member would have to make in order to participate
  16. Participants
  17. How to join

1. Mission

Compose and assess implementation of W3C guideliness which can be used to ensure that authoring tools achieve two objectives:

  1. to provide author support for creating accessible Web documents, and
  2. to make authoring tools accessible to authors with disabilities.

2. Scope

2.1 Scope of WAI AU guidelines

The scope of applicability for WAI AU is tools which are used to produce Web content. These include:
  1. Editing tools specifically designed to produce Web content (eg WYSIWYG HTML editors)
  2. Tool which offer the option of saving material in a web format (eg Word Processors or desktop publishing packages)
  3. Tools which translate documents into web formats (eg from PDF to HTML)
  4. Tools which produce Multimedia, especially where it is intended for use on the web (eg video production adn editing suites)
  5. Tools for site management or site publication (including on-the-fly conversion and website publishing tools)

2.2 Criteria for success

The adoption of Authoring Tool Guidelines as a Recommendation by the W3C. Widespread implementation of the guidelines would be a further measure of success. Given lead times for development of software this is unlikely to be achieved within the duration of the activity.

3. Duration of work items

The WAI AU Activity is expected to continue for approximately eight and a half months, until 1 October 1999.

4. Deliverables

The WAI Authoring Tools Guidelines, as Working drafts and as a Proposed Recommendation.

5. Dependencies of other groups on this group

5.1. Groups which will use deliverables

  1. The deliverables will be used by the WAI Education and Outreach activity to promote the development of tools which lead to a more accessible web.
  2. Activities such as the Amaya project, the graphics activity, and others, will use the guidelines in designing their own goals and outcomes.

5.2 Liaison Methods

The Chair of the WAI AU sits on the WAI Coordination Group (CG) which is made up of chairs of all the WAI groups and two or more at-large representatives of the WAI IG.

6. Dependencies of this group on other groups

6.1 Groups on whose work this activity explicitly depends:
  1. The WAI Page Authoring Guidelines group
  2. The WAI User Agent Guidelines group
  3. The WAI Interest Group
6.2 Groups whose work will be or is likely to be used

W3C Groups:
  1. The WAI Protocols and Formats group
  2. The WAI Evaluation and Repair Working Group
  3. The Internationalisation (I18N) activity
Other Groups:
  1. Groups with specific expertise in user interface and assistive technology.
  2. Developers of Authoring Tools.
  3. Writers' and content providers' groups.

7. Intended degree of Confidentiality

The WAI AU home page, proceedings, and charter are all public.

8. Relation to other groups

8.1 Relation to W3C Groups

  1. This group is related to other W3C groups via the dependencies on deliverables described in sections 5 and 6 above.

8.2 Relation to External Groups

The WAI AU activity will rely on the expertise of various groups, some of whom may be outside the W3C, as described in the dependencies in item 5 above.

9. Milestones for work items and deliverables

Note: The milestones assume that the Working group will produce a working draft every six weeks. It will be presented to the WAI IG for comment, with one week allowed for comment and a further week for those comments to be reviewed by the WG and incorporated into the document before release as a public working draft. There are then four weeks before the working group produces its next (internal) working draft.

10. Meeting mechanisms & schedules

The primary fora for WAI AU discussion are the WAI AU mailing list, and regular (weekly to fortnightly) teleconferences. As an alternative to telconferences the group will trial the use of an Internet-based chat system, which will provide logging of the session. If the group unanimously feels that this is an improvement it may be adopted in place of some scheduled telephone conferences.

The WAI AU will hold regular face-to-face meetings, where practicable in conjunction with other WAI face-to-face meetings or with an event where WAI IG members gather. WAI AU meetings are announced to W3C Member organizations, to WAI AU participants through the WAI AU mailing list, to WAI IG participants via the WAI IG mailing list, and to the general public via the WAI home page.

11. Communication mechanisms

11.1 Communication within the group

  1. WAI AU mailing list
  2. Publication of minutes or log files for all meetings
  3. WAI AU group home page
  4. Face-to-face meetings

11.2 Communication with W3C

  1. WAI AU coordinates with other WAI working groups through the WAI Coordination Group;
  2. WAI AU coordinates with W3C through the WAI Domain Leader;
  3. WAI Domain Leader communicates about W3C and WAI activities through postings to WAI IG;
  4. WAI groups report to the WAI IG at quarterly face-to-face meetings.

11.3 Communication with the public

12. Voting mechanisms and Escalation

One vote per member organisation or technical expert's organisation, via e-mail, as per the standard W3C process for working groups [http://www.w3.org/Consortium/Process/Plan/process.html#GroupsWG]

13. Level of involvement of Team

70% Charles McCathieNevile,
5% Ian Jacobs, 5% Judy Brewer, 5% Daniel Dardailler

14. W3C staff contact

Charles McCathieNevile

15. Estimated time and effort commitments a group member would have to make in order to participate

It is expected that participants would need to commit 3-6 hours per week, including meetings other than face to face meetings. Participants are expected to attend teleconferences and meetings, or send regrets to the chair at least one day in advance of teleconferences, one week in advance of meetings. Participants are expected to respond in a timely manner to discussion taking place on the email list. Participants are also expected to maintain up-to-date familiarity with the WAI Page Authoring and User Agent Guidelines, as Working Drafts as well as Recommendation.

16. Participants

As the Web Accessibility Initiative is a multi-stakeholder/partnership project, it is critical that different stakeholders in Web accessibility are represented on the WAI AU group. These include:

17. How to join

To join the working group please complete the following information and return by email to wai-au-call@w3.org.

==============================================================

First Name:

Last Name:

Email Address

Telephone Number

Employer / Organisation:

Area of interest:
(Non W3C members please state area of expertise)

I have read the charter for this group, and agree to participate as per the charter

Intellectual Property Rights: To the best of my knowledge, I believe my organization has the following/does not have any IPR claims regarding Guidelines for the Accessibility of Authoring Tools.

==============================================================


Jutta Treviranus, Charles McCathieNevile

7 January 1999

Copyright  ©  1998, 1999 W3C (MIT, INRIA, Keio ), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.