W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2010

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 12 Sep 2010 05:12:19 -0500
Message-ID: <AANLkTinHNdxC-Ansr7EMxzmt1m4tmo7vKQ72=uZfSP77@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since the last report we have had:

7 WONTFIX bug resolutions.
1 NEEDSINFO bug resolution.
2 WORKSFORME bug resolutions.
1 INVALID bug resolution.
7 FIXED bug resolutions
2 DUPLICATE bugs.
1 LATER bug.
4 REOPENED bugs.
6 NEW a11y bugs reported.

The latest A11y Resolved Bug Comparison is at:
http://www.d.umn.edu/~lcarlson/html5bugchart/20100911/

19 total NEW a11y bugs existed on September 11, 2010. A September 11
bug snapshot is at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20100911

A backlog of fifty-three a11y bugs on the HTML5 Spec await task force
decision of whether to apply the a11ytf keyword or not.

Details are as follows.


1. WONTFIX BUGS:

1.1 Bug 10448: "Consider broadening the set of allowed roles for
command elements" reported by Maciej Stachowiak.
Ian's Rationale: "Half of this proposal still makes no sense. Links as
progress bars? Buttons as scrollbars? Image map areas as range
controls? Heck, even the link as button thing makes no sense to me. If
we want a button-like UI to look like a link for visual users, why
would we then go out of our way to turn them back into buttons for AT
users? Won't that just confuse users when tech support people say "now
click the link" and the AT says it's a button? I really don't
understand the motivation here. How do any of these suggestions
improve accessibility?.
See also http://lists.w3.org/Archives/Public/public-html/2010Jun/0392.html"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10448

1.2 Bug 10462: "merge ARIA mapping tables and list" reported by Steve Faulkner.
Ian's Rationale: "Ah, I see. That list is non-normative intentionally
— it's actually inaccurate, and would have to be dramatically
complicated to be made perfectly accurate (as would be needed to put
it into a normative table). This is because the normative requirements
have subtle complexities like referring to elements that define
commands, as opposed to referring only to elements by element name.
Also, I think having the 'no restriction' elements in the table would
make the table much more difficult to read."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10462

1.3 Bug 10467: "Provide headings in the WAI-ARIA section of the spec
to make it easier to understand"" reported by Steve Faulkner.
Ian's Rationale: "It seems pretty clear already. There's only a few
paragraphs that apply to only one or the other, and they are already
marked up with class=impl, so they get hidden when in author mode."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10467

1.4 Bug 10478: "Modify table, tr and td roles" reported by Steve Faulkner.
Ian's Rationale: "Using tables in this way is non-conforming. The way
to make such a page accessible and conforming is to fix the page to
use appropriate markup, not to add ARIA. On the other hand, if the
author doesn't care about conformance then it doesn't matter what ARIA
is allowed, so changing this wouldn't matter...RIA explicitly says
that 'grid' is equivalent to HTML table, that 'row' is equivalent to
HTML tr, and that "gridcell" is equivalent to HTML td. If this is
wrong, then ARIA should be fixed; I would be glad to update HTML when
ARIA changes, but I do not think we should go out of sync in the
meantime...How can a data table cell ever legitimately be any of these
other than gridcell? Can you show conforming examples where these
roles are used?...It doesn't just sound like it applies to tables, it
explicitly says it is equivalent to tables. Search for "HTML table" in
the role chapter and the only two hits are saying how 'grid' and
'rowgroup' are the right roles for <table> and <tbody> respectively."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10478

1.5 Bug 10484: "default roles for figcaption and caption: Make it
simple to achieve accessibility" reported by Leif Halvard Silli.
Ian's Rationale: "For <figcaption> and <caption>: ARIA doesn't have a
clear role that fits here, so having a default seems bad — it would
be better to let the UA map things to the accessibility APIs directly,
following platform conventions. On the other hand, there are lots of
roles that might fit in various circumstances, so we don't want to
disallow roles. Hence the situation in the spec now. I would rather
leave magic like defaulting roles based on other roles to the ARIA
spec editors. It doesn't seem like something that would be
HTML-specific. If ARIA could be simplified, the place to do that is
the ARIA spec, not the HTML spec."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10484

1.6 Bug 10452: "Consider documenting attributes that map to ARIA
properties in a separate table" reported by Maciej Stachowiak.
Ian's Rationale: "It wouldn't be a pain for me, it would be a pain for
readers..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10452

1.7 Bug 10480: "Add role="presentation" on the ASCII fish image
reported by Leif Halvard Silli.
Ian's Rationale: "Based on my (re)reading of the ARIA spec, role=img
is more appropriate here than role=presentation, so I've left it as
is."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10480


2. NEEDSINFO BUGS:

2.1 Bug 10483: "<figcaption> should be considered the caption of
<figure> _itself_" reported by Leif Halvard Silli.
Ian Rationale: "I have no idea what you're requesting here or what
problem it would solve."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10483#c1
Leif's responses:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10483#c2
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10483#c3


3. WORKSFORME BUGS:

3.1 Bug 10434: Mint a link type for pointing to long descriptions
(rel="longdesc") reported by Leif Halvard Silli.
Ian Rationale: "The problem isn't lack of documentation, it's lack of
implementation experience and implementation commitment."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434#c6

3.2 Bug 10497: What happens to role of <img alt="non-empty"> inside a
<figure role="img">? reported by Leif Halvard Silli.
Ian Rationale: I agree, but that's an ARIA issue, not an HTML issue.
Not sure what to do with the status of this bug. Should it be resolved
somehow? Transferred to ARIA?...Marking WORKSFORME for now (since the
HTML side doesn't need this), but if it should be transferred to ARIA
feel free to do so."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10497


4. INVALID BUGS:

4.1 Bug 10495: "default role(s) 'inheriting' for figure - common use
cases" reported by Leif Halvard Silli.
Ian's rationale: "Invalid use of bug system. Please file just one
issue per bug."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10495


5. FIXED BUGS:

5.1 Bug 10447: "<output>  should have a status role by default after
all" reported by Maciej Stachowiak.
Ian's rationale: "Same as before. Checked in as WHATWG revision r5418.
Check-in comment: revert earlier change here based on updated information"
http://html5.org/tools/web-apps-tracker?from=5417&to=5418
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10447

5.2 Bug 10450: "Allow lists to be used as menus or tab sets " reported
by Maciej Stachowiak.
Ian's rationale: "I didn't add "presentation", but added the others.
If there's a use case for presentation that doesn't involve
non-conforming use of these elements, please reopen the bug (or file a
new one, if the use case applies to other elements also)."
http://html5.org/tools/web-apps-tracker?from=5419&to=5420
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450

5.3 Bug 10451: "Consider restricting the roles allowed for the label
element" reported by Maciej Stachowiak.
Partially Accepted see diff.
Ian's rationale: "I've limited <label> to no roles. I don't understand
how any of the roles listed make any sense. <label> is only supposed
to be used to label form controls. I couldn't find an appropriate
role, but until recently I had just left the elements without
appropriate roles mostly unrestricted, and I missed <label> when
fixing that recently."
http://html5.org/tools/web-apps-tracker?from=5426&to=5427
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10451

5.4 Bug 10486: "References to "image" ARIA role should be img"
reported by Maciej Stachowiak.
Ian's rationale: "Concurred with reporter's comments."
http://html5.org/tools/web-apps-tracker?from=5422&to=5423
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10486

5.5 Bug 10493: "'ARIA restricts usage of this role to one per page' is
an unclear statement" reported by Steve Faulkner.
Ian's rationale: "I just removed the parentheticals altogether, since
they were a bit out of place... everything in ARIA has restrictions,
it was a bit weird just to call these out specifically."
Check-in comment: remove some inaccurate non-normative statements
http://html5.org/tools/web-apps-tracker?from=5423&to=5424
Steve's comment: "a clarification was requested not removal".
Steve tagged bug: TrackerRequest
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10493

5.6 Bug 10494: "Modify aria example and fix spelling" reported by
Steve Faulkner.
Change Description: "fixed spelling; no other changes"
Ian's rationale: "What would the example do, if not what I described?
Isn't what I described the whole point here?"
Check-in comment: typo
http://html5.org/tools/web-apps-tracker?from=5424&to=5425
Steve's comment: "Hi leif, thanks for the info, I now understand how
it works and why and it does indeed work as described in voiceover,
but not in jaws etc on windows. closing the issue as resolved fixed."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10494

5.7 Bug 10496: "fix error in aria conformance checker advice" reported
by Steve Faulkner.
Ian's rationale: "Concurred with reporter's comments."
Check-in comment: Try giving a better suggestion.
http://html5.org/tools/web-apps-tracker?from=5425&to=5426
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10496


6. REOPENED BUGS:

6.1 Bug 9817: "Details element Focus problem" by Rich Schwerdtfeger.
Reopened by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9817

6.2 Bug 10479: "add role=radiogroup to details element" by Steve Faulkner.
Reopened by Ian Hickson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10479

6.3 Bug 10463: "Provide a comprehensive HTML5 to accessibility API
mapping reference" by Steve Faulkner.
Reopened by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10463

6.4 Bug 10449: "Consider allowing various command-like ARIA roles for h1-h6"
Reopened by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10449


7. NEW BUGS:

7.1 Bug 10591: "Conflicting info for table element in aria section"
reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10591

7.2 Bug 10592: "'h1 to h6 element that does have an hgroup ancestor'
not listed in ARIA section" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10592

7.3 Bug 10593: "thead, tfoot and tbody conflicts in aria section"
reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10593

7.4 Bug 10594: "Conforming use of various aria attributes not
specified" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10594

7.5 Bug 10596: "Clarify what <img> represents if no@alt, no@title and
NOT the sole content of a <figure>+<figcaption> element" reported by
Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10596

7.6 Bug 10600: "Strong semantics role="presentation" for <img
alt="<empty>"> is wrong or inaccurate" reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10600


8. LATER BUGS:

8.1 Bug 10464: "Provide clear user friendly links to WAI-ARIA
documents in the ARIA section of the spec" reported by Steve Faulkner.
Ian's Rationale: "Marking LATER until the tools are available. If you
meant something other than cross-referencing roles, properties, and
states, then please file a separate bug that clearly states the
request."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10464


9. DUPLICATE BUGS:

9.1 Bug 10465: "Provide correct aria mapping and role info for the
table element" reported by Steve Faulkner.
This bug has been marked as a duplicate of bug 10478 by Steve.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10465

9.2 Bug 10485: "The img element with non-empty alt should default to
the img aria role" reported by Maciej Stachowiak
This bug has been marked as a duplicate of bug 10481 by Maciej.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10485


10. "A11yTF" KEYWORD BACKLOG:

We currently have fifty-three HTML5 Spec bugs awaiting task force
decision of whether to apply the a11ytf keyword or not.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision

One bug on document "HTML5: Techniques for providing useful text
alternatives Bugs" awaits task force decision. Michael(tm) Smith is
editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML:_The_Markup_Language_Reference_Bugs_Awaiting_Decision

One bug on document "HTML5: Techniques for providing useful text
alternatives Bugs" awaits task force decision. Michael(tm) Smith is
editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML_Working_Group_Decision_Policy_Bugs_Awaiting_Decision

No bugs on document on the document "HTML5: Techniques for providing
useful text alternatives Bugs" await task force decision. Steve
Faulkner is editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#Text_Alternatives_Techniques_Bugs_Awaiting_Decision


11. RELATED REFERENCES:

Weekly Resolved and Rejected Bugs Reports Archive
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Weekly_Resolved_and_Rejected_Bugs_Reports

A11y Resolved Bug Comparisons:
http://www.d.umn.edu/~lcarlson/html5bugchart/

New Bug Snapshots
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot

Backlog of Bugs Awaiting "A11yTF" Keyword Decision
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision

"A11yTF" Keyword Criteria (Draft)
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria

Bug Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Bug_Status_Table

Escalating a Bug to an Issue:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Escalating_a_Bug_to_an_Issue

Accessibility Change Proposal Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status

Best Regards,
Laura

--
Laura L. Carlson
Received on Sunday, 12 September 2010 10:12:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:18 GMT