Archive index

A11y Slackers Gitter Channel Archive 31st of August 2015

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    08:26
    [jitendra, a11y] @stevef: ok
  2. zakim-robot
    08:41
    [heydon, a11y] @aadrian Actually, one of the tracks already does that. It’s called The Inaccessible PDF Song.
  3. aardrian
    16:04
    @Heydon Screams or demonstrates a screen reader hobbled by PDF?
  4. zakim-robot
    18:44
    [heidi valles, a11y] Label question - looking at a survey form where questions are not <label>s but aria-labelledby is used on the answer textareas, to ref the relevant question id. Ok a11y-wise? Not being able to click the question to focus the answer box seems slightly off, but is it much of a problem?
  5. zakim-robot
    18:50
    [heidi valles, a11y] @heydon: i will send a track!
  6. garcialo
    18:53
    Heidi, that is fine. I assume the questions the aria-labelledby is using is visible?
  7. garcialo
    18:53
    are*
  8. rodneyrehm
    18:54
    oh, <iframe> is only keyboard focusable in IE12, if the document in the iframe contains a focusable element.
  9. zakim-robot
    18:56
    [heidi valles, a11y] Thanks @garcialo , they are visible questions.
  10. garcialo
    19:00
    Sounds like you're good then. =)
  11. zakim-robot
    19:04
    [heidi valles, a11y] I'd never do it this way, but okaying it for someone else :wink:
  12. powrsurg
    20:25
    I just noticed that when I have aria-labelledby and aria-describedby in on my radiobuttons the <label> that also goes with it is not read
  13. powrsurg
    20:25
    in NVDA
  14. powrsurg
    20:26
    was using aria-labeledby to set the main selector of what the radiobuttons should have, and aria-describedby to associate the tooltiptext with it
  15. powrsurg
    20:27
    but then it just says "1 of 2" and "2 of 2" without what is in the labels. The values on the radiobuttons are 1 and 0, but I want it to read Yes and No
  16. cptvitamin
    20:29
    @powrsurg the value of the <label>s is 1 and 0?
  17. cptvitamin
    20:32
    all you need is <label><input type=“radio" value=“1”>Yes</label>
  18. cptvitamin
    20:33
    and the aria-describedby that references your tooltip (attribute on the input)
  19. powrsurg
    20:33
    https://gist.github.com/powrsurg/e0aa6ba23ece91b097c2
  20. cptvitamin
    20:35
    yeah, you don’t need the aria-labelled there
  21. cptvitamin
    20:36
    in fact, you don’t need the for attribute on the label either since the way you have it its implied
  22. powrsurg
    20:36
    the aria-labelledby has the "Set Team as Active?"
  23. powrsurg
    20:36
    text
  24. cptvitamin
    20:37
    aria-labelled by replaces the accessible name
  25. powrsurg
    20:38
    I want the user to be able to tab to the element and have it read off what it they're toggling (setting the team as active), and reading off the description that explains the settings
  26. powrsurg
    20:38
    which it does. Just doesn't read off the values, but instead says "1 of 2" for the values
  27. cptvitamin
    20:39
    aria-labelled by takes a space separated list of IDrefs
  28. cptvitamin
    20:39
    so you could combine both Set Team as Active and Yes/No
  29. powrsurg
    20:39
    yeah, I tried putting on an id on the labels ... it sorta works
  30. powrsurg
    20:39
    should aria-describedby always be read after the aria-labeledby?
  31. cptvitamin
    20:39
    yes
  32. powrsurg
    20:40
    so I should actually add it after the aria-described by so that it'll read the description and then say "Yes" for the user
  33. cptvitamin
    20:40
    no, you don’t want to do that
  34. cptvitamin
    20:40
    its important that the accessible name has the value Yes/No
  35. cptvitamin
    20:41
    have you considered using a fields/legend here?
  36. cptvitamin
    20:41
    fieldset
  37. cptvitamin
    20:42
    aria-describedby is not always read, not always read in a timely manner, can be user configured to not read, so you don’t want to put the really important part of this label (Yes/No) in aria-describedby
  38. powrsurg
    20:42
    that is VERY good to know
  39. cptvitamin
    20:43
    i think fieldset/legend is the correct approach here
  40. powrsurg
    20:43
    I tend to use fieldsets for grouping many like types of things, not just to properly handle radiobuttons.
  41. powrsurg
    20:43
    so for me it's like billing address, shipping address ...
  42. cptvitamin
    20:44
    http://www.w3.org/TR/2008/WD-WCAG20-TECHS-20080430/H82.html
  43. cptvitamin
    20:44
    see Example 1
  44. cptvitamin
    20:45
    put your aria-describedby on the legend element
  45. powrsurg
    20:46
    okay, I need to bring that up during our next dev discussion ...
  46. cptvitamin
    20:47
    You could also consider a more modern approach, however, support and proper implementation is not 100% of the way there: http://www.deque.com/blog/aria-group-viable-alternative-fieldset-legend/
  47. garcialo
    20:52
    @cptvitamin I love your avatar.
  48. powrsurg
    20:52
    Would having role="radiogroup" change things at all?
  49. cptvitamin
    20:53
    @powrsurg where would you put that?
  50. powrsurg
    20:55
    Yeah, that doesn't make sense
  51. powrsurg
    20:55
    sorry
  52. powrsurg
    20:55
    literally did not sleep at all last night
  53. cptvitamin
    20:55
    @garcialo you mean that picture of me from 10 years ago when I had a bright smile, a positive attitude and a youthful complexion? Before all that was taken away from me?
  54. garcialo
    21:21
    @cptvitamin Ah yes, truly the beauty of youth.