Archive index

A11y Slackers Gitter Channel Archive 8th of October 2015

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    03:13
    [James Nurthen, a11y] Jaws has a virtual braille display too.
  2. MichielBijl
    10:02
    Is it just me, or is the audio out of sync with this video: https://www.youtube.com/watch?v=a-GnfF55sdA&feature=youtu.be
  3. zakim-robot
    10:30
    [heydon, a11y] role="timer" has an implicit value of aria-live="off", meaning it's not "live" by default. How do I trigger readout? It seems a pointless value since I can just use a setInterval() decrememnter and add aria-live=“assertive” when I reach an important number in the countdown.
  4. powrsurg
    13:54
    Has anyone looked at the new Accelerated Mobile Pages thing Google is pushing?
  5. stevefaulkner
    13:56
    @powrsurg briefly
  6. zakim-robot
    13:56
    [Chris DeMars, a11y] I read about it yesterday
  7. MichielBijl
    13:56
    @Heydon seems there is no guidance in either WAI ARIA or the Authoring Practices :(
  8. powrsurg
    13:58
    @stevefaulkner what are your thoughts? My initial reaction is this is going to cause accessibility problems in the long run
  9. MichielBijl
    13:59
    @powrsurg I read an article. It's basically just a new set of invalid attributes right?
  10. powrsurg
    14:00
    part of the spec requires: <style>body {opacity: 0}</style><noscript><style>body {opacity: 1}</style></noscript>
  11. MichielBijl
    14:00
    The idea behind it is stupid if you ask me; “2000: let's add all the ads!” “2015: oh noes, our websites are slow due to ads; let's come up with tags to solve it”
  12. MichielBijl
    14:01
    But I'm biased anyway; so don't listen to me.
  13. powrsurg
    14:01
    <amp-img> instead of <img>
  14. powrsurg
    14:01
    stuff like that
  15. MichielBijl
    14:02
    Yeah, let's make everything invalid…
  16. garcialo
    14:02
    Invalid...but fast!
  17. MichielBijl
    14:02
    It uses JS to parse this stuff I;m guessing?
  18. MichielBijl
    14:02
    Let's use JS to solve our JS overload! Wait what?
  19. MichielBijl
    14:03
    But, before I comment any further I should probably read up on the subject ;)
  20. powrsurg
    14:03
    Honestly, my initial reactions are "why do we need this?", "who thought this was a good idea?"
  21. MichielBijl
    14:03
    My thought exactly.
  22. powrsurg
    14:04
    yeah, I'm only briefly looking into it now
  23. powrsurg
    14:04
    yes, it uses JS
  24. powrsurg
    14:04
    I haven't found examples yet where they use JS in the page besides using the library
  25. powrsurg
    14:06
    I haven't seen anything yet that can't be done with plain ole HTML and I'm not getting why we need to redefine everything to somehow make it faster
  26. powrsurg
    14:15
    Wow, no author-written JavaScript or third-party libraries. Lovely
  27. stevefaulkner
    14:15
    yeah
  28. garcialo
    14:15
    You suck at JavaScript; only use ours.
  29. MichielBijl
    14:18
    haha
  30. stevefaulkner
    14:19
    only acc issue i think could be with the custom elements, <amp-img> for example, has alt attribute defined, but haven't yet seen how that is expressed in DOM
  31. powrsurg
    14:25
    I guess we need to see how they do the carousel and the like
  32. powrsurg
    14:32
    backwards compatibility is basically shot
  33. garcialo
    14:33
    @powrsurg getElementById("carousel").setAttribute("style","display:none");
  34. stevefaulkner
    14:37
    i don't see issue, its an allowed subset of current HTML elements with some custom elements thrown in, with some strict conformance requirements
  35. stevefaulkner
    14:41
    maximum-scale=1,user-scalable=no issue AMP ampproject/amphtml#481
  36. powrsurg
    15:09
    I really thought disabling user zooming was really bad practice
  37. stevefaulkner
    15:11
    and yes it is
  38. zakim-robot
    16:47
    [heydon, a11y] @michiel: Yeah, it seems to be some sort of under-specced stub :((
  39. zakim-robot
    18:04
    [Chris DeMars, a11y] So I think I'm going to reference the wcag 2.0 at a glance page for what needs to be followed but also add my notes and other resources in the doc too.
  40. mejsullivan
    18:38
    quick question, does anyone have a good resource for mobile web - off screen text treatments?
  41. garcialo
    18:43
    I've heard that off-screen text act oddly on iOS; looking for info on it now
  42. mejsullivan
    18:46
    Ya that's what I've heard too
  43. zakim-robot
    19:54
    [Francis Storr, a11y] Anyone have any tips on getting VoiceOver to play nicely with correctly marked up tables with multiple layers of headers? Using the first example page (http://www.w3.org/WAI/tutorials/tables/multi-level/) asking VoiceOver for the column heading that should announce "Example 4 Inc” gives “Example 2 Co”. I have the same table locally but using scope attributes instead of headers and have the same problem. This is on 10.10.5 with Safari 9 and Chrome latest.
  44. garcialo
    21:51
    I think Paul has some examples....let me check
  45. garcialo
    21:51
    hmmm...doesn't look like he has multilayer examples
  46. garcialo
    21:51
    just http://pauljadam.com/demos/tableA11yTest.html
  47. zakim-robot
    21:55
    [ccwilcox, a11y] Those demos are saying VoiceOver fails with scope and header attributes even for simple tables