- From: <bugzilla@jessica.w3.org>
- Date: Sat, 22 Sep 2012 00:42:05 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18952
Maciej Stachowiak <mjs@apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjs@apple.com
--- Comment #3 from Maciej Stachowiak <mjs@apple.com> 2012-09-22 00:42:05 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> >
> > Status: Rejected
> > Change Description: No spec change.
> > Rationale: Fortunately, we already have such machine-detectable
> > mechanisms. If an author refers to hidden="" content from <img usemap>,
> > aria-describedby="", etc., then they have established that that
> > hidden="" content is the second type of hidden content in your list.
> > Otherwise, tools should presume it is of the first type.
>
> I think you are missing the distinction of "...it's available for users to read
> if they perform *some command* to ask to see that content."
>
> In the case of aria-describedby, the value of that attribute is currently
> provided without user-intervention via the accessible description in the AAPI.
> The mechanism for a user to choose to "hear" that content or not does not exist
> in any current implementation (that I am aware of).
It exists in Safari+VoiceOver. aria-label and aria-labeledby are read
automatically. aria-description and aria-describedby are read only on demand
(you have to hit VO-H). We've always assumed that was supposed to be the
distinction between "label" and "description".
Regards,
Maciej
--
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 Saturday, 22 September 2012 00:42:06 UTC