Archive index

A11y Slackers Gitter Channel Archive 17th of August 2015

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    Aug 17 00:50
    [Rob Dodson, a11y] Great thanks @dsturley and @dylanb !
  2. zakim-robot
    01:20
    [Marcy Sutton, a11y] :thumbsup:
  3. zakim-robot
    12:28
    [dylanb, a11y] good morning a11ys!
  4. zakim-robot
    12:28
    [Katy Moe, a11y] afternoon :simple_smile:
  5. LjWatson
    12:29
    @DylanB Morning? What time do you call this? :p
  6. deborahgu
    12:36
    time zones are fun
  7. StommePoes
    12:37
    internets (or ham radio) is wonderful
  8. LjWatson
    12:37
    @deborahgu Indeed :)
  9. zakim-robot
    12:42
    [dylanb, a11y] @ljwatson: I don't know what fantasy world you inhabit, when I look outside, I see dew on the grass and the sun rising in the sky :stuck_out_tongue:
  10. LjWatson @LjWatson grins @dylanb
  11. zakim-robot
    12:51
    [dylanb, a11y] New version of aXe FF extension available - updated to axe-core 1.1.0 https://addons.mozilla.org/en-US/firefox/addon/axe-firefox-devtools/
  12. zakim-robot
    13:31
    [dylanb, a11y] @stevef: with information links that have actual information when you click them - just for you :simple_smile:
  13. stevefaulkner
    15:32
    @dylanb ☑️☑️
  14. zakim-robot
    15:36
    [dylanb, a11y] @stevef: Chrome extension updated to the FF UI too
  15. zakim-robot
    19:52
    [dylanb, a11y] Rubyists rejoice, aXe is now integrated with R-Spec https://github.com/dequelabs/axe-matchers
  16. zakim-robot
    19:53
    [dylanb, a11y] Also providing Cucumber integration
  17. zakim-robot
    20:10
    [Winston Hearn, a11y] so i’m normally a front-end engineer but i’m helping report a piece (for the verge) on how much remains to be done to make the web usable by everyone, I asked in @random last week but I realized that with Gitter, not everyone could see the message, so i’ll ask in here again.
  18. zakim-robot
    20:12
    [Winston Hearn, a11y] if you rely on accessible tech in any capacity as a normal part of your web usage, would you be willing to answer some pretty open ended questions about your experiences? If you’re interested, let me know a good email for you, or you can email me directly: winston.hearn@voxmedia.com
  19. aardrian
    20:36
    @WinstonHearn I rely on self-made bookmarklets to scale text and sometimes fix contrast/focus issues. I do not believe I qualify, but I still thought it's worth noting that even folks who don't use accessible tech still have their own tricks to make stuff easier to use.
  20. aardrian
    20:37
    Yeah, I think I offered that just to hear myself talk.
  21. aardrian
    20:37
    Two items of note for testing Edge on Win10...
  22. aardrian
    20:37
    1. "NVDA and Windows 10" http://www.nvaccess.org/win10/
  23. aardrian
    20:38
    1. VMs from Microsoft for testing Edge (and installing NVDA): http://dev.modern.ie/tools/vms/windows/
  24. zakim-robot
    20:49
    [Winston Hearn, a11y] happy to have all thoughts! i’m a firm believer in hearing a wide range of input as possible. If you want to add your thoughts, feel free to email.
  25. zakim-robot
    21:08
    [Karl Groves, a11y] Tangentially related to a11y: Are HTTP status messages localized?
  26. rodneyrehm
    21:56
    I’m pretty sure they’re not, Karl
  27. rodneyrehm
    21:56
    at least I cannot remember ever having seen “404 Nicht Gefunden” rather than “404 Not Found"
  28. rodneyrehm
    21:57
    … unless you’re asking about a browser’s rendering of an HTTP error status in case there was no content - that’s likely localized
  29. zakim-robot
    22:20
    [Cameron Cundiff, a11y] @dylanb: I’d love to be able to access the axe-core API directly without inserting it into the DOM, i.e. serverside
  30. zakim-robot
    22:21
    [Cameron Cundiff, a11y] I could see passing json representation of a node directly to the auditor
  31. zakim-robot
    22:22
    [Cameron Cundiff, a11y] and getting a list of results
  32. zakim-robot
    22:22
    [Cameron Cundiff, a11y] if this is something you’re interested in working on either in axe-core or a11yance/core, lets talk
  33. garcialo
    22:57
    It looks like they MAY be localized. http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1 I'm still looking around though. =p
  34. garcialo
    23:04
    I would assume the browser would need to do the localization, so maybe @alice has some insight?
  35. zakim-robot
    23:12
    [Alice Boxhall, a11y] @garcialo I don't know offhand, but I would assume that browser status messages are localised - but I'm not sure how to trigger one to check?
  36. garcialo
    23:16
    Wouldn't changing the OS language do that? I'm not brave enough to check. =p
  37. zakim-robot
    23:19
    [Alice Boxhall, a11y] You can change the browser language I believe, but you'd need to figure out how to trigger the browser UI before it's worth doing that
  38. garcialo
    23:20
    Ah, you're talking above my head. What is "triggering the browser UI?"
  39. zakim-robot
    23:36
    [Alice Boxhall, a11y] @garcialo
  40. zakim-robot
    23:36
    [Alice Boxhall, a11y] ffffuuuuuuu
  41. garcialo
    23:36
    ??
  42. zakim-robot
    23:36
    [Alice Boxhall, a11y] autocomplete misfire
  43. garcialo
    23:36
    hah
  44. zakim-robot
    23:36
    [Alice Boxhall, a11y] @garcialo: What I mean is that normally for a 404 etc. you see something which the remote server provides
  45. zakim-robot
    23:36
    [Alice Boxhall, a11y] not something from the browser
  46. zakim-robot
    23:37
    [Alice Boxhall, a11y] in which case it's up to them to localise it
  47. zakim-robot
    23:37
    [Alice Boxhall, a11y] so I'm not sure how to see a status page from the browser
  48. garcialo
    23:37
    Okay, it's probably something else I don't understand. I was thinking that the status code came from the remote server, but that the Reason Phrase would be from the browser.
  49. zakim-robot
    23:41
    [Alice Boxhall, a11y] Try something like https://developer.mozilla.org/en-US/ksdjhfkhsdf
  50. garcialo
    23:45
    So then if it's not the browser, it would be the web server that would need to localize the status phrase.
  51. zakim-robot
    23:46
    [Alice Boxhall, a11y] exactly. I think there something is browser UI though - I'm just not sure how to get to it
  52. garcialo
    23:47
    And if that's the case, then it would either need to check where every request was coming from and try and assume a locale based on IP...or just provide all reasons in English =p
  53. garcialo
    23:49
    But the browser could handle the responses and localize based on OS lang
  54. zakim-robot
    23:49
    [Alice Boxhall, a11y] IP or else a cookie or session state or something
  55. garcialo
    23:49
    Ah, true.
  56. zakim-robot
    23:49
    [Alice Boxhall, a11y] but basically yeah, it's up to the server to do that
  57. zakim-robot
    23:50
    [Alice Boxhall, a11y] and the browser can access OS lang as you say
  58. garcialo
    23:50
    So end result, is that we don't know. Sorry, Karl. =p
  59. garcialo
    23:51
    But I would presume not.
  60. zakim-robot
    23:51
    [Alice Boxhall, a11y] I think basically the question doesn't fully make sense
  61. zakim-robot
    23:51
    [Alice Boxhall, a11y] the answer is very much "it depends" and it depends on a lot of things
  62. garcialo
    23:51
    yeah