Re: 5-Day CfC: Advance Core AAM 1.1 to CR

Hey James.

As I commented in the github issue, those are essentially notes/flags
for us; not text to be included in the TR (or even the PR) version.

--joanie


On 09/07/2017 04:04 PM, James Craig wrote:
> + 1 to ship Core-AAM 1.1 as-is or with the non-normative changes
> captured in Issue-645 https://github.com/w3c/aria/issues/645
> 
> As mentioned previously, all AAM documents should move to a “Living
> Standard” at the earliest opportunity. As each platform’s API changes
> are tied to entirely different release cycles, it does not make sense
> for any of the AAM docs to continue down the Rec Track path.
> 
> Thanks,
> James
> 
> 
>> On Sep 7, 2017, at 11:05 AM, Joanmarie Diggs <jdiggs@igalia.com
>> <mailto:jdiggs@igalia.com>> wrote:
>>
>> This is a Call for Consensus (CfC) to the ARIA Working Group on the
>> question of advancing the "Core Accessibility API Mappings 1.1" (Core
>> AAM) to Candidate Recommendation. The specification can be found here:
>> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html
>>
>> Action
>>
>> 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 proposal, or have comments concerning it, please
>> respond by replying on list to this message no later than 14:00 Boston
>> Time, Tuesday, 12 September 2017.
>>
>> For objections only, please copy the main public-aria@w3.org list to
>> allow technical discussion of the objection to happen there.
>>
>> Process
>>
>> This CfC is conducted per the ARIA WG decision policy:
>> https://www.w3.org/WAI/ARIA/decision-policy
>>
> 
>   James Craig  •  Accessibility Design & Quality  •  jcraig@apple.com
> <mailto:jcraig@apple.com>
> 

Received on Thursday, 7 September 2017 20:26:03 UTC