[caesar] Is there a resource that lists out how different screen readers treat aria-describedby? i.e. do they read it immediately with the element vs. only if the user requests it?
for example JAWS with aria-describedby on an image will read "press Jaws key plus alt plus r to read descriptive text" but for form fields it will read it automatically.
[caesar] Yeah, I also disagree with their success criteria that the aria-describedby info needs to be read out, but I got what I wanted (whether or not the SR reads it with or without user interaction)
[alastc] maybe there is an optimal rhythm? I.e. spread them out a little more? (Not that I've been keeping track, but I see role=drinks pop up quite a lot on twitter)
[michiel] alastc: yeah we try to do it every 3-4 months.
[michiel] But it was in Brighton as opposed to Amsterdam this time.
[alastc] ah
[michiel] So figured it didn’t matter it was closer to the other one.
[alastc] no idea then, I won't slander Brighton's accessibility scene ;)
[michiel] Heh, just blame me getting it together about two weeks in advanced. We normally have most organisational stuff done a couple months in advance.
[alice] If any of you are already trying the devtools accessibility experiment I would deeply appreciate your feedback - both things you like and things you find annoying/difficult
[alice] feel free to private message me here, or leave feedback here or in #a11y-devtools, or email me at aboxhall@chromium.org, or @ or DM me on twitter (@sundress) - whatever works for you!
[stephenwyattbush] looking for recommendations for best conference talks (ideally on youtube) about a11y to show to a room full of engineers who don’t yet know much about it. videos which will help build empathy and get them excited to build accessible ui
Gitter Channel Archive 11th of November 2016
