Archive index

A11y Slackers Gitter Channel Archive 4th of September 2015

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    Sep 04 00:15
    [Chris DeMars, a11y] I like that @valhead ! #DZY
  2. stevefaulkner
    10:01
    :point_up: September 3, 2015 6:09 PM will arrange one in next week or so, just back from hols and going to Budapest sunday for TPG lovefest...
  3. stevefaulkner
    10:36
    FYI https://twitter.com/stevefaulkner/status/639734946886721536
  4. stevefaulkner
    10:56

    A11ySlackers chat log 3rd September 2015 http://w3c.github.io/a11ySlackers/archives/2015/09/2015-09-03.html

  5. MichielBijl
    12:17
    @stevefaulkner your new Twitter photo looks like you're the new tattoo king of London.
  6. MichielBijl
    12:17
    Or $random-urban-area
  7. stevefaulkner
    14:38
    @MichielBijl is that a good thing?
  8. MichielBijl
    14:48
    @stevefaulkner it's a cool photo, so I'd say so
  9. MichielBijl
    14:48
    Does anybody here know why on earth Safari dev tools keep changing my units in the inspector?
  10. MichielBijl
    14:48
    padding-bottom: 48px; becomes padding-bottom: 3pc; WebKit Staph!
  11. MichielBijl
    14:49
    I suspect it might be css minify though
  12. MichielBijl
    14:50
    Yep
  13. MichielBijl
    14:50
    Argh
  14. zakim-robot
    15:02
    [Greg Tarnoff, a11y] @Here suggestions on accessible datepickers? I need to support IE11 and they don’t have a built in one for datetime-local input types. Testing of jQuery UI and Bootstrap seem less than accessible (also don’t want to include those libraries for one component) if I don’t have to).
  15. zakim-robot
    15:02
    [Alex Sexton, a11y] for the most part, I think the most accessible datepickers are free-text inputs with clever parsing (and confirmation)
  16. zakim-robot
    15:03
    [callumacrae, a11y] +1 to text input, forced date pickers are horrible! also, progressive enhancement
  17. zakim-robot
    15:03
    [Alex Sexton, a11y] the dojo calendar and stuff were generally well regarded for a11y, but I think for the most part, a straight-up-datepicker isn never going to be as nice as just being able to type a date
  18. garcialo
    15:05
    Date pickers are good for communicating to users the day of the week they're choosing along with the date.
  19. garcialo
    15:05
    Unless you're one of those math kids that can figure it out from the date alone. =p
  20. garcialo
    15:06
    Although, you could probably get around that without a date picker...hmmm
  21. zakim-robot
    15:08
    [Alex Sexton, a11y] You can set a linked field that reads the date out based on Intl.DateFormat which can include the day of the week.
  22. zakim-robot
    15:08
    [Alex Sexton, a11y] and you can still add a datepicker to the text-input
  23. garcialo
    15:08
    Yeah
  24. zakim-robot
    15:08
    [Lindee Keller, a11y] Hi, a11ies. I'm back with more questions about aViewer 2013. It appears the problem I'm having (only MSAA info is displayed) probably is because I upgraded to Windows 10. Tried running it in compatibility mode, just in case, but that didn't do anything. We're doing an accessibility overhaul at my organization and I'd really like the other devs to have a tool that quickly shows what info is and isn't being conveyed to AT. Any ideas?
  25. garcialo
    15:11
    Aside from using a screen reader like NVDA, you could use something like Fangs or FireEyes has a SimulAT option.
  26. garcialo
    15:11
    Fangs link - https://addons.mozilla.org/en-us/firefox/addon/fangs-screen-reader-emulator/
  27. garcialo
    15:12
    FireEyes link - http://getfireeyes.com/ (you can click Register to download without completing the form)
  28. zakim-robot
    15:13
    [Greg Tarnoff, a11y] @slexaxton: Totally agree with the plain text + parsing. In fact testing it is in fact faster to enter a date than hunt & click datepicker, but the client who is paying my UX knowledge decided my UX knowledge is crap and wants a freakin’ date picker in all browsers they support.
  29. garcialo
    15:14
    Hah
  30. zakim-robot
    15:14
    [Greg Tarnoff, a11y] They have thrown out so much of my advice at this point, they should have paid 1/3 less and gotten a front end dev code monkey.
  31. garcialo
    15:16
    Meh, they should be charged more the more they don't want you to do something.
  32. garcialo
    15:17
    Or rather, the more they want to be involved in the process.
  33. zakim-robot
    15:17
    [Greg Tarnoff, a11y] I’m just glad it is almost over. Honestly, I implement this datepicker and update some docs, then I’m just available for questions.
  34. stevefaulkner
    16:35
    @lindeek think i know why aViewer is not working as expected with chrome, will try to get you an updated working version over weekend