Archive index

A11y Slackers Gitter Channel Archive 16th of October 2015

What fresh hell is THIS now? - Patrick Lauke
  1. MichielBijl
    11:21
    @powrsurg I would also like to see an example
  2. MichielBijl @MichielBijl is curious
  3. powrsurg
    13:34
    http://codepen.io/powrsurg/pen/YyEzYj
  4. powrsurg
    13:34
    Sorry, you all responded after I left ...
  5. powrsurg
    13:34
    though for some reason this DOES read everything ... except it reads the alt text for the image BEFORE it reads the text from the div
  6. zakim-robot
    14:26
    [jitendra, a11y] is this really useful <a href="#">Overview <span class="sr-only">(current)</span></a> ?
  7. zakim-robot
    14:44
    [dylanb, a11y] @jitendra: it can be
  8. zakim-robot
    15:06
    [jitendra, a11y] @dylanb: What happens without it
  9. zakim-robot
    15:07
    [jitendra, a11y] to inform user about active page
  10. zakim-robot
    15:14
    [dylanb, a11y] @jitendra: if it is useful/required to inform a user about the state of some UI control and this is not possible with ARIA (for example ARIA does not have a breadcrumb role), then you use on off screen text like that
  11. zakim-robot
    15:45
    [Joe Watkins, a11y] @powrsurg did you try using aria-atomic="true" along with the aria-live?
  12. powrsurg
    16:05
    good, point, let met try
  13. powrsurg
    16:05
    btw, the kindle fire's screen reader seems to be pretty darn good from my testing
  14. powrsurg
    16:39
    @Joe Watkins (I dunno if I just tagged that right). I added aria-atomic="true" to the codepen and that didn't change it
  15. powrsurg
    17:04
    I assume Android's TalkBack successfullness is tied into the Android version?
  16. garcialo
    17:04
    are there other places TalkBack is used?
  17. powrsurg
    17:06
    I mean does it work better say on Android 5 than 4.2, or does it get updated with other android services
  18. zakim-robot
    17:45
    [Cameron Cundiff, a11y] Hi friends! Anyone have example apps demoing AngularJS accessibility?
  19. zakim-robot
    17:45
    [Cameron Cundiff, a11y] @dylanb: I’m already looking at https://dylanb.github.io/todomvc/index.html#/
  20. zakim-robot
    17:45
    [Cameron Cundiff, a11y] thank you for creating that :simple_smile:
  21. zakim-robot
    17:46
    [Cameron Cundiff, a11y] @marcysutton: have y’all created any demo apps for accessibility in AngularJS?
  22. zakim-robot
    17:47
    [Marcy Sutton, a11y] I made this demo for ngEurope, it’s pretty basic though http://marcysutton.github.io/angular-a11y/demos/scroll-ui/
  23. zakim-robot
    17:47
    [Marcy Sutton, a11y] otherwise I worked on Angular Material for a while - https://material.angularjs.org
  24. zakim-robot
    17:48
    [Cameron Cundiff, a11y] cool!
  25. zakim-robot
    17:48
    [Cameron Cundiff, a11y] thanks for the pointer
  26. zakim-robot
    17:48
    [Cameron Cundiff, a11y] are the controls in the Angular Material in good shape accessibility-wise?
  27. zakim-robot
    17:49
    [Marcy Sutton, a11y] I hope so! I know it has some color contrast issues especially for buttons, and the select has issues..but hopefully the majority of it is still accessible
  28. zakim-robot
    17:49
    [Cameron Cundiff, a11y] awesome!
  29. zakim-robot
    17:50
    [Marcy Sutton, a11y] i still work on it a bit, but it’s a very part-time thing
  30. zakim-robot
    17:50
    [Cameron Cundiff, a11y] I’m going to host a workshop on accessible web dev and having examples is great
  31. zakim-robot
    17:50
    [Cameron Cundiff, a11y] single page/javascript especially
  32. zakim-robot
    17:51
    [Marcy Sutton, a11y] sweet!
  33. deborahgu
    17:52
    Yay!
  34. zakim-robot
    17:52
    [Marcy Sutton, a11y] I did some work on http://distiller.com to make it somewhat accessible, a lot of it is rendered client-side
  35. zakim-robot
    17:52
    [Marcy Sutton, a11y] ordering whiskey for delivery from a screen reader = highlight of my career
  36. zakim-robot
    17:52
    [Cameron Cundiff, a11y] haha
  37. zakim-robot
    17:52
    [Cameron Cundiff, a11y] perfect!
  38. deborahgu
    17:53
    Accessible single page is I feel the biggest problem right now, because single-page is the hip thing and the overlap between people who write accessible JS and people who write single page apps is slim
  39. zakim-robot
    17:53
    [Marcy Sutton, a11y] relevant: http://www.smashingmagazine.com/2015/05/client-rendered-accessibility/
  40. deborahgu
    17:53
    and there's a lot of misunderstanding, ie "role=application and keyboard shortcuts makes it accessible, right?"
  41. zakim-robot
    17:53
    [Cameron Cundiff, a11y] @deborahgu precisely why I want to focus on it
  42. deborahgu @deborahgu highfives
  43. zakim-robot
    17:54
    [Cameron Cundiff, a11y] :simple_smile:
  44. MichielBijl
    18:44
    @deborahgu wouldn't setting focus to the <body>suffice in a single page application
  45. MichielBijl
    18:45
    That is just a thought; I haven't experimented with this
  46. powrsurg
    20:58
    It's disappointing to get everything working well in NVDA, TalkBack, mostly correct in iOS' VoiceOver (the thing I mentioned earlier being the minor issue) ... and then finding an issue in ChromeVox that is really non-starter for letting it through
  47. zakim-robot
    20:59
    [Alice Boxhall, a11y] @powrsurg Please feel free to bug me about ChromeVox bugs - I can pass them on to the team
  48. powrsurg
    21:03
    I've got a unorderd list that where the list items just have a radio button that is visually hidden and then the label that uses the content attribute on "label::before" to add an image based on the state (using content instead of a background image to make it work in windows high contrast mode). The label also has text. It just reads "List with four items. List item image."
  49. powrsurg
    21:03
    I just discovered it so I haven't created a test URL yet as an example ...
  50. zakim-robot
    21:06
    [Alice Boxhall, a11y] So is all the text in the content attribute?
  51. zakim-robot
    21:06
    [Alice Boxhall, a11y] Or is there text in "regular" DOM as well?
  52. powrsurg
    21:09
    the test is inside the <label>
  53. powrsurg
    21:10
    I just wrote up a codepen for it and codepen is under heavy load ....
  54. zakim-robot
    21:18
    [Alice Boxhall, a11y] :disappointed:
  55. powrsurg
    21:18
    ... and of course it works in the pen
  56. zakim-robot
    21:22
    [Alice Boxhall, a11y] Of course :disappointed:
  57. MichielBijl
    21:25
    @powrsurg that is such a weird feeling
  58. MichielBijl
    21:25
    “Okay I just tested the exact same thing, why, how, what?!”
  59. powrsurg
    21:28
    yeah, I hate creating "simple" test cases ... they always work in those situations
  60. powrsurg
    21:29
    http://codepen.io/powrsurg/pen/ojoxaB is the pen I put together that works here but not in my example ... maybe because the thing is within an iframe ...
  61. powrsurg
    21:32
    great, I have chromevox on and the magnifier and muted
  62. powrsurg
    21:32
    and all my windows are closed
  63. powrsurg
    21:33
    ... got too focus on the touch screen and forgot I could use the trackpad
  64. powrsurg
    21:34
    that's it, it's friday and I was supposed to be done a half hour ago. I think this is the universe telling me to quit
  65. zakim-robot
    21:36
    [Alice Boxhall, a11y] Haha
  66. zakim-robot
    21:36
    [Alice Boxhall, a11y] those irreproducible bugs will still be there on Monday!
  67. MichielBijl
    22:11
    @powrsurg just do http://codepen.io/powrsurg/debug/ojoxaB no iframe ;)