Marcy Sutton-Todd

It's a bummer that React Router still doesn't handle focus at all. Is that going to be addressed soon? Sending focus to a wrapper element or a heading would be...

That post is from May 2019, and it's almost 2021–hence my comment. Given @ryanflorence's past commitment to accessibility including Reach UI and Reach Router, I'd hope the React Training team...

I get this same warning with Webpack 4 and Cypress Component Testing. I wasn't encouraged much by the related thread on the axe-core repo but I can confirm the webpack...

:+1: This is feeling a bit like a healthier take on ngAria....I love your thinking here!

I did some reaching out online for use cases on Wilco's suggestion; not exactly scientific but there are some great insights in this thread, particularly from James Teh and Marco...

# application-role-inaccessible-content - **description:** Ensures the ARIA application role is used effectively to not hinder navigation of content with assistive technologies - **help:** role application should not create inaccessible content...

To capture what we just discussed as a team: I like this idea, however it isn't straight-forward to do. The CSS can come from anywhere, and the accessible name calculation...

This issue comes up a lot....we did some enforcement of labeling in [Angular Material](https://github.com/angular/material) by attempting to create an `aria-label` from text (applicable to custom form controls which require some...

Yes–I'd like to avoid guesswork as well. We should outline specific use cases and try to learn from previous implementations so this library doesn't make the same mistakes. What gave...

Focusability is pretty all over the place for those controls in browsers though, I think we need to do some testing to determine support.