W3C home > Mailing lists > Public > public-pfwg@w3.org > February 2014

Re: Effect of role=presentation on img elements with svg

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Tue, 4 Feb 2014 12:04:51 +0100
To: James Craig <jcraig@apple.com>
Cc: public-pfwg@w3.org, Bryan Garaventa <bryan.garaventa@whatsock.com>, Steve Faulkner <faulkner.steve@gmail.com>, Joanmarie Diggs <jdiggs@igalia.com>, Cynthia Shelly <cyns@microsoft.com>, "T.V Raman" <raman@google.com>, "Gunderson, Jon R" <jongund@illinois.edu>, Jason White <jason@jasonjgw.net>
Message-ID: <20140204120451571294.6d13a2e7@xn--mlform-iua.no>
James Craig, Mon, 03 Feb 2014 17:45:02 -0800:
>>> I think the core of this debate is still that the name “presentation” 
>>> has historically meant, that the entire sub-tree is devoid of 
>>> semantic meaning,

Agreed. That’s how the thinking goes.

For my own part, I did not think that way about e.g. <table 
role=presentation>, but I did think that way about <img 
src="table.svg">.

>>> but that’s not what role="presentation" means, 
>>> which is why we’re talking about choosing a new name. There is too 
>>> much historical baggage that comes with that term. 

Has the component for reporting ARIA bugs been set up?

Here are some things that I think ARIA 1.1. should be updated with:

1. Presentation role section should have more examples, to explain the 
”edge” cases, such as the fact that role="presentation" does not 
prevent AT from looking into the subdom of resources referenced via 
@src (and I suppose of @data, of the object element). Would also be 
good to exemplify edge cases such as <video role="presentation"> - what 
its effect is (not).

3. Definition of ”descendants”, in connection with the accessible name 
calculation, so that readers of ARIA understand that ”descendants” is 
not only only child elements but also elements of resources that a 
linked to the element via @src, @data or (I think) otherwise.

4. Clarification, for role=Presentation, of what ”implicit native role 
semantics” covers and what it does *not* cover. Definition and examples.
-- 
leif halvard silli
Received on Tuesday, 4 February 2014 11:05:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:00 UTC