Archive index

A11y Slackers Gitter Channel Archive 17th of July 2017

What fresh hell is THIS now? - Patrick Lauke
  1. LauraOU
    @LauraOU
    Jul 17 12:28
    @zakim-robot Also the hotspots aren't keyboard accessible, so a keyboard/screenreader user won't be able to get to them
  2. zakim-robot
    @zakim-robot
    Jul 17 13:51
    [skymaiden] hello :wave: I'm having trouble with aria menus and voiceover screen reader not being able to access submenus. Would it be better to ask for help here, in the aria-patterns room, or the focus-management room?
  3. [skymaiden] (i have a test case on codepen to explain in more detail)
  4. [skymaiden] it's also quite possible that it's a problem between my desk and my chair :p (not an experienced voiceover user)
  5. zakim-robot
    @zakim-robot
    Jul 17 14:04
    [dereklewis] @skymaiden, it'd be great if you'd share the pen
  6. [skymaiden] https://codepen.io/skymaiden/full/mwXoNZ/
  7. [skymaiden] submenus are accessible via keyboard and mouse, but I can't navigate to submenus with Voiceover & Chrome...
  8. [skymaiden] the codepen is a simplified version of my real project, which is being rolled out progressively over a couple of weeks (so I can't really point to the real project online yet)
  9. zakim-robot
    @zakim-robot
    Jul 17 14:12
    [dereklewis] It's working on Safari for you, correct?
  10. [skymaiden] nope I can't get it to work correctly anywhere actually (desktop or mobile)
  11. [skymaiden] Voiceover let's me go over and over the first level menu, so I removed the tabindexes to see if that helps but still nothing
  12. stacycarston
    @stacycarston
    Jul 17 15:00
    I can't check with VoiceOver, but if it helps at all I did take a look with NVDA / FF and it's working pretty well. There are a few small focus management things I'd change, though maybe that's just your simplified example.
  13. zakim-robot
    @zakim-robot
    Jul 17 15:03
    [skymaiden] thanks for checking with nvda/ff :) i'd be interested in the focus management feedback you have (looking into moving focus directly to first list item right now)
  14. stacycarston
    @stacycarston
    Jul 17 15:26
    • When the menu is closed, the menu button should get focus
    • When you leave a submenu, it would be nice to move focus to the submenu parent, instead of the close button / first option
    • I like your plan to move focus to the first menu item on open (instead of close button)
  15. zakim-robot
    @zakim-robot
    Jul 17 15:33
    [skymaiden] thanks for the feedback +1
  16. LauraOU
    @LauraOU
    Jul 17 15:55
    @zakim-robot I did look with IOS/voiceover and saw the problem you describe
  17. zakim-robot
    @zakim-robot
    Jul 17 16:08
    [garcialo] @dereklewis Doesn’t AMP do its own validation?
  18. [dereklewis] Yep, they have their own validator, but it's invalid HTML5 so the accessibility validators throw a bunch of errors for normal AMPHTML
  19. [garcialo] ah, gotcha
  20. [garcialo] sounds like AMP’s validator should add some accessibility stuff to their validator
  21. [garcialo] er…except phrased in a way that makes sense
  22. zakim-robot
    @zakim-robot
    Jul 17 16:15
    [dereklewis] Yeah, I didn't realize a11y was overlooked until I started running validators
  23. [dereklewis] It's not completely overlooked to be fair, they've put a great deal of effort into making their components have the proper aria attribs
  24. zakim-robot
    @zakim-robot
    Jul 17 16:47
    [garcialo] I haven’t looked at many of the components…mostly just the ones I know we use
  25. zakim-robot
    @zakim-robot
    Jul 17 17:28

    [george_zamfir]
    :keyboard: Improvements to keyboard accessibility in Slack :keyboard:

    Hi Everyone :wave:

    As some of you may have noticed, today we announced that keyboard navigation support is coming to Slack (https://twitter.com/SlackHQ/status/886994844958076928). It will become available in Slack over the coming days, but we wanted you to receive access first.

    *What is it & how does it work?\

    Navigating Slack from your keyboard is now easier — simply use the *up and down keys** to read through your message history. And tab key to move from one element to another, as you’d expect.

    Outside of supporting basic tab navigation, we’ve made it easy to quickly navigate commonly-used sections of Slack: the channel sidebar, channel header, message history, message input, and flexpane. Simply press *Control + `* to jump between these sections so you can quickly get to where you want.

    We encourage you to check out the full list of keyboard commands to see what works best for you: https://get.slack.help/hc/en-us/articles/115003340723

    *We’d love your feedback! <3*

    Our goal was to make Slack as easy to use via keyboard as it is with a mouse, and we hope that attention to detail shows. Let us know if we hit the mark, or if you see things that can be improved by either replying to this message or typing “/feedback” into any channel or DM.

    Thanks and happy tabbing!

    Sincerely,
    The accessibility team at Slack