- From: Deborah Kaplan <dkaplan@safaribooksonline.com>
- Date: Mon, 12 Oct 2015 13:52:53 -0400 (Eastern Daylight Time)
- To: Ivan Herman <ivan@w3.org>
- cc: "public-dpub-accessibility@w3.org" <public-dpub-accessibility@w3.org>
> That is of course correct. But I interpreted that option ("details with src and role") as providing the possibility to add a role that would make it clear that the src is some sort of an alternative description, ie, that it is not (necessarily) just a generic role.
>
> Maybe it is worth making it clearer in the text what we really mean by this combination.
I will clarify that as I have clarified some of the other terms, then.
Because as far as I'm concerned, details, annotation, figure, iframe,
etc, is all actually a distraction from the main point. We are asking for
either an element, and attribute, or an attribute with a specific value
(most likely a role), because (as far as I know), we need one of those 3
things in order to communicate the required meaning. If we are given a
role value (e.g. "role=extended-description"), and a spec explaining
how that role should be treated by UA/AT, then all the rest of it
just falls to browser and AT implementation, and content producers could
use details or iframes or annotations as pleased them.
Deborah
Received on Monday, 12 October 2015 17:57:54 UTC