Archive index

A11y Slackers Gitter Channel Archive 21st of March 2016

What fresh hell is THIS now? - Patrick Lauke
  1. garcialo
    Mar 21 00:50
    @kevinchao89 apologies for the non-answer, I had literally woken up like a minute earlier and totally thought my answer was sufficient at the time. @heydon's answer is good, but here is some more information about infinite scrolling http://www.webaxe.org/infinite-scrolling-and-accessibility/
  2. zakim-robot
    Mar 21 07:55
    [heydon] @dean One of the grave issues with infinite scroll regards keyboard users. It makes it impossible for them to get to the content after the stream.
  3. zakim-robot
    Mar 21 07:57
    [dean] yep, I’m with you @heydon - it was more a question out of curiosity more than anything else. How are the likes of Twitter & Pinterest perceived in the accessibility community?
  4. pkra
    Mar 21 10:41
    Here's something "fun": http://codepen.io/pkra/pen/zqrwQx?editors=1000 // http://s.codepen.io/pkra/debug/zqrwQx
  5. pkra
    Mar 21 10:42
    If anyone happens to try this in AT I have not tested , I'd be grateful if you would let me know about the results.
  6. zakim-robot
    Mar 21 10:59
    [heydon] @dean: Twitter’s web interface is thought of quite poorly for infinite scroll, I think. Otherwise not too bad except the lack of alt text support.
  7. powrsurg
    Mar 21 13:58
    Am I crazy, or didn't Chrome or Firefox's Dev tools (or maybe Firebug) used to have a section that showed the computed accessibleName for an element?
  8. zakim-robot
    Mar 21 14:02
    [techthomas] @powrsurg Chrome’s Dev tool has that
  9. zakim-robot
    Mar 21 14:03
    [techthomas] Anyone know any good resources about hardware kiosk accessibility? Any lessons learned?
  10. powrsurg
    Mar 21 14:05
    Weird, I had to refresh the page for it to show
  11. zakim-robot
    Mar 21 14:06
    [techthomas] @powrsurg: yes I have some intermittent issues with it as well. very nice tool though, I’m not sure if its available anywhere else
  12. powrsurg
    Mar 21 14:09
    Yeah, I had just wanted to double check on how some accessibility name calculation was actually being done on a former client's site that was asking for a review (we're still friendly with them). The social icon links were all anchors with no text, but had titles
  13. powrsurg
    Mar 21 14:10
    some instances of anchors that used background images that rotate on mouse over that I feel should have been content images ... but they're for a column header image where the column header text right after it is a link to the same page so I guess that's okay ...
  14. jnurthen
    Mar 21 15:33
    @powrsurg Chrome Dev Tools does only if you have the Accessibility Developer Tools installed - https://chrome.google.com/webstore/detail/accessibility-developer-t/fpkknkljclfencbdbgkenhalefipecmb?utm_source=chrome-app-launcher-info-dialog
  15. powrsurg
    Mar 21 15:33
    yeah, I have that installed
  16. jnurthen
    Mar 21 15:36
    blob
  17. jnurthen
    Mar 21 15:36
    then it should be there
  18. jnurthen
    Mar 21 15:36
    alt=screenshot showing Chrome Accessibility Dev Tools with the Accessibility Properties tab open
  19. powrsurg
    Mar 21 16:17
    Yeah, It was weird. I had to refresh the page for it to show. I opened the page via a Firefox extension to open the page in Chrome. Maybe it doesn't work on fresh tabs?
  20. zakim-robot
    Mar 21 17:54
    [alice] @powrsurg: Do you know if you get Chrome extensions in general when you open things via that Firefox extension?
  21. zakim-robot
    Mar 21 17:54
    [alice] i.e. does it open in Chrome Browser proper, or in some kind of Chrome frame thing?
  22. powrsurg
    Mar 21 17:56
    browser proper
  23. zakim-robot
    Mar 21 17:56
    [alice] And in the same profile where you have the extension installed?
  24. powrsurg
    Mar 21 17:59
    you can make a Firefox profile open a Chrome profile (or vice versa)?
  25. zakim-robot
    Mar 21 17:59
    [alice] I don't know :)
  26. zakim-robot
    Mar 21 18:00
    [alice] I'm just trying to think of reasons why the extension wouldn't show up
  27. zakim-robot
    Mar 21 18:12
    [alice] You can also get name computation info from the Accessibility Inspection devtools experiment
  28. zakim-robot
    Mar 21 18:13
    [alice] enable chrome://flags/#enable-devtools-experiments, restart, then enable Accessibility Inspection via devtools settings
  29. zakim-robot
    Mar 21 18:15
    [alice] name computation steps in devtools experiment
  30. zakim-robot
    Mar 21 22:49
    [afercia] Hello everyone :wave: I'm new here.
  31. jnurthen
    Mar 21 22:49
    Hi @afercia
  32. zakim-robot
    Mar 21 22:50
    [afercia] Happy to see so many brilliant minds around :) Hi @jnurthen
  33. zakim-robot
    Mar 21 22:50
    [afercia] English is not my main language so please bear with me ;)
  34. jnurthen
    Mar 21 22:51
    welcome. Not sure how many people will be around this week as many people are travelling or already in San Diego for CSUN
  35. zakim-robot
    Mar 21 22:52
    [cordelia] Welcome, @afercia!
  36. zakim-robot
    Mar 21 22:52
    [afercia] Oh yes, have read about CSUN, a bit too far for me.
  37. zakim-robot
    Mar 21 22:52
    [afercia] Thanks @cordelia
  38. zakim-robot
    Mar 21 22:56
    [afercia] Anyone with experience about assertive live regions with role=alert and how Firefox + NVDA behace in that regard?
  39. zakim-robot
    Mar 21 22:58
    [cordelia] I’ve been working a bit with live regions lately. Are you encountering an issue there? I ran into a bug recently with role=“alert” and aria-live=“assertive” reading content twice… Can’t remember which browser / screen reader combination it was.
  40. zakim-robot
    Mar 21 23:01
    [afercia] For me, Firefox + NVDA announce "Alert" when setting CSS overflow other than visible on the body :) Worth noting this happens without any content change in the live region.
  41. zakim-robot
    Mar 21 23:02
    [afercia] I can just try to guess why this happens, but to me it seems a bug since there's no content change.
  42. zakim-robot
    Mar 21 23:06
    [cordelia] Hm…. Live regions announce when their CSS display property changes, I believe, so I wonder if overflow is also considered a sort of display change. You could try setting aria-live=“off” before doing the overflow change.
  43. zakim-robot
    Mar 21 23:09
    [afercia] @cordelia thanks yes, that or I was thinking to completely hide the live region and make it visible only before a content change
  44. zakim-robot
    Mar 21 23:13
    [afercia] Would greatly appreciate any thoughts and recommendations, I've also prepared a simplified test case: http://s.codepen.io/afercia/debug/zqZyKe
    Thanks very much!
  45. zakim-robot
    Mar 21 23:15
    [afercia] Worth noting NVDA + Internet Explorer 11 don't exhibit this behavior, so I tend to think it's something that happens just with Firefox in combination with NVDA
  46. zakim-robot
    Mar 21 23:38
    [cordelia] @afercia, great test page! About to head out for my flight to CSUN and won’t have a Windows machine with me, but hopefully someone else can try out and provide suggestions