You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, Swagger UI team! I'm an accessibility engineer working for a federal contractor, and we use Swagger UI in our open data websites, like https://data.medicaid.gov/api.
Having worked on big open source projects in the past, I sympathize with a 1k issue backlog. At the same time, our clients and users (and ultimately your entire community of users) would benefit immensely from these updates, many of which appear to be straightforward markup fixes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, Swagger UI team! I'm an accessibility engineer working for a federal contractor, and we use Swagger UI in our open data websites, like https://data.medicaid.gov/api.
I've been following the issues and discussions here, and it's unclear to me where accessibility falls on your list of priorities. A few folks have been diligently logging issues over the past few years, most recently
this rock star: https://github.com/swagger-api/swagger-ui/issues?q=is%3Aissue+is%3Aopen+accessibility+author%3Acjfreedman. Update 8/13/24: It looks like the author of those issues deleted their account. See this link instead: https://github.com/swagger-api/swagger-ui/issues?q=is%3Aissue+is%3Aopen+accessibilityHaving worked on big open source projects in the past, I sympathize with a 1k issue backlog. At the same time, our clients and users (and ultimately your entire community of users) would benefit immensely from these updates, many of which appear to be straightforward markup fixes.
Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions