Accessible Platform Architectures Working Group Charter

The mission of the Accessible Platform Architectures Working Group (APA WG, formerly part of the Protocols and Formats Working Group) is to ensure W3C specifications provide support for accessibility to people with disabilities. The group advances this mission through review of W3C specifications, development of new specifications and technical support materials, collaboration with other Working Groups, and coordination of harmonized accessibility strategies within W3C.

This mission is complementary to the work of other Web Accessibility Initiative (WAI) groups.

Join the Accessible Platform Architectures Working Group . Group.

22 October 2015 Initial Usual
Start date 08 August 2018
End date 31 July 2018 2021
Charter extension The charter extension history is documented in " About this charter " Confidentiality Proceedings are public . Initial Chairs Janina Sajka
Team Contacts (FTE %: 40) Michael Cooper (25%) (0.30 FTE Primary TC ), Ruoxi Ran (0.25 FTE for COGA Task Force , Personalization Semantics , and AHR ), Shadi Abou-Zahra (5%) Liam Quin (10%) (0.05 FTE for RQTF ), Judy Brewer (0.10 FTE for RQTF )
Meeting Schedule Teleconferences: Weekly The Working Group and its Task Forces generally each hold weekly teleconferences, but this may vary over time according to agenda and preferences.
Face-to-face: approximately 2 The Working Group generally meets during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year year.


Success Criteria

  • Advancement of personalization support on the web via specifications published by this group and features incorporated into other work.
  • Improved accessibility of W3C web technologies as measured by the activity of accessibility proponents in coordination with APA, accepted comments on specifications, and other tracked Working Group dialog;
  • Release of Web Technology Accessibility Guidelines as Working Group Note and indications of its use by other Working Groups;
  • Documentation of new accessibility issues and solutions, potentially with spin-off work begun;
  • Record of active and sustained coordination between APA and other stakeholders.


Draft state indicates the state of the deliverable at the time of the charter approval. Expected completion indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.

Normative Specifications

The Working Group will deliver the following deliverables W3C normative specifications:

Personalization Semantics Content Module

This specification will be assist specification developers in ensuring technologies address accessibility user requirements.

Draft state: Working Draft

Expected completion: Q3 2019

Adopted Working Draft: Personalization Semantics Content Module 1.0, , 16 March 2018

Reference Draft: Personalization Semantics Content Module 1.0, , 16 March 2018. Exclusion period began 13 February 2018; Exclusion period ended 13 July 2018.

Produced under Working Group Charter: . This deliverable was initially published as W3C Technical Reports by the Accessible Rich Internet Applications Working Group and supporting resources. is being moved to the Accessible Platform Architectures Working Group.

Personalization Semantics Help and Support Module

This specification will assist specification developers in ensuring technologies address accessibility user requirements.

Draft state: Editor's Draft

Expected completion: Q2 2020

Personalization Semantics Tools Module

This specification will assist specification developers in ensuring technologies address accessibility user requirements.

Draft state: Editor's Draft

Expected completion: Q2 2021

The Working Group may publish additional Personalization Semantics modules during the course of this charter, and may work with other groups to incorporate personalization features into the native features of web technologies, instead of or in addition to the above work.

Other Deliverables

Other non-normative documents may be created such as:

  • Web Technology Accessibility Guidelines (Note) Personalization Semantics Explainer to explain the use cases for Personalization Semantics, structure of the vocabulary, and how to use the technology in content;
  • Framework for Accessible Specification of Technologies (FAST) to assist specification developers in ensuring technologies address accessibility user requirements (see WTAG unofficial editors' draft requirements;
  • FAST checklist ); to help Working Groups self-review against the FAST;
  • Inaccessibility of CAPTCHA (Note) to explain problems and solutions for people with disabilities in human vesus bot differentiation techniques (see earlier version of CAPTCHA note ); techniques;
  • Media Accessibility User Requirements (Note) to describe features needed in audio-visual media for content to be accessible for users with disabilities;
  • Reviews of web technology specifications sent to maintaining entities;
  • Working Group Notes to formalize accessibility knowledge on specific topics as the need arises (Note); arises;
  • Other Deliverables
  • Research reports addressing, as needed, gaps identified during accessibility reviews of draft specifications, and/or technical questions emerging through other aspects of accessibility reviews;
  • Gap analysis and roadmap for inclusion of people with cognitive disabilities.. disabilities;
  • Use case and requirement documents;
  • Test suite and implementation report for the specification;
  • Primer or Best Practice documents to support web developers when designing applications.


