Archive index

A11y Slackers Gitter Channel Archive 31st of January 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jan 31 09:48
    [michiel] @garicalo: I think it’ll be hard to find an accessible carousel because people that care about accessibility / usability don’t use no fucking carousels…
  2. Srinivas Yedhuri
    @sri429
    Jan 31 10:57
    Q: Any good examples of an accessible color picker?
  3. Job van Achterberg
    @jkva
    Jan 31 11:03
    @sri429: not exactly a picker but https://toolness.github.io/accessible-color-matrix/ was posted yesterday
  4. Perhaps useful
  5. zakim-robot
    @zakim-robot
    Jan 31 13:06
    [karlgroves] Hey a11y folks. New post from me: Anatomy of an Accessibility Program https://www.linkedin.com/pulse/anatomy-accessibility-program-karl-groves
  6. zakim-robot
    @zakim-robot
    Jan 31 13:14
    [deconspray] @karlgroves <sweet/>
  7. Mallory
    @StommePoes
    Jan 31 14:18
    This colour palette has been sititing in our powerpoint docs for a while as well http://mkweb.bcgsc.ca/biovis2012/color-blindness-palette.png
  8. I have no idea what the dots vs the triange-arrow things means
  9. Mallory
    @StommePoes
    Jan 31 14:23
    "I never seen any official recomendations in terms of numbers here, just make sure it is easy to aim for different users" I've generally been telling people not to sit so hard on the "44px" number I keep seeing, for these reasons: https://www.smashingmagazine.com/2012/02/finger-friendly-design-ideal-mobile-touchscreen-target-sizes/
  10. And the message I take from that article isn't the pixels (I don't do anything in px, christ), but "it needs to stick out from around the fingers somewhere" and "I'd better not easily accidentally hit something next to it". Those two things are pretty decent guidelines, I think.
  11. zakim-robot
    @zakim-robot
    Jan 31 15:58
    [beth] @michiel a FED girl I work with created an accessible carousel. To a screen reader user, it looks like a list of items, but to sighted users, it’s a carousel that they can navigate through. It’s pretty neat, but may not be applicable to all carousel situations. Ours was a carousel of images with descriptive text below each, so the screen reader user only saw a list of descriptions.
  12. [conley] +1 ^^
  13. zakim-robot
    @zakim-robot
    Jan 31 16:25
    [quidkid] Can you use multiple h1 tags on a page and still have it be accessible? if so, how and otherwise why not? problem is this website is all one page but it has different slides which gives off an illusion of different pages
  14. [conley] I wouldn't recommend that from and SEO perpective
  15. [conley] use h2s
  16. zakim-robot
    @zakim-robot
    Jan 31 16:33
    [michiel] beth: that sounds really good, do you have a link to that?
  17. zakim-robot
    @zakim-robot
    Jan 31 16:40
    [beth] @michiel It hasn’t been rolled out yet, but I can send you the code if you'd like.
  18. [michiel] That’d be cool! If you could also send it to garcialo (as he was the one asking for it).
  19. [michiel] You can send it to hellothisisareallycoolaccessiblecarousel@michiel.moiety.me
  20. [beth] Seriously? Are you giving me a fake email address, like you would give a girl a fake phone number at a bar?
  21. [michiel] :D
  22. [michiel] No, that’ll actually get to me.
  23. [beth] ok, we’ll see. :smirk:
  24. zakim-robot
    @zakim-robot
    Jan 31 16:50
    [beth] @garcialo I sent an HTML sample to @michiel for what I think is an accessible carousel. If he says it’s indeed accessible, I will share with you also.
  25. [michiel] alt=mail from Beth to my obviously very fake e-mailaddress https://usercontent.irccloud-cdn.com/file/GRYOW7fh/Screen%20Shot%202017-01-31%20at%2016.52.17.png
  26. [michiel] And you were skeptical :P
  27. [michiel] waits for spam to start rolling in on that address.
  28. [beth] I already signed you up for at least 12 different porn sites. ;)
  29. zakim-robot
    @zakim-robot
    Jan 31 16:58
    [conley] Hopefully those sites are accessible
  30. [beth] @conley LOL
  31. zakim-robot
    @zakim-robot
    Jan 31 17:03
    [michiel] Doesn’t PornHub carry audio described videos?
  32. [michiel] thinks this conversation escalated rather quickly…
  33. [quidkid] @conley thank you!
  34. [conley] @quidkid np
  35. [conley] :hear_no_evil: @michiel
  36. [beth] Time to shut down that email address @michiel
  37. [quidkid] also i have a div that has those two indicator dots like you would see on a carousel that toggles that div from say the default slide to the next. how would i go about making this accessible? should it be arrow keys or enter to trigger that switch?
  38. zakim-robot
    @zakim-robot
    Jan 31 17:39
    [garcialo] @beth
  39. [garcialo] oops
  40. [garcialo] @beth While I see the merit in having it presented differently to make it accessible, I personally prefer presenting it the same way to non-sighted/sighted SR users and sighted non-SR users, but I’ll definitely check yours out
  41. [garcialo] here’s the one we put together. I’m quite fond of it (as fond as one can be about a filthy filthy carousel) https://ebay.gitbooks.io/mindpatterns/content/disclosure/carousel.html
  42. zakim-robot
    @zakim-robot
    Jan 31 17:44
    [conley] @garcialo awesome
  43. [garcialo] @conley Constructive feedback is always welcome, of course ;)
  44. [conley] For sure!
  45. powrsurg
    @powrsurg
    Jan 31 21:41
    I was recently handed a layout for a thumbnail gallery where clicking on the images would change/expand out a different block of text that appears over it. Would it be too far fetched for me to consider it a tab panel?
  46. zakim-robot
    @zakim-robot
    Jan 31 23:11
    [beth] Can someone tell me if there’s a correct semantic order for client-side error messages for input textfields? I am thinking that if the user enters incorrect information, we return an error and place focus on that error. Then if the user moved forward they would be placed inside the field that contains the error. Is it incorrect to have the error after the field, so the user has to navigate backwards to make the correction?
  47. [cordelia] Could you put focus on the error input field itself, and use aria-describedby to associate the error text with the input text field?
  48. zakim-robot
    @zakim-robot
    Jan 31 23:16
    [cordelia] I don’t think it matters too much if the error text is immediately before vs. immediatley after the field, as long as they are associated with one another in the code.
  49. zakim-robot
    @zakim-robot
    Jan 31 23:26
    [michiel] You could also use: https://www.w3.org/TR/wai-aria-1.1/#aria-errormessage :)
  50. [michiel] Well, in the future :P
  51. [michiel] Not too sure about current support for that.