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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Tue, 23 Feb 2010 18:08:19 -0600
Message-ID: <1c8dbcaa1002231608v609f2e09r8999f7359f85b3dc@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since last week's report we have had:

3 WONTFIX bug resolutions
7 NEEDSINFO bug resolution
3 WORKSFORME bug resolution
1 INVALID bug resolution
1 FIXED bug resolution

1 REOPENED bug
3 NEW a11y bugs reported

A new Bugzilla component has been set up for the document “"HTML5:
Techniques for providing useful text alternatives".  It would be
helpful if that document is reviewed by the task force and WAI so we
make sure it is in compliance with WCAG.
http://www.w3.org/Bugs/Public/buglist.cgi?&product=HTML+WG&component=alt+techniques+(editor%3A+Steven+Faulkner)

The details are as follows.


1. RESOLVED WONTFIX BUGS:

Bug 8644 "Fallback mechanism for embedded content" reported by Gez Lemon.
Editor's Rationale: "alt="" isn't about providing a short text
alternative, it's about providing an alternative. It just so happens
that a limitation of <img>, <area>, and <input> forces the
alternatives for those particular elements to only be text, with no
markup. However, that's a bug, not a feature."
LC Suggestion:  The bug reporter along with anyone interested follow
up with specific functional requirements and rationale.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8644

Bug 8743: "Auditory icons clashing with AT" reported by Gez Lemon.
Editor's Rationale: "How icons are used is entirely up to the UA."
LC Suggestion: The bug reporter along with anyone interested follow up
with specific functional requirements and rationale.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8743

Bug 8872: "Split out and modify parts of Section 4.8.2.1 the img
element" reported by Steve Faulkner.
Editor's Rationale: "I'm all in favour of the referenced document, but
I don't think we should remove the text from the HTML5 spec. We should
just have both. The more places we have this the more likely it is
that authors will see it."
LC Suggestion: The task force follow up on this bug. A format
specification is not a tutorial. Detailed non-normative guidance in
the application of the text alternatives is not appropriate for
inclusion in a markup language specification. It could be seen as
usurping the role of WCAG 2.0 and WAI approved techniques documents.
The spec in this case should be confined to a concise description,
consistent with WCAG 2.0, of the function of text alternatives, a
_brief_ discussion of various possibilities as outlined in WCAG 2 and
a link to the document "HTML5: Techniques for providing useful text
alternatives". That document should be reviewed by this task force and
WAI so that it in compliance with WCAG. Steve's document has a
Bugzilla component set up. Five bugs have been filed to date.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8872
http://dev.w3.org/html5/alt-techniques/ guideline
http://www.w3.org/Bugs/Public/buglist.cgi?&product=HTML+WG&component=alt+techniques+(editor%3A+Steven+Faulkner)

All WONTFIX bugs
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Resolution:_WONTFIX_Bugs


2. RESOLVED NEEDSINFO BUGS:

Bug 8652: "what to display when images are not available is not
well..." reported by Steve Faulkner.
Editor's Rationale: "As far as I can tell the spec already covers
everything suggested in comment 2 in far more detail than proposed..."
LC Suggestion: The bug reporter and anyone else who is interested try
to give Ian the information that he needs.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8652

Bug 8715: "Scrolling elements into view" reported by Joshue O Connor.
Editor's Rationale: Did Not Understand Request.
LC Suggestion: The bug reporter and anyone else who is interested try
to give Ian the information that he needs.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8715
Also it is unclear if this bug is an  a11ytf bug or not, as it has the
a11ytf keyword but Michael's comment 3 says the task force does not
intend to work on it.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8715#c3
Suggest adding this bug to the a11ytf pile if Josh or other task force
members provides info.

Bug 8723: "Image map is underspecified " reported by Steve Faulkner.
Editor's Rationale: "If you could help me a little more that would be
great. Could you quote the text that applies to other elements which
doesn't apply to <area> and which I should apply to <area> as well?
I'm not sure I fully understand your request yet and I'd like to make
sure I understand it before trying to make any changes. Thanks!"
LC Suggestion: The bug reporter and anyone else who is interested try
to give Ian the information that he needs.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8723

Bug 8738: "Role-based navigation" reported by Gez Lemon.
Editor's Rationale: "accesskey="" on <command> is the same as on any
other element. I don't understand what is special about <command>
here. Could you elaborate? If you could paste the relevant parts of
the cited document that would be great, I read through it but couldn't
work out the relevance to <command>. The summary of this bug doesn't
mention <command>, just "role-based navigation". Is this a separate
issue? Is the request here to add role-based navigation to HTML,
independent of <command>?"
LC Suggestion: The bug reporter and anyone else who is interested try
to give Ian the information that he needs.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8738

