[Bug 10919] Allow role="presentation" to override the default role of any element

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10919

--- Comment #20 from steve faulkner <faulkner.steve@gmail.com> 2011-05-18 13:38:16 UTC ---
(In reply to comment #15)
> (In reply to comment #14)
> 
> > http://dev.w3.org/html5/spec/text-level-semantics.html#the-a-element
> 
> I suppose that you, eventually, also meant 
> 
> http://dev.w3.org/html5/spec/the-map-element#the-area-element
> 
> ?
> 
> As for use cases, here are 3 usecase for a, area and summary.
> 
> 
> <a>: For <a href=* role=presentation> then the usecase 'Describing a Newspaper
> Image' of the Instate Longdesc CP, lists one:
> 
> http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc#Use_Cases
> http://www.d.umn.edu/~lcarlson/research/ld.html#uc-10
> 
> Example:
> 
> <a href=large-version.jpg 
>       role=presentation >
>      <img longdesc=description.html 
>                src=small-version.jpg
>                alt="Lorem ipsum">
> </a>
> 
> Here the link is just presentational - it has little value for someone who is
> unsighted.
> 
> Another, possible use case: some times an element is split into more than one
> anchor element, where each has hte same URI. May be it would be useful to make
> it so that only one of the links are pereceived as a link.
> 
> For <area>, then I am  not certain what happens it if gets role=presentation,
> but I suppose it means that @aria-*,  @alt and @title attribute are ignored. If
> so, then may be  it could be useful e.g. if one wanted to use anchor elements -
> only - for AT and perhaps both area and anchors for non AT.
> 
> For <summary>, if <summary> is given role=presentation, then it would be equal
> to there not being any summary element - summary would instead just be a normal
> part of the body of the details element. When there is no summary element, then
> HTML5 says: 'If there is no child summary element, the user agent should
> provide its own legend (e.g. "Details").'  Clearly, there are use cases for not
> having a summary element. But whether there are usecases for having <summary>
> be treated as the content of the <details> elelement - that I don't know. But
> if thbe content <summary> is entirely useless - e.g. if it is just whitespace
> or a presentational image ... etc.


screen magnifification software uses information from the accessibility tree,
many people who use screen readers have some sight and may well beneefit form a
large view of an image.

your use case is poorly considered.

-- 
Configure bugmail: http://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 Wednesday, 18 May 2011 13:38:18 UTC