Archive index

A11y Slackers Gitter Channel Archive 26th of July 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jul 26 03:02
    [nschonni] TBH, I don't know the accessibility story by "yeah"? @tink https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
  2. [mattmay] I know the story. I'll be standing over Flash's corpse with a silver dagger because of it.
  3. zakim-robot
    @zakim-robot
    Jul 26 03:37
    [nschonni] I had to check about AIR, because that's the second coming of Flash. We still need it for Balsamiq :p
  4. zakim-robot
    @zakim-robot
    Jul 26 18:35
    [virtualalex] Does windows have a “voice over” built in?
  5. [virtualalex] or do win users need to download something?
  6. [scottohara] there’s windows narrator: https://support.microsoft.com/en-us/help/22798/windows-10-narrator-get-started
  7. [scottohara] but there’s also screen readers like JAWS and NVDA, to name a couple
  8. [virtualalex] is JAWS free?
  9. [scottohara] it has a free trial
  10. [virtualalex] ok NVDA is free I know
  11. [virtualalex] thank you for your help
  12. zakim-robot
    @zakim-robot
    Jul 26 18:43
    [virtualalex] Does Android have a voice over utility also?
  13. [tyronem] It’s called TalkBack, and it’s built-in.
  14. [virtualalex] great thanks
  15. [virtualalex] I am writing a sort of guide…
  16. zakim-robot
    @zakim-robot
    Jul 26 19:14
    [quidkid] I’m having trouble deciding whether to use aria-expanded or aria-pressed for a a hamburger menu button that leads to a side nav. Also what is the difference between role=“menu” and role=“navigation” and when should I use which?
  17. zakim-robot
    @zakim-robot
    Jul 26 19:30
    [ugi] @quidkid I’d use aria-expanded. aria-pressed is more appropriate for widgets like a toggle switch (i.e a ‘Mute’ button on a media player). role=“navigation” is a landmark role, role=“menu” is a widget role. Use menu role on widgets that look like menu bars found in desktop applications. Use navigation role where you can use <nav> tag, for grouping links.
  18. [quidkid] @ugi
  19. [quidkid] thank you!
  20. [quidkid] also for the <nav> should i stick my menu button inside?
  21. [elliottregan] I wouldn’t. I think that this pattern would be relevant here: http://heydonworks.com/practical_aria_examples/#submenus
  22. [elliottregan] use aria-haspopup="true" for the menu toggle.
  23. zakim-robot
    @zakim-robot
    Jul 26 19:35
    [ugi] probably not the button itself, but the contents of the hamburger menu may be placed inside a nav.
  24. [scottohara] the button should be placed inside of the navigation

  25. [scottohara] here’s a piece i wrote about that: http://www.scottohara.me/blog/2016/08/10/not-really-about-the-button.html

    but to summarize, if your nav landmark is hidden behind a hamburger menu (on large or small screen) then it will be invisible to assistive technology.

    if you keep the nav landmark unhidden, and put the menu button within it / hide a sub-container of the navigation, then the nav landmark will stay discoverable to users, even if a nav is hidden

  26. zakim-robot
    @zakim-robot
    Jul 26 19:48
    [ugi] ^ +1