Archive index

A11y Slackers Gitter Channel Archive 1st of April 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Apr 01 10:41
    [lefthandev] Is there a resource out there where I can find out more about aria-importance?
  2. zakim-robot
    @zakim-robot
    Apr 01 12:02
    [mgifford] I’m trying to pull together examples of good language for accessibility within the procurement process. So far I’ve got this list https://github.com/mgifford/a11y-contracting
  3. [mgifford] My hope is that by documenting this & exploring with the accessibility community, we can find ways to make procurement processes give us better results.
  4. James Nurthen
    @jnurthen
    Apr 01 13:48
    @lefthandev there is no aria-importance
  5. zakim-robot
    @zakim-robot
    Apr 01 14:59
    [michiel] Is https://w3c.github.io/html/ giving a 404 for anyone else?
  6. [garcialo] yes, for me
  7. [michiel] Thanks
  8. [garcialo] @mgifford Could you add something like “Accessibility issues must be categorized as bugs; not features."
  9. [garcialo] I wasn’t sure which section would make the most sense to put it in :p
  10. [mgifford] That’s a nice one..
  11. zakim-robot
    @zakim-robot
    Apr 01 15:05
    [mgifford] I’ve worded it as "WCAG related accessibility barriers are categorized as bugs; not feature requests"
  12. [mgifford] I tried to make it a bit more specific, as there are accessibility issues like ATAG, which aren’t needed for WCAG compliance (of the front end). They are very useful, but should be seen as features.
  13. [mgifford] Hope that makes sense @garcialo
  14. zakim-robot
    @zakim-robot
    Apr 01 15:10
    [garcialo] makes snese
  15. [garcialo] sense*
  16. [garcialo] when working with sales folk, I use the opportunity to sort of probe whether they actually know about the jargon…I try to volunteer as little specifics as possible so they have the opportunity to impress me by knowing what WCAG, Section 508, VPATs, etc. are
  17. [garcialo] so, I’ll just ask “What do y’all do for accessibility?"
  18. zakim-robot
    @zakim-robot
    Apr 01 15:19
    [garcialo] and when I ask what they’re doing it, I also leave it vague without going into specifics so that I’m not giving them the language they need to use…so “What accessibility best practices do you follow for design/development/testing” rather than “Does your site conform to WCAG 2.0 Level AA?"
  19. zakim-robot
    @zakim-robot
    Apr 01 15:48
    [michiel] “I also leave it vague”—garcialo
  20. [michiel] Words to live by
  21. zakim-robot
    @zakim-robot
    Apr 01 15:56
    [michiel] garcialo when will you be in Europe?
  22. zakim-robot
    @zakim-robot
    Apr 01 16:03
    [garcialo] I’ve never been to Europe
  23. [garcialo] but I’ll look into it
  24. [michiel] ++
  25. [michiel] You should visit, it’s lovely, we have privacy laws and such.
  26. zakim-robot
    @zakim-robot
    Apr 01 18:27
    [michiel] Garcialo: any plans to add SSL to http://a11ynot.com?
  27. zakim-robot
    @zakim-robot
    Apr 01 19:05
    [garcialo] It's on GitHub pages. I'm kind of surprised it doesn't just do it already :p
  28. zakim-robot
    @zakim-robot
    Apr 01 19:19
    [lefthandev] @jnurthen there is : ) https://rawgit.com/w3c/coga/master/techniques/index.html#limit-the-number-of-features-and-choices-on-the-same-screen.x
  29. [lefthandev] @jnurthen in theory : )

  30. [karlgroves] > aria-importance

    WCAG WTF

  31. zakim-robot
    @zakim-robot
    Apr 01 19:26
    [lefthandev] @karlgroves Guess it's work in progress : )

  32. [karlgroves] >W3C Editor's Draft 01 April 2017

    (trollface emoji)

  33. [lefthandev] ha ha
  34. zakim-robot
    @zakim-robot
    Apr 01 20:01
    [michiel] @garcialo: GH pages only adds SSL if you don’t have a custom domain.
  35. [michiel] But, you can add SSL via CloudFlar.
  36. [michiel] CloudFlare.
  37. [michiel] I did that this afternoon for roledrinks.
  38. [michiel] It’s not end-to-end, but better than nothing eh.
  39. [garcialo] Yeah, I was noticing that. I'll probably set it up when I get back home.
  40. zakim-robot
    @zakim-robot
    Apr 01 20:07
    [michiel] Nice :)
  41. [michiel] Takes like 10 minutes (or faster if can read faster than I can).
  42. zakim-robot
    @zakim-robot
    Apr 01 21:52
    [lefthandev] @jnurthen @karlgroves I should say having read the cognitive task force info, I find it really interesting. I'd initially came across an early stage example that had some aria properties I'd never seen before - hence my quandary :ok_hand:
  43. James Nurthen
    @jnurthen
    Apr 01 23:13
    As far as I'm aware there is no aria-importance. The current proposal is coga-simplification but the spec it is in has not even reached first public working draft yet.
  44. zakim-robot
    @zakim-robot
    Apr 01 23:23
    [karlgroves] Call me crazy but perhaps coga should use only examples that feature actual ARIA stuff or (where appropriate) link to whatever proposal features that stuff.
  45. James Nurthen
    @jnurthen
    Apr 01 23:24
    @karlgroves you are crazy :)
  46. This is the current spec. Can't say I have read it myself though. https://rawgit.com/w3c/personalization-semantics/master/semantics.html
  47. zakim-robot
    @zakim-robot
    Apr 01 23:34
    [karlgroves] @jnurthen: w3c/coga#66