Re: ARIA mapping status

Hi Maciej,

= the following have been escalated =

1. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450>
'Allow lists to be used as menus or tab sets'
reason: role of presentation on lists was rejected by editor.
rationale to be provided in change proposal

2. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10449>
'consider allowing various command-like ARIA roles for h1-h6'
 reason: disagreement with editor
rationale to be provided in change proposal

3. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10448>
'Consider broadening the set of allowed roles for command elements'
 reason: disagreement with editor
rationale to be provided in change proposal

4. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10493>
'"ARIA restricts usage of this role to one per page" is an unclear
statement'
 reason: disagreement with editor
rationale to be provided in change proposal


== The following require discussion by the aria mapping sub team ==

1. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10452>
'Consider documenting attributes that map to ARIA properties in a separate
table'
 -> RESOLVED WONTFIX (as a side note, it seems like a matter of style how
the different tables are broken down, so maybe we can let this one slide)

2. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10462>
'merge ARIA mapping tables and list'
 -> RESOLVED WONTFIX (again, it seems like a matter of style how the
different tables are broken down, so maybe we can let this one slide)

3. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10463>
'provide a comprehensive HTML5 to accessibility API mapping reference'
 -> RESOLVED WONTFIX -- note, this requests a spec change that is not
reflected in the proposal

4. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10467>
'provide headings in the WAI-ARIA section of the spec to make it easier to
understand'
 -> RESOLVED WONTFIX (seems purely an editorial matter again; is this really
important?)

5. details element
 -> no bug on this, but proposal authors agreed that what is in spec
generally makes sense; proposal needs updating

6. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10496>
'fix error in aria conformance checker advice'
 -> RESOLVED FIXED
 7.  <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10464>
'provide clear user friendly links to WAI-ARIA documents in the ARIA section
of the spec'
 -> RESOLVED LATER -- editor proposes to do this later using an automatic
cross-reference tool. Strikes me as reasonable.


= the following are NEW BUGS=

1. conforming use of various aria attributes not specified
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10594

2. thead, tfoot and tbody conflicts in aria section
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10593

3. "h1 to h6 element that does have an hgroup ancestor" not listed in ARIA
section
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10592

4. conflicting info for table element in aria section
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10591

5.Details element Focus problem
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9817
 NOTE: this is not a new bug but has been added to 10066 as it relates to
the <details>, <summary> mapping.



On 9 September 2010 09:44, Maciej Stachowiak <mjs@apple.com> wrote:

