Archive index

A11y Slackers Gitter Channel Archive 1st of September 2015

What fresh hell is THIS now? - Patrick Lauke
  1. powrsurg
    Sep 01 00:24
    literally did not sleep at all last night
  2. powrsurg
    Sep 01 00:24
    ..
  3. powrsurg
    Sep 01 00:24
    dunno how that got sent
  4. powrsurg
    Sep 01 00:24
    sorry
  5. jonathantneal
    05:31
    Is aria-current a thing to use now or is it dead? http://www.heydonworks.com/article/the-accessible-current-page-link-conundrum
  6. jonathantneal
    05:55
    For hamburger menus, I see a pattern of using the [aria-expanded] attribute on the trigger with [aria-controls="id_of_the_navigation"] on the target. For submenus, it’s just [aria-haspopup="true"] on the trigger. Is the aria-controls attribute not necessary because the sublink is the next tab-able item?
  7. jonathantneal
    06:06
    I misspoke, in the hamburger menu, expanded and controls are on the trigger. The target only has an id.
  8. MichielBijl
    07:44
    @jonathantneal definitely not dead, still working out the kinks in the spec
  9. MichielBijl
    07:44
    There is discussion over which values it should take
  10. MichielBijl
    07:45
    The last consensus was a predefined list with everything else triggering true.
  11. MichielBijl
    07:45
    Let me find the minutes for that.
  12. MichielBijl
    07:48
    Right near the end: http://www.w3.org/2015/08/06-aria-minutes.html
  13. MichielBijl
    07:48
    “Proposal: The aria-current attribute is an enumerated type. Any value not included in the list of allowed values SHOULD be treated by assistive technologies as if the value true had been provided. If the attribute is not present or its value is an empty string, the default value of false applies and the aria-current state MUST NOT be exposed by user agents or assistive technologies.”
  14. zakim-robot
    08:14
    [heydon, a11y] @heidi Cool! heydon@heydonworks.com
  15. zakim-robot
    08:50
    [Wilco Fiers, a11y] Anyone have any thoughts on the accessibility of isomorphic apps?
  16. zakim-robot
    08:52
    [Wilco Fiers, a11y] I've been pondering this for a while now, but I'm really not too sure if apps that load content client side, but can can also be build on the server should be considered a single page, or multiple pages.
  17. garcialo
    15:38
    Isn't isomorphic mostly backend?
  18. garcialo
    15:39
    As in, the user would get the same interface whether the app was running all on the client or all on the server.
  19. zakim-robot
    17:27
    [Marcy Sutton, a11y] If it’s a seamless refresh from server-rendered to client-rendered, I don’t think it should be a problem. Perhaps some focus management might be needed if the user is directed visually to a certain place. But isn’t the idea that you shouldn't notice JS enhancing the page?
  20. zakim-robot
    17:30
    [Marcy Sutton, a11y] I suppose if you’re going to support no-JS, the server-rendered solution would have to work by itself. That opportunity is one benefit of serving up a site this way, but I’m pretty firmly in the supporting-JS camp :simple_smile:
  21. zakim-robot
    17:31
    [Kevin Lozandier, a11y] @dylanb: I’d be down to go to a11y-nyc
  22. zakim-robot
    17:46
    [heydon, a11y] @wilco @marcysutton @garcialo My thinking is that if an event either from the server or the client affects the UI’s state in a way that needs to be explicated to the user, the difference is arbitrary. Both instances need to be similarly accessible.
  23. garcialo
    18:22
    Exactly.
  24. zakim-robot
    18:26
    [dylanb, a11y] @lozandier: yes, I owuld like to go too
  25. zakim-robot
    18:26
    [dylanb, a11y] *would
  26. stevefaulkner
    19:17

    A11ySlackers chat log 31st of August 2015 http://w3c.github.io/a11ySlackers/archives/2015/08/2015-08-31.html

  27. zakim-robot
    20:14
    [zamith, a11y] @Channel: It was nice to get this merged, but I’d like to know of even better ways to write it. kif-framework/KIF#713
  28. zakim-robot
    20:15
    [zamith, a11y] PS: Sorry if I’m not supposed to use at channel
  29. zakim-robot
    20:17
    [Bill Nordwall, a11y] @zamith using [at] channel will notify all 433 people in the room, so I’d recommend using it sparingly
  30. zakim-robot
    20:19
    [Jon Metz, a11y] On the other hand, it brought me back to the room to dust this thing off.
  31. zakim-robot
    20:20
    [Marcy Sutton, a11y] hi @metzessible :wave:
  32. zakim-robot
    20:20
    [Jon Metz, a11y] Hi @marcysutton!
  33. zakim-robot
    20:20
    [Marcy Sutton, a11y] Still always looking for accessibility wins if anyone wants to spread some praise :simple_smile: http://a11ywins.tumblr.com/
  34. zakim-robot
    20:31
    [zamith, a11y] @billnordwall: I noticed that after I sent the message :confused:
  35. zakim-robot
    20:32
    [zamith, a11y] used to internal slack, with fewer people
  36. zakim-robot
    20:56
    [Faruk Ateş, a11y] Idle question: Why do so many accounts here have [BOT] behind their name?
  37. zakim-robot
    20:58
    [Faruk Ateş, a11y] @heydon: Hey, we’re doing our accessibility audit & tools writeup, thank you for your Revenge.css bookmarklet. :simple_smile:
  38. zakim-robot
    20:59
    [Faruk Ateş, a11y] @heydon: We’re quite appreciative of the super friendly copy text it employs. It’s non-blamey, very human. Nice work :simple_smile:
  39. zakim-robot
    21:16
    [Marcy Sutton, a11y] @kurafire: it’s the pipe between this and Gitter http://www.paciellogroup.com/blog/2015/07/anybody-can-be-an-a11y-slacker/
  40. zakim-robot
    21:17
    [Faruk Ateş, a11y] Ah, I see.
  41. zakim-robot
    21:18
    [Faruk Ateş, a11y] I figured something like that; there’s a front-end devs slack that has a website client interface via the JS console
  42. zakim-robot
    21:18
    [Faruk Ateş, a11y] It’s, uh, neat? Special? Unique snowflake?
  43. zakim-robot
    21:18
    [Faruk Ateş, a11y] But similar thing: users using that “chat” method get a different display
  44. zakim-robot
    21:18
    [Faruk Ateş, a11y] (& no avatar)
  45. zakim-robot
    21:19
    [Faruk Ateş, a11y] cheers!