Archive index

A11y Slackers Gitter Channel Archive 13th of July 2016

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jul 13 09:08
    [heydon] Tooltips are really difficult AUX to get right. I’m not sure they work in inline text at all, really. Steve did some which have an explicit “click to open / read” function using button semantics: https://www.paciellogroup.com/blog/2016/01/simple-standalone-toggletip-widget-pattern/
  2. zakim-robot
    @zakim-robot
    Jul 13 11:20
    [michiel] Whoop, got my ticket to ffconf in Brighton November 11th =D
  3. Job van Achterberg
    @jkva
    Jul 13 11:27
    @michiel you're going? I was considering it
  4. Not sure how good it is
  5. Ah I forget, you will live close by then
  6. zakim-robot
    @zakim-robot
    Jul 13 11:33
    [michiel] You cans tay over if you want :)
  7. [michiel] But yeah, for me it's only 50 quid away.
  8. [michiel] ianpouncey is going as well.
  9. [michiel] Heard it's really good :)
  10. Job van Achterberg
    @jkva
    Jul 13 11:35
    Only Thurs is still available
  11. @michiel I assume you're going Friday>
  12. zakim-robot
    @zakim-robot
    Jul 13 11:35
    [michiel] Hmm, Ian and I are going on Friday.
  13. Job van Achterberg
    @jkva
    Jul 13 11:35
    Should've acted faster :) oh well
  14. zakim-robot
    @zakim-robot
    Jul 13 11:36
    [michiel] Would've gotten two if I knew you wanted to come.
  15. Job van Achterberg
    @jkva
    Jul 13 11:36
    Don't worry about it, already have Fronteers in Oct
  16. zakim-robot
    @zakim-robot
    Jul 13 11:37
    [michiel] Do you need an intervention for your conference attendance?
  17. [michiel] Intervention Conf.
  18. Job van Achterberg
    @jkva
    Jul 13 11:40
    I'll make my own! With drinks, and talk!
  19. So the colors...associate with the days...
  20. zakim-robot
    @zakim-robot
    Jul 13 11:45
    [michiel] Such contrast. Much colours.
  21. Job van Achterberg
    @jkva
    Jul 13 11:46
    The "Exchange" to the right of "Oct 7" is broken
  22. {p.id} :P
  23. zakim-robot
    @zakim-robot
    Jul 13 11:52
    [michiel] Tenon found a 108 issues
  24. Job van Achterberg
    @jkva
    Jul 13 11:52
    Psh, Tenon
  25. zakim-robot
    @zakim-robot
    Jul 13 11:53
    [michiel] aXe found 9 violations…
  26. [michiel] Chrome Accessibility Audit gave 3 different warnings.
  27. [michiel] Of which one contains 96 warnings for not having enough contrast.
  28. Job van Achterberg
    @jkva
    Jul 13 11:57
    Hmm, if only the TPG color contrast analyser also showed rgba
  29. Too bad I don't speak Swift
  30. Omg it's an option
  31. <3
  32. Well, RBG. But good enough =)
  33. *RGB
  34. zakim-robot
    @zakim-robot
    Jul 13 12:00
    [michiel] I know that Céd is working on bringing in different colour notations :)
  35. Job van Achterberg
    @jkva
    Jul 13 12:00
    ++
  36. [jv] do they assume people won’t read it or will use magnifying glass?
  37. [michiel] It's for the environment, less paper used.
  38. [michiel] I can only assume :P
  39. zakim-robot
    @zakim-robot
    Jul 13 13:28
    [kate] Doesn't everyone just stick it in the box the device came in, never to see the light of day again?
  40. powrsurg
    @powrsurg
    Jul 13 14:12
    people take it out of the box?
  41. also, what are people's thoughts on Facebook's mobile app making the post-writing screen display in one font size and then lowers the font size when you start to wrap for the first time?
  42. dynamic font-size reduction
  43. zakim-robot
    @zakim-robot
    Jul 13 14:32
  44. zakim-robot
    @zakim-robot
    Jul 13 14:57
    [michiel] jv, might want to add an alt text ;)
  45. zakim-robot
    @zakim-robot
    Jul 13 15:04
    [bkardell] @heydon: thanks for the link
  46. Mark Sadecki
    @cptvitamin
    Jul 13 15:24
    anyone have any guidance on how to handle web based code editors and the keyboard trap they create (TAB inserts a TAB, and does not move you beyond the editor.) Any best practices on how to intuitively create a modifer that allows the keboard user to exit the editor? Was thinking about ESC to move focus beyond the editor. SHIFT+TAB should not be affected since there really isn’t a use case for that in the editor itself.
  47. zakim-robot
    @zakim-robot
    Jul 13 15:31
    [jv] @michiel: on twitter?
  48. zakim-robot
    @zakim-robot
    Jul 13 16:16
    [michiel] jv: you posted a link to an image here; some users don't see that.
  49. zakim-robot
    @zakim-robot
    Jul 13 16:36
    [marcysutton] The Chrome accessibility inspector is in stable. I wrote up how to enable it: https://gist.github.com/marcysutton/0a42f815878c159517a55e6652e3b23a
  50. zakim-robot
    @zakim-robot
    Jul 13 17:00
    [jv] @michiel: but i added text too along with photo
  51. zakim-robot
    @zakim-robot
    Jul 13 17:46
    [jdan] @marcysutton thanks!
  52. [alexlande] nice, turning that on now
  53. [chriswhawkins] Thanks @marcysutton -- Does this replace the Accessibility Developer Tools extension, do you know? (Including the accessibility audit feature enabled by ADT extension)
  54. [chriswhawkins] http://chromelens.xyz/ is another extension I just started using, today. It has a pretty handy feature to trace tabindexing and export as an image (nice for reviews and stakeholders, etc)
  55. zakim-robot
    @zakim-robot
    Jul 13 17:53
    [marcysutton] it is different, the extension doesn’t have the same API access. The extension does provide the audit feature though
  56. [marcysutton] If you inspect the same node in both tabs you’ll see the extension doesn’t have as much accessibility information
  57. powrsurg
    @powrsurg
    Jul 13 20:42
    http://codepen.io/powrsurg/pen/BzmZJA Any idea why the focus goes into the "Link elsewhere" on blur? At that point the display block is lost on #footip
  58. This happens in Firefox and Chrome
  59. powrsurg
    @powrsurg
    Jul 13 21:24
    Actually with what I just updated it to I have no idea where the focus is going ...
  60. zakim-robot
    @zakim-robot
    Jul 13 21:46
    [marcysutton] It seems to be somewhere in between the “Link elsewhere” and the link following…..but not actually focusable because of the display:none
  61. [marcysutton] It quietly misses the focus but sets the sequential focus point
  62. [marcysutton] (like the one you get if you click somewhere on the screen)
  63. eagsalazar
    @eagsalazar
    Jul 13 22:54
    I've read people advise to prefer semantic markup to using aria-role where possible. How does that principle apply to things like <dialog> where some browsers don't support that tag? My assumption is that screen readers won't get the role if you don't also include aria-role="dialog" right? Is there some list of where that line is on a per-element basis? Or is it as simple as "all new html5 elements should also use aria-role"?
  64. zakim-robot
    @zakim-robot
    Jul 13 22:56
    [dalecruse] This site is a great resource: http://www.html5accessibility.com/
  65. eagsalazar
    @eagsalazar
    Jul 13 22:59
    Thanks, that is perfect!