Gitter Channel Archive 3rd of December 2015
Gitter Channel Archive 3rd of December 2015
What fresh hell is THIS now? - Patrick Lauke
<h1> thing to bypass the header and navigation”: I’m going to suggest that, yes, it meets 2.4.1, but it’s essentially the same as auto-focussing on the search box on a page because the designer/developer has made the assumption that that’s what all users will obviously be doing on that page. A much better approach would be to either have a skip link, consistently use the <main> element correctly or consistently use one <h1> element at the the beginning of the page’s content as per H69 (http://www.w3.org/TR/2015/NOTE-WCAG20-TECHS-20150226/H69)
but maybe I'm an unusuallystupid user
Meh, could say the same for me.
<h1> so it must be JavaScript.
[karlgroves] > I'm also going to explain how to use a screen reader!
That would be useful. Esp. if you were to show specific approaches to testing in terms of what to expect and what failures look (sound?) like.
[karlgroves] @collumacrae That’s kind of the challenge, right? I’ve been doing testing for > a decade and I still have to use cheat sheets to use screen readers.
@dna I think @michiel got it right. I use VO and the web rotor pretty often. I also do use JAWS and NVDA but they’re just for spot checking.
Didn
[karlgroves] @callumacrae: I didn’t mean to dissuade you by posting that WebAIM article. You may have an interesting perspective.
For instance, a really quick way to check alt attributes is to use the rotor to list all images. Does each one make sense? See any weird stuff like filenames?
<button><span>Add</span> to basket</button> & button span { text-transform: uppercase; } ?
<button>ADD to basket</button>? Is that what you mean?
<button>Add to basket</button>, uppercased using CSS
[karlgroves] > It's absolutely a bug somewhere,
Yeah, the browser
[karlgroves] > Happens in both Chrome and Safari
Legacy Webkit crap is doing it.