RE: 48-Hour Call for Consensus (CfC): Advance DPub AAM to Candidate Recommendation


> -----Original Message-----
> From: Gunderson, Jon R []
> Sent: Friday, May 19, 2017 9:17 AM
> To: Joanmarie Diggs <>; ARIA Admin <public-aria-
> Cc: Siegman, Tzviya - Hoboken <>
> Subject: RE: 48-Hour Call for Consensus (CfC): Advance DPub AAM to Candidate
> Recommendation
> +1
> -----Original Message-----
> From: Joanmarie Diggs []
> Sent: Thursday, May 18, 2017 11:23 AM
> To: ARIA Admin <>
> Cc: Siegman, Tzviya - Hoboken <>
> Subject: 48-Hour Call for Consensus (CfC): Advance DPub AAM to Candidate
> Recommendation
> This is a Call for Consensus (CfC) to the Accessible Rich Internet Applications
> (ARIA) Working Group to advance the Digital Publishing Accessibility API
> Mappings (DPub AAM) [1] to Candidate Recommendation.
> ==============================================
> Background regarding the need for a second CfC
> ==============================================
> As you may be aware, there was a CfC to advance DPub AAM to CR back in
> February [2], which received only votes of support. Thus the steps taken to
> advance the spec were begun. However, W3C management asked several
> questions about the stated exit criteria. After some discussion with them, my
> conclusion (as co-chair of the ARIA Working Group) was that the W3C
> management was correct and that it would be beneficial for all stakeholders to
> make the stated exit criteria more concrete and precise.
> Around that same time, I (as a developer contributing to WebKit) began
> implementation of the mappings specified in the DPub AAM for ATK/AT-SPI2 and
> noticed some problems with several of the mappings for AX API and one mistake
> in the mappings for my own platform. Shortly thereafter, I discovered that the
> mappings of DPub's landmark roles for UIA were inconsistent with the mappings
> for ARIA's landmark roles for UIA.
> Because multiple normative changes to DPub AAM were needed, and because
> we had not yet transitioned this spec to CR due to the aforementioned issue
> with the exit criteria statement, it seemed wiser to me that we fix all of the
> issues first and then (re)request transition of DPub AAM to CR.
> ==============
> Current status
> ==============
> The issues in the mappings have been fixed and committed to the spec [3][4]. In
> addition, the testable statements have been written and added to W3C's test
> suite [5]. Test results have also been generated for both AX API and ATK/AT-SPI2
> [6]. At the present time, Safari's implementation is 100% complete and passing.
> WebKitGtk's is 100% complete and has only one failure (which I, as a developer,
> am addressing currently). Thus we're well on our way to proving the mappings
> stated in DPub AAM are correct and fully implementable.
> Michael has updated the DPub AAM for final review and approval [7]. The
> updated exit criteria are in the appendix, referenced from the Status and at [8].
> For your convenience the exit criteria statement is as follows:
> <quote>
> For this specification to advance to Proposed Recommendation, it has to be
> shown that mappings defined in this specification are implemented on the target
> platforms. Consistent with the plan for the Digital Publishing WAI-ARIA Module
> 1.0 [dpub-aria-1.0] (Dpub-ARIA), the requirement is that each role is successfully
> mapped in at least two implementations and each implementation maps at least
> 75% of the roles.
> </quote>
> ==============
> Action to take
> ==============
> This CfC is now open for objection, comment, as well as statements of support
> via email. Silence will be interpreted as support, though messages of support are
> certainly welcome.
> If you object to this proposed action, or have comments concerning this
> proposal, please respond by replying on list to this message no later than 17:00
> Boston Time, Monday 22 May.
> --joanie
> [1]

> [2]

> [3]

> [4]

> [5]

> [6]

> [7]

> [8]

> aam.html#exit_criteria


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.


Received on Friday, 19 May 2017 13:30:25 UTC