What fresh hell is THIS now? - Patrick Lauke
[karlgroves] Thanks for sharing that @emplums
@mattbartist also check this out
http://blog.tenon.io/web-accessibility-in-high-risk-segments/
The flow chart makes the point clear: If you’re in a high-risk segment, chances are you’ll be making your site accessible eventually. Do it now and save money
[karlgroves] > It’s not a contract or anything legal, it’s just a formalized way of explaining the accessibility of your product to prospective clients
@emplums It becomes one. I’ve seen contracts go completely sideways for vendors when the VPAT is inaccurate. Then the purchaser says “Hey, you know how you said your form fields all had labels? Well, actually, here’s a bunch of form fields that aren’t labelled. Fix them”
[karlgroves] I’m obviously biased, but TPG. ;)
Any of the big 3 a11y firms have people on staff I’d trust to write a VPAT
translateX: 10px
, not translateX: -10px
) to move into the window when they receive focus.
overflow: hidden
on the <ul>
) and the rest are hidden (aria-hidden
) unless the user presses the next/previous buttons which triggers a translateX
on the list to bring them into view. On VoiceOver in Safari if the user tabs to focus on the "Next" button the VoiceOver cursor follows but this moves the list to the last element. And since technically the last focused element isn't really the last link in the list, the user can still press the "Next" button which causes the list to translate and show a bunch of empty space at the end. Does anyone know why this happens or if there's a way to avoid it? My guess is the Voiceover cursor moves to the end of the element before moving to the newly focused element but I can't find any information to verify.