I've decided to monetize this website using Web Monetization and become a Coil member because I've had enough of intrusive online advertising, tracking, and having my personal information bought and sold across the web.
When a table is created with appropriate HTML elements or ARIA roles, screen readers can inform users about table characteristics and provide keyboard commands for navigating tabular content.
Emoji help us communicate complex ideas easily, but on the web we need to make sure everyone can understand them — screen readers don't always recognise emoji without the right markup.
The word "semantic" is regularly used in web development, but what do we really mean by it, and why does it matter for structure and meaning?
CSS Flexbox can create a disconnect between DOM order and visual presentation, breaking keyboard navigation. I explore why asking authors not to use flexbox this way seems illogical.
Sometimes parent/child relationships are evident on-screen but missing from the DOM; the `aria-owns` attribute can establish that relationship in the accessibility layer, though screen reader support remains inconsistent.
Many websites provide keyboard shortcuts for common tasks, but the way they're delivered using JavaScript is problematic for Windows screen reader users because the screen reader intercepts the keys.
I've been looking into how browsers and screen readers handle content generated with CSS before/after pseudo-selectors, and whether it's actually accessible to everyone.
Search engines struggle to extract meaning from web content because information is presented so many different ways, but marking it up using schema.org vocabularies makes it easier and is very straightforward to do.
I've written about making session timeout warnings accessible to all users, including those using assistive technologies like screen readers, by moving keyboard focus to the notification and using proper ARIA attributes.