Archive index

A11y Slackers Gitter Channel Archive 19th of January 2017

What fresh hell is THIS now? - Patrick Lauke
  1. Srinivas Yedhuri
    @sri429
    Jan 19 06:55
    Hi All, Any good example for an accessible lookup control
  2. zakim-robot
    @zakim-robot
    Jan 19 10:40
    [jbuller] Does anyone here have knowledge of how accessible Oracle Fusion (HR) systems are in the real world not just their VPATs?
  3. zakim-robot
    @zakim-robot
    Jan 19 12:14
    [karlgroves] @jbuller Is there a date on the VPAT?
  4. zakim-robot
    @zakim-robot
    Jan 19 12:38
    [jbuller] @karlgroves This one is 2015 http://www.oracle.com/us/corporate/accessibility/templates/t2-4921.html
  5. zakim-robot
    @zakim-robot
    Jan 19 12:45

    [karlgroves] Several years ago, Oracle’s VPATs were pretty laughable. Their a11y team does a much better job with VPATs now. @jamesn from Oracle comes here frequently.

    I’m not going to speak for Oracle or @jamesn, but IMO Oracle views these documents as legal documents (and rightly so given their use).

    I’d recommend really reading these things super carefully to parse out what the document says. You should do your own independent testing, too. Unfortunately I don’t see them being too forthcoming with specifics

  6. [karlgroves] Don’t get me wrong, the doc is clear.
  7. zakim-robot
    @zakim-robot
    Jan 19 13:08
    [jbuller] Thank you @karlgroves for that. I’ve written to @jamesn
  8. [karlgroves] Cool
  9. zakim-robot
    @zakim-robot
    Jan 19 13:33
    [felix.berger] So, I was surprised to see the current support of aria-current. Attempting to implement it on a page navigation right now, i realize that all patterns utilize recursive links for the aria-current="page". This is why I wonder if the attribute is actually compatible with non recursive navigation "link" items (ev strong-replacement) ... any opinions on this topic are appreciated :)
  10. [tink] @felix.berger not sure what you mean by recursive navigation?
  11. zakim-robot
    @zakim-robot
    Jan 19 13:39
    [felix.berger] what I meant by recursive was a link whose href target the page currently active (eg a home-link that is clickable on the home page)
  12. [tink] Yes, you can use aria-current then.
  13. [felix.berger] okay, that's very cool!
  14. [felix.berger] thank you so much
  15. [tink] Or on a non-recursive navigation like <a aria-current="page">...</a>
  16. zakim-robot
    @zakim-robot
    Jan 19 14:04
    [skymaiden] hello :) yesterday i asked about dialog vs alertdialog vs alert
  17. [skymaiden] am i correct in understanding them to be like this?
  18. [skymaiden] - dialog = covers application (at least partially), interrupts
    • alert = brief important message, non-interrupting
    • alertdialog = super important dialog, interrupts
  19. [skymaiden] i’m working on a video player not a website, and am trying to best align the visual behaviour to accessibility practices
  20. [tink] @skymaiden an alert is intended for important notifications where there is no expectation of user interaction, so no need to move focus to the alert content.
  21. zakim-robot
    @zakim-robot
    Jan 19 14:09
    [tink] An alertdialog is intended for important notifications where user interaction is expected, and keyboard focus is taken to the alertdialog when it opens.
  22. [skymaiden] thank you @tink ! clear explanation :)
  23. [tink] NP :)
  24. [skymaiden] i have another question: have mobile/touch recommendations for complex applications evolved over the last year or so? about 18 months ago there wasn’t much mention of mobile accessibility in the w3c guidelines...
  25. [skymaiden] menu interactions for example (on desktop the advice was to use arrow keys, there aren’t any on touch devices)
  26. [skymaiden] (i’m looking on the github project and haven’t found anything yet, but i might be looking in the wrong places)
  27. zakim-robot
    @zakim-robot
    Jan 19 14:22
    [tink] There is some brief guidance in https://w3s.github.io/aria-in-html/#aria-touch
  28. [tink] It includes references to a gap analysis, and a link to the original issue on the ARIA spec which was closed and is now referred to from an issue on the APG spec w3c/aria-practices#8
  29. [skymaiden] thank you!
  30. Mallory
    @StommePoes
    Jan 19 15:02
    This isn't quite as much info but if you were to map the current WCAG to a mobile-oriented way of thinking, someone tried it here https://www.w3.org/TR/mobile-accessibility-mapping/
  31. zakim-robot
    @zakim-robot
    Jan 19 15:18
    [alastc] The new (very DRAFT!!!), not-approved, mobile-oriented guidelines are here: https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3AMATF As far as I can tell there is still a gap in terms of aria-touch (corrected URL: https://w3c.github.io/aria-in-html/#aria-touch) where patterns require particular keys, but they give you an idea of the issues being tackled.
  32. Hinerangi Courtenay
    @skymaiden
    Jan 19 15:28
    Thanks a lot @StommePoes and @zakim-robot!
  33. powrsurg
    @powrsurg
    Jan 19 18:24
    So I have a text area where people can put in text that will go out to a user when a new user registers. After it I had a button that someone could click that would show a snippet of help text for formatting, variables that would be replaced, etc.
  34. I currently have it as a button with aria-expanded and aria-controls and all that good stuff
  35. But should it actually be using details/summary?
  36. and is there a way of associating all of that with the textarea, and should it?
  37. Mallory
    @StommePoes
    Jan 19 19:01
    It could be a details-summary, so long as no focusables inside it... and you add in all the stuff you already have because d/s doesn't work still in most browsers...
  38. just blink and ff so far I think
  39. powrsurg
    @powrsurg
    Jan 19 19:09
    Shouldn't it be okay to have a focusable in the summary?
  40. I feel like I'm potentially doing too much
  41. Michael Fairchild
    @mfairchild365
    Jan 19 19:27
    I wrote a thing and thought I'd share it https://mfairchild365.github.io/2017/01/19/aam-overview
  42. zakim-robot
    @zakim-robot
    Jan 19 19:46
    [marcysutton] Nice post!
  43. Michael Fairchild
    @mfairchild365
    Jan 19 19:49
    thanks! Feel free to share!
  44. zakim-robot
    @zakim-robot
    Jan 19 19:54
    [marcysutton] I need more time to read through the whole thing, but it looks very useful!
  45. James Nurthen
    @jnurthen
    Jan 19 21:39
    @jbuller I don't (can't) use slack so if you have messaged me there I will never see it.