This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
WAI has submitted a proposal for text alternatives: http://www.w3.org/2009/06/Text-Alternatives-in-HTML5. This document comprises the change proposal. Discussion has taken place <http://lists.w3.org/Archives/Public/public-html/2009Aug/0781.html>. This bug is to put PFWG on record with respect to this. This also relates to Tracker ISSUE-31. PFWG plans to discuss the detailed solution in the HTML Accessibility Task Force. The issue of longdesc (ISSUE-30) is impacted by this issue. The PFWG does not have a consensus position on longdesc at the time of entering this issue. PFWG will enter a bug for long descriptions when it has a position.
*** Bug 6496 has been marked as a duplicate of this bug. ***
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: It's not clear what exactly is being requested here. Could I ask for individual bugs to be filed for each problem, and for the problems to be described in the bugs? The change proposal covers a wide range of topics and it is unclear exactly what the problems being solved by the change proposal are.
After speaking with Maciej, he suggested that instead of "Rejected", I use the following status when asking for more information: Status: Did Not Understand Request So, to reiterate (since apparently at least Laura was confused about this), I have no objection here, and would be happy to fix the spec to address problems raised, I just don't yet fully understand the problems being raised. See comment #2 for details.
Please refer to the Change proposal "Replace img guidance for conformance checkers with suggested text" [1] for details on how to implement the text alternatives proposal from WAI. It is a large issue that requires a comprehensive solution. Thank you. [1] http://esw.w3.org/topic/HTML/ChangeProposals/ImgElement20090126 This is associated with HTML TRACKER ISSUE-31 http://www.w3.org/html/wg/tracker/issues/31 Issue is detailed at: Omitting Shot Text Alternatives on <img> http://esw.w3.org/topic/HTML/IssueAltAttribute
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
Reopening this as the bugs in the dependency tree provide further information for the editor's consideration. http://www.w3.org/Bugs/Public/showdependencytree.cgi?id=8171 This is a large issue that requires a comprehensive solution. This bug is escalated in HTML TRACKER ISSUE-31 http://www.w3.org/html/wg/tracker/issues/31 The issue is detailed at: Omitting Short Text Alternatives on <img> http://esw.w3.org/topic/HTML/IssueAltAttribute The Change proposal "Replace img guidance for conformance checkers with suggested text" provides details on how to implement the text alternatives proposal from WAI. http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
I still have no idea what the problem for this bug is. Could you state clearly what the bug is so that I can fix it?
Laura?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: It's not clear what exactly is being requested here. Please file individual bugs to be filed for each problem, and describe the problems in those bugs.
Bug Triage Sub Team notes this is already listed under ISSUE 31. We have added the TrackerIssue keyword. We feel the issue is sufficiently clear.
Marking this bug WONTFIX as it is the main bug for HTML TRACKER ISSUE-31 and the editor has not fixed it per the Change proposal provided at: http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126 Which is a HTML Accessibility Task Force Recommendation http://lists.w3.org/Archives/Public/public-html/2010May/0033.html It is Proposal 2 on http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElementSurveyConformaceChoices Proposal 1 is the Editor's solution. This bug will be resolved when Issue 31 is resolved.
Adding TrackerRequest keyword. The proposed tracker issue is: text-alternatives: Implement the HTML Accessibility Task Force recommendations on alternatives including ways to provide on various elements, and advice for using them We note this bug was previously escalated to ISSUE-31, which is now closed (chair decision at http://lists.w3.org/Archives/Public/public-html/2011Apr/0453.html). During the time since the chair decision on ISSUE-31, the HTML Accessibility Task Force has done a lot of work on text alternatives, as represented in bugs depending on this one. We believe this meets the bar to be considered as new information sufficient to reopen the issue or create a new one.
Just some administrivia: removing TrackerIssue, TrackerRequest and adding WGDecision as this was already covered by the decision on Issue 31. This bug is already listed on the New Information Status page as being associated with Issue 31: http://dev.w3.org/html5/status/new-information-status.html#ISSUE-031b (In other words, the request based on New Information will still be processed, will still consider the contents of this bug, but the TrackerRequest and TrackerIssue keywords are meant to create a new issue, and refer to an existing raised/issue respectively)