Skip to content
This repository has been archived by the owner on Mar 27, 2023. It is now read-only.

Accessibility Issues

Jeremy Wilken edited this page Jan 18, 2022 · 2 revisions

Clarity is managed by a team at VMware, and we work closely with our internal accessibility experts to triage and track accessibility issues. We maintain a list of reported issues internally, not on GitHub, so we can have a single view of reports that has input from our experts.

If you work at VMware

If you are part of VMware, please do not submit a bug report to Clarity on GitHub. Instead, please make sure that your issue is linked to a Clarity issue and work with your accessibility partner if you have questions. If you have other questions or need additional support from us, please use our Slack support channel #clarity-support instead of filing issues or discussions here.

This helps us see the related issues across the organization, and if we determine an issue is from a product we'll close the GitHub issue. It is hard to track which issues in GitHub are related to products due to anonymity of users, not knowing what products they are related to, and so forth.

If you don't work at VMware

If you are not part of VMware and have an accessibility issue to raise, please post it as a new bug report and we'll pass it along to our accessibility partners to review. We may close the issue after it has been confirmed so we maintain one list of the reports.