- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 8 Jul 2021 23:31:58 +0100
- To: w3c-wai-ig@w3.org
On 08/07/2021 20:37, bryan rasmussen wrote: > On MDN https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_presentation_role > it says > > The presentation role is used to remove semantic meaning from an > element and any of its related child elements. > > and then in an important looking blue box it says "Note: Opinions may > differ on how assistive technology should handle this technique. The > information provided above is one of those opinions and therefore not > normative." > > that's nice because I could have sworn that I have used different > screen readers in which the role="presentation" is not read - but in > VoiceOver currently the role = presentation is read. > > This makes me wonder - is there a way to remove content from a > screenreader reading it that will also leave it otherwise visible and > available to keyboard navigation? > > And two what are these various ways that other assistive technologies > handle role="presentation" > I think you're getting confused here about what MDN says. It's not saying that the element and its children are removed/hidden when role="presentation" (or role="none") is there. it means their native *semantics* are removed. e.g. <h1 role="presentation">Test</h1> is not a heading level 1 anymore as far as assistive technologies are concerned, but it's exactly the same as if you used <div>Test</div> or some other neutral container element with no intrinsic semantics. P -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 8 July 2021 22:32:28 UTC