Milestones Note: The group will document significant changes from this initial schedule

Detailed milestones and updated publication schedules are available on the group home page. Specification publication status page .

  • October 2018: FPWD Note Web Technology Accessibility Guidelines Apr 2016 Jul 2017 Inaccessibility of CAPTCHA Apr 2016 Sep 2016 Media Accessibility User Requirements Dec 2015 Personalization Semantics Help and Support Module
  • October 2018: FPWD of Personalization Semantics Tools Module
  • July 2019: Rec of Personalization Semantics Content Module
  • May 2020: Rec of Personalization Semantics Help and Support Module
  • May 2021: Rec of Personalization Semantics Tools Module


A detailed plan to achieve these milestones is documented in For all specifications, this Working Group will seek horizontal review for accessibility, internationalization, performance, privacy, and security with the APA WG Project Management Plan relevant Working and Interest Groups, and with the TAG . Invitation for review must be issued during each major standards-track document transition, including FPWD and at least 3 months before CR , and should be issued when major changes occur in a specification.

Dependencies Dependencies on

Additional technical coordination with the following Groups will be made, per the W3C Process Document :

W3C Groups

Accessibility Guidelines (WCAG) Working Group
Coordinate on development of techniques and general content accessibility issues.
ARIA Working Group
Coordinate on resolution of architectural issues identified by ARIA and meeting user needs identified by APA.
CSS Working Group
Coordinate on general CSS accessibility topics.
Internationalization Activity Working Group
Coordinate how to address accessibility and internationalization in W3C specs.
SVG Working Group
Coordinate on general graphics accessibility topics.
Timed Text Working Group
Ensure Media Accessibility User Requirements are met in TTML and WebVTT .
Web Content Accessibility Guidelines (WCAG) Working Group Coordinate on development of techniques and general content accessibility issues.
WAI Interest Group
Engage in specification review and research activity.
Web Real-Time Communications Working Group
Ensure Media Accessibility User Requirements are met in WebRTC.
Web Payments Working Group
Coordinate on accessibility of payments.
Web Platform Working Group
Coordinate on general HTML and web API accessibility topics.
Furthermore, Accessible Platform Architectures Working Group expects to follow these W3C Recommendations: QA Framework: Specification Guidelines . Character Model for the World Wide Web 1.0: Fundamentals Architecture of the World Wide Web, Volume I Liaisons to

External Groups Organizations

APA WG does not maintain formal liaisons to external groups, but does coordinate on an as-needed basis on topics of mutual relevance. At charter time, these organizations include: DAISY Consortium ; OpenAjax Alliance Accessibility Task Force ; Linux Foundation Open Accessibility Workgroup ;
IETF (where
Coordinate on protocols that impact accessibility). accessibility of web content.
ISO/IEC JTC 1/SC 35 User interfaces
Coordinate user interface requirements and applicability to web content.
Coordinate on accessibility of web technologies.


To be successful, the Accessible Platform Architectures Working Group is expected to have 10 6 or more active participants for its duration, with participation where possible including representation from industry including browser and assistive technology implementers, disability communities, and accessibility research. Effective participation in the Accessible Platform Architectures Working Group is The Chairs, specification Editors, and Test Leads are expected to consume two to four hours per week for each participant; twice as much contribute half of a working day per week towards the Working Group. There is no minimum requirement for chairs and editors. other Participants.


The Working Group communicates by regular teleconferences, email, IRC, Web-Based Survey, issue tracker comments, group encourages questions, comments and occasional face issues on its public mailing lists and document repositories, as described in Communication .

The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to face meetings. At charter time, the group uses terms of the following mailing lists: W3C Patent Policy . ordinary


Technical discussions for this Working Group discussion; are conducted in public comments on publication; Working Group discussions involving a wider audience than : the WG membership, and where specification review announcements meeting minutes from teleconference and submissions are copied; announcements of Working Group activities including publications, key events, face-to-face meetings will be archived for public review, and specification reviews. The Working Group may form task forces, which may conduct work using separate teleconferences, email lists, technical discussions and other tools. At time of charter, task forces include: Cognitive issue tracking will be conducted in a manner that can be both read and Learning Disabilities Accessibility Task Force (jointly with the Web Content Accessibility Guidelines WG), HTML Accessibility Task Force (jointly with written to by the HTML general public. Working Group), Research Drafts and Development Task Force, Editor's Drafts of specifications will be developed on a public repository, and Specification Accessibility Task Force. may permit direct public contribution requests. The meetings themselves are not open to public participation, however, except by explicit one-time invitation from the chair(s).

Details about available communication mechanisms, as well as other information Information about the group (deliverables, (including details about deliverables, issues, actions, status, participants, face-to-face meetings, teleconferences, etc.) is and meetings) will be available from the Accessible Platform Architectures Working Group home page as well as the WAI home page . page.

This group coordinates with other WAI groups uses the public mailing list ( archive ) and GitHub . Additional communication channels are also used. The public is invited to ensure a common approach review, discuss and contribute to addressing accessibility requirements. this work.

The group may use a confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.

Decision Policy

At charter time, the decision policy is under review within the This group in order will seek to develop a decision process that supports greater asynchronous participation make decisions through consensus and minimize dependence on weekly teleconferences. Until completed, the Working Group decision policy is as explained in Process Document section 3.3 of due process, per the W3C Process Document . (section 3.3 ). The Working Group maintains specific procedures to establish and measure consensus and address objections in the Accessible Platform Architectures Working Group Decision Policy . All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director.

This charter is written in accordance with the W3C Process Document (Section 3.4, Votes) , and includes no voting procedures beyond what the Process Document requires.

Patent Policy

This Working Group operates under the W3C Patent Policy (5 (Version of 5 February 2004 Version). updated 1 August 2017). 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 .


This Working Group will use the W3C Document license for Recommendation-track deliverables and the W3C Software and Document license for Note-track deliverables and licensed non-TR publications.

About this Charter

This charter for the Accessible Platform Architectures Working Group has been created according to section 5.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.

Charter History

This Working Group is one The following table lists details of two split important changes from the former Protocols and Formats Working Group . This group focuses on technology review while initial charter, per the ARIA Working Group W3C Process Document (section 5.2.3) :

Charter Period Start Date End Date Changes
Initial Charter focuses on technology development . A diff version between this charter and 22 October 2015 31 July 2018 none
Rechartered 08 August 2018 31 July 2021

Changes from the previous PFWG charter is available. Primary changes in this charter: ( diff from previous charter ):

  • Moved Web Technology Accessibility Guidelines Added Personalization Semantics as a Rec-track deliverable, transferred from Recommendation track to Note track. the ARIA Working Group ;
  • Explicitly called out existing Note-track efforts Increased work on Inaccessibility of CAPTCHA and Media Accessibility User Requirements; retained option non-normative resources to create new Note-track deliverables as needed when in scope. support accessibility horizontal review;
  • Added scope Clarified participation and deliverables communication procedures;
  • Added licensing section to incorporate efforts previously carried out by specify the Research W3C Document license for Recommendation-track deliverables and Development Working Group . the W3C Software and Document license for others;
  • Split the specification development function Increased staff effort from .4 FTE to .7 FTE to provide additional support for Research Questions Task Force and accessibility horizontal review, and because of the specification review function new Personalization Semantics deliverable.

Work in the scope of this group was, before the previous charter, carried out by the Protocols and Formats Working Group. Specification review is in this group, and specification development is in the ARIA Working Group . Recommendation-track deliverables were moved to the other group. Moved from Member visibility to Public visibility.