Archive index

A11y Slackers Gitter Channel Archive 15th of February 2016

What fresh hell is THIS now? - Patrick Lauke
  1. simevidas
    Feb 15 02:40
    Quick question: I have two sets of controls that occupy the same space on my website (only one of which is visible at any point in time); the first set is visible by default, and the second set can be activated after which it is displayed on top of the first set via CSS positioning. Both sets are siblings in the DOM. What would be the best approach to dynamically remove the "passive" set from the TAB sequence? (Only the visible, active set of controls should be tabbable.)
  2. jnurthen
    Feb 15 02:51
    Why don't you display:none the region which is not visible?
  3. simevidas
    Feb 15 02:56
    @jnurthen Ah, I see. I was using opacity: 0 on the 2nd set, because I'm fading it in on top of the 1st set. I will add display: none to the mix. Thanks!
  4. stevefaulkner
    Feb 15 07:25
    @MichielBijl ;-)
  5. MichielBijl
    Feb 15 07:25
    =P
  6. MichielBijl
    Feb 15 07:31
    It occurred to me that Rich is holding that chat bubble with his middle finger out, so it had to be done.
  7. jkva
    Feb 15 07:48
    Hoo boy, that's a long flight
  8. jkva
    Feb 15 07:48
    http://www.webdirections.org/respond16/
  9. MichielBijl
    Feb 15 08:04
    I think you can catch most of those at some European conferences ;)
  10. jkva
    Feb 15 08:04
    That sounds better logistically :P
  11. stevefaulkner
    Feb 15 08:17
    Role attribute obsolete in form or nav tags http://stackoverflow.com/questions/35397871/role-attribute-obsolete-in-form-or-nav-tags
  12. powrsurg
    Feb 15 14:51
    What about the progress tag? I'm about to start working on file upload progress bar and wasn't sure if I'd need to duplicate the attributes on the element
  13. stevefaulkner
    Feb 15 15:10
    @powrsurg support details at http://html5accessibility.com/
  14. powrsurg
    Feb 15 15:11
    I should have known that ... thanks
  15. jonathantneal
    Feb 15 20:48
    Poor Edge (or Edge users?), @stevefaulkner!
  16. stevefaulkner
    Feb 15 20:55
    @jonathantneal edge is not practically usable for AT users just yet
  17. jonathantneal
    Feb 15 20:57
    I imagine once it clicks in on the OS level, it’s probably great. Have they hinted anything about their plans?
  18. MichielBijl
    Feb 15 21:02
    Accessibility is second on their plan list for 2016 :)
  19. MichielBijl
    Feb 15 21:02
    s/plan/action/
  20. MichielBijl
    Feb 15 21:02
    s/action/priority/
  21. jkva
    Feb 15 21:02
    Naturally. Why start out by making something that works for people
  22. MichielBijl
    Feb 15 21:03
    https://blogs.windows.com/msedgedev/2016/02/03/2016-platform-priorities/#accessibility?platform=hootsuite
  23. MichielBijl
    Feb 15 21:04
    I think it was due to some accessibility framework change, but I'm really not the right person to talk about that.
  24. powrsurg
    Feb 15 21:53
    Has anyone ever had NVDA not read off the buttons you're tabbing to?
  25. powrsurg
    Feb 15 21:55
    and aViewer does nothing
  26. jnurthen
    Feb 15 22:16
    Sounds like they are hidden for some reason. Do you have aria-hidden on them (or on a parent region?)
  27. powrsurg
    Feb 15 22:22
    no. Nothing was seeing anything ...
  28. powrsurg
    Feb 15 22:22
    I think that's the point Firefox needs a restart ...
  29. jnurthen
    Feb 15 22:23
    yeah.... sometimes a buffer refresh fixes it but I can't recall how to do that in NVDA