Archive index

A11y Slackers Gitter Channel Archive 15th of August 2016

What fresh hell is THIS now? - Patrick Lauke
  1. Job van Achterberg
    @jkva
    Aug 15 08:23
    _>
  2. zakim-robot
    @zakim-robot
    Aug 15 12:51
    [michiel] Morning slackers!
  3. jkva @jkva looks at his watch
  4. Job van Achterberg
    @jkva
    Aug 15 12:54
    I didn't know Oxford was that far off ;)
  5. zakim-robot
    @zakim-robot
    Aug 15 12:54
    [michiel] Afternoon* slackers!
  6. Job van Achterberg
    @jkva
    Aug 15 12:54
    \o/
  7. Afternoon Michiel!
  8. zakim-robot
    @zakim-robot
    Aug 15 12:55
    [michiel] Sometimes I have to work with Billy so I'm on EST :P
  9. zakim-robot
    @zakim-robot
    Aug 15 13:12
    [stanislauzubovich] Morning, do someone have statistics on UK users with disabilities?
  10. [michiel] No one has reliable ones ;)
  11. [michiel] If we count people with glasses it's about 40-50%
  12. zakim-robot
    @zakim-robot
    Aug 15 13:18
    [michiel] The one I always use: whichever way you look at it, it's higher than the percentage of IE users.
  13. [stanislauzubovich] I know there is statistics on US people from 2010s or smth like this
  14. [michiel] I'll stop being unhelpful, but also can't be helpful with this one I'm afraid.
  15. zakim-robot
    @zakim-robot
    Aug 15 14:21
    [scottgemmell] Hello, a client wants the h1 on a page to be 12px (same as body copy and most other text). Any good reasons I can reject this would be useful.
  16. Job van Achterberg
    @jkva
    Aug 15 14:23
    @scottgemell: Because it'd make no visual sense because it does not distinguish the site heading from body copy? Semantically it's fine. Has the client motivated this requirement?
    • @scottgemmell ^
  18. zakim-robot
    @zakim-robot
    Aug 15 14:25
    [scottgemmell] Yes. I explained headings would not be distinguishable.
  19. Job van Achterberg
    @jkva
    Aug 15 14:26
    @scottgemmell: You could argue that it make the content hard to understand and visually unclear, which might make visitors frustrated and cause them to leave. But that's hard to back up without A/B testing.
  20. But as long as they're aware of the risks... as long as the content is readable and understandable, it's not a problem per se
  21. zakim-robot
    @zakim-robot
    Aug 15 14:27
    [scottgemmell] Bother. Thanks for feedback. I guess I will lose this one. :(
  22. OceanWolf
    @OceanWolf
    Aug 15 14:36
    Give the client what they want, you can show them what it looks like, give them an alternative, if they still want it, then fine, their fault for loosing visitors, so long as you get paid
  23. zakim-robot
    @zakim-robot
    Aug 15 16:42
    [simong] marcysutton: Are you still looking on running axe within Node? If you are, I’d be happy to help in any way I can. We’re currently running it in phantom, but it’s just too slow for what we want to do (There’s a 5second penalty on doing phantom.exit(0) -_-).
  24. [marcysutton] We do run it in node, there are some problems specific to JSDOM though
  25. zakim-robot
    @zakim-robot
    Aug 15 16:47
    [simong] oh ok
  26. [marcysutton] I guess a better way of putting it is we handle axe in Node, but it does require a rendered DOM to run checks against
  27. [simong] Are you running an older version? I’d be interested in hearing how you’re doing it currently as we’re looking to process a few million HTML files maybe
  28. [marcysutton] An older version of Node?
  29. [marcysutton] I'm in 4x
  30. [simong] No sorry, I misunderstood, I thought you were successfully using axe + jsdom and that it was working ok on an older version of axe
  31. [marcysutton] The newer version of axe handles window better than it used to, you still need an HTML Document context in some form
  32. [simong] ok, I’ll give HEAD a try
  33. [marcysutton] the latest public release has those fixes (2.0.5)
  34. [marcysutton] you would notice it right away if it choked on window
  35. zakim-robot
    @zakim-robot
    Aug 15 16:52
    [marcysutton] http://marcysutton.com/slides/carmen-sanfrancisco-cascadia/assets/player/KeynoteDHTMLPlayer.html#46
  36. [simong] Hmm ok. Do you think it’s feasible to get it to work with jsdom?
  37. [marcysutton] I just did a talk on part of this problem
  38. [marcysutton] The JSDOM problem I'm still looking into, it needs a bit more support for some reason
  39. [marcysutton] But I am definitely working on it =D
  40. [simong] Thanks! I’ll poke around a bit as well and report back if I get something working
  41. zakim-robot
    @zakim-robot
    Aug 15 17:19
    [simong] This gets me the violations that don’t rely on document.createRange: http://pastebin.com/rSX8GuR4
  42. zakim-robot
    @zakim-robot
    Aug 15 18:04
    [marcysutton] Yep this is because JSDOM and Cheerio are both partial implementations
  43. [marcysutton] I have filed a bug internally and will investigate our options
  44. [marcysutton] There are tradeoffs for that speed you need :)
  45. [simong] Supposedly, someone is working on the createRange method for jsdom (tmpvar/jsdom#317), so maybe soon ..
  46. [simong] Yeah for sure
  47. [marcysutton] sweet!
  48. [marcysutton] sees date of that issue was filed in 2011 :(
  49. [simong] The last comment was March 18 (2016) though!
  50. [marcysutton] That is an appallingly slow pace though. :snail:
  51. [marcysutton] Websites and apps have been built, launched and retired in that amount of time
  52. zakim-robot
    @zakim-robot
    Aug 15 18:10
    [marcysutton] Although the web standards track is slower for good reason, tooling needs to evolve quicker than that
  53. zakim-robot
    @zakim-robot
    Aug 15 18:19
    [scottohara] Does anyone have/have seen an example of a properly implemented carousel that doesn’t just have abysmal a11y support?
  54. [scottohara] The main one that I have heard before is the Slick slider, but I’ve seen some pretty bad implementations of that one too
  55. [marcysutton] I think @estelle was working on one
  56. [marcysutton] But I have a hard time recommending sliders... /shrug
  57. zakim-robot
    @zakim-robot
    Aug 15 18:42
    [scottohara] heh. i have no desire to recommend one. as i’m currently working on a site where i’m recommending to remove them. but i thought i’d see if there were better options, so if it has to be kept, i can at least compare to a carousel that isn’t a hot garbage fire on wheels
  58. [scottohara] :)
  59. zakim-robot
    @zakim-robot
    Aug 15 20:14
    [aarongustafson] Ok folks, test your mettle: https://a-k-apart.com/
  60. [aarongustafson] @scottohara: Have your tried https://github.com/filamentgroup/responsive-carousel
  61. Job van Achterberg
    @jkva
    Aug 15 20:15
    Wow, cool challenge @aarongustafson
  62. zakim-robot
    @zakim-robot
    Aug 15 20:31
    [scottohara] Oh thanks. I'll give that a look
  63. zakim-robot
    @zakim-robot
    Aug 15 21:27
    [estelle] I have a "merry-go-round" script. It looks like a carousel, and to the sighted user behaves like a carousel, but to the screen reader is an unordered list of options, fully accessible.
  64. [estelle] Example: http://estelle.github.io/merry-go-round/horse.html
  65. [estelle] http://estelle.github.io/merry-go-round/
  66. [estelle] Repo: https://github.com/estelle/merry-go-round
  67. [estelle] @marcysutton and @scottohara (forgot to mention you before answering you)
  68. [estelle] The reason it's called merry-go-round is because carousels are expected to work and fail in specific ways. This provides all options up front without requiring aria-live to update the AT that the screen has changed.
  69. [estelle] So it's calling it "carousel" was confusing to those testing it with screen readers
  70. zakim-robot
    @zakim-robot
    Aug 15 22:04
    [jiatyan] So, how do we submit a broken link report on an official WCAG page? eg. https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html <-- "Writing Better Web Page Titles" is broken.
  71. zakim-robot
    @zakim-robot
    Aug 15 22:14
    [michiel] jiatyan: GitHub would do :)
  72. [michiel] Also: http://www.w3.org/WAI/WCAG20/comments/
  73. zakim-robot
    @zakim-robot
    Aug 15 22:20
    [jiatyan] dank je @michiel
  74. Mallory
    @StommePoes
    Aug 15 22:44
    @stanislauzubovich UK https://www.gov.uk/government/publications/disability-facts-and-figures/disability-facts-and-figures
  75. UK http://www.citizensonline.org.uk/accessibilitytips/
  76. The first one has education levels, employment, heads of households, etc. Digested figures, not the base data. I got the base data of the US census and it's fun to poke through the ginourmous endless scrolling tables (per State) but not fun to find info in.
  77. The second one just has a lot of somewhat random statistics mixed in everywhere.
  78. gov.uk has some stats for them somewhere