Archive index

A11y Slackers Gitter Channel Archive 4th of November 2015

What fresh hell is THIS now? - Patrick Lauke
  1. MichielBijl
    08:28
    My talk is in 30 minutes, scared shitless…
  2. MichielBijl
    08:28
    I don't mind talking in front of developers, but project managers are a whole different thing. Let's see how it goes…
  3. MichielBijl
    10:06
    Well, I didn't die, so that's a start
  4. MichielBijl
    10:21
    I feel bad for people that follow both @StommePoes and me on twitter; we litter their timeline like there is no tomorrow :P
  5. StommePoes
    11:33
    poor marcy
  6. zakim-robot
    12:33
    [dean] Good initiative - http://www.accessearth.org/ - may be of interest here.
  7. MichielBijl
    12:43
    Interesting, thanks for sharing!
  8. MichielBijl
    12:44
    I remember being on a call with some W3C people that were working on a standard for this. That was very interesting too.
  9. MichielBijl
    12:44
    Think that was late last year.
  10. stevefaulkner
    15:03
    @alice @rickb followed my own advice and filed bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=29261
  11. alice
    16:34
    @stevefaulkner Wohoo!
  12. StommePoes
    16:45
    w3c/aria#102 from @wcagtest
  13. garcialo
    17:39
    @stevefaulkner You need to get a new computer.
  14. stevefaulkner
    17:42
    This message was deleted
  15. garcialo
    17:43
    Which is the one running Windows NT? That needs to be thrown out!
  16. stevefaulkner
    17:43
    Windows NT?
  17. garcialo
    17:43
    https://www.w3.org/Bugs/Public/show_bug.cgi?id=29261
  18. stevefaulkner
    17:44
    Ah that's a bugzilla silliness 😀
  19. garcialo
    17:44
    Poor bugzilla =(
  20. ricksbrown
    19:23
    @stevefaulkner thanks for that
  21. zakim-robot
    21:11
    [jiatyan] On styling links, are there any accessibility reasons to include different styles for hover and visited state? (Designer had killed both.)
  22. garcialo
    21:16
    Sounds like that would be more usability in being able to tell the difference between the states. Don't know of any accessibility-specific reasons that you'd need different styles for those states.
  23. zakim-robot
    21:17
    [jiatyan] I was looking for more ammunition :simple_smile:
  24. garcialo
    21:17
    Do the links have underlines?
  25. garcialo
    21:18
    Or some other visual indication?
  26. zakim-robot
    21:18
    [jiatyan] They do have underlines. Underline is all they have.
  27. garcialo
    21:18
    Yeah, then they're fine. =p
  28. garcialo
    21:19
    probably fine
  29. zakim-robot
    21:21
    [jiatyan] :simple_smile: thanks
  30. zakim-robot
    21:29
    [ldavis] I don't know if this is the right place to ask this question, but here I go. I have a custom radio object (role - radiogroup, nested role radio's and supporting aria attributes) Some of the structures are formatted in a table layout and others are not. With JAWS , the non table structures work great while the table layouts fail to respond as radio controls and switch to some forms or smart nav mode... Is there a way to stop this mode switching even with tables?
  31. zakim-robot
    21:33
    [ldavis] (ultimate goal to add screen reader support to legacy content without having to mangle existing content more then needed)
  32. zakim-robot
    21:50
    [bdruth] @ldavis: more *than needed
  33. zakim-robot
    21:59
    [ldavis] heh how dare you grammar police
  34. zakim-robot
    22:10
    [bdruth] lol
  35. stevefaulkner
    22:37
    @ldavis - code example exhibiting issue would be helpful, also details of browser/AT combo and version
  36. stevefaulkner
    22:39

    [ldavis] the table layouts fail to respond as radio controls and switch to some forms or smart nav mode... Is there a way to stop this mode switching even with tables?

    if they are layout tables have set role=presentation on the table element?

  37. stevefaulkner
    22:41
    @ldavis info on role=presentation http://www.w3.org/TR/aria-in-html/#use-of-role-presentation
  38. zakim-robot
    23:08
    [ldavis] @stevef: Role presentation does fix the radio up down navigation, but not the reading back. I'll bring up a simple example. Likely post up tomorrow.
  39. zakim-robot
    23:08
    [ldavis] thanks again!