Clickable Confusion with NVDA
Read ArticleUnderstanding why non-interactive Storybook components are often announced as clickable by NVDA and other screenreaders.
theAdhocracy
Understanding why non-interactive Storybook components are often announced as clickable by NVDA and other screenreaders.
Notes from the fully remote React Summit 2020 (or at least the talks I tuned in for). Lots covered, from static-site generators and the Jamstack through to React state management and accessibility. What a fun day!
The search page is live, the index is populated, but it all looked a bit rubbish and it didn't quite work as well as I wanted. Now it's using custom-styled components, queries are tracked/stored via the URL for persistence, and you can filter results based on category.
YouTube embeds can be expensive on page load metrics, but what alternative is there? How about loading a thumbnail that hot-swaps itself for an <iframe> when clicked? Sounds great, but wouldn't …
Another month, another big and fully remote JavaScript conference. JSNation fit into my schedule a little less (and didn't quite overlap with my interests as neatly) but it was a fun event with some interesting talks on topics that are often only on my periphery. Much to think about!
Apparently, ARIA live regions don't play nicely with React. Whilst they work fine in many browsers, they simply don't function in VoiceOver without some workarounds.
An extremely detailed overview of how to use the native <dialog> element in React to build a state-driven modal component. As ever, the answer is significantly more complicated than it would be …