Archive index

A11y Slackers Gitter Channel Archive 15th of September 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Sep 15 01:13
    [ghanek] @herin can you explain what you seek a little more?
  2. zakim-robot
    @zakim-robot
    Sep 15 04:58
    [jv] Should I avoid using hover for interaction to make my website touch friendly?
  3. zakim-robot
    @zakim-robot
    Sep 15 05:19
    [caesar] @jv my opinion is "sort of". To me, a hover effect is essentially a mouse-driven focus state, which is but one of several possibilities for how an element receives focus.
  4. zakim-robot
    @zakim-robot
    Sep 15 05:33
    [caesar] Nooooooooo! They removed "earcons" from the latest version of Talkback!
  5. [caesar] That was my favourite feature!
  6. Omar Diab
    @osdiab
    Sep 15 08:05
    Hi, I have a question about the aria-valuenow attribute. I’m including a an input of type=“number” in my site, which is written in React. The MDN docs on the aria-valuenow element indicate that it is a required attribute for this input type, which to me implies that if I want to fill it in properly I need to be tracking the value of the form element in JS and fill in that attribute properly… is that intended? What’s the default behavior if I didn’t fill that in at all, given the value of this number element isn’t something I’m manipulating programmatically, nor is it a value that needs any special text representation beyond the number itself?
  7. Thanks in advance! getting a feel for how to best abide by ARIA recommendations.
  8. zakim-robot
    @zakim-robot
    Sep 15 16:38
    [quidkid] one of our designers is inspired by this site for future designs. I’m looking at it and my gut tells me I need to hit up y’all for some accessibility reality check. the scrolljacked part of the site worries me but i’m not sure how to explain it as an issue
  9. [quidkid] http://urban-walks.com/
  10. zakim-robot
    @zakim-robot
    Sep 15 16:59
    [eric] scrolljacking may interfere with nonstandard input devices and navigation, plus it can be disorienting when there’s not a 1:1 connection between the user’s movement command and the response from the page
  11. [eric] there’s also some animation on that page that looks like it’d be a potential vestibular trigger
  12. [eric] in my opinion, anything that gets an Awwwwards site of the day badge is probably pretty user-hostile
  13. [eric] while I’m at it, the tap and hold to drag the map action on that site might conflict with scrolling up or down, you’re mixing your input metaphors
  14. zakim-robot
    @zakim-robot
    Sep 15 18:19
    [quidkid] thank you so much!! is there anything official in WCAG AA against scroll jacking? i’m looking now. would it be 3.2.5? 3.2.5
    Change on Request
    Level AAA
    Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
  15. [quidkid] or is there a double a that this falls under?
  16. zakim-robot
    @zakim-robot
    Sep 15 18:32
    [eric] @quidkid under the deadline gun, but I’ll take a look in a bit - I’m pretty sure I have an article bookmarked somewhere that spells it out
  17. [quidkid] @eric not to worry, whenever you can get to it. def appreciate it though! hope there is a AA justification for it though
  18. zakim-robot
    @zakim-robot
    Sep 15 20:44
    [quidkid] so if someone tells me but hey Apple’s website here is using that same effect with the scrolling and animation and they are supposed to be all about accessibility. what do I say?? I’m trying to make the right call in terms of accessibility but also not unnecessarily restrict the designers. https://www.apple.com/mac-pro/
  19. [backwardok] I’ve had a similar thing come up to me several times, usually about Google, and my general response is that just because a company does something inaccessible doesn’t mean that it’s right, no matter how much they care about it
  20. [backwardok] and then point to an actual guideline that mentions the violation
  21. zakim-robot
    @zakim-robot
    Sep 15 21:22
    [caryn] @quidkid - I absolutely agree with @backwardok. Apple does a lot of things right, but their website is not one of them, unfortunately.
  22. zakim-robot
    @zakim-robot
    Sep 15 22:41
    [spell] Hi Gang! How would any of you markup the following to be as accessible as possible? Appreciate your insights! https://www.screencast.com/t/4zftLdh82mx
  23. zakim-robot
    @zakim-robot
    Sep 15 22:47
    [svinkle] @spell Is this static or dynamic, meaning someone can move the position of the blue pointer?
  24. zakim-robot
    @zakim-robot
    Sep 15 23:20
    [spell] Static.
  25. [spell] Upn submit, the graphic would update.
  26. zakim-robot
    @zakim-robot
    Sep 15 23:37
    [svinkle] @spell Initial thought would be ol +li with an aria-labelledby in order to describe what the list is for, along with aria-current="step" to denote where the user is in the process.
  27. [svinkle] And check the contrast ratio for the upcoming steps.
  28. [spell] @svinkle I like. aria-current is nice touch, too. Thank you! Okay on contrast. Thanks!