W3C home > Mailing lists > Public > public-pfwg@w3.org > January 2014

RE: ARIA Agenda Planning for Toronto

From: Cynthia Shelly <cyns@microsoft.com>
Date: Tue, 21 Jan 2014 00:13:39 +0000
To: Janina Sajka <janina@rednote.net>, James Craig <jcraig@apple.com>
CC: James Nurthen <james.nurthen@oracle.com>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
Message-ID: <2f0309c8603f47d795194b4bcf03fd37@BLUPR03MB166.namprd03.prod.outlook.com>
Can we talk about task and bug management systems on Saturday?  I'd like to set up a test instance of TFS before then. 

Michael and/or Janina, would you be able do this with me on Friday at lunch or dinner, so I can be sure that I understand all the requirements?  

-----Original Message-----
From: Janina Sajka [mailto:janina@rednote.net] 
Sent: Monday, January 20, 2014 1:13 PM
To: James Craig
Cc: James Nurthen; W3C WAI Protocols & Formats; Cynthia Shelly
Subject: Re: ARIA Agenda Planning for Toronto


Just conversing about agenda planning with Rich, and some possible approaches to think about ...

We could modularize and take up particular aspects of what we plan to achieve in ARIA.Next as separate modules, on parallel timelines. The parallel timelines plus the modularity are two key concepts to consider.

1.)	We've more or less comitted to do ARIA 1.1 to sync with HTML 5.1
as the best specified, best tested a11y web environment to date.
However,

2.)	That doesn't preclude people working on other modules in
parallel, i.e. input support, text editing, SVG, Epub support, etc.

Thoughts?

Janina

James Craig writes:
> 
> 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/

> > 
> > 

-- 

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 Tuesday, 21 January 2014 00:14:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:44:59 UTC