HTML Accessibility Task Force Teleconference

20 Dec 2010

See also: IRC log




<trackbot> Date: 20 December 2010

<scribe> scribe: Rich

<scribe> Agenda:


Rich: Most things will be on hold until Microsoft can attend and answer their questions

Charles: Microsoft is mainly concerned about IFrame

Rich: do you think that aria-invalid and aria-selected meet our needs?

Charles: yes for aria-invalid as is.
... aria-selected is is not fully defined
... David bolter's use of Mark's make sense
... but what about cursor?
... What about SVG?
... I like to know I can serialize everything through the layers
... Now with Canvas I know I can do everything mainly because we have a 2D API for establishing the screen position but SVG, how might we serialize it?

Rich: Because SVG mixes content and presenation

Charles: there is some provision for CSS positioning

Charles, It may be as simple in 1.1 where we might have a cursor role

Charles: where is the focus ring in anything

Rich: SVG focus is well defined but different

Charles: yes

Rich: do they have a draw path?

Charles: yes
... you could that if I were focused on a path

Rich: we need to work on this with SVG

Charles: I think we have a very strong proposal for canvas.

Rich: So, we need an ARIA 1.1 to establish the scenario for aria-selected being applied to text and host language markup.
... as a global property

Charles: yes

Rich: Let's push for an ARIA 1.1
... We need to do some implementations but other than that I think we are OK

Charles: Microsoft is moving forward with global composition modes. It means I want to have XOR, etc. It will be in the next preview.

Rich: I think we need to make sure AT's support support aria-invalid for other elements

Charles: I think it would not work for text area tags but it would for <divs>
... I will try to do this with spelling and grammar errors in the canvas subdom

Rich: we can tell authors that if they want to make RTE accessible in canvas you need to use the aria markup for selection and invalid content vs. contenteditable sections
... where we can't get the API in place to expose grammar and spelling errors

Charles: I hope this is a step to infuencing contenteditable's implementation

Rich: we can get selection and caret information from text fields albeit IE and the rest of industry are inconsistent
... no meeting until January 10, 2011

<scribe> meeting: W3C HTML 5 Canvas Accessibility Working Group

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/12/20 20:34:37 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: richardschwerdtfe
Found Scribe: Rich

WARNING: No "Topic:" lines found.

WARNING: No "Present: ... " found!
Possibly Present: Charles Rich html-a11y joined silvia trackbot
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Found Date: 20 Dec 2010
Guessing minutes URL: http://www.w3.org/2010/12/20-html-a11y-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]