Archive index

A11y Slackers Gitter Channel Archive 8th of August 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Aug 08 13:34
    [quidkid] @ugi thank you so much!!
  2. [lisacan] For those working with SPAs, I published an article on accessible development practices: https://medium.com/@lisacan/building-accessible-single-page-apps-2ea3e4fbbc01
  3. zakim-robot
    @zakim-robot
    Aug 08 19:50
    [emplums] Has anyone dealt with this? https://web-a11y.slack.com/archives/C071U5Y3H/p1501548588930066
  4. [emplums] It means that for <select> in Chrome for something like a time input, VO Is only reading "5"
  5. [emplums] I'd want it to read "hours, 5"
  6. [emplums] otherwise there's totally no context when tabbing through a form with a bunch of <select>s in them (thinking face emoji)
  7. [emplums] Doesn't seem like a great experience
  8. [alexlande] I usually only test VO in Safari. The behavior is really inconsistent across other browsers
  9. [emplums] Yeah.. but don't enough people use VO with Chrome to want to build for that too?
  10. [alexlande] which is probably not super helpful, but I’ve never had any luck fixing VO bugs in Chrome
  11. [emplums] (joy/allthethings emoji)
  12. [emplums] I'm wondering if this would qualify as a bug & I should file with with the Chrome team
  13. zakim-robot
    @zakim-robot
    Aug 08 19:56
    [alexlande] Probably, couldn’t hurt. I don’t know if non-Safari browsers make an effort to be VO compatible. I’ve always thought not
  14. zakim-robot
    @zakim-robot
    Aug 08 20:10
    [marcysutton] Yes file or!
  15. [marcysutton] *it! Ugh autocorrect
  16. [marcysutton] If it hasn't already been filed that is...but I have trouble searching for Chromium issues like that. @robdodson or @alice might have some insight
  17. zakim-robot
    @zakim-robot
    Aug 08 20:42
    [backwardok] I was under the impression that VO is mainly to be used with safari, and that most VO users use safari?
  18. [backwardok] but also I’ve found that Chrome + VO is a pretty bad combination most of the time
  19. zakim-robot
    @zakim-robot
    Aug 08 20:52
    [marcysutton] Yep that's true about Safari. But if we can make Chrome play better with VO, we should!
  20. [shawn.henning] I believe Chrome is trying to fix that. I think someone in here is working on it. I am also hoping FireFox 57 will improve the constant "busy" state of FF when using it with VO.
  21. [garcialo] I think the largest population using Chrome + VO are developers for companies that test for accessibility :p
  22. zakim-robot
    @zakim-robot
    Aug 08 21:48
    [emplums] (thinking face emoji) I feel guilty ignoring it but.... (joy/allthethings emoji)
  23. [emplums] If no one actually uses it..
  24. [garcialo] file the ticket; don’t go out of your way if hacking in the support will be a lot of effort
  25. [garcialo] focus efforts on making more trafficked parts are accessible
  26. [garcialo] making sure more trafficked parts are accessible
  27. zakim-robot
    @zakim-robot
    Aug 08 22:01
    [emplums] Yeah I'm going to go ahead and file a ticket/see if there's already a ticket
  28. [emplums] Wait.. is this a Chrome bug or a VO bug?
  29. zakim-robot
    @zakim-robot
    Aug 08 22:06
    [garcialo] does it work with Safari + VO?
  30. zakim-robot
    @zakim-robot
    Aug 08 22:13
    [ugi] good point @garcialo. looks more like a VO bug to me, but might also be related to how Chrome exposes the accessibility tree. for some reason, VO focuses on the <option> element instead of the <select>, when using Tab to browse the document. You can VO+Shift+Up to focus back on the Select when that happens.
  31. zakim-robot
    @zakim-robot
    Aug 08 22:21
    [backwardok] I feel like I remember seeing somewhere on Apple pages where it mentioned VO working with Safari, but I can’t seem to find it
  32. [backwardok] I also don’t know that you’d get anyone at Apple to fix a VO + Chrome bug, but I guess there’s no harm in trying?
  33. zakim-robot
    @zakim-robot
    Aug 08 22:33
    [emplums] @garcialo @ugi It works on VO + Safari - it reads "<select label> + <option name>" but in Chrome it just reads "<option name>"
  34. [marcysutton] I'd say file it with Chromium then.
  35. [emplums] Ok! So something like, "expose select labels to screen readers"?
  36. [garcialo] @backwardok I remember seeing something similar at one point; I’ve also not been able to refind it
  37. [garcialo] well, I either read it or heard it somewhere, but have been able to find the source
  38. [marcysutton] It looks like Chrome does pick up an explicit label for the accessible name, but it isn't exposed in Voiceover.
  39. [garcialo] correction: haven’t been able to find the source
  40. [marcysutton] Muppets combobox in Chrome Developer Tools' accessibility tree inspector
  41. [marcysutton] that's for a native select.
  42. zakim-robot
    @zakim-robot
    Aug 08 22:40
    [emplums] ooh ok, so it's probably a VO thing?
  43. [marcysutton] probably? i'd still file it anyway.
  44. [emplums] ok! =D
  45. zakim-robot
    @zakim-robot
    Aug 08 22:46
    [alice] Yeah if anyone can make a reduced test case for the <select> thing in chrome + VO I can help file a bug
  46. [alice] Muppets combobox in Chrome Developer Tools' accessibility tree inspector
  47. [quidkid] should tabs and accordions have cursor: pointer;? I know technically buttons shouldn’t have pointer events but I’m having trouble trying to figure out when to use a button or a tag for a tab widget or accordion widget. but i’ve also come across how cursor:pointer is necessary for touch screen devices so i’m really confused
  48. [dpogue] cursor: pointer shouldn't affect any behavioural thing, except that some people don't think things are clickable unless the cursor changes (which by default it does not for button elements)
  49. [emplums] @alice I'll make you one :)
  50. [emplums] I've never filed a bug in Chrome before so I'd love the help!
  51. zakim-robot
    @zakim-robot
    Aug 08 22:54
    [emplums] @alice Is a codepen okay for a reduced test case? If so here's one that demonstrates the bug: https://codepen.io/eplummer26/pen/gxWOaq
  52. [emplums] Focusing on the select element in chrome just reads "Vanilla", focusing on it in Safari reads "Vanilla, flavors"
  53. [ghanek] Jamie Teh is leaving NV Access, to work at Mozilla. This is exciting news. Congrats!
    https://www.nvaccess.org/post/jamie-moving-on-from-nv-access/
  54. zakim-robot
    @zakim-robot
    Aug 08 23:02
    [alice] @emplums Yep, that works!
  55. [alice] Would you like me to file it for you and CC you?
  56. zakim-robot
    @zakim-robot
    Aug 08 23:15
    [alice] Seems like in chrome focus moves to the menu item, whereas in Safari it moves to the popup button
  57. zakim-robot
    @zakim-robot
    Aug 08 23:48
    [emplums] @alice that would be great! Thank you! My email is eplummer26@gmail.com