This ticket list the tasks required to meet the Level A of the WCAG accessibility guide lines:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Build a first version of the alternative text that describe how the chart is composed alone those lines:
The chart is titled NNN, is an histogram chart with 3 different stacked series: series A, series B and series C.
The chart has an X axis interval from May 10th to May 25th 2020.
The chart has a Y axis interval from 0 to 100.
The series A has 10 different values, from a min of 4 to a max of 10, average of 6.
The series B has 10 different values, from a min of 10 to a max of 40, average of 20.
The series C has 10 different values, from a min of 2 to a max of 30, average of 10.
If during a preparatory investigation we found that this approach is too complex and lead us to an higher complexity we should pivot the decision toward a basic table rendering of the chart.
Provide alternatives for time-based media.
N/A
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
The legend should use semantic markup to describe its structure. #613
Make it easier for users to see and hear content including separating foreground from background.
N/A we are not conveying content using colors
#589
Make all functionality available from a keyboard.
The legend should be accessible from the keyboard. The chart itself will not be make accessible with the keyboard due to the technical difficulties and efforts to make an image like that accessible from the keyboard. On a second stage (TODO add step 2 ticket) some efforts will go in that direction.
Provide users enough time to read and use content.
N/A
Do not design content in a way that is known to cause seizures or physical reactions.
There isn't flashing mechanism in the chart renderer, although moving your mouse over the legend or the chart cause the chart elements to fade in/out depending on the hovered elements. This can cause quick flesh if you are moving your mouse too quickly but we should investigate if this is considered as a failure or not
Provide ways to help users navigate, find content, and determine where they are.
This should be tackled together with G2.1 on the legend. #613
Make it easier for users to operate functionality through various inputs beyond keyboard.
Make text content readable and understandable.
NA, the language of the page is already configured by Kibana or shall be configured by the chart consumer
Make Web pages appear and operate in predictable ways.
Help users avoid and correct mistakes.
We display some errors, specially when hiding all the series or when there is no data input. We should fix the possible guideline failures on in these cases.
Maximize compatibility with current and future user agents, including assistive technologies.
Check markup compatibility to meet the criteria
This ticket list the tasks required to meet the Level A of the WCAG accessibility guide lines:
Build a first version of the alternative text that describe how the chart is composed alone those lines:
If during a preparatory investigation we found that this approach is too complex and lead us to an higher complexity we should pivot the decision toward a basic table rendering of the chart.
N/A
The legend should use semantic markup to describe its structure. #613
N/A we are not conveying content using colors
#589
The legend should be accessible from the keyboard. The chart itself will not be make accessible with the keyboard due to the technical difficulties and efforts to make an image like that accessible from the keyboard. On a second stage (TODO add step 2 ticket) some efforts will go in that direction.
N/A
There isn't flashing mechanism in the chart renderer, although moving your mouse over the legend or the chart cause the chart elements to fade in/out depending on the hovered elements. This can cause quick flesh if you are moving your mouse too quickly but we should investigate if this is considered as a failure or not
This should be tackled together with G2.1 on the legend. #613
add the
Abort or Undoon brushGuideline 3.1 – Readable
NA, the language of the page is already configured by Kibana or shall be configured by the chart consumer
We display some errors, specially when hiding all the series or when there is no data input. We should fix the possible guideline failures on in these cases.
Check markup compatibility to meet the criteria