V7: Video Killed the Web Browser Star | Rob Weychert
Grrr… it turns out that browsers exhibit some very frustrating behaviour when it comes to the video element. Rob has the details…
I’ve already add the search element to thesession.org, but while browser support is still rolling out, I’m being extra verbose:
<search role="search">
...
</search>
Brought to you by the department of redunancy department.
I’ll remove the ARIA role once browsers are all on board. As Scott says:
Please be aware that this element landing in the HTML spec today does not mean it is available in browsers today. Issues have been filed to implement the search element in the major browsers, including the necessary accessibility mappings. Keep this in mind before you get all super excited and willy nilly add this new element to your pages.
Grrr… it turns out that browsers exhibit some very frustrating behaviour when it comes to the video element. Rob has the details…
I enjoyed this self-documenting journey of exploration.
Receive one email a day for 30 days, each featuring at least one HTML element.
Right up my alley!
I’m very taken with Github’s tab-container element—this is exactly how I think web components should be designed!
You’re not going to get a Webby Award or thousands of views on Codepen for how amazingly crafted your HTML is. You’ll need to be OK going unrecognized for your work. But know that every time I use a screen reader or keyboard on a site and it works correctly, I have a little spark of joy.
You might want to use `display: contents` …maybe.
is=”too-hard”
Extending the wheel, instead of reinventing it.
An exception to my general rule that ARIA attributes should be added with JavaScript.
Abstracting common interaction patterns as a starting point for accessible components.