CSS Flexbox can create a disconnect between the DOM order and visual presentation of content, causing keyboard navigation to break. For this reason, the CSS Flexible Box Layout module warns against resequencing content logic, but asking authors not to use flexbox in this way seems illogical in itself.
This is one of my favourite winter things. You can make it at any time of year of course, but there is something about the smell of apples and spices that makes me all warm and fuzzy. You might put that down to the cider, I couldn’t possibly comment…
The 12th in a series of posts that bring together the two sides of my blog: Food and technology. I’ve asked the great and the good from the web standards community to share their favourite recipes. This versatile dessert is from Adrian Roselli.
When a parent/child relationship is evident on-screen, but it isn’t represented in the DOM, the aria-owns attribute can be used to establish that relationship in the accessibility layer.
I don’t know who will read this. I don’t even know why it has suddenly become important to write it, but for whatever it’s worth, this is an account of an event in my life that changed everything.
When keyboard access doesn’t work, the Jaws screen reader makes it possible to explore content using simulated mouse movements instead. This function is broken in Firefox, due to changes made (some time ago) in its graphics rendering engine. This post describes a workaround that has proved successful for some.