Archive index

A11y Slackers Gitter Channel Archive 25th of January 2016

What fresh hell is THIS now? - Patrick Lauke
  1. dylanb
    Jan 25 01:29
    @LjWatson how are you accessing the gitter channels?
  2. jkva
    07:59
    Morning everybody
  3. cr2a-graphique
    08:24
    hi men Good monday morning too
  4. MichielBijl
    08:46
    @dylanb afaik she uses IRC :)
  5. stevefaulkner
    12:47
    @StommePoes you around?
  6. jkva
    12:48
    @stevefaulkner : She's not (in transit) but I can proxy if you want
  7. stevefaulkner
    12:50
    @jkva do you (or anyone) have linux/orca set up?
  8. stevefaulkner
    12:50
    need something tested
  9. jkva
    12:51
    @stevefaulkner Sorry, running OSX
  10. stevefaulkner
    12:52
    @jkva no problem!
  11. jkva
    12:52
    @stevefaulkner: I expect @StommePoes to be around in 2 hours or so.
  12. stevefaulkner
    12:56
    :+1:
  13. MichielBijl
    13:12
    @stevefaulkner I have, what do you need?
  14. MichielBijl
    13:13
    I'm running Orca 3.16 on Ubuntu 15.10 if that's okay.
  15. stevefaulkner
    13:18
    @MichielBijl I need updates for the orca results here http://www.html5accessibility.com/tests/hidden2013.html
  16. stevefaulkner
    13:18
    Orca 3.4.2 Epiphany 3.4.1/ Webkit 1.8.3 + Orca 3.4.2, Firefox 24, Ubuntu 12.04
  17. stevefaulkner
    13:18
    as in latest versions
  18. MichielBijl
    13:24
    Should I create a PR?
  19. MichielBijl
    13:25
    @stevefaulkner Because I don't see the file on GitHub?
  20. stevefaulkner
    13:25
    hold on
  21. stevefaulkner
    13:34
    @MichielBijl here it is https://github.com/stevefaulkner/HTML5accessibility/blob/gh-pages/tests/hidden-2016.html
  22. MichielBijl
    13:36
    Do you want me to update the current Orca/Firefox column or add a new one?
  23. stevefaulkner
    13:37
    update current please
  24. MichielBijl
    13:39
    Does test number 4 pass if it's read out?
  25. MichielBijl
    13:39
    That's the position left thing.
  26. stevefaulkner
    13:40
    yes
  27. MichielBijl
    13:47
    Crap, date got changed, hang on…
  28. MichielBijl
    13:49
    Have updated PR.
  29. stevefaulkner
    13:59
    thanks :+1:
  30. MichielBijl
    14:00
    For science!
  31. powrsurg
    14:38
    Does aXe actually evaluate the color contrast on placeholders? We've got a page that passes but I swear that can't be enough contrast. And heck, I'm not actually sure on how to get the computed value of the color of a placeholder. I looked in Chrome's inspector but didn't see -webkit-input-placeholder in the computed tab.
  32. powrsurg
    14:42
    And when did Chrome get an "Accessibility Properties" tab?
  33. zakim-robot
    14:45
    [jdan] @powrsurg looks like you need to enable a setting in devtools - http://stackoverflow.com/questions/26852922/inspect-webkit-input-placeholder-with-developer-tools
  34. zakim-robot
    14:46
    [jdan] I was unaware that webkit placeholders and the shadow DOM were related, but now I see this in my devtools :simple_smile:
  35. zakim-robot
    14:46
    [jdan] Pasted image at 2016-01-25, 9:46 AM
  36. powrsurg
    14:49
    Interesting. Had never considered it such
  37. powrsurg
    14:49
    makes sense
  38. powrsurg
    14:50
    still, brings up the question of whether aXe is checking it. But now I can manually check at least
  39. MichielBijl
    14:56
    @jdan, can you give an alt for you image?
  40. powrsurg
    15:00
    @jdan, his alt is showing the Shadow DOM in Chrome's inspector for the placeholder attribute.
  41. jnurthen
    15:14
    The last time I looked at the axe
  42. jnurthen
    17:37
    Sorry - thought my full message went through but I was on my phone....
  43. jnurthen
    17:39
    The last time I looked at aXe it didn't check colour contrast of placeholders. Looking at the source right now to see if it has been added. If you are doing the test manually make sure to take into account the opacity of the text which is specified in the browser.
  44. jnurthen
    17:41
    No - confirmed it doesn't appear to. You can look at the colour contrast source here - https://github.com/dequelabs/axe-core/tree/master/lib/checks/color
  45. MichielBijl
    17:50
    @jnurthen placeholders being optional, does colour contrast really matter?
  46. jnurthen
    17:50
    Yes - you are providing hint text to people, they should be able to read them
  47. MichielBijl
    17:51
    But more often than not, if placeholders have sufficient contrast, people think the form is pre-filled/causes confusion. If the text is really important, it is probably better to provide it beside/underneath the input.
  48. jnurthen
    17:54
    I agree it is a hard problem. We set them to {
    color: #737373;
    font-style: italic;
    opacity: 1;
    } which is the best we could do to visually distinguish them from text
  49. MichielBijl
    17:54
    Hmm, that's a good one.
  50. jnurthen
    17:55
    I'd like to see that as the "standard" for placeholders.....
  51. jnurthen
    17:55
    of course what I would really prefer is that the browsers default was good