4.1.2.A. Improve the aria-label attribute of used_filters panel button and accessibility support (high)
As a screen reader user,
I want accessibility tags to be applied correctly to all buttons and dataflow filters,
So that the screen readers can announce appropriate and useful information.
e.g. aria labels should be used for dataflow filter so that a screen reader will read the number of applied and available filters
Issue | Examples | Description | Code used | Recommendation |
---|---|---|---|---|
25 | .Stat Data Explorer (BETA) • Regional Statistics, LGA 2017, 2011-2017 | Buttons in filters have been given aria-labels and properties which describe their functionality. For sighted users, the amount of filters available and being used is presented. The aria labels do not include this information. So screen reader users do not have access to the same information as sighted users. | Ensure the number information is included as part of the aria label. Additionally, add further text to ensure the number is understandable in this context. Alternatively, remove the 'aria-label' attribute from the button. This means the button content will be read by screen readers instead of the aria-label value. |
|
26 | .Stat Data Explorer (BETA) | Visually, it is clear that the button disables accessibly support, as this is displayed on mouseover and keyboard focus; however, in the markup, the button is implemented as "pressed" and this communicates that accessibility support is disabled (as opposed to becoming disabled when the button is clicked). So screen reader users think that clicking the button turns the accessibility support on. |
should be already implemented --> to be verified Change the aria-label of the button to "Accessibility support". The 'aria-pressed' attribute will then communicate if the support is activated or not. |
Edited by Jens Dossé