>
> Recently, there has been an effort (mainly by Steve Faulkner and myself) to
> break down the A11Y Task Force's proposal for ARIA mappings into a set of
> fine-grained bugs. The root bug for this is <
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10066>. At the suggestion of
> my fellow co-chairs, I am posting a status report on this effort.
>
> Summary:
>
> - 13 points of agreement (apparent consensus)
> - 1 clear point of disagreement (escalated)
> - 10 items with next action on proposal authors
> - 2 items with next action on editor
> - 1 item with next action on PFWG
> - 1 other
>
> = No Action Needed; consensus found =
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10438>
> 'math should be changed changed from no role to "math" role'
>  -> RESOLVED WONTFIX; A11Y TF proposal has been updated to match
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10439>
> '<input type=file> has "button" role, but is typically a compound control'
>  -> RESOLVED FIXED
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10440>
> 'menu type=context should have "menu" role'
>   -> RESOLVED WONTFIX; A11 TF proposal has been updated to match
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10441>
> '<link> that represents a hyperlink should probably have no role by
> default'
>   -> RESOLVED WONTFIX; A11 TF proposal has been updated to match
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10444>
> 'ARIA section does not list elements that have no default role or role
> restrictions'
>  -> RESOLVED FIXED
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10445>
> 'Certain elements with no role should have that as a strong semantic'
>  -> RESOLVED FIXED
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10446>
> 'Consider limiting the roles of certain media and plugin elements'
>  -> RESOLVED FIXED (partial fix, but A11Y TF proposal is already updated
> for the difference)
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10451>
> 'Consider restricting the roles allowed for the label element'
>  -> RESOLVED FIXED
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10465>
> 'provide correct aria mapping and role info for the table element'
>  -> RESOLVED WORKSFORME
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10486>
> 'References to "image" ARIA role should be "img"'
>  -> RESOLVED FIXED
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10487>
> 'Allow radio buttons and checkboxes to be used as radio and check menu
> items respectively'
>  -> RESOLVED FIXED
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10493>
> '"ARIA restricts usage of this role to one per page" is an unclear
> statement'
>  -> RESOLVED FIXED
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10496>
> 'fix error in aria conformance checker advice'
>  -> RESOLVED FIXED
>
>
>
> = No Action Needed; disagreement has been escalated =
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=8000>
> 'ARIA roles added to the a element should be conforming in HTML5'
>   -> RESOLVED WONTFIX
>
>
> = Next Action on Proposal Authors =
>
> For most of these, the editor has fully or partially rejected a portion of
> the proposal, with a stated rationale. For each of these, the proposal
> authors should take one of the following actions:
> - If they agree with the rationale given, then please update the proposal
> to match.
> - If they have relevant new information which should be given fresh
> consideration by the editor, then reopen the bug (but please don't
> chain-reopen too many times).
> - If there is a clear point of disagreement, then mark it TrackerRequest.
> We can roll all these up into one tracker issue.
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10447>
> '<output> should have a status role by default after all
>  -> RESOLVED FIXED -- this was reversed from the original request by
> consensus of A11Y folks; needs to be updated in the A11Y TF proposal
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10448>
> 'Consider broadening the set of allowed roles for command elements'
>  -> RESOLVED WONTFIX -- this seems like a philosophical difference at this
> point so maybe reopening more is not the best course
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10449>
> 'onsider allowing various command-like ARIA roles for h1-h6'
>  -> RESOLVED WONTFIX
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450>
> 'Allow lists to be used as menus or tab sets'
>  -> RESOLVED FIXED -- partially accepted except for presentation roles -
> perhaps should be adjusted in A11Y TF proposal, or else reason for
> "presentation" specifically should be given.
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10452>
> 'Consider documenting attributes that map to ARIA properties in a separate
> table'
>  -> RESOLVED WONTFIX (as a side note, it seems like a matter of style how
> the different tables are broken down, so maybe we can let this one slide)
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10462>
> 'merge ARIA mapping tables and list'
>  -> RESOLVED WONTFIX (again, it seems like a matter of style how the
> different tables are broken down, so maybe we can let this one slide)
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10463>
> 'provide a comprehensive HTML5 to accessibility API mapping reference'
>  -> RESOLVED WONTFIX -- note, this requests a spec change that is not
> reflected in the proposal
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10467>
> 'provide headings in the WAI-ARIA section of the spec to make it easier to
> understand'
>  -> RESOLVED WONTFIX (seems purely an editorial matter again; is this
> really important?)
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10494>
> 'modify aria example and fix spelling;
>  -> RESOLVED NEEDSINFO -- partially addressed but request for additional
> info
>
> details element
>  -> no bug on this, but proposal authors agreed that what is in spec
> generally makes sense; proposal needs updating
>
>
> = Next Action on Editor =
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10479>
> 'add role=radiogroup to details element'
>  -> reopened; needs new response from editor
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10485>
> 'The img element with non-empty alt should default to the img aria role'
>  -> reopened; needs new response from editor
>
>
> = Next Action on PFWG =
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10478>
> 'modify table, tr and td roles'
>  -> RESOLVED WONTFIX -- there seems to be a dispute over what the ARIA spec
> says here and what it should say; no consensus even among PWFWG members.
>  -> I have submitted a comment to PFWG which sparked a thread: <
> http://lists.w3.org/Archives/Public/public-pfwg-comments/2010JulSep/0029.html
> >
>
> = Other =
>
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10464>
> 'provide clear user friendly links to WAI-ARIA documents in the ARIA
> section of the spec'
>  -> RESOLVED LATER -- editor proposes to do this later using an automatic
> cross-reference tool. Strikes me as reasonable.
>
>
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html