Archive index

A11y Slackers Gitter Channel Archive 25th of October 2016

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Oct 25 00:29
    [caesar] Question on the use of <abbr> and keyboard accessibility... use of <abbr> is a sufficient technique for WCAG 2.0 - 3.1.4 Abbreviations, but if it's not keyboard accessible does that mean it fails 2.1.1 Keyboard?
  2. zakim-robot
    @zakim-robot
    Oct 25 01:22
    [karlgroves] No. <abbr> is not an element that can gain focus and cannot be acted upon.
  3. zakim-robot
    @zakim-robot
    Oct 25 02:38
    [caesar] So if an organisation is aiming for AA only, then using an abbreviation without expanding it is a pass?
  4. zakim-robot
    @zakim-robot
    Oct 25 02:43
    [karlgroves] The fact that an <abbr> element shows the title element on hover is, in this case, inconsequential. Using the element to expand the definition is still an appropriate approach for 3.1.4
    https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H28
  5. [caesar] OK cool, but not required for AA...
  6. [karlgroves] Right
  7. zakim-robot
    @zakim-robot
    Oct 25 02:49
    [caesar] Thanks
  8. zakim-robot
    @zakim-robot
    Oct 25 07:56
    [dean] Morning all. Random question that’s been going on in my head…. If you had <button>cancel</button>, then on a screenreader it would announce “button cancel”… I’m curious though, what would be announced on a braille reader? would it spell out “button cancel” on the display, or does it do something different?
  9. Fiona Holder
    @FionaHolder
    Oct 25 08:31
    morning all
  10. Mallory
    @StommePoes
    Oct 25 10:33
    dean it should depend on the screen reader actually, and then possibly the braille display could add/remove something as well
  11. But the order of the words is SR-specific
  12. some say the control type first then the name. others go other way around
  13. On the Orca mailing list they've been discussing with Joanie about maybe making that configurable by user
  14. @dean ^
  15. zakim-robot
    @zakim-robot
    Oct 25 10:42
    [dean] Thanks Mallory! I wondered if it would say the control type, so good to know.
  16. Mallory
    @StommePoes
    Oct 25 10:49
    if it knows the role, it can say the type
  17. so <div onclick="foobar()">cancel</div> is just "cancel" (or even "clickable cancel" maybe) but <div role="button">cancel</div> should be button cancel or cancel button, as would of course an actual real button. Same for link, heading, into list (or list with x items), out of list/leaving list, etc
  18. What SRs say for all sorts of things can sometimes really vary. Also sometimes one SR will say something while others are completely silent on it.
  19. JAWS by default is pretty wordy, telling me things are draggable or instructions (which don't seem to work) for things with aria-controls on it or if someone puts a role of tab on something but they otherwise didn't mark up the tab panel correctly it'll say some weird things. NVDA and Orca are generally quieter by default.
  20. James Nurthen
    @jnurthen
    Oct 25 14:24
    @dean if you have jaws you can see what would be on a Braille display. There is a Braille display viewer in the jaws folder.
  21. zakim-robot
    @zakim-robot
    Oct 25 14:27
    [dean] ahhh neat James, I wasn’t aware of that.
  22. zakim-robot
    @zakim-robot
    Oct 25 15:52
    [lefthandev] VoiceOver also has an onscreen braille panel. It’ll display both braille and a plain-text version of the descriptions that are announced, so sighted users can follow along.
  23. James Nurthen
    @jnurthen
    Oct 25 16:26
    @lefthandev cool - I had never noticed that option before in VO
  24. zakim-robot
    @zakim-robot
    Oct 25 16:38
    [joe] Anyone have experience with the sr-only link at the top of the body that will skipping to main content?
  25. zakim-robot
    @zakim-robot
    Oct 25 17:10
    [garcialo] Anyone know of a tool like http://colorsafe.co/, but that is more accessible?
  26. [cordelia] http://jxnblk.com/colorable/demos/text/
  27. zakim-robot
    @zakim-robot
    Oct 25 17:17
    [garcialo] Cool, I’ll check it out :)
  28. zakim-robot
    @zakim-robot
    Oct 25 18:20

    [george_zamfir] Hi everyone :wave:

    We've launched a new feature to stop animations (emojis, gifs & giphys) exclusively to this team (web-a11y.slack.com) :slack:
    *:slack: New Slack feature to disable animations, now in beta for this team :slack:*

    We’ve been working on a feature to disable all animations, including emojis, gifs & giphys. If you’d like to try it out before the public launch we released it exclusively for everyone on this team. If you have any feedback we’d love to hear it <3

    *How do I disable animations?*
    On the web & desktop client you can toggle animations in: Preferences - Advanced - Other Options - Allow animated images & emoji. However, you may need to restart the desktop client first.

    *How does it work?*
    Rather than displaying an animated image we capture a still frame and display that instead. The preference works for all teams at once however, it does not sync across platforms / devices at this point. Baby steps :baby:

    *Important notes:*

    • Please keep the conversation about this feature to this team while we’re getting ready for primetime :movie_camera:
    • We launched silently on mobile already but if you have feedback on that as well we’d love to hear it <3

    Thank you for all your feedback & support :clap:

    p.s. How can you tell it’s working? Deadpool above shouldn’t be animated =)

  29. zakim-robot
    @zakim-robot
    Oct 25 18:50
    [marcysutton] Whoa! Awesome!!
  30. [lowellreade] "*Important notes:*
    • Please keep the conversation about this feature to this team while we’re getting ready for primetime :movie_camera:
    • We launched silently on mobile already but if you have feedback on that as well we’d love to hear it <3"
  31. zakim-robot
    @zakim-robot
    Oct 25 19:52
    [dean] ooooh sounds great…. I don’t see Deadpool though?
  32. zakim-robot
    @zakim-robot
    Oct 25 20:01
    [doeg] @dean the photo is in the #slack-a11y-feedback room :)
  33. [dean] aha thanks @doeg
  34. zakim-robot
    @zakim-robot
    Oct 25 20:34
    [elisaf] Hey all, another question. If you provide a link to download a PDF file, is it required to post a link to the reader download page?
  35. zakim-robot
    @zakim-robot
    Oct 25 20:51
    [george_zamfir] /giphy deadpool
    deadpool
  36. [george_zamfir] (I hope it’s nothing inappropriate. My animations are off! :D)
  37. zakim-robot
    @zakim-robot
    Oct 25 21:42
    [garcialo] @elisaf It’s required by Section 508, but not by WCAG.
  38. zakim-robot
    @zakim-robot
    Oct 25 22:02
    [mattmay] @elisaf: Two opinions. 1) I'd argue that a link is no longer needed for basic (no forms, etc) PDFs to pass 1194.22(m), since all shipping major browsers support PDF natively now.
  39. [mattmay] 2) If, OTOH, a tagged PDF is to be read by an AT user, unfortunately Reader is still the only mainstream app that can do that. So an AT user would need a pointer.