Hey Steve if Mike is still on that crazy hiring binge, P just sacked one of the most amazing a11y people I've worked with. Nobody knows why, except maybe she was highest on the pay scale...
In other news, the guy who wrote the SitePoint article about Baking Your Very Own Web Component where everyone kinda piled on because it wasn't even keyboardable, is nearing the completion of his Part 2, where he not only keyboards it but aria-ises the hell out of it. ...and it looks like it might even work somewhere for real! (combobox, not sure how good real support is...)
Yeah I happened to see another colleague in there, Kathy Wahlbin. Figured I'd better connect even though I only said hi to her for a hot minute at the booth.
I noticed Kathy (who's on all these W3C groups and does stuff with IAAP and 500 other things) has no mention of Pearson on her LinkedIn. Either removed or never added in the first place. She's been running her own business alongside so that's on there.
[oliviernourry]@stommepoes ah thanks! Yes, I work with Philippe Bron (technically he's my client, but all the same). Glad you saw his talk! We are striving to building an ecosystem to help people get a hold on accessibility, without being discouraged by the sheer number of hthings you need to know. It's an exciting job, even if not easy
I need to check and see how much user agent faking I'll need to do. I know some of them prevent you from visiting mobile if you're on a desktop/laptop.
@oliviernourry] I enjoyed Philippe's talk, he brought it without it getting dry, which is a skill if you ask me. I hope that perhaps he'll be able to speak on it at a Dutch event, which I've suggested, but I've not a lot of influence in that, other than having suggested him as a speaker.
it's got 2010 in the date, and no link to anything newer anywhere. This was after scrolling search results from MDN, W3Schools, and lots of personal blogs. Meanwhile, I need the most up to date source from the horse's mouth and that is not terribly googleable (or ddgable)
Someone should just hide all that old stuff somewhere so SEs can show only the latest (and I do not mean the latest wiki or github.io page, but the latest spec page)
That's what I teach: how to recognize recommended stuff versus outdated things or drafts. I do also sometimes forgot to check the status of the page I'm reading.
alt=screenshot fake twitter convo: browzrh8r says "IE Sucks!!!" and @IE replies "IE adopts an island of kittens and donates them to children everywhere!!! #Kids+KittiesRULE"
[sethkane] Do anyone have a sample image or a tool of what bad color contrast looks like to a visually disabled person? I know there are tons of color blindness overlays, plugins and such but when testing the ratio requirements it would be awesome to show people why it is so important to have the correct color contrast ratio. Thanks
[oliviernourry]@sethkane most of times I use the "cataract" filter of any tool out there (Colour contrast Analyzer has one that's pretty easy to use IMO). With poorly contrasted text, it's even harder to read blurred text.
@steveFaulkner is it only because it's semantically a span that this has no accessible name until we aria-label it? "The addition of a label, using aria-label, to the custom element provides an Accessible Name for the element."
The tequila example never made sense to me... I can't see any benefit to adding is=tequila-button. You already have a working button, and you can script whatever the hell you want on a button. I thought a <tequila-foobar> is something you make because what you want to make doesn't exist.
I also had hoped you could is="select" if your thingie was vaguely select-like, with a listbox attached to it... but you can't shadow-DOM things that already have their own shadow-DOM, so sad pandas there.
[karlgroves] <button is=tequila-button> should (ostensibly) inherit all methods & properties of the button element’s prototype and then also take on any additional/ modified methods & properties of the <tequila-button>
I feel like I'm the only one that finds the entire concept of Custom Elements problematic. Maybe it's just from working on a CMS for years and having to build out functionality to strip out tags that Microsoft Office would include in HTML markup back in the day, but I loved having a set of known HTML elements that were valid and anything else should be stripped away.
[lliskovoi] question: If HTML5 input types are used, should there be an additional error message when the field is filled out incorrectly since the messages in the pop-up aren’t read out by a screen reader (at least not VO)?
[simong] I’m working on a documention conversion tool (pdf -> semantic html) and one of the things it does is convert math expressions into mathml. Some of these expressions are identified with formula index/label (e.g., a number between parentheses to the right of the formula). Is there a right way of combining the mathml expression and the "formula label” ?