Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Echarts native support for accessibility #28173

Open
frassinier opened this issue Apr 22, 2024 · 3 comments
Open

Echarts native support for accessibility #28173

frassinier opened this issue Apr 22, 2024 · 3 comments

Comments

@frassinier
Copy link
Contributor

frassinier commented Apr 22, 2024

Screenshot

image

Description

After setting aria.show to true, ECharts will automatically generate a description of the chart according to the title, chart, data, etc. Users can also set description manually through the configuration object.

Increasing accessibility support in Apache/Superset through enhanced a11y features, such as generating aria-label with Echarts, is crucial for ensuring inclusivity and usability for all users, including those with disabilities.

By adhering to WCAG guidelines and making adjustments to colors and patterns as required, we not only enhance the user experience for individuals with disabilities but also align with standards for accessibility, promoting a more inclusive and equitable platform for all users.

Apache/Echarts has built-in capabilities for describing charts.
Let's decide to enable this feature by default, promoting inclusive content for all users. Otherwise, it may be worth considering the implementation of a feature flag to provide flexibility and accommodate varying user preferences.

Design input

If we wish to take additional steps, we can also consider altering the pattern of each series, as illustrated in #28171 description

@villebro
Copy link
Member

@frassinier great feature request/POC! This is something we're eagerly hoping to support soon, but we need a mechanism for making it possible to enable/disable this type of functionality on a per-user basis. Please take a look at #28047 for more details.

@frassinier
Copy link
Contributor Author

@villebro Excellent! I like the idea of setting up a user preferences service!

@rusackas
Copy link
Member

Hah, just left a comment to that effect on the PR, but it looks like you beat me to the punch here :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants