Re: ARIA Agenda Planning for Toronto

I think James N’s topic below will be part of the same discussion as these other two:

- How IndieUI Events and ARIA work together.
- Cynthia’s “Should ARIA Specify UA Behavior” topic. 

Aside from that which is already speced in IndieUI, I think for ARIA 2.0 (not sure if it’s in the 1.1 scope) we should determine how to specify certain ARIA controls as HTML5 “commands” so that—among other benefits—custom ARIA buttons should get key handlers by default. This is the part of the UAIG that has been removed due to lack of implementations. There are currently *zero* implementations in the tested accessible rendering engines, and I think that is because it was specified in such a way that it broke DOM Events, but I think we can fix it and make it work.


On Jan 20, 2014, at 12:47 PM, Janina Sajka <janina@rednote.net> wrote:

> James:
> 
> You had asked for a topic at the F2F:
> 
> "Making ARIA Keyboard more robust yet more generic"
> 
> I would like to propose that we take this topic up Thursday morning, as
> we discuss global concerns for ARIA moving forward--before we get into
> the details of the 1.1 feature set.
> 
> How long do you think you need for this discussion?
> 
> Janina
> 
> 
> I currently have this set for Friday at 4PM, but am now thinking I'd
> like to move it to Thursday morning as it's a global question that
> affects how we think of the particulars as through the remainder of our
> F2F work.
> 
> How much time do you think you need for this discussion?
> 
> 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 Monday, 20 January 2014 21:01:37 UTC