Archive index

A11y Slackers Gitter Channel Archive 12th of December 2016

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Dec 12 01:45
    [indrekpaas] Hi everyone! I've updated WAI-ARIA roles, states and properties auto-completions to add support for Sublime Text 3 and ARIA 1.1 attributes: https://github.com/indrekpaas/sublime-wai-aria
  2. [indrekpaas] http://i.imgur.com/qeMuJT2.gif
  3. [indrekpaas] Until it gets merged into Package Control channel, you can install it manually:
    1. Package Control: Add Repository → https://github.com/indrekpaas/sublime-wai-aria
    2. Package Control: Install Package → Sublime WAI-ARIA
  4. [indrekpaas] Cheers!
  5. zakim-robot
    @zakim-robot
    Dec 12 06:26
    [stevebarnett] Hi, maru! :wave:
  6. [maru] @stevebarnett :) :)
  7. zakim-robot
    @zakim-robot
    Dec 12 17:23
    [beth] Does anyone know how to code an "a href" so that additional visually hidden descriptive text is read to NVDA & JAWS users after the link when the link receives focus on arrow (opposed to on tab)? Right now we’re using aria-decribed by for the additional text, but it only being read if the user tabs to the link… which is not a standard screen reader user interaction.
  8. Mallory
    @StommePoes
    Dec 12 17:46
    hidden text without aria stuff should get read out
  9. like <a href="foo"><span class="sr-only">I'm just pulled offscreen, I'm read when you arrow to me</span> visible link text too</a>
  10. zakim-robot
    @zakim-robot
    Dec 12 17:52
    [melsumner] @beth: I borrowed the sr-only class from Bootstrap, it works out okay
  11. [beth] @stevef I know aria is not reliable, I will try your suggestion. Thank you!
  12. zakim-robot
    @zakim-robot
    Dec 12 18:52
    [johnkmcnabb] @beth do you think it's important for that descriptive text to be read when using the down arrow? I mean, won't the screen reader user have the benefit of the context of surrounding info, pretty much like a sighted person would?
  13. zakim-robot
    @zakim-robot
    Dec 12 19:00
    [johnkmcnabb] I think I have some answers for my own question:
    1) the descriptive text might not be near the link (either position-wise on the screen for low vision users, or sequential-wise for blind users)
    2) the links might be in a table, so if a screen reader user were to list all links on the page, they might get: download statement, download statement, download statement...
    3) Offscreen text labels work with Dragon Naturally speaking , but ARIA labels don't
  14. zakim-robot
    @zakim-robot
    Dec 12 19:28
    [beth] @johnkmcnabb The screen reader user would not have the same info because the context of my comment is an icon that comes after a link that lets the user know they are leaving an accessible page and going to a page on a site that may or may not be accessible. The icon itself has a key at the bottom of the page that alerts sighted users as to what it means, but for non-sighted users, we want this information made available to them when the link is in focus so that they know before they select it that they might be dropped onto a non-accessible page.
  15. [beth] However as it stands, it’s not being read to JAWS or NVDA users who arrow to it. My understanding is that screen reader users do not typically navigate with the tab key, but with the arrow keys, so having it read only when tabbed to is not going to work.
  16. zakim-robot
    @zakim-robot
    Dec 12 19:58
    [johnkmcnabb] Yeah that makes sense!
  17. zakim-robot
    @zakim-robot
    Dec 12 22:08
    [cameron] https://a11ywins.tumblr.com/ :heart_eyes:
  18. [cameron] thanks Marcy, once again :)
  19. [cameron] what a great resource
  20. zakim-robot
    @zakim-robot
    Dec 12 22:18
    [marcysutton] you are welcome! I try to update it every so often