Toegankelijkheidsverbeteringen Q1-2025

[joeribekker]

Versie: 2.6.13

Ruwe eerste inschattingen op basis van rapport (op te vragen bij Joeri).

• 1.3.1 Info en relaties (3 dagen)
• 1.3.5 Identificeer het doel van de input (config?)
• 1.4.11 Contrast van niet-tekstuele content (config? maar wellicht betere default)
  2.5.3 Label in naam (zelfde als 1.3.1?)
• Accessibility improvements - Form fields #4716

• 1.1.1 Niet-tekstuele content (1 uur)
• 4.1.2 Naam, rol, waarde (formio, echt geen idee)
• 4.1.3 Statusberichten (4 uur)
• Accessibility improvements - Aria tags #4717

• 1.4.3 Contrast (2 uur)
• 1.4.4 Herschalen van tekst (3 dagen)
• 1.4.10 Reflow (3 dagen)
• Accessibility improvements - Textual #4718

• 3.3.1 Fout identificatie (6 uur)
• 3.3.2 Labels of instructies (config? maar niet zeker, dacht dat we "j" voor jaar gebruikten in NL)
• 3.3.3
• Accessibility improvements - Error and help messages #4719

• 2.1.1 Modal sluit knop
• 2.4.1 Skiplink
• 2.4.4 Linkdoel
• 2.4.6 Koppen en labels (2 dagen)
• 2.4.7 Focus zichtbaar (4 uur)
• Accessibility improvements - Visibility and navigation #4720

Totaal: 13 dagen werk

[robinmolen]

The accessibility improvements will be resolved in dedicated issues:

• Accessibility improvements - Form fields #4716
• Accessibility improvements - Aria tags #4717
• Accessibility improvements - Textual #4718
• Accessibility improvements - Error and help messages #4719
• Accessibility improvements - Visibility and navigation #4720

[joeribekker]

@robinmolen can you edit the original ticket and hang them below the relevant bullet?

[robinmolen]

Issue 2.5.3 is about the datepicker inputs that currently aren't connected to their labels. I've discussed this issue with Sergei, and we came to the conclusion that this issues cannot be resolved at this time.

The current datepicker (flatpickr) has some accessibility issues that we cannot solve. In the future, if/when we can use the pure React datepicker, this issue will be solved. Unfortunately we can't do anything at this time

[sergei-maertens]

Can't estimate without having seen the accessiblity report(s)

[robinmolen]

November 26th a new Accessibility test was performed which resulted into a new rapport. Most items in this rapport are 'small' improvements (color contrasts, changing html elements), but there are also a couple 'larger' issues. The list below contains the rapported accessibilty items, which I've tests with the macOS VoiceOver screenreader:

Improvements that should be relatively simple:

• 1.1.1 (non-textual content) The logo in the pdf contains a textual alternative, but cannot be accessed.
• 1.3.1 (information and relations) Missing relations between (submission rapport) PDF field labels and values.
• 1.3.1 (information and relations) When a (submission rapport) PDF field doesn't have a values, we should provide a "No information provided" alternative. (This is to ensure that users understand that a field was left empty)
• 1.4.3 (color contrast) Error messages have a contrast of 3,7:1. This should be 4,5:1
• 1.4.11 (non-textual color contrast) Checkbox and radio button borders have a contrast of 2,9:1. This should be 3,0:1
• 2.1.1 (navigation - keyboard) Tooltip cannot be accessed by screen readers
• 2.4.2 (navigation - page title) The title in the PDF meta description contains leading and trailing whitespace
• 3.1.2 (language) Some texts are non translatable. The rapport mentions the title of the select component delete button.
• 4.1.2 (name, role, value) The dropdown variant of the progress menu doesn't contain aria-expanded information

All these smaller improvements should be completable in around 3 days

Improvements that are a bit more complicated:

• 2.4.7 (navigation - focus visibility) When the form is displayed on a small screen, or greatly zoomed-in, the progress menu will be shown as a dropdown menu. When you focus any menu items in the dropdown, and repeatable press the tab key, you can place the focus outside the menu. The menu stays expended, resulting in the focused element not being visible.
  This might required some major re-writing.
  Could take a couple of days
• 3.3.3 (error suggestion) When a specific input pattern is expected, the error message should provide the expected format or an example.
  With examples in the error messages this could be resolved in 1 day.
• 4.1.2 (name, role, value) The select component contains problems with name and role on the select element, aria-selected="true" on the parent div, missing aria tags
  This could be resolved in 2 days (It could be that we cannot fix the issues for this component. Lets start with a time-box of 1/2 day, and assess from there)
• 4.1.3 (status messages) The loading spinners have issues with aria-live which results into status updates not being announced
  This could be resolved in about 1 week

Estimate (including previously done work): 6 weeks