Michail Yasonik

The current structure is something along the lines of: ``` Tab name Tab content ``` To work with assistive tech, it needs to have a structure similar to what I...

If an accessible implementation of tabs is not feasible, 3 things can be improved to mitigate some problems: 1. Add a focus state to the `` (to highlight the associated...

> Is this true for the alternate style that is available? Are you aware of the alternate style vs the default? Hadn't seen it before but just checked it out...

Just to elaborate a bit further: Making a truly accessible canvas is... difficult. And currently a lot of the tools to do so seem to be experimental (namely, [hit regions](https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/Tutorial/Hit_regions_and_accessibility)...

Ah, I totally forgot we already support a `isLoading` prop! Updated the issue for our existing setup.

1. Sibling to the button, not inside (all button contents is collapsed into a simplified role that's plain text "button content" so we can't have anything inside. 2. Yes! (Well,...

I can't think of a way to not add a `` to all buttons while also not introducing any new props or components...

Scott O'Hara's great! Thanks for finding that! If we want to move towards an alternate solution like he suggests, I can draft up an example of what we could do....

It's not an ideal situation but it's a big, old codebase so there are layers of deprecated library choices, WIP migrations, and many teams. In an ideal state we wouldn't...

We were thinking that using the `attributes` config as is could be dangerous because wouldn't that mean that defining something like `to: href` would mean you can't have a `to`...