Archive index

A11y Slackers Gitter Channel Archive 11th of September 2015

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    07:03
    [heydon, a11y] Just wanted to share that yesterday, in the a11y workshop I was running, I did a quiz asking teams to name as many accessible naming techniques as they could. The top team got 7. Together we thought of 8… aria-labelledby, aria-label, text node, title, alt, value (type=submit), <title> (body/SVG), for attr. Can anyone think of any more?
  2. zakim-robot
    08:37
    [vcurd, a11y] If you count <title> then would <label> and <legend> not count also?
  3. LjWatson
    08:40
    @vcurd what's the context for your question? I don't have the chat history before about 30 mins ago.
  4. zakim-robot
    08:48
    [vcurd, a11y] @ljwatson: @heydon had asked if there were any other accessible naming techniques, other than aria-labelledby, aria-label, text node, title, alt, value (type=submit), <title> (body/SVG), for attr. I think that if you count <title> for documents then <label> and <legend> also count.
  5. zakim-robot
    08:59
    [vcurd, a11y] @ljwatson: @heydon For that matter, <caption> for tables and <figcaption> for figures may count.
  6. LjWatson
    09:40
    @vcurd yes, all of those things provide accessible names for their respective parents and/or the doc itself.
  7. jonathantneal
    13:44
    Is there a certain way buttons or select boxes need to be marked when their changes can immediately effect content beneath them (eg when selects are used as instantaneous filters)?
  8. jonathantneal
    13:49
    I think https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions may be the answer.
  9. deborahgu
    14:10
    yep, that's it
  10. deborahgu
    14:10
    although you want to be mindful about the level of verbosity.
  11. deborahgu
    14:11
    if what is changing is a bunch of values immediately below the checkbox, there is an argument for not announcing it, since the person moving through the form will presumably get to those values next.
  12. deborahgu
    14:12
    That is a particularly good use case for making sure you have some actual screen reader users in your tests, because you can be overly verbose in live regions. Definitely, though, the inaccessible default is in alerting too little, not too much.
  13. jonathantneal
    14:19
    Thanks.
  14. zakim-robot
    16:59
    [Greg Tarnoff, a11y] @marcysutton: @valhead (little late to the party - weird week) I haven’t seen any controls in the wild other than the one Rachel Nabors found at malazrybarnyfilm.cz
  15. zakim-robot
    17:02
    [Greg Tarnoff, a11y] Which of course seems to have changed now, so you’d probably have to watch the screencast we did.
  16. zakim-robot
    17:03
    [Val Head, a11y] @gregtarnoff: Yep, that’s the same one I was thinking of :simple_smile: It wasn’t really labeled well, but it’s the only one I’ve seen in the wild too.
  17. zakim-robot
    18:29
    [Marcy Sutton, a11y] thanks for the info! I was hoping to highlight something for a11ywins, but sounds like we have to make something :simple_smile:
  18. zakim-robot
    18:30
    [Marcy Sutton, a11y] I gave a shout-out to your article at Creative Mornings this morning @valhead, when someone asked in Q&A about accessibility for motion design
  19. zakim-robot
    19:14
    [Val Head, a11y] @marcysutton: aw, that’s so cool. Thanks! :simple_smile: And if I see any good toggles out there I’ll let you know.