RE: Concerns and unaddressed issues for the HTML 5 specifications

Status?  This item is urgent if we are going to use this information in the Status sections of the Last Call WDs.

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: public-html-a11y-request@w3.org [mailto:public-html-a11y-request@w3.org] On Behalf Of Paul Cotton
Sent: Monday, May 23, 2011 8:30 AM
To: Janina Sajka; Richard Schwerdtfeger
Cc: w3c-wai-pf@w3.org; public-html-a11y@w3.org; jbrewer@w3.org
Subject: RE: Concerns and unaddressed issues for the HTML 5 specifications

>bugzilla numbers

I actually asked for issue numbers or bug numbers.  If all the items are already WG issues then there is no need to give the bug numbers since this information is easily available.  I was only looking for numbers for unescalated bugs, if any.

Sent from my Windows Phone

-----Original Message-----
From: Janina Sajka
Sent: Sunday, May 22, 2011 10:42 PM
To: Richard Schwerdtfeger
Cc: w3c-wai-pf@w3.org; public-html-a11y@w3.org; jbrewer@w3.org
Subject: Re: Concerns and unaddressed issues for the HTML 5 specifications


Dear All:

I propose we move the gathering of issues to be flagged as unresolved for HTML LC to the HTML-A11Y list.

Rich, can you please forward this to HTML-A11Y? I don't feel right doing so on your behalf.
Note also, please, that Paul has requested additional specificity, e.g.
bugzilla numbers, asthose may be available.

Janina

Richard Schwerdtfeger writes:
>
>
> We were given a to-do to provide this to the PF group.
>
> There are a number of concerns and unaddressed issues that need to be 
> addressed that need to be included as notes in the specification:
>
> For the Canvas 2D API spec:
>
> 1. This API does not yet provide the ability to supply an assistive 
> technology with the bounds of a drawing object on the physical canvas 
> bound to canvas elements in the canvas subtree. To do this properly 
> the specification needs to provide clickable canvas regions, 
> representing the canvas element in the subtree. This would mean the 
> inclusion of hit testing capability in canvas that would bind pointing 
> device events retrieved from the canvas drawing surface to the canvas subtree.
>
> This could appear in the "status of this document" section.
>
> 2. drawFocusRing needs to be separated into separate functions to 
> separate the concept of focus rings and the drawing of visual points 
> of regard for managed children. Also, a defect exists whereby an 
> author can choose to use canDrawCustom when no system setting is 
> provided for how the ring should be drawn and author will be allowed 
> to draw a focus ring without driving a magnifier. (Note: this issue 
> was raised with the chairs, the additional information was provided 
> but not discussed)
>
> 3. A text baseline needs to be added to the textMetrics. (Note: the 
> chairs asked for more clarification on what textMetrics were provided,  
> the additional information was provided but not discussed). The 
> revised text is provided in the updated change proposal.
>
> For the WAI-ARIA section 3.2.7 in HTML 5:
>
> A section needs to include text on the syntactic processing of ARIA 
> role, states, properties.  (Note: Michael Cooper has an action item to 
> provide this text. All the text but the role attribute was created at 
> the HTML Accessibility Face to Face in San Diego). This was an action 
> item for entering CR and a defect was opened in HTML 5.
>
> Rich Schwerdtfeger
> CTO Accessibility Software Group

--

Janina Sajka,   Phone:  +1.443.300.2200
                sip:janina@asterisk.rednote.net

Chair, Open Accessibility       janina@a11y.org
Linux Foundation                http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative    http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)

Received on Monday, 23 May 2011 21:00:45 UTC