[Bug 14937] Replace poor coding example for figure with multiple images

https://www.w3.org/Bugs/Public/show_bug.cgi?id=14937

steve faulkner <faulkner.steve@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #2 from steve faulkner <faulkner.steve@gmail.com> 2011-12-08 07:40:48 UTC ---
(In reply to comment #1)
> 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: This isn't an antipattern. It is a best practice. If current ATs
> don't make it accessible, then I recommend approaching AT vendors and
> explaining to them that they're not properly exposing HTML semantics.

You obviously misunderstand, this issue has nothing to do with AT, your 'best
practice' is based on a fiction that the title attribute content is available
to all users via the browser, it is most evidently not. All browser vendors are
aware of the issue (http://markmail.org/message/udftstmjgis5bdiu), but have
chosen not to do anything about it (for the last ten years). When you have
convinced browser vendors (apple, google, opera and microsoft) to fix the
issue, i.e. keyboard and touch screen users can access the title attribute
content, then you can claim your anti-pattern as a best practice. Until that
point it does not deserve to be in the W3C HTML5 spec and its inclusion does a
disservice to a range of users.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 8 December 2011 07:40:50 UTC