Carolyn MacLeod
Carolyn MacLeod
Done - see https://github.com/w3c/aria/pull/1351 Decided to split out the "authors MUST/MUST NOT" into a separate paragraph to make it stand out more (instead of just adding new sentences to the...
Now that ARIA 1.2 is CR and says authors MUST give form a name (not just SHOULD, as in ARIA 1.1), I will provide a PR for this issue. The...
I guess they're a lot like "Clickable Tiles", but with a different look.
On a similar topic, the 4 clickable tiles on the overview page: Carbon Design Kit, Carbon Components, Carbon CodePen, and Theming Sandbox have a slightly different problem. Looking at the...
> We could be more explicit about such limitations in a note in the menu button pattern ... This is a good idea.
Typical keyboard interaction for a custom component is to use the TAB key (and SHIFT+TAB) to navigate into and out of the component, and to use arrow keys (UP, DOWN,...
@patrickhlauke > Regarding complexity of F6 (and CTRL + TAB) is the concern mainly about hijacking native browser functionality via preventDefault()ing? Probably. :) My 2c: - I think hijacking CTRL...
More reading from other past `aria-controls` discussion: https://github.com/w3c/aria/issues/716
I have been told that a menu button inside a scrollable table can have its menu clipped if the button and the menu are siblings (i.e. if the menu is...
Hi, @LJWatson! > Do we have any data on why it was never implemented in other screen readers? I found a [request to support aria-controls navigation in NVDA](https://github.com/nvaccess/nvda/issues/8983), but there's...