Professional web designer on a closed course. Do not attempt.
This is a great HTML boilerplate, with an explanation of every line.
I remember discussing this with Tantek years ago:
There are a few elements who need to be placed inside of another specific element in order to function properly.
If I recall, he was considering writing “HTML: The Good Parts”.
Anyway, I can relate to what Eric is saying here about web components. My take is that web components give developers a power that previous only browser makers had. That’s very liberating, but it should come with a commensurate weight of responsibility. I fear that we will see this power wielded without sufficient responsibility.
Receive one email a day for 30 days, each featuring at least one HTML element.
Right up my alley!
A good tutorial on making password fields accessible when you’ve got the option to show and hide the input.
I really like the approach that Carie takes here. Instead of pointing to specific patterns to use, she provides a framework for evaluating technology. Solutions come and go but this kind of critical thinking is a long-lasting skill.
I really enjoyed this 20 minute chat with Eric and Rachel all about web standards, browsers, HTML and CSS.
It’s official. The extremely niche browser behaviour I documented is a bug.
I like this proposal, and I like that it’s polyfillable (which is a perfectly cromulent word).
I’m very taken with Github’s tab-container element—this is exactly how I think web components should be designed!
This is handy—an up-to-date list of tests run on form fields with different combinations of screen readers and browsers.
These definitions work for me:
I love the story that Terence relates here. It reminds me of all the fantastic work that Anna did documenting game console browsers.
An excellent collection of advice and examples for making websites responsive and accessibile (responsive + accessible = responsible).
A minimal style sheet that applies some simple rules to HTML elements so you can take a regular web page and drop in this CSS to spruce it up a bit.
Heydon’s newest short video is right up my alley.
My stack requires no maintenance, has perfect Lighthouse scores, will never have any security vulnerability, is based on open standards, is portable, has an instant dev loop, has no build step and… will outlive any other stack.
I like this proposal for a declarative Ajax pattern. It’s relatively straightforward to polyfill, although backward-compatibility is an issue because of existing browser behaviour with the