Re: 48-Hour Call for Consensus (CfC): Publish heartbeat of "Using ARIA in HTML"

hi james, thanks for the feedback.

--

Regards

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


On 13 June 2014 18:18, James Nurthen <james.nurthen@oracle.com> wrote:

>  I have some comments on the 2 major sections that have been added.
>
> 2.4 Fourth rule of ARIA use It should be pointed out that it is
> absolutely fine to have aria-hidden used on elements which would normally
> be focusable if those elements also have display:none It is very common to
> hide entire regions of pages to everyone using display:none and the aria
> spec encourages authors to also apply aria-hidden to these regions. This
> fourth rule as written would seem to prohibit this use.
>
>
agreed

> 2.5 Fifth rule of ARIA use As written this doesn't seem to have anything
> to do with ARIA. It seems more like a WCAG technique (and such techniques
> already exist) to me. I don't see anything incorrect but it doesn't really
> seem to be aria related, particularly as the examples given can't even be
> used for synthetic widgets.
>
>
 2 points
1. the text is not yet complete ( apologies, should have made this clear in
the doc)
2. it has everything to do with ARIA as the only place accessible name
calculation is defined is in the ARIA spec (AFAIK). the accessible name
calculation algorithm is used/implemented in browsers to calculate the acc
name for all controls, not just custom controls.

Would appreciate it if you could file bugs on the spec
https://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG&component=Using%20ARIA%20in%20HTML&priority=P3



> Reagrds,
> James
>
>
>
> On 6/13/2014 10:09 AM, janina@rednote.net wrote:
>
> Colleagues:
>
> This is a Call for Consensus (CfC) to the Protocols and Formats Working
> Group (PFWG) approve publication of a heartbeat draft of "Using ARIA in
> HTML," as requested by the document editor in:
> http://lists.w3.org/Archives/Public/public-html-a11y/2014Jun/0026.html
>
> A concurrent CfC is ongoing in the HTML-A11Y Task Force.
>
> Background Information
>
> Thanks to Mark Sadecki for gathering the following relevant background
> data on this publication request.
>
> Stabilized Heartbeat Draft:http://www.w3.org/WAI/PF/HTML/aria-in-html/2014-06-24-HB-draft.html
>
> Bugs resolved since last publication:http://j.mp/1l2o6XI
> ORhttps://www.w3.org/Bugs/Public/buglist.cgi?bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED&chfieldfrom=2013-10-03&chfieldto=2014-06-10&component=+Using%20ARIA%20in%20HTML&list_id=39139&product=HTML%20WG&query_format=advanced
>
> Diff since last publication:http://www.w3.org/WAI/PF/HTML/aria-in-html/CH-aria-in-html-20140624.html
>
> ## Notable Additions
>
> * Fourth rule of ARIA use
>     * Do not use role="presentation" or aria-hidden="true" on a
>     * focusable element.
> * Fifth rule of ARIA use
>     * All interactive elements must have an accessible name.
>     * Clarifications to 2.11  Using ARIA role=application
>  
> ACTION TO TAKE
>
> According to agreed PFWG Consensus Procedures, 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 Close of Business Boston Time, Tuesday 17 June.
>
> Janina
>
>
>
>
> --
> Regards, James
>
> [image: Oracle] <http://www.oracle.com>
> James Nurthen | Principal Engineer, Accessibility
> Phone: +1 650 506 6781 <+1%20650%20506%206781> | Mobile: +1 415 987 1918
> <+1%20415%20987%201918>
> Oracle Corporate Architecture
> 500 Oracle Parkway | Redwood City, CA 94065
> [image: Green Oracle] <http://www.oracle.com/commitment> Oracle is
> committed to developing practices and products that help protect the
> environment
>