上海时时乐上Web Accessibility initiative

WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities

上海时时乐178平台:Protocols and Formats Working Group (PFWG Public Page

The Protocols and Formats Working Group has closed.

The Protocols and Formats Working Group is no longer chartered to operate. Its work will continue in two new Working Groups:

Resources from the PFWG remain available to support long-term institutional memory, but this information is of historical value only.

Meetings

The PFWG holds face-to-face meetings in various locations as needed. Information about upcoming and past meetings is in the PFWG Meetings page. In the past, PFWG meetings were held in W3C Member space; information about those meetings is available in the PFWG Group Meetings page.

Work

Technical Specifications

Accessible Rich Internet Applications (WAI-ARIA) 1.1

WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.

The work has been divided into a series of modules and related documents. ?The current editor's working drafts of these are:

Requirements for Accessible Rich Internet Applications 1.1 (public editor's draft)
This roadmap that describes the problem, what W3C specifications will be used to correct the problem, and the timeline for the new specifications. See also the Public Working Draft of the Requirements for Accessible Rich Internet Applications 1.1.
Accessible Rich Internet Applications (WAI-ARIA) 1.1 (public editor's draft)
This specification provides an ontology of roles, states, and properties that set out an abstract model for accessible interfaces and can be used to improve the accessibility and interoperability of Web Content and Applications. This information can be mapped to accessibility frameworks that use this information to provide alternative access solutions. Similarly, this information can be used to change the rendering of content dynamically using different style sheet properties. The result is an interoperable method for associating behaviors with document-level markup. See also the Public version of WAI-ARIA 1.1.
Core Accessibility API Mappings 1.1 (public editor's draft)
Describes how user agents should map WAI-ARIA features to platform accessibility APIs. Other Accessibility API Mappings specifications depend on and extend this Core specification for specific technologies, including native techology features and WAI-ARIA extensions. See also the Public Working Draft of the Core Accessibility API Mappings.
Accessible Name and Description: Computation and API Mappings 1.1 (public editor's draft)
Describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs. See also the Public Working Draft of the Accessible Name and Description: Computation and API Mappings 1.1.
HTML Accessibility API Mappings 1.1 (public editor's draft)
This document describes how user agents map HTML5.1 [[!HTML51]] elements and attributes to platform accessibility API roles, states and properties on a variety of platforms, based on the Core Accessibility API Mappings [[!CORE-AAM]] specification for user agents. This document is designed to leverage these core mappings for the HTML5.1 host language.
SVG Accessibility API Mappings 1.1 (public editor's draft)
This document describes how user agents maps SVG2 markup to platform accessibility APIs based on the Core Accessibility API Mappings [CAAM] specification for user agents.
Digital Publishing Accessibility API Mappings 1.1 (public editor's draft)
This document describes how user agents maps digital publishing markup to platform accessibility APIs based on the Core Accessibility API Mappings [CAAM] specification for user agents.
WAI-ARIA Authoring Practices 1.1 (public editor's draft)
Provides recommended approaches to create accessible Web content using WAI-ARIA roles, states, and properties to make widgets, navigation, and behaviors accessible. Also describes considerations that might not be evident to most implementors from the WAI-ARIA specification alone.

Formal Public Working Drafts of these documents can be found from the WAI-ARIA Overview Page.

Editors' sources for the above specifications are maintained in the W3C ARIA GitHub repository. GitHub users can watch this repository and send pull requests.

Media Accessibility User Requirements

Media Accessibility User Requiremenst (public editors' draft) aggregates the requirements of an accessibility user that the W3C HTML5 Accessibility Task Force has collected with respect to audio and video on the Web. See also the Public Working Draft of Media Accessibility User Requirements.

Editors' sources for the above specification is maintained in the W3C PFWG GitHub repository. GitHub users can watch this repository and send pull requests.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

WAI-ARIA 1.0 has been completed.

The work has been divided into five documents. ?The following documents are W3C Recommendations:

Accessible Rich Internet Applications (WAI-ARIA)
This specification provides an ontology of roles, states, and properties that set out an abstract model for accessible interfaces and can be used to improve the accessibility and interoperability of Web Content and Applications. This information can be mapped to accessibility frameworks that use this information to provide alternative access solutions. Similarly, this information can be used to change the rendering of content dynamically using different style sheet properties. The result is an interoperable method for associating behaviors with document-level markup.
WAI-ARIA User Agent Implementation Guide
Describes how user agents should map WAI-ARIA features to platform accessibility APIs.

The following documents were developed for WAI-ARIA 1.0 but have not been, and are not expected to be, finalized.

Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)
This roadmap that describes the problem, what W3C specifications will be used to correct the problem, and the timeline for the new specifications.
WAI-ARIA Primer
Explains the accessibility problems posed by hybrid technologies such as DHTML and AJAX and introduces the technologies to map controls, AJAX live regions, and events to accessibility APIs. Also describes new navigation techniques to mark common Web elements such as menus, primary content, secondary content, banner information and other types of Web structures.
WAI-ARIA Authoring Practices
Provides recommended approaches to create accessible Web content using WAI-ARIA roles, states, and properties to make widgets, navigation, and behaviors accessible. Also describes considerations that might not be evident to most implementors from the WAI-ARIA specification alone.

Role Attribute

Role Attribute 1.0 is a W3C Recommendation.

The Role Attribute allows the author to annotate markup languages with machine-extractable semantic information about the purpose of an element. Use cases include accessibility, device adaptation, server-side processing, and complex data description. This attribute can be integrated into any markup language. The role attribute is necessary to support WAI-ARIA to define roles in XML-based languages, when the languages do not define their own role attribute.

Other publications

In addition to the work underway above, the PFWG has been responsible in the past for the incorporation of a number of the accessibility improvements introduced into W3C formats from HTML 4.0 onward including CSS, SMIL, SVG and VoiceXML. Some specific publications developed in service of this work:

Inaccessibility of Visually-Oriented Anti-Robot Tests: Problems and Alternatives
This paper evaluates the accessibility problems with CAPTCHA, a visual verification system popular on many Web sites, and evaluates a number of more-accessible alternatives to the same problems CAPTCHA claims to solve.
Natural Language Usage -- Issues and Strategies for Universal Access to Information
This paper suggests a possible implementation of a language annotation system to clarify meaning in potentially ambiguous terms.
XML Accessibility Guidelines
The discussions for XAG take place on the public wai-xtech list. This specification is developed by the Working Group.
Some of these are are discussed in the following education notes:

About the PFWG

Work of the PFWG is in accordance with the W3C Process. PFWG work is funded in part by the WAI Core project. The work of this group does not necessarily reflect the views or policies of the funder.

The charter of the working group outlines the goals, work methods, and requirements for participation. It also explains why the working drafts and email archives of this group are in the members-only area. This activity is conducted by the 上海时时乐上 as part of its Web Accessibility Initiative

Mailing Lists

Patent Disclosures

W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent.

Janina Sajka <[email protected]> - Chair, PFWG
Michael Cooper <[email protected]> - Staff Contact

  • 四兄弟合伙创业 种植羊肚菌成功 2019-05-10
  • 最美季节走醉美线路——新疆伊犁大环线文章中国国家地理网 2019-05-07
  • 网络小贷牌照批设被紧急叫停 2019-05-01
  • “爸爸的苹果”,甜甜的爱(青春派) 2019-04-23
  • 全世界人民都要顺应人类社会发展规律,不断扩大社会财富公有制的范围,不断缩小社会财富私有制的范围,以便最终消灭社会财富私有制,建立共产主义社会财富公有制。 2019-04-06
  • 立秋日 滇池上空出现七彩云霞 2019-04-06
  • 抢不到门票和机票 如何假装在俄罗斯看世界杯? 2019-03-23
  • 新飞电器破产拍卖 网友:我家的冰箱坏了找谁修 2019-03-15
  • 网友举报货车扰民 交管部门用这个锁定"肇事车" 2019-03-15
  • 沈从文被包装成"情爱高手" 咱能不能别这么糟蹋经典! 2019-03-11
  • 高清:中国男篮抵达洛杉矶 长途飞行队员略显疲惫 2019-02-26
  • 小长假 新疆接待游客353.6万人次 2019-02-26
  • 【10-15万】最新汽车报价 2019-02-01
  • 户县民间艺人打造“微杆秤” 小小杆秤留住记忆 2019-02-01
  • 【访民情 惠民生 聚民心】果勒买里村丰收忙 2019-01-27
  • 25| 85| 281| 714| 266| 518| 323| 750| 916| 336| 617| 177| 765| 126| 849|