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
Is your feature request related to a problem? Please describe.
Some screen reader users might be interested in having a description of what the chart looks like. This might help them better create a mental model of the visualization.
Describe your proposed solution
Given the chart type passed in type, AutoVizuA11y defines what explanation (from a set of predefined explanations) to give to the user. This explanation should be optionally provided, heard after pressing a new shortcut. We believe this new explanation should also be customizable by the Developer, but having some options already available eases the implementation process.
Describe alternatives you've considered
Only this solution was considered.
Additional context
This idea came from suggestions given during the usability test conducted with screen reader users. The proposed solution was inspired from the following paper: https://dl.acm.org/doi/abs/10.1145/3544548.3581139
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Some screen reader users might be interested in having a description of what the chart looks like. This might help them better create a mental model of the visualization.
Describe your proposed solution
Given the chart type passed in
type
, AutoVizuA11y defines what explanation (from a set of predefined explanations) to give to the user. This explanation should be optionally provided, heard after pressing a new shortcut. We believe this new explanation should also be customizable by the Developer, but having some options already available eases the implementation process.Describe alternatives you've considered
Only this solution was considered.
Additional context
This idea came from suggestions given during the usability test conducted with screen reader users. The proposed solution was inspired from the following paper: https://dl.acm.org/doi/abs/10.1145/3544548.3581139
The text was updated successfully, but these errors were encountered: