This is everything I posted in: code
Some attributes in ARIA are boolean(-like). These attributes may seem a lot like boolean attributes in HTML, but there are some important differences to be aware of.
I’ve released the code I use to generate WCAG conformance reports using the Eleventy static site generator. Here’s some context.
So that I could control what and how to display.
Why and how the right HTML elements can improve the user experience of people that use assistive technologies.
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.
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.
Protip for working on WordPress sites using a slow connection
In which I describe how to do progressive enhancement by declaring handler and enhancer functions on HTML elements.
In which I show a trick to embed videos responsively and how to make it work with Wordpress.
Explaining two ways of adding icons whilst offering a basic alternative.