This adage has been "the first rule of ARIA" since the beginning.
There are a few ARIA "widgets" that have no HTML equivalent, such as Tabs or a spreadsheet-like Grid. Those are heavily documented so you can basically copy and paste whenever you need them.
Avoiding sprinkling ARIA on already-semantic HTML, because this can lead to confusing or inconsistent behaviors for the end user.
I'm a creative technologist with extensive experience building accessible, user-friendly digital products and tools. X-Apple. X-Google. 15+ years in tech.
Open to freelance work, employment, co-founder roles.
The joy of US "at-will" employment is that every company's Code of Conduct reserves the right to "separate" you for undermining mission alignment. The whole system is toxic.
You might consider the Accessibility Tree and its semantics. Plain divs are basically filtered out so you're left with interactive objects and some structural/layout cues.
This is a cool idea! At first I thought it was that they give you notes about what happened, and you have to process the information real-time and suggest practical improvements.
They do pick up the "title" attribute sometimes and apply it as a label. But it's not really the same as being able to keyboard navigate to the browser-generated tooltip.
Ex-Apple. Ex-Google. Creative technologist with extensive experience building for the web platform. Focused on crafting accessible, user-friendly digital products and tools.
> For instance, the Esc key does not close non-modal dialogs by default
Modal dialogs are the ones that pop up on the screen and take over the main experience. Those come with escape key. I think you have to program the click-away with JavaScript however.
Non-modal dialogs are uncommon, but basically they are more like menu pop-ups that can be ignored when open, so no need for escape key.