-
Notifications
You must be signed in to change notification settings - Fork 26
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
Accessibility improvements - Visibility and navigation #4720
Accessibility improvements - Visibility and navigation #4720
Comments
2.1.1 is fixed/solved by the changes of #4717. The close button is now an actual button element |
For WCAG 2.4.3 Focus Order we might have some issues. Various elements change in order when resizing the view (or when you increase the zoom on the browser). These order changes are only visual, meaning that the tab-order follows the order of the DOM. This results into an unexpected tab-order. Elements that are involved:
The easiest solution would be to prevent/remove the order changes, but this will have an impact on the UI |
2.4.7 the skiplink is now the first focusable element in the dom tree. When this element receives focus, it will be shown |
2.4.2 The form name is now part of the submission report PDF filename. Changes for the page titles still needs to happen |
…the form step pages
…the form step pages
…ia-label The added context doesn't add anything for users that don't use screenreaders. So the additional context should only be used when it is needed
…ia-label The added context doesn't add anything for users that don't use screenreaders. So the additional context should only be used when it is needed
Thema / Theme
Frontend
Omschrijving / Description
This issue is related to #4622
This issue targets the visibility and navigation improvements of the accessibility rapport:
Added value / Toegevoegde waarde
No response
Aanvullende opmerkingen / Additional context
No response
The text was updated successfully, but these errors were encountered: