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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 3 Oct 2010 13:38:13 -0500
Message-ID: <AANLkTikR2PgKbTO9U5Ptoax4Kt5Zf75Af50S=jKHWc_i@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

It was a busy week in bugland. Since the last report we have had:

19 WONTFIX bug resolutions. Details are in section 1.
7 NEEDSINFO bug resolutions. Details are in section 2.
3 WORKSFORME bug resolutions. Details are in section 3.
4 INVALID bug resolutions. Details are in section 4.
10 FIXED bug resolutions. Details are in section 5.
7 REOPENED bugs. Details are in section 6.
7 ASSIGNED bugs. Details are in section 7.
42 NEW a11y bugs reported. Details are in section 8.
1 LATER bug. Details are in section 9.
1 DUPLICATE bug. Details are in section 10.

A11y bug resolutions compared to HTML working group bug resolutions
from the start of using Bugzilla for HTML5 to October 2 are at:
http://www.d.umn.edu/~lcarlson/html5bugchart/20101002/

32 total NEW a11y bugs existed on October 2, 2010. An October 2, 2010
bug snapshot is at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20100918

A backlog of 107 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 9428: "Permit <object> to be used without the data or type
attribute present" reported by Leif Halvard Silli.
Ian's Rationale: "I am not convinced there are use cases here. I
maintain that the stated requirement is a sensible one."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9428

1.2 Bug 10444: "ARIA section does not list elements that have no
default role or role restrictions" reported by Maciej Stachowiak.
Ian's Rationale: "Thanks. Once I've removed the list I'll mark this
WONTFIX. It turned out to be a maintenance nightmare, and had too many
inaccuracies to be useful. Furthermore, making it accurate would make
it essentially unusable. The problem is that the roles don't just
depend on the element names."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10444#c7

1.3 Bug 10449: "Consider allowing various command-like ARIA roles for
h1-h6" reported by Steve Faulkner.
Ian's Rationale: Turning an <h1> into a button is an invalid
(non-conforming) use of <h1>, quite apart from anything to do with
ARIA. So that is not an example of what I was asking for, which is for
a *conforming* example of something where an <h1> should have a role
other than "heading"."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10449
Steve added TrackerRequest
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10449#c13

1.4 Bug 10463: "provide a comprehensive HTML5 to accessibility API
mapping reference" reported by Steve Faulkner.
Ian's Rationale: "What the HTML spec is doing here is what the WAI
requested we do. If you disagree, then please escalate this."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10463

1.5 Bug 10594: "Conforming use of various aria attributes not
specified" reported by Steve Faulkner.
Ian's Rationale: "I don't really understand what I'm supposed to
clarify here. We're not going to add to the HTML spec long paragraphs
listing all the things that you are allowed to do with ARIA, that's
ARIA's job."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10594
Steve added TrackerRequest
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10594#c8

1.6 Bug 10600: "Strong semantics role="presentation" for <img
alt="<empty>"> is wrong or inaccurate" By  Leif Halvard Silli.
Ian's Rationale: "no spec change...It's intentional."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10600#c4

1.7 Bug 10614: " Clarify what <img role=presentation
alt=<not-the-empty-string> > means" reported by Leif Halvard Silli.
Ian's Rationale: "This bug report is a big mish mash of weirdly
formatted quotes and I really am unclear as to what is being
requested. However, it seems to be a request to define one of the
"role" values, in which case it's out of scope of the HTML spec and
should be filed with the ARIA spec."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10614#c4

1.8 Bug 10618: "Use 'unmapped' rather than 'no role' in the
weak/strong ARIA tables" reported by Leif Halvard Silli.
Ian's Rationale: "The "strong native semantics" of "no role" means
that the role="" attribute is not specified implicitly and must not be
specified explicitly. The element literally has no role. This seems
clear to me. If it's not clear then I guess reopen the bug and I'll
just cross-reference all the occurrences of "No role" to a paragraph
that says this."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10618

1.9 Bug 10708: "change normative alt text authoring requirements to
informative advice" reported by Steve Faulkner.
Ian's Rationale: "Requirements don't have to be machine-checkable.
Heck, most requirements aren't, including the most important
accessibility ones (such as making sure you use elements according to
their semantics)."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10708

1.10 Bug 10772: "accesskey and an ordered set of unique
space-separated tokens" reported by Gregory J. Rosmaita.
Ian's Rationale: "A 'word' is just used to mean the same as token -- a
string of characters with no whitespace (no word separators). This is
pretty common practice in the industry."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10772

1.11 Bug 10773: "accesskey should chosen from document's declared
charset" reported by Gregory J. Rosmaita.
Ian's Rationale: "A set can have just one (or even zero) items in it,
there is no contradiction here."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10773

1.12 Bug 10774: "fallback for accesskey insufficiently defined"
reported by Gregory J. Rosmaita.
Ian's Rationale: "1.1: The spec makes allowances for that already, by
exposing the key to the DOM and by suggesting that access keys be made
known in the menus. Doing more than that would be requiring UI, which
is inappropriate. 1.2: I disagree; the user agent is the _user's_
agent, not the author's, and can therefore ignore the author's wishes
if the user so desires (or if the user agent's implementor supposes
that the user would so desire)."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10774

1.13 Bug 10776: "accesskey value token subsets" reported by Gregory J. Rosmaita.
Ian's Rationale: "No, it only means to skip the steps for the one
bogus value, not for the whole attribute. There might be more values
after this one."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10776

1.14 Bug 10777: "user agent assignment of modifier keys subset of
accesskey processing subset reported by Gregory J. Rosmaita.
Ian's Rationale: "As far as I can tell this is all addressed already."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10777

1.15 Bug 10778: "use element.accessKeyLabel to generate list of
available accesskeys reported by Gregory J. Rosmaita.
Ian's Rationale: "That doesn't make any sense. The user agents are the
ones that generate accessKeyLabel, how would they use it to do
anything?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10778

1.16 Bug 10779: "triggering the Action of the command via accesskey
reported by Gregory J. Rosmaita.
Ian's Rationale: "I don't understand why the proposed text is any less
"oblique". It seems to just say the exact same thing but with some
additional meaningless fluff (e.g. "check if the command's Hidden
state facet is false (visible)"). Regarding the additional
consideration, I don't understand what is being requested. Also,
please file just one issue per bug."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10779

1.17 Bug 10782: "problems with button example for accesskey" reported
by Gregory J. Rosmaita.
Ian's Rationale: "o spec change
Rationale: Invalid use of bug system. Please only report one issue per
bug. Regarding the listed problems..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10782#c1

1.18 Bug 10831: "Provide tablist and tab states for menu and command
elements respectively"  reported by Everett Zufelt.
Ian's Rationale: "A tab box is just a different overflow presentation.
It's not a semantic distinction. Thus this really should be done in
CSS (or more likely, XBL driven from CSS)."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831#c1
Everett's reply: "You couldn't be more wrong. A tablist is 100%
semantic, it conveys meaning about the purpose and role of a certain
segment of the document."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831#c2

1.19 Bug 10851: "Javascript access to rendered (calculated) styling
information of a DOM node" reported by Jon Gunderson.
Ian's Rationale: "Closing based on comment 1 and comment 2. Please
reopen if this is indeed an HTML spec issue, but if so please indicate
more clearly what you would like changed exactly.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10851#c3=10851


2. NEEDSINFO BUGS:

2.1 Bug 9775: "positioned to a multiple of the line dimensions of the
first line of the cue" reported by contributor@whatwg.org.
Ian's comment: "I don't understand the request here. The idea here is
that you can position all the subtitles from one speaker reliably on
one line, with all the subtitles from another reliably on another
line, without having to worry about what the font size is. See, for
instance, the titles here:
http://www.youtube.com/watch?v=bw5JBWdaUHI#t=0m12s"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9775#c3

2.2 Bug 9817: "Details element Focus problem"
Ian's comment: "I still don't understand. Why would <details> be
focusable? Surely only its disclosure widget would be focusable. I
really don't follow what the problem is here. Note that just removing
tabindex="" support from <summary> would presumably not change
anything here, since you can still put links and widgets and so on
inside <summary>."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9817#c8

2.3 Bug 10248: "Canvas requires a Caret Drawing call method" reported
by Rich Schwerdtfeger.
Ian's comment: "To do this, we need to first come up with an API that
would be used enough for this to be worth the cost, and would be used
correctly more often than used incorrectly. Since purely
accessibility-driven APIs are generally ignored by authors, we need a
stalking horse to get authors to use this API (much as the focus ring
drawing API is a stalking horse for getting the bounding box of the
control in the first place). The obvious stalking horse here is "draw
a caret". Unfortunately, I have not been able to come up with an API
that (a) satisfies the accessibility use cases (blinks according to
the system rate, draws the caret at the OS-set caret width, etc), (b)
is sanely usable (handles clipping around the edge of a control,
handles scrolling of a long text control in a small field, etc), and
(c) is easier than just hand-rolling a custom caret painter. Without
something that satisfies all three of these requirements, I don't
think it makes sense to make an API available - it would actually be a
net _negative_ to accessibility since people would likely use it wrong
more often than they use it right, if they used it at all. So I am
marking this NEEDSINFO: the need is for an API that satisfies these
constraints. In practice it may make more sense to stop people from
wasting their time writing editors in <canvas>, which is not what
<canvas> was for, and indeed makes little to no sense. Trying to
provide a caret API just justifies people doing this. It would be like
providing a way for people to say what the semantic of a <blockquote>
was, so that they could keep using it to indent text, while still in
theory being able to make ATs act correctly. Note also that on some
platforms, in particular Windows, many ATs actually do caret tracking
by doing image analysis of the display to find where the blinking
caret is, because so many applications hand-roll their own carets in
an inaccessible fashion. So this might not be a huge problem in many
cases."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10248

2.4 Bug 10249: "Canvas requires a content selection method" reported
by Rich Schwerdtfeger.
Ian's comment: "Need a proposal for how to do this. I can't find any
that would work."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10249

2.5 Bug 10592: "h1 to h6 element that does have an hgroup ancestor"
not listed in ARIA section" reported by Steve Faulkner.
Ian's Rationale: "Rationale: I don't understand. Could you elaborate?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10592
Steve's comment:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10592#c3

2.6 Bug 10780: "reference to definition of Action insufficient for
definition of accesskey reported by Gregory J. Rosmaita.
Ian's comment: "There's no reason to believe the element in question
would be focusable. For example, <command> elements aren't even
normally visible, let alone focusable. What should happen in that
case?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10780#c1

2.7 Bug 10784: change summary from an attribute to an element"
reported by Gregory J. Rosmaita.
Ian's comment: "I don't understand what problem this is solving."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10784#c2


3. WORKSFORME BUGS:

3.1 Bug 9773: "There is not a clear difference between "subtitles" and
"captions". These are mostly used to describe "closed captions"
(binary transmissions in TV broadcasts) vs "subtitles" (text files),
as far as I know." reported by contributor@whatwg.org.
Ian's Rationale: "I updated the spec to have clearer distinctions a
while back. The difference between the terms is not what you describe,
however."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9773

3.2 Bug 10593: "thead, tfoot and tbody conflicts in aria section"
reported by Steve Faulkner.
Ian's Rationale: "This seems to have been fixed already.'
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10593

3.3 Bug 10839: "Providing visible indication that descriptions and
captions are available" reported by John Foliot.
Ian's Rationale: "The spec already does this as much as it can.."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10839


4. INVALID BUGS:

4.1 Bug 9657: "Content model of object" reported by Leif Halvard Silli
Ian's Rationale: "I don't understand why we would want to duplicate
the error from HTML4 here.  An <object> representing its fallback is
essentially acting as if it wasn't there. Having a paragraph contain a
paragraph is bogus."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9657

4.2 Bug 9774: "consecutive lines displayed below each other" reported
by contributor@whatwg.org.
Ian's Rationale: "The text "consecutive lines displayed below each
other" is talking about the writing direction, not subtitles. We can't
use "after" since this is _defining_ the word "after". (e.g. writing
on roadways in English-speaking countries is written left-to-right
bottom-to-top, with subsequent lines appearing "after" each other
being above each other, not below.)"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9774

4.3 Bug 10481: "Default role of <IMG> should be img" reported by Leif
Halvard Silli.
Ian's Rationale: "This bug is out of control. I have no idea what I'm
even supposed to respond to anymore. If there is something that needs
changing, please file a simple bug with a clear and succinct statement
of the problem, without going on for pages and pages about how I'm
misunderstanding the spec or discussing the finer points of ARIA's
definitions, which all be happening on a mailing list."
Steve added the TrackerRequest Keyword.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10481#c53

4.4 Bug 10606: "Define what alt="<whitespace>" means for <img>"
reported by Leif Halvard Silli.
Ian's Rationale:"Problem 1: I don't see why authors would think alt="
" was equivalent to alt="". The spec is clear about the meaning of
"empty" and this kind of distinction is all over the platform. Pretty
much the only place where they _are_ the same is inter-element
whitespace. Problem 2: If people don't trust the spec, we can't fix
the problem by adding yet more text to the spec. Problem 3: I do not
buy the premise that any authors would even think about this. If you
disagree with any of these please file a new bug specifically for that
issue."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10606


5. FIXED BUGS:

5.1 Bug 10478: "modify table, tr and td role" reported by Steve Faulkner.
Ian's comment: "I gave up trying to understand this."
http://www.w3.org/Bugs/Public/show_activity.cgi?id=10478
Check-in: "remove anything to do with ARIA from the definitions of table
elements"
http://html5.org/tools/web-apps-tracker?from=5568&to=5569

5.2 Bug 10479: "add role=radiogroup to details element" reported by
Steve Faulkner.
Ian's comment: "So I went to make sure that "search" didn't support
aria-expanded, but it does. So then I checked what did, and I realised
that I'd made a mistake and not just direct "group" descendants
support aria-expanded, but a whole bunch of roles do. So I changed the
spec to allow any of the roles that support aria-expanded, including
role=radiogroup."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10479
Check-in:
http://html5.org/tools/web-apps-tracker?from=5510&to=5511

5.3 Bug 10518: "Add example showing how to use <a> elements in image
maps" reported by Leif Halvard Silli.
Ian's comment: "Concurred with reporter's comments."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10518
Check-in:
http://html5.org/tools/web-apps-tracker?from=5571&to=5572

5.4 Bug 10591: "conflicting info for table element in aria section"
reported by Steve Faulkner.
Ian's comment: "Concurred with reporter's comments."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10591
Check-in:
http://html5.org/tools/web-apps-tracker?from=5514&to=5515

5.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.
Ian's comment: "<figcaption> should only be used as a caption of a
no-alt <img> if there's no other content in the <figure>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10596
Check-in:
http://html5.org/tools/web-apps-tracker?from=5516&to=5517

5.6 Bug 10603: "Clarify what default roles UAs may assign to elements
not listed in the ARIA section" reported by Benjamin Hawkes-Lewis.
Ian's comment: "...I haven't made any changes yet but I shall remove
the two paragraphs mentioend above when I next look at this bug (I'm
in the middle of some other edits right now, but Maciej asked me to
comment ASAP)."
Ian's comment: "Clarified confusing paragraphs by removing them
altogether, as per comment 2."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10603#c3
Check-in:
http://html5.org/tools/web-apps-tracker?from=5566&to=5567

5.7 Bug 10604: "Don't say 'empty' about @alt anywhere, say 'empty
string' everywhere" reported by Leif Halvard Silli.
Ian's rationale: "It seems that if 'empty value' is ambiguous, 'empty
string' would be too, so I just added a generic definition of 'empty'"
to the terminology section."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10604
Check-in:
http://html5.org/tools/web-apps-tracker?from=5523&to=5524

5.8 Bug 10605: "Replace 'the alt attribute's value may be omitted'
with '@alt may be omitted'" reported by Leif Halvard Silli.
Ian's comment: "omitting a content attribute value makes no sense"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10605
Check-in:
http://html5.org/tools/web-apps-tracker?from=5555&to=5556

5.9 Bug 10710: " Require controls to have programatically associated
names reported by Benjamin Hawkes-Lewis.
Ian's rationale: "As a side note, I don't think programmatically means
what you think it means..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10710#c1
Check-in comment: Require label for <input type=button>
http://html5.org/tools/web-apps-tracker?from=5549&to=5550

5.10 Bug 10781: "are accesskeys case sensitive? reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10781
Ian's rationale: "Concurred with reporter's comments."
Check-in comment: handled in terms of case-sensitivity.
http://html5.org/tools/web-apps-tracker?from=5570&to=5571


6. REOPENED BUGS:

6.1 Bug 10642: "No alternative text description for video key frame
(poster)" reported by Everett Zufelt.
Ian's Rationale:” The rationale provided is that text is needed to
help users of ATs determine the topic and mood of the video. However,
that information is not (necessarily) provided by the poster frame,
and thus cannot be considered an alternative to the poster frame. It
is also not an alternative to the video. It is the title or caption of
the video, for which we already have a multitude of mechanisms such as
title="", <figcaption>, <h1>, and aria-labelledby=""."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10642#c22
Everett Reopened: Where authors are intentionally presenting content
as an image the image must have an alternative text representation.
The title of a video is not sufficient to replace the poster image in
every scenario."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10642#c23

6.2 Bug 10661: "use an ISO 639-2 specified language for HTML5
documents" reported by Gregory J. Rosmaita.
Ian's Rationale: "Please obtain a sense of humour and then try again."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10661
REOPENED by Gregory. Gregory's comment: "i once had a sense of humor
--  hen i started working on HTML5... regardless of humor, the natural
language definition of the w3c document should be either "en" or
"en-us""
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10661#c7
Ian's Rationale: "No new information added this last resolution."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10661#c8

6.3 Bug 10693: "Need a means for navigating between related timed
tracks of media elements" reported by Silvia Pfeiffer.
Ian's comment: "Could you provide an example of software that does
what you describe? I'm not really understanding what it is you want
browsers to do here. Is the request to have browser UI to do
something, or would it be sufficient to have an API to allow scripts
to provide such a feature?"
Ian's Rationale: "Could you provide an example of software that does
what you describe? I'm not really understanding what it is you want
browsers to do here. Is the request to have browser UI to do
something, or would it be sufficient to have an API to allow scripts
to provide such a feature?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10693#c1
John Foliot:  "This has been identified as a probable issue within
HTML5 by the media sub-team of the Accessibility Task Force. The bug
has been filed at this time to meet the October 1st cutoff date, with
more details forth coming."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10693#c3

6.4 Bug 10709: "@title should be a required attribute for FRAME and
IFRAME in HTML5" reported by Gregory J. Rosmaita.
Ian's Rationale: "I concur with Maciej's comments."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10709

6.5 Bug 10713: "Drag and Drop: Add guidance for keyboard-only
interaction" reported by Gez Lemon.
Ian's comment: "I'm not sure which part of that e-mail I'm supposed to
be looking at. Is this requesting just a paragraph similar to the one
starting "On a visual medium with a pointing device..."? But for some
other medium and other input device? Which ones exactly? Audio medium
with a keyboard input device? What should it say?"..."no spec change
Rationale: see comment 1."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10713#c2

6.6 Bug 10842: "Support the isolation of speech from other  background
sounds in AV media" reported by John Foliot.
Ian's comment: "Please don't link to long documents in the bugs, just
describe the problem. That notwithstanding, though, I really have no
idea what this request is intended for. Do you mean that HTML should
have an API to perform audio analysis and background muting? Or is
this a request for a user agent requirement of some kind? I'm not
clear at all what is being requested here. What is the HTML feature
that I can add to address this bug?...I don't understand. Could you
elaborate?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10842#c1
John Foliot "** This has been identified as a probable issue within
HTML5 by the media
sub-team of the Accessibility Task Force. The bug has been filed at this time
to meet the October 1st cutoff date, with more details forth coming. **"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10842#c3

6.7 Bug 10873: "Provide a method of explicitly setting a tooltip for
an element" reported by Everett Zufelt.
Ian's Rationale: "The title="" attribute is as close as we can get to
this without being media- or device-specific. Just consider title=""
to be for tooltips and in practice you will be fine. The reason that
the spec dodges the issue as it does is that we have to leave precise
user interface details up to the user agent. For example, the Lynx
implementors might prefer to show the advisory text in a status line
rather than in a tooltip."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10873#c1
REOPENED by John Foliot: "The Editor's response does not address the 3
technical requirements articulated in the initial bug..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10873#c2
TrackerRequest applied by John Foliot.


7. ASSIGNED BUGS:

ASSIGNED means "This bug is not yet resolved, but is assigned to the
proper person. From here bugs can be given to another person and
become NEW, or resolved and become RESOLVED."

7.1 Bug 9876: "Clarify that a figure can be any content with a
caption" reported by contributor@whatwg.org.
REOPENED by James Graham.
"So I think the original point here was that <figure> provides a means
to group an image and a caption together. There is no point in
limiting the scope to only cases where the <figure> is not the primary
content in the page because such a limitation will be ignored in
practice. It is also not clear what value it would bring and, in some
cases would be downright odd. For example consider a scientific
article that provides captioned <figure>s in the main article, but
where each image links to a page displaying only the image+caption,
but at a larger size. Requiring that authors use different markup for
the same content in these two situations seems perverse."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9876#c8
Ian's comment: none.

7.2 Bug 10419: "<video> should allow muted as a content attribute"
reported by Adrian Bateman.
Ian's comment: "I don't think muted="" makes sense, since it would
interact poorly with reflection. However, I could see an argument for
adding something like defaultmuted=""..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10419#c1

7.3 Bug 10450: "Allow lists to be used as menus or tab sets" reported
by Maciej Stachowiak.
FIXED by Ian on Sept 7.
TrackerRequest by Steve on September 9.
FIXED by Martin on Sept 14.
TrackerRequest by Maciej  on Sept 15.
ASSIGNED by Ian on Sept 27.
http://www.w3.org/Bugs/Public/show_activity.cgi?id=10450

7.4 Bug 10712: "Drag and Drop: Add an attribute to identify drop
targets" reported by Gez Lemon.
Ian's comment: "Would this attribute's presence essentially change the
dragover and dragenter events to always seem canceled? It would be
useful to have implementor feedback on this feature. Is this something
implementors would be interested in supporting?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10712

7.5 Bug 10775: "how is user to decide which set of access keys to
use?" reported by Gregory J. Rosmaita.
Ian's comment: "I'll add a bunch of non-normative text to the spec to
explain how this works more clearly, since the current text is clearly
not understandable enough. Sorry for making it so opaque."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10775

7.6 Bug 10837: "playbackrate: undefined behavior when the user agent
can't play back at the requested rate" reported by Frank Olivier.
Ian's comment: "How can you not be able to support it? At the worst,
you'll just have to keep seeking backwards and show a frame here and a
frame there; it's just a quality of implementation issue. If you
simply can't seek to that point the spec also defines how to handle
that (same as if you can't seek forward, in fact). You just stall. I
don't understand what the problem is here."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10837

7.7 Bug 10849: "provide means to add image content catagories to
images" reported by Steve Faulkner.
Ian's comment: "I haven't examined the proposal in detail yet, but
before I do: do we have experimental implementations or any
implementors committed to supporting this? At this stage I'd really
rather not add new features without a clear commitment from user agent
implementors, given how close we are to LC."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10849


8. NEW BUGS:

8.1 Bug 10772: "accesskey and an ordered set of unique space-separated
tokens" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10772

8.2 Bug 10773: "accesskey should chosen from document's declared
charset" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10773

8.3 Bug 10774: "fallback for accesskey insufficiently defined"
reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10774

8.4 Bug 10775: "how is user to decide which set of access keys to
use?" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10775

8.5 Bug 10776: "accesskey value token subsets" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10776

8.6 Bug 10777: "user agent assignment of modifier keys subset of
accesskey processing subset" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10777

8.7 Bug 10778: "use element.accessKeyLabel to generate list of
available accesskeys" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10778

8.8 Bug 10779: "triggering the Action of the command via accesskey"
reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10779

8.9 Bug 10780: "reference to definition of Action insufficient for
definition of accesskey reported by Gregory J. Rosmaita.
hhttp://www.w3.org/Bugs/Public/show_bug.cgi?id=10780

8.10 Bug 10781: "are accesskeys case sensitive?" reported by Gregory
J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10781

8.11 Bug 10782: "problems with button example for accesskey" reported
by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10782

8.12 Bug 10831: "Provide tablist and tab states for menu and command
elements respectively"  reported by Everett Zufelt.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831

8.13 Bug 10837: "playbackrate: undefined behavior when the user agent
can't play back at the requested rate" reported by Frank Olivier.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10837

8.14 Bug 10839: "Providing visible indication that descriptions and
captions are available" reported by John Foliot.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10839

8.15 Bug 10840: "Allow the user to independently adjust the  volumes
of the audio description and original soundtracks" reported by John
Foliot.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10840

8.16 Bug 10841: "We require a method to allow the user to control
playback timing in order to have more time to understand the material"
reported by John Foliot.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10841

8.17 Bug 10842: "Support the isolation of speech from other
background sounds in AV media" reported by John Foliot.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10842

8.18 Bug 10843: "Support user control over the visual presentation  of
caption text" reported by John Foliot.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10843

8.19 Bug 10849: "provide means to add image content catagories to
images" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10849

8.20 Bug 10851: "Javascript access to rendered (calculated) styling
information of a DOM node" reported by Jon Gunderson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10851

8.21 Bug 10853: "HTML5 lacks a verbose description mechanism" reported
by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10853

8.22 Bug 10873: "Provide a method of explicitly setting a tooltip for
an element" reported by Everett Zufelt.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10873

8.23 Bug 10888: "Access Command Requirements for HTML5" reported by
Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10888

8.24 Bug 10896: "enable device independent access to event handlers"
reported by Leonie Watson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10896

8.25 Bug 10903: "provide an introduction to wai-aria in the wai aria
section of the spec" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10903

8.26 Bug 10905: "clarify how assigning an accesskey to an element
affects the elements default role" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10905

8.27 Bug 10906: "make the conforming use of placeholder dependent on
the presence of a label" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10906

8.28 Bug 10914: "Allow multiple space separated values for the ARIA
role attribute" reported by Martin Kliehm.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10914

8.29 Bug 10915: "clarify why a command element that is not in a menu
is conforming" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10915

8.30 Bug 10916: "Add a new <control> element to convey the common
semantics of a script enabled UI control" reported by Adrian Bateman.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10916

8.31 Bug 10917: "modify user agent requirement for details element"
reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10917

8.32 Bug 10918: "provide better examples" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10918

8.33 Bug 10919: "Allow role="presentation" to override the default
role of any element" reported by Martin Kliehm.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10919

8.34 Bug 10921: "put back direct link to the W3C version of the canvas
2d context spec" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10921

8.35 Bug 10927: "collection of all interactive (actionable, focusable)
elements" reported by Cynthia Shelly.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10927

8.36 Bug 10931: "Add details or summary to focus management section"
reported by Cynthia Shelly.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10931

8.37 Bug 10932: "add area to 7.4.2 Focus management" reported by Cynthia Shelly.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10932

8.38 Bug 10933: "add link types that create hyperlinks to 7.4.2 Focus
management" reported by Cynthia Shelly.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10933

8.39 Bug 10935: "consider 10.4 Bindings impact on UAG" reported by
Cynthia Shelly.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10935

8.40 Bug 10938: "Add <textual/> - a visible textual substitute element
w/link capability" reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10938

8.41 Bug 10941: "Media elements need control-independent "pause" for
presenting lengthy descriptions/captions" reported by Masatomo
Kobayashi.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10941

8.42 Bug 10964: "Canvas needs to support a backing store in the DOM
subtree capable of supporting screen reading" reported by Rich
Schwerdtfeger.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10964


9. LATER BUGS:

9.1 Bug 10645: "Add a modal attribute to html5 to indicate a modal
segment of the DOM (modal dialog)" reported by Everett Zufelt.
Ian's Rationale: "Concurred with reporter's comments, but it's still too early."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10645


10. DUPLICATE BUGS:

10.1 Bug 10783: "change summary from an attribute to an element"
reported by Gregory J. Rosmaita.
This bug has been marked as a duplicate of bug 10784 by Gregory.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10783


11. "A11yTF" KEYWORD BACKLOG:

We currently have 107 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 " HTML Working Group Decision Policy" awaits task
force decision. Maciej Stachowiak, Paul Cotton, Sam Ruby are the
editors 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


12. 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, 3 October 2010 19:41:55 GMT

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