W3C

Protocols and Formats Working Group Charter The Protocols and Formats Working Group is now closed . It has been replaced by the Accessible Platform Architectures and Accessible Rich Internet Applications Working Groups. Group Charter

The mission of the Protocols and Formats Accessible Rich Internet Applications Working Group (PFWG), (ARIA WG, formerly part of the WAI Technical Activity , Protocols and Formats Working Group) is to ensure W3C specifications provide support for develop technologies that enhance accessibility to of web content for people with disabilities. The group advances this mission through review This includes continued development of W3C specifications, technical support materials, the Accessible Rich Internet Applications (WAI-ARIA) suite of technologies and other technical specifications that when needed to bridge known gaps.

This mission is complementary to the work of other Web Accessibility Initiative (WAI) groups within the WAI Technical Activity and

Join the WAI International Program Office Activity Accessible Rich Internet Applications Working Group . The PFWG is part of the WAI Technical Activity.

Start date 22 October 2015
End date 8 31 July 2018
Charter extension 31 October 2015 2018. The charter extension history is documented in " About this charter "
Confidentiality The group operates in Member-only space but conducts some activities in public. Proceedings are public .
Initial Chairs Janina Sajka Rich Schwerdtfeger
Current Chairs Joanmarie Diggs, James Nurthen. Changes to chairs is documented in " About this charter "
Initial Team Contacts
(FTE %: 45) 25)
Michael Cooper (25%)
Usual Meeting Schedule Teleconferences: Weekly
Face-to-face: approximately 2 per year

Scope

Success Criteria

  • Other W3C specifications have improved accessibility. Release of WAI-ARIA 1.1 and supporting specifications as a W3C Recommendation. Release of WAI-ARIA Implementation Guide as a W3C Recommendation. Release of HTML 5 Accessiblity API Guide as a W3C Recommendation. Release of Role Attribute as a W3C Recommendation. Recommendation;
  • Demonstrate successful implementation Begin work on future versions of WAI-ARIA and the improved accessibility of RIch Web (Web 2.0) content in a broad range of user agents. supporting specification modules;
Out of Scope Education and evangelization outside of the W3C.

Deliverables

The following deliverables would will be published as W3C Technical Reports: Reports and supporting resources. Accessibility API Mapping Guides fill the role previously filled by WAI-ARIA 1.0 User Agent Implementation Guide, modularized and developed on separate timelines to address multiple host languages.

The ARIA Working Group notes expects to formalize accessibility knowledge work jointly with other Working Groups on specific topics as many of the need arises (Note) above deliverables, and may form joint task forces.

Other Deliverables

  • Feedback Test suites for technical specifications;
  • DTDs, schemata, and other resources to W3C specification developers support automated validation of content that uses WAI-ARIA;
  • Requirements for normative deliverables including future WAI-ARIA samples versions;
  • WAI-ARIA test suite, acid tests samples;
  • Accessibility API to ARIA binding information (UA developers lead?) WAI-ARIA 2.0 Roadmap;

Milestones

Some deliverables below are not projected to achieve completion by the end of the three-year span of this charter. The Working Group intends to begin work on them during this charter period and continue work in a future charter period. Timelines projected beyond the end of the current charter period are indicated as "Post 2018".