Bug 8740: "How do pseudo-class selectors interact with WAI-ARIA?"
reportd by Gez Lemon.
Editor's Rationale: "Wouldn't this be a question for for either the
ARIA spec or the Selectors spec? (As it happens I concur with hsivonen
and don't think ARIA should affect selectors, but that doesn't seem to
be in the HTML spec's bailiwick.)"
LC Suggestion: The bug reporter and anyone else who is interested try
to answerer Ian's question.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8740

Bug 8747: "Defining how a license applies to elements" reported by Gez Lemon.
Editor's Rationale: "Existing pages use rel=license as described in
the spec. There isn't enough information in those pages for any
algorithm (accessibility-related or otherwise) to identify the item to
which the license applies. As Toby mentioned, that's why we have RDFa,
or microdata, or other such solutions. I'm not sure, therefore, how to
address this bug. Please reopen the bug if there is something I can do
to further help here."
LC Suggestion: The bug reporter and anyone else who is interested try
to give Ian the information that he needs.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8747

Bug 8752: "Allow user to manage focus changes" reported by Gez Lemon.
Editor's Rationale: "How exactly do you mean "hold off"? Do you mean
that the focusing steps should optionally asynchronously wait for a
period of time and then change the focus? Or do you mean that focus
changes should just be disabled at the user agent's option?"
LC Suggestion: The bug reporter and anyone else who is interested try
to give Ian the information that he needs.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8752

All NEEDSINFO bugs
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Resolution:_NEEDSINFO_Bugs


3. RESOLVED WORKSFORME BUGS:

Bug 8750: "User able to override the hidden attribute in incorrectly
rendered pages" reported by Gez Lemon.
Editor's Rationale: "The rendering section already establishes that
UAs can render pages however they like, including presenting
everything that's hidden, the whole DOM tree, the source of scripts,
or whatever else the user might want to see."
LC Suggestion: The bug reporter and anyone else interested verify that
this resolution works for everyone.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8750

Bug 8751: "User should have ability to override automatic scrolling"
reported by Gez Lemon.
Editor's Rationale: "The spec already allows for this - that's why the
scrolling requirement is a "should" and not a "must" (only bringing
the user's attention to the given element is a "must", and the spec
doesn't say how the UA is to do that)."
LC Suggestion: The bug reporter and anyone else interested verify that
this resolution works for everyone.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8751

Bug 8754: "Overflow when text is resized" reported by Gez Lemon.
Editor's Rationale: "This doesn't seem to be in scope for HTML..."
LC Suggestion: The bug reporter and anyone else interested verify that
this resolution works for everyone.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8754

All WORKSFORME bugs
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Resolution:_WORKSFORME_Bugs


4. RESOLVED INVALID BUGS:

Bug 8644 "Undo for drag and drop" reported by Gez Lemon.
Editor's Rationale: "This does not appear to be a change request."
LC Suggestion: The bug reporter and anyone else interested verify that
the bug is in fact invalid.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8753

All INVALID bugs
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Resolution:_ INVALID_Bugs


5. RESOLVED FIXED BUGS:

Bug 8716: "Replace img Guidance for Conformance Checkers with
Suggested Text for Short Text Alternatives" reported by Laura Carlson.
Editor's Rationale: "Partially Accepted. I guess it's worth trying to
make this more readable. I've duplicated the text from #unknown-images
and put it into the validator section, in an attempt to follow the
suggestion. I'm not sure this is a real improvement though, to be
honest. If anyone thinks it was better without the duplication, please
file a bug to that effect."
LC Suggestion: The "Guidance for conformance checkers" section of the
spec is indeed more readable.
http://dev.w3.org/html5/spec/text-level-semantics.html#guidance-for-conformance-checkers
But the substantive parts of this bug were not addressed. The bug
probably doesn't need to be reopened as HTML Issue 31 supersedes it.
The HTML Chairs have called for Change Proposals and one has been
drafted.
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8716

All FIXED bugs
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Resolution:_FIXED_Bugs


6. REOPENED BUGS:

he following three bug was reopened. Steve details it in his bug comments.

Bug 8722: "Focus behaviour should be same for canvas regions as for
elements" reported by Steve Faulkner. This bug had been rejected with
the editor's rationale "Rationale: making this a 'may' is consistent
with the best interests of users and consistent with all other user
interface requirements in the spec." Steve provided more information
and reopened the bug.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8722

All REOPENED bugs
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Status:_REOPENED_Bugs


7. NEW BUGS:

Bug 9061: "Allow image maps on the canvas element" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9061
LC Suggestion: Apply "a11ytf" "a11y_canvas" keywords and CC the a11y
list, as Canvas sub-group has this option in discussion.

Bug 9098: "Correct the img element definition. Replace with suggested
text." Reported by Laura Carlson on behalf of Vlad Alexander.
LC Suggestion: Apply "a11ytf" and "a11y_text-alt" keywords. This Bug
relates to with HTML Issue 31 and the current change proposals.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9098

Bug 9113: "axis on td and th elements" text could say "Use the scope
attribute on the relevant th"  Reported contributor@whatwg.org.
LC Suggestion: If any task force member sees a need to apply the
"a11ytf" keyword to track this bug please speak up.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9113

All NEW bugs
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Status:_NEW_Bugs


8. RELATED REFERENCES:

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

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

Accepted Bugs:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/accepted

Bugs With No Official Task Force Work Plan
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/rejected

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

Accessibility Issues in the HTML5 Tracker:
http://www.w3.org/WAI/PF/HTML/wiki/Issues

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

Accessibility Bugs touched since the last report:
http://www.w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&keywords=a11ytf&bug_status=RESOLVED&chfieldfrom=2010-02-17&chfieldto=2010-02-23

Best Regards,
Laura

--
Laura L. Carlson
Received on Wednesday, 24 February 2010 00:08:52 GMT

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