This is everything I posted in: code
Element.scrollIntoView takes as its argument either a boolean value or an object. The object syntax gives more alignment capabilities and smooth scroll, but it works in less browsers.
In cards, you could use grid tracks instead of padding.
Heading structures give screenreader users and others a table of contents for our sites. By being conscious of that, we can make better choices about heading levels and their contents.
display: contents, we can have more accessible markup for our CSS Grids. One caveat: supporting browsers currently break this.
Alternative text is a great opportunity to make the non-text parts of the web accessible. However, look out for redundancy, and only add it when it conveys something that isn’t already there.
The benefits and downsides of providing a fallback for the aria-expanded attribute, and why it is now best to not provide a fallback at all.
Some tips for building password manager proof login forms.
A trick to build a file upload control that uses a native input element, but looks custom.
Today I learned about the sequential focus navigation starting point, which helps browsers decide what to do with focus when you link to content that is not focusable
This is how to temporarily trap focus in an element, a functionality that can be used to make modal interface elements more accessible.