Edge cases to consider when choosing or building bespoke UI components:

• keyboard navigation + Esc key behavior
• headless/overridable styles
• i18n
• screen reader support
• date pickers
• nested modals
• sorting/filtering/multiselect in comboboxes/data grids

What else?

Edge cases to consider when choosing or building bespoke UI components:

• keyboard navigation + Esc key behavior
• headless/overridable styles
• i18n
• screen reader support
• date pickers
• nested modals
• sorting/filtering/multiselect in comboboxes/data grids

What else?

https://youtu.be/9-6deom3ZdY

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

Any good standards or reference implementations for keyboard nav? I feel like it is MacOS v Windows but instead of two every website defines their own

“Developing a Keyboard Interface” from the ARIA Authoring Practices Guide (APG) is a great place to start.

They also have an index of example implementations with links to demos on CodePen.

Chaotic neutral technorati. Hard determinist machiavellian. Tight aggressive numbers man. Backbench electoral plumber. Black hat. Black tie. Damn good too

“Developing a Keyboard Interface” from the ARIA Authoring Practices Guide (APG) is a great place to start.

They also have an index of example implementations with links to demos on CodePen.

https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/

https://www.w3.org/WAI/ARIA/apg/example-index/