Archive index

A11y Slackers Gitter Channel Archive 23rd of September 2015

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    01:08
    [Jesse Beach, a11y] @stevef: I'm looking through Chromium bugs and seeing similar aria-labelledby issues, but none like the one I found. I'm wondering if you've seen it before and logged it?
  2. zakim-robot
    01:09
    [Jesse Beach, a11y] http://codepen.io/jessebeach/pen/rOMNoW
  3. zakim-robot
    01:09
    [Jesse Beach, a11y] Using VoiceOver on Chrome, the title attribute value and the abbr tag content are used to calculate the accessible name for the element that gets used by aria-labelledby
  4. stevefaulkner
    10:10
    @jessebeach Hi, from my reading of the acc name calculation stuff, the calculated accessible name for the element should be "quilled pen". Unfortunately browser implementations are all over the shop...
  5. StommePoes @StommePoes waves
  6. stevefaulkner
    10:20
    :clap:
  7. StommePoes
    10:21
    for my next trick...
  8. rodneyrehm
    10:30
    anyone interested in a non-document-wide positive tabindex solution (i.e. “the ability to define the order of keyboard focus for a selected set of elements without affecting the global focus order”) want to have a look at https://jsbin.com/gumexa/10/edit?html,js,output and possibly comment on medialize/ally.js#40 - thx
  9. zakim-robot
    11:12
    [Katy Moe, a11y] Hey all. A dev I work with has come up with the idea of marking up forms as ordered lists (as well as the usual <form>, <fieldset>, etc). So when the screen reader got to the top of the form, it would say something like “list 5 items”, giving you an indication of the length of the form. Is this in any way semantic?
  10. stevefaulkner
    11:17
    @kmoe anecdotal reports from users suggests this is not helpful/unecessary , @LjWatson may have some thoughts.
  11. StommePoes
    11:18
    I avoid lists in my forms religiously though I could see the value in knowing at the beginning how many questions I have to answer (usability studies on registration/survey/checkout forms have shown people like to know how far they have to go and how close they are to the end)
  12. StommePoes
    11:18
    But I still don't list my forms :P
  13. StommePoes
    11:20
    I have seen, usually on questionaires and school tests, a short statement before the form like "there are 34 questions"
  14. zakim-robot
    11:33
    [Katy Moe, a11y] Yeah, that makes sense @StommePoes, just keep it simple
  15. zakim-robot
    18:21
    [Jesse Beach, a11y] @stevef, Ok, that's what I thought as well. I'll log a bug with Chromium. Just need to check on Windows with JAWS and see if the behavior is endemic.
  16. zakim-robot
    19:18
    [mkattut, a11y] Hey has anyone played with Adobe Presenter 11 to see how accessible it is?
    I found http://blogs.adobe.com/presenter/2015/01/accessibilty-in-presenter.html#more-6434
    and https://helpx.adobe.com/presenter/using/accessibility-508-compliance.html
    but what I really want to know is whether or not a screen reader could access the presentation slides in this new version. (I also wouldn't mind any other assessments of Presenter 11 that you might have)
  17. zakim-robot
    20:07
    [marcoz, a11y] Hi all. Am here now too, I think. Still a lot confused about this Slack thing, using it on my iPad, but getting there. :)
  18. zakim-robot
    20:09
    [Alice Boxhall, a11y] OMG Hi @marcoz!
  19. zakim-robot
    20:10
    [marcoz, a11y] Hi @alice ! :)
  20. zakim-robot
    20:14
    [dylanb, a11y] Wilkommen @marcoz
  21. zakim-robot
    20:16
    [marcoz, a11y] Thanks @dylanb ! :)
  22. zakim-robot
    20:16
    [marcoz, a11y] But since it's late in Germany, now going to bed. See you around, everyone!
  23. aardrian
    20:35
    Does anybody have examples (ideally off the top of your heads) of React-driven sites that are either good or poor in terms of accessibility?
  24. zakim-robot
    21:07
    [Jesse Beach, a11y] @stevef, that Chromium issue, if you're interested in tracking: https://code.google.com/p/chromium/issues/detail?id=535300
  25. zakim-robot
    21:07
    [Jesse Beach, a11y] @alice: ^
  26. stevefaulkner
    21:15
    @jessebeach, thanks I track all chrome acc bugs :-)
  27. zakim-robot
    21:18
    [Alice Boxhall, a11y] @jessebeach: Thanks for the ping, I'll be able to debug better when I'm at my laptop which has in-progress code for showing acc name computation steps in devtools
  28. zakim-robot
    21:18
    [Alice Boxhall, a11y] (the above being a situation I'm very cross with myself about, but nm, soon to be remedied)
  29. stevefaulkner
    21:21
    @marcoz HEY!
  30. zakim-robot
    21:21
    [Jesse Beach, a11y] @aardrian, check out https://www.messenger.com/ with the React Chrome Extension: https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en
  31. zakim-robot
    21:22
    [Jesse Beach, a11y] My colleague, Matt King, is actively working with their team to weave ARIA into the app
  32. zakim-robot
    21:24
    [Jesse Beach, a11y] Most of the work I do at FB involves React and accessibility
  33. stevefaulkner
    21:25
    that messenger site is suoer crap acc wise
    :-(
  34. aardrian
    21:32
    @Jesse Thanks. @stevefaulkner Not in front of good tools right now. I'll have to take your word for it.
  35. garcialo
    21:34
    @aardrian http://wave.webaim.org/report#/messenger.com
  36. aardrian
    21:35
    @garcialo Ooh, forgot about that. Thanks!
  37. garcialo
    21:35
    anytime =)
  38. garcialo
    21:36
    I wonder how confusing things would be if Google Wave had actually taken off.
  39. stevefaulkner
    21:37
    airwave?
  40. garcialo
    21:38
    airwave??
  41. stevefaulkner
    21:38
    "Wave had actually taken off"
  42. garcialo
    21:39
    ah, I think I kind of understand what you're saying
  43. garcialo
    21:39
    perhaps I'm just sleepy
  44. stevefaulkner
    21:40
    @garcialo I am making asinine word associations
  45. garcialo
    21:42
    ah, good
  46. garcialo
    21:42
    that's what I thought you were doing =p
  47. zakim-robot
    21:42
    [Alice Boxhall, a11y] @garcialo presumably if it had taken off, it would have been less confusing
  48. garcialo
    21:43
    Yeah probably. I just meant how confusing it would be telling non-a11y people to use WAVE and them thinking of Wave.
  49. stevefaulkner
    21:44
    @garcialo as you were, in your somniferous state, so you shall continue
  50. garcialo
    21:44
    That's pretty deep
  51. stevefaulkner
    21:45
    nn
  52. zakim-robot
    21:45
    [Alice Boxhall, a11y] @garcialo: Oh, right. I was confused.
  53. garcialo
    21:46
    I wonder how less confusing this conversation would have been if Google Wave had taken off.
  54. aardrian
    21:46
    waves
  55. garcialo @garcialo falls over.
  56. zakim-robot
    21:47
    [Justin Stockton, a11y] stands up. throws his hands over his head. sits back down...
  57. garcialo @garcialo hugs Jusin
  58. garcialo
    21:48
    *Justin
  59. zakim-robot
    21:48
    [Justin Stockton, a11y] :smile:
  60. aardrian
    21:48
    Also stands and throws his hands, then sits
  61. aardrian
    21:48
    Slowest wave ever.
  62. garcialo
    21:49
    Sorry @aardrian, I don't know how soft you are.
  63. garcialo
    21:49
    ...also, don't know you that well yet
  64. aardrian
    21:50
    I'm as soft as a meat popsicle can be while sucking in his gut all day.
  65. stevefaulkner
    21:54
    The web is so chock full of absurdities it's the mundanities that become alluring
  66. zakim-robot
    21:58
    [Justin Stockton, a11y] mundanities sounds like the name of a boring cookie
  67. zakim-robot
    21:58
    [Marcy Sutton, a11y] I finally had to turn Twitter off today. too angry.
  68. zakim-robot
    21:58
    [Marcy Sutton, a11y] (speaking of absurdities)
  69. zakim-robot
    22:10
    [Alice Boxhall, a11y] @marcysutton: :disappointed:
  70. zakim-robot
    22:27
    [Jesse Beach, a11y] @stevef, I don't disagree, but it's much better than it was 2 months ago and getting better each day.