Hi, there,
We have several API references generated using Swagger UI. At the moment, we are improving accessibility of those references. As the majority of the UI cannot be customised by us, do you have a statement about how Swagger UI supports accessibility guidelines WCAG 2.1?
Hi Astro-Choco
I'm not sure we have an official WCAG policy, but we do track accessibility (a11y) and are actively improving as much as we can in that space. If you're interested in the progress you can look at the `cat: a11y` label in GitHub issues: https://github.com/swagger-api/swagger-ui/issues?q=is%3Aopen+is%3Aissue+label%3A%22cat%3A+a11y%22
As for customization, it should be possible to customize any of the UI elements you require, there is a flexible plugin system that allows for this. To learn more about it, take a look at https://github.com/swagger-api/swagger-ui/blob/master/docs/customization/overview.md.
As for the WCAG statement, are you aware of any statements in Open Source that we can forward to the team to take a look at?
Hi ponelat,
Thank you for helping out. 🙂 GitHub has some statement of support for WCAG 2.1: https://government.github.com/accessibility/.
Would you help forward to the team?