HTML July 2010 Jan 2011 Timeline View Summary Q3 2010 Second Last Call Working Draft of WAI-ARIA First Public Working Draft of Role Attribute Last Call Working Draft of Role Attribute (document inherited from XHTML 2 and nearly complete so ready for rapid advancement) Public Working Draft (on Rec track) of WAI-ARIA User Agent Implementation Guide Public Working Draft of WAI-ARIA Authoring Practices Public Working Draft of WAI-ARIA Roadmap Process public comments on WAI-ARIA Second Last Call, WAI-ARIA User Agent Implementation Guide, WAI-ARIA Authoring Practices, WAI-ARIA Roadmap, Role Attribute Publish topical accessibility guidance as needed Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Q4 2010 Candidate Recommentation of WAI-ARIA Candidate Recommendation of Role Attribute Last Call Working Draft of WAI-ARIA User Agent Implementation Guide First Public Working Draft of
Milestones
Note: The group will document significant changes from this initial schedule on the group home page.
Specification FPWD LC CR PR Rec
WAI-ARIA 1.0 1.1   July 2010
Sept 2010 Oct 2015 Jan 2011 Apr 2016 Mar 2011 Jun 2016
Digital Publishing WAI-ARIA 1.0 User Agent Implementation Guide module   Sept 2010 Jun 2015 Jan 2011 Feb 2016 Jan 2011 Jun 2016 Mar 2011 Aug 2016
Role Attribute Graphics WAI-ARIA module July 2010 Sep 2010 Oct 2015 Nov 2010 2016 Dec 2010 Oct 2017 Jan 2011 Dec 2017
Core Accessibility API Guide Mappings
Oct 2015 Mar 2011 2016 Apr 2016
Accessible Name and Description: Computation and API Mappings 1.1
Oct 2015 Jan 2012 Mar 2016 Mar 2012 Apr 2016
HTML Accessibility API Guide Public Working Draft of WAI-ARIA Authoring Practices Proposed Recommendation of Role Attribute (small module, implementation testing is trivial) Call for Implementations of WAI-ARIA Collect and evaluate implementations of WAI-ARIA Work with WAI-ARIA implementers to address interoperability issues Publish topical accessibility guidance as needed Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Q1 2011 WAI-ARIA Implementation Report Mappings
Last Call Working Draft of HTML
Dec 2015 Mar 2016 Apr 2016
SVG Accessibility API Guide Candidate Recommendation of WAI-ARIA Implementation Guide Proposed Recommendation of WAI-ARIA Implementation Guide (advanced quickly because testing done as part of the ARIA CR process) Mappings
Proposed Recommendation Working Draft of
Feb 2016 Oct 2016 Dec 2016
Digital Publishing WAI-ARIA Role Attribute becomes W3C Recommendation Publish topical accessibility guidance as needed Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Q2 2011 Candidate Recommendation of HTML Accessibility API Guide WAI-ARIA becomes W3C Recommendation WAI-ARIA Mappings Aug 2015 Oct 2016 Jun 2017 Aug 2017
User Agent Implementation Guide becomes W3C Recommendation WAI-ARIA Authoring Practices becomes Working Group Note WAI-ARIA Primer becomes Working Group Note Context Properties May 2016 May 2017 Nov 2017 Jan 2018
WAI-ARIA Roadmap becomes Working Group Note Publish topical accessibility guidance as needed Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Q3 2011 Requirements for future versions of 2.0 Jun 2017 Post 2018 Post 2018 Post 2018
Cognitive WAI-ARIA Publish topical accessibility guidance as needed Support implementation of Module Nov 2015 Feb 2017 Apr 2018 Jun 2018
WAI-ARIA Interaction Module 1.0 Publish topical accessibility guidance as needed Review Mar 2016 Sep 2017 Post 2018 Post 2018

A detailed plan to achieve these milestones is documented in the ARIA WG Project Management Plan .

Dependencies

Dependencies on W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed

Q4 2011 Updated Inaccessibility of CAPTCHA Accessible Platform Architectures Working Group Note Publish topical accessibility guidance as needed Support implementation of WAI-ARIA 1.0 Publish topical accessibility guidance as needed Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Q1 2012 HTML Accessibility API Implementation Report Proposed Recommendation of HTML Accessibility API Guide Publish topical accessibility guidance as needed Support implementation of WAI-ARIA 1.0 Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Q2 2012 HTML Accessibility API Guide becomes W3C Recommendation Publish topical accessibility guidance as needed Support implementation of WAI-ARIA 1.0 Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Q3 2012
Publish topical accessibility guidance as needed Support implementation of WAI-ARIA 1.0 Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Collaborate on joint deliverables.
Q4 2012 Publish topical accessibility guidance as needed Support implementation of WAI-ARIA 1.0 Review W3C Working Drafts as needed Coordinate accessibility issues with CSS Working Groups as needed Q1 2013 Group
Publish topical accessibility guidance as needed Support implementation of WAI-ARIA 1.0 Review W3C Working Drafts as needed Coordinate accessibility issues with Working Groups as needed Q2 2013 Publish topical accessibility guidance as needed Support implementation of media queries support for context awareness. Provide requirements for future WAI-ARIA 1.0 Review W3C Working Drafts as needed support. Coordinate on general CSS accessibility issues with Working Groups as needed topics.
Dependencies W3C Groups
Ubiquitous Web Activity Digital Publishing Interest Group
Representation of the accessibility aspect Coordinate development of device independence digital publishing roles.
Internationalization Activity
Coordinate how to address accessibility and internationalization in W3C specs specs.
Hypertext Coordination Technical Architecture Group
Coordination on accessibility of browser-oriented specifications Confirm the ARIA relationship to various host languages is interoperable and forwards-compatible.
HTML WG Privacy Interest Group
Implementation Identify and resolve privacy implications of ARIA features of the technology that capture user environment information, particularly specific assistive technology being used, in order to customize the user experience.
SVG WG Working Group
Implementation of ARIA, review of the Role attribute Develop graphics role module and SVG Accessibility API Mappings..
WAI Coordination Web Content Accessibility Guidelines (WCAG) Working Group
Coordinating the roles of the WAI Work on HTML 5 and ARIA Techniques for WCAG 2.0 .
Web Platform Working Groups when issues relevant to the PFWG mission are found Group
Implementation of ARIA and HTML Accessibility API Mappings, coordinate development of APIs that address accessibility use cases, and work on other joint deliverables including Canvas 2D Context .

