You can read more about all changes since the 15 September 2020 Process Document, read the complete disposition of comments, or peruse the diff. Tooling Policy: Defined guidelines for the tools that groups use for publication and collaboration, to ensure long-lived access to W3C publications, and to enable access and effective participation by anyone.Track Separation: Recommendations, Notes+Statements, Registries are on separated publication tracks to make it easier to know what the intended end-state of a document might be.TAG and AB Publications: The W3C Technical Architecture Group (TAG) and Advisory Board (AB) are now allowed to publish Notes.
W3C Statements: Notes endorsed by W3C as a whole, through an Advisory Committee Review.Registries Track: Introduced a specialized track for maintaining Registries at W3C.The W3C Membership approved the 2 November 2021 W3C Process Document, which takes effect today. The DPub-AAM is part of the WAI-ARIA suite described in the WAI-ARIA Overview. It provides Accessibility API Mapping guidance for the roles defined in the Digital Publish WAI-ARIA Module. It does this by extending the Core Accessibility API Mappings 1.1 and the Accessible Name and Description: Computation and API Mappings 1.1 specifications for user agents. The implementation of this specification in user agents enables authors to produce more accessible e-books, by conveying structural book constructs used by the digital publishing industry to assistive technologies. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing. The Digital Publishing Accessibility API Mappings (DPub-AAM) defines how user agents map the Digital Publishing WAI-ARIA Module markup to platform accessibility APIs. The Accessible Rich Internet Applications Working Group has published a First Public Working Draft of Digital Publishing Accessibility API Mappings 1.1.
0 kommentar(er)
