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

Show a warning for non accessible charts for screen readers #13573

Merged
merged 2 commits into from
Aug 22, 2017

Conversation

timroes
Copy link
Contributor

@timroes timroes commented Aug 18, 2017

Since making charts accessible in general (#11842) is quite some task, I moved it to phase 2. For phase 1 (6.0) we can just show a warning for non accessible charts. We can use this also to mark individual visualization types as accessible.

Fix #13572

@timroes timroes added Project:Accessibility Feature:Vislib Vislib chart implementation Feature:Visualizations Generic visualization features (in case no more specific feature label is available) bug Fixes for quality problems that affect the customer experience labels Aug 18, 2017
@timroes timroes merged commit 5514f34 into elastic:master Aug 22, 2017
@timroes timroes deleted the visualize-a11y branch August 22, 2017 09:25
timroes added a commit that referenced this pull request Aug 22, 2017
* Show warning for non accessible visualizations, fix 13572

* Mark markdown vis as accessible
timroes added a commit that referenced this pull request Aug 22, 2017
* Show warning for non accessible visualizations, fix 13572

* Mark markdown vis as accessible
@timroes
Copy link
Contributor Author

timroes commented Aug 22, 2017

Backports:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Vislib Vislib chart implementation Feature:Visualizations Generic visualization features (in case no more specific feature label is available) Project:Accessibility v6.0.0-rc1 v6.0.0 v7.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants