We did an accessibility audit on Radix UI and want to know what the best next step is.

[zoltan-dulac]

Good Afternoon.

I am a member of Publicis Sapient's Accessibility Center of Excellence, and since our front-end team is interested in using your library on client work, we decided to do an audit of it, testing the component library using a number of screen reader/browser pairs:

• Voicover/Safari on OSX and iOS
• NVDA/Firefox on Windows.
• Talkback/Chrome on Android.

We have a list of 35 accessibility issues that we would like to open. These are currently in a spreadsheet, but before we do the laborious job of cutting and pasting them into the Issues tab on this project's GitHub, we thought we'd better ask if this is the best way to give feedback, or if you'd like to review the spreadsheet first.

Please note that we may be able to fix these ourselves, but we have to allocate time and figure out budget for this. Before we do that, what say you on what the best next steps should be?

Please let us know: we are really eager to help if possible. Thanks for your consideration.

Zoltan.

[cusserycms]

Have the same questions as above

[BleedingDev]

Was there any outcome? :)

[lindelleric]

Any news on this?