Archive index

A11y Slackers Gitter Channel Archive 11th of November 2015

What fresh hell is THIS now? - Patrick Lauke
  1. stevefaulkner
    11:00
    slackers...
  2. zakim-robot
    11:16
    [callumacrae] hello!
  3. MichielBijl @MichielBijl waves at Steve
  4. MichielBijl @MichielBijl waves at Callum
  5. StommePoes @StommePoes waves somewhat wildly at nobody in particular. I'm in good health, don't worry.
  6. stevefaulkner
    12:27
    @alice closed the fieldset/legend bug after James Craig provided info (and i updated spec), if its not enough ping me :-)
  7. StommePoes
    15:19
    So there are some ideas for making icons available to Windows High Contrast. Are there ideas for making SVGs switch their colours for WHC?
  8. StommePoes
    15:20
    Otherwise it's looking like a lot of Javascript to manually manipulate attributes in the DOM.
  9. zakim-robot
    15:25
    [alice] @stevefaulkner James' response seems to suggest that they expose the Legend as description rather than name?
  10. stevefaulkner
    15:27
    @alice yeah it gets exposed as AXDescription, but AX mappings are funky
  11. stevefaulkner
    15:28
    @alice will do some testing to see how it is affected by aria-label etc
  12. zakim-robot
    15:29
    [alice] @stevefaulkner Thanks!
  13. zakim-robot
    15:29
    [alice] I guess - does it get exposed as name as well?
  14. zakim-robot
    15:29
    [alice] I can easily check on Mac..
  15. stevefaulkner
    15:46
    @alice so using this test page http://codepen.io/stevef/pen/VvVVvz latest safari/mac
    legend only = AXDescription
    aria-label+legend = AXDescription from label, legend dropped
    aria-label+legend used as describedby = AXDescription from label, AXHelp from legend
  16. stevefaulkner
    15:46
    @alice so AXDescription in this case = accname
  17. zakim-robot
    16:05
    [alice] @stevefaulkner I see, thanks!
  18. zakim-robot
    16:05
    [alice] Is there some advice somewhere to expose the accname as AXDescription on mac?
  19. zakim-robot
    16:05
    [alice] (er, for fieldset only, I mean)
  20. stevefaulkner
    16:29
    @alice not exactly, http://w3c.github.io/aria/html-aam/html-aam.html#el-fieldset needs making clearer, suggestions welcome
  21. stevefaulkner
    16:32
    @alice WIP...
  22. MichielBijl
    16:51
    Does someone here work at SnappCarr?
  23. MichielBijl
    16:51
    Or SnappCar rather.
  24. MichielBijl
    16:51
    Thought I heard something like that.
  25. zakim-robot
    17:04
    [jamesn] @car: yes exactly that. Would really help not just for web components.
  26. zakim-robot
    17:07
    [car] @jamesn: for now, we just have to do what we can. :)
  27. zakim-robot
    17:07
    [jamesn] @car:
  28. zakim-robot
    17:07
    [artistic_abode] Does anyone else have a hard time using the 3 finger swipe that is required to scroll on iOS with VoiceOver? I get so frustrated, it's nearly impossible for me to get 3 fingers to touch the screen at once and swipe. Any advice?
  29. zakim-robot
    17:07
    [jamesn] @car: Yep
  30. zakim-robot
    17:09
    [car] @artistic_abode: maybe (not sure) if you orient the screen landscape, it might be easier?
  31. zakim-robot
    17:13
    [artistic_abode] It is a little easier that way. Still more difficult than TalkBack on Android that only requires 2 fingers though. It would be awesome if you could change the gesture. 3 fingers is a lot to ask for, what if you were missing an index finger or something. the more different in length the fingers are the harder it is to get them all on the screen at the same time.
  32. zakim-robot
    18:23
    [heidi] w3 says about <nav>: "When support for HTML5 improves there may be no need to continue to add the ARIA role="navigation”.” - are we there yet? or is <nav role=“navigation”> still advised?
  33. zakim-robot
    18:48
    [fstorr] @heidi: some versions of IE still need that. I’m sure there’s a browser support table somewhere online but I can’t find it at the moment.
  34. zakim-robot
    18:50
    [heidi] @fstorr http://caniuse.com/#feat=html5semantic
  35. garcialo
    18:50
    http://www.html5accessibility.com/
  36. zakim-robot
    18:51
    [heidi] which is right… :simple_smile:
  37. garcialo
    18:53
    @stevefaulkner updates the one I provided, so probably caniuse
  38. zakim-robot
    18:56
    [heidi] so role=“navigation” on a <nav> would only be useful for IE8...
  39. garcialo
    18:56
    Joking aside, my money would be on the site I provided. You should probably test the instances you're concerned with and see which is more accurate. If you notice @stevefaulkner's site is outdated, ping him and he'll change it.
  40. garcialo
    18:57
    and by "ping," I of course mean, create an issue on GitHub https://github.com/stevefaulkner/HTML5accessibility/issues
  41. zakim-robot
    18:57
    [heidi] thanks @garcialo
  42. garcialo
    18:59
    np
  43. MichielBijl
    19:53
    I came across <nav role="main"> today, now that is something you don't see everyday.
  44. zakim-robot
    19:54
    [marcysutton] haha weird
  45. MichielBijl
    20:06
    Something that wasn't funny was body:not(.wizard) [type="checkbox"]:not(:checked) { position: absolute; left: -9999px; }.
  46. MichielBijl
    20:06
    insert rage face here
  47. MichielBijl
    20:07
    Luckily for me, I'm in charge of the refactor of the whole project :D
  48. MichielBijl
    20:07
    Add #a11y to all the things!
  49. zakim-robot
    20:43
    [jdan] all the things! we’re doing a pretty hefty rewrite of some of our more important pages at Khan Academy, so it’s a really good opportunity to build in accessibility from the start
  50. zakim-robot
    20:43
    [jdan] or, shall I say, prevent ourselves from making the page _in_accessible
  51. zakim-robot
    23:32
    [dpeter] are there any books anyone would recommend for learning web accessibility? in particular, i'd like to learn more advanced accessibility strategies beyond, like, a TODO app.
  52. zakim-robot
    23:32
    [dpeter] also are there any leaders in web accessibility -- individuals/companies? (this is probably subjective so feel free to just throw things out?)
  53. garcialo
    23:35
    I would check out http://rosenfeldmedia.com/books/a-web-for-everyone/ - not really targeted towards development, but there are plenty of resources online for that.
  54. garcialo
    23:38
    As far as leaders, it really depends on the topic. Everyone has their strengths and their weaknesses. For WCAG knowledge, that would likely be the domain of the a11y consulting companies WebAIM, The Paciello Group, SSB Bart, Simply Accessible, and Deque. Really though, it's probably just best to check Twitter for #a11y and see what's getting attention; the WebAIM Mailing list has a lot of good conversation from people of all levels.
  55. zakim-robot
    23:40
    [dpeter] thank you @garcialo!
  56. zakim-robot
    23:58
    [marcysutton] @dpeter: this one might be good for you: https://shop.smashingmagazine.com/products/apps-for-all