🤡 The wrong way to use aria-roledescription to call out someone as a fascist:

html5accessibility.com/stuff/2…

#a11y #webDev #politics #ARIA
[share author='stevef' profile='https://html5accessibility.com/stuff/author/stevef/' avatar='' link='https://html5accessibility.com/stuff/2020/10/06/micro-note-on-aria-roledescription/' posted='2020-10-06 13:28:50' guid='81daf735-8b2361906e7d629a-214181df' message_id='https://html5accessibility.com/stuff/2020/10/06/micro-note-on-aria-roledescription/']aria-roledescription is not a label

It is an alternative expression of the Aural UI of the role of an element.

inappropriately using aria-roledescription may inhibit users’ ability to understand or interact with an element.
ARIA 1.1

The wrong way to use aria-roledescription and call out someone as a fascist:

code

<img aria-roledescription="fascist" src="dt.PNG"
alt="Donald Trump">

This is wrong because you are not identifying the subject of the image as a fascist, you are overwriting the <img> element role so it effectively becomes a <fascist> element. Also, there is no explicit text identification of the subject as a fascist.

A much better way to achieve the aim of identifying a fascist (and not misusing aria-roledescription):
Example of a fascist
code
<figure>
<figcaption>Example of a fascist</figcaption>
<img src="dt.PNG" alt="Donald Trump">
</figure>

html5accessibility.com/stuff/2…

André Polykanine reshared this.

in reply to Steve Faulkner

Yes, but these are usually are not rendered in to virtual buffer or are not located within context, sometimes for the right reasons. Say, a description is generated on-focus. It will disappear as soon as the focus moves away. So, it sort of depends on the screen reader and OS, but the behaviour is inconsistent. A good exampleare automatically-generated image descriptions.
⇧