Furthermore, Protocols and Formats Accessible Rich Internet Applications Working Group expects to follow these W3C Recommendations:

Liaisons to External Groups

none ARIA 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:

Participation

To be successful, the Protocols and Formats Accessible Rich Internet Applications Working Group is expected to have 10 or more active participants for its duration, with participation where possible including representation from industry, industry including browser and assistive technology implementers, disability communities, accessibility research and government. accessibility research. Effective participation to Protocols and Formats in the Accessible Rich Internet Applications Working Group is expected to consume four two to eight four hours per week for each participant; twice as much per week for chairs and editors. The Protocols and Formats Accessible Platform Architectures Working Group will allocate also the necessary resources for building Test Suites for each specification.

Participants are reminded of the Good Standing requirements of the W3C Process.

Communication

The work of the Working Group primarily takes place on weekly teleconferences. This communicates by regular teleconferences, email, IRC, Web-Based Survey, issue tracker comments, and occasional face to face meetings. At charter time, the group uses the Member-only following mailing list w3c-wai-pf@w3.org ( archive ) for topical lists:

The Working Group may form task forces, which may conduct work using separate teleconferences, email lists, and other tools. At time of charter, task forces include: Digital Publishing Accessibility Task Force (jointly with the Digital Publishing IG), SVG Accessibility Task Force (jointly with the SVG WG), WAI-ARIA Authoring Practices Task Force, and WAI-ARIA User Agent Implementation Task Force.

Information Details about available communication mechanisms, as well as other information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the WAI Accessible Rich Internet Applications Working Group home page as well as the Protocols and Formats Working Group WAI home page .

Decision Policy

As explained in the Process Document ( section 3.3 ), this This group will seek coordinates with other WAI groups 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 ensure a formal vote) and any objections, and move on. common approach to addressing accessibility requirements.

Decision Policy

When deciding a substantive technical issue, the Chair may put a question before At charter time, the group. When decision policy is under review within the Chair conducts a formal vote group in order to reach develop a decision process that supports greater asynchronous participation and minimize dependence 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 weekly teleconferences. Until completed, the proposal. This charter Working Group decision policy is written as explained in accordance with Section 3.4, Votes Process Document section 3.3 of the W3C Process Document and includes no voting .

The Working Group maintains specific procedures beyond what to establish and measure consensus and address objections in the Process Document requires. ARIA Working Group Decision Policy .

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 Protocols and Formats Accessible Rich Internet Applications Working Group has been created according to section 6.2 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.

In July 2013, this charter was extended to 30 September 2013 This Working Group is one of two split from the former Protocols and Formats Working Group . In February 2015, This group focuses on technology development while the APA Working Group focuses on technology review . A diff version between this charter was extended to 18 May 2015 . In May 2015, this and the previous PFWG charter was extended to 15 July 2015 . In July 2015, is available. Primary changes in this charter was extended to 13 August 2015 . In August 2015, charter:

Charter extension: On 6 September 2018 the charter was extended to 8 31 October 2015 2018 to allow time to address Advisory Committee input on the proposed new charter .

Please also see the previous charter Chairs: Joanmarie Diggs was appointed co-chair for this group. on 4 January 2017. Rich Schwerdtfeger stepped down as co-chair on 30 October 2017. James Nurthen was appointed co-chair on 30 March 2018.


Michael Cooper, PFWG ARIA WG Team Contact
Janina Sajka, PFWG Rich Schwerdtfeger, ARIA WG Chair

$Date: 2017/08/11 18:16:14 2018/09/06 14:13:46 $