W3C home > Mailing lists > Public > public-pfwg@w3.org > September 2013

Re: 48-Hour CfC to publish an HTML-A11Y heartbeat draft

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Thu, 19 Sep 2013 22:57:18 +0100
Message-ID: <CA+ri+VkK3P4WH-kah=Yxd+MeaODdM5iy=n1JiYbVgKD1A1SHxg@mail.gmail.com>
To: Dominic Mazzoni <dmazzoni@google.com>
Cc: Janina Sajka <janina@rednote.net>, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Thanks Dominic,

I have filed 2 bugs against the spec based on your comments and included
you on the CC list

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>


On 19 September 2013 17:46, Dominic Mazzoni <dmazzoni@google.com> wrote:

> I enthusiastically support this document. Well done!
>
> I have just two minor comments, but nothing that needs to block
> publication of this draft.
>
> * I don't quite understand the "Add ARIA inline or via script" section.
> It'd be helpful to explain why exactly it would not be "safe" to use ARIA
> inline. Obviously if an ARIA attribute is something that dynamically
> changes, like aria-checked or aria-activedescendant, it should be modified
> by a script. But if that's the main concern, why not just say so
> explicitly? What are the specific concerns about adding ARIA inline in a
> context where scripting is disabled?
>
> * For role=application, I basically agree with the advice, but it would be
> helpful to start the section with a high-level explanation of how some
> screen readers behave, for context - without needing to reference another
> source. It'd also be good to note that many screen readers essentially
> don't behave differently at all (like VoiceOver or ChromeVox).
>
> - Dominic
>
> On Thu, Sep 19, 2013 at 9:31 AM, Janina Sajka <janina@rednote.net> wrote:
>
>> Colleagues:
>>
>> This is a Call for Consensus (CfC) to publish a heartbeat draft of the
>> following HTML-A11Y Task Force publication:
>>
>>         Using WAI-ARIA in HTML
>>         http://htmlwg.org/heartbeat/WD-aria-in-html-20130822/
>>
>> As always, please respond to this email with any objections, edits
>> questions, or concerns.  Silence will be taken to mean there is no
>> objection, but positive responses are welcome. If there are no
>> objections by end of business Boston Time Monday 23 September, this
>> resolution will carry.
>>
>> Janina
>>
>> --
>>
>> Janina Sajka,   Phone:  +1.443.300.2200
>>                         sip:janina@asterisk.rednote.net
>>                 Email:  janina@rednote.net
>>
>> Linux Foundation Fellow
>> Executive Chair, Accessibility Workgroup:       http://a11y.org
>>
>> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
>> Chair,  Protocols & Formats     http://www.w3.org/wai/pf
>>         Indie UI                        http://www.w3.org/WAI/IndieUI/
>>
>>
>>
>
>
Received on Thursday, 19 September 2013 21:58:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:26 UTC