It was difficult to come in thinking I was a senior developer and instead feeling like a junior. I often spent more time than I should have on my own just trying to understand things, frustrating myself in the process. I’d go a day or two or three of making no progress before reaching out to someone to explain something I didn’t understand but feeling like I should, feeling like I wasn’t good enough.
I could quote every line of this article. I can’t tell you how much it resonates with my own experiences this year.
When a button picks up the [disabled] attribute, focus shifts from the button to the document. For screen reader users, this triggers an announcement. For people who use the keyboard to navigate (both screen reader users and sighted users), they’re now no longer in the field they were working in and might be disoriented. Fortunately, there’s a relative easy, better approach.
When Chris Coyier asked me to look at the font loading behavior for the new redesign of CSS-Tricks, I’ll admit that I was excited. A new case study on a web site with an intimidating, exhaustive, encyclopedic amount of existing web development content!
This article marks the third time I try to create a useful menu pattern for accessible-app - but hopefully the third time’s the charm. But before I explain the (hopefully) final and correct menu solution let’s look back to past trails and (eventually failed) implementations.