WCAG 2.2 AA Sub-study on form content for the Municipality of Wierden

This report describes the results of the sub-study on the accessibility of the content of the forms on wierden.nl
. The study was conducted in accordance with WCAG 2.2 Levels A and AA (EN 301 549), using the WCAG-EM evaluation method.
 

Logo of the Municipality of Wierden

Summary

This study was conducted by Shift2 between March 9, 2026, and March 23, 2026, on behalf of the municipality of Wierden. For this sub-study, a representative sample was compiled from three forms comprising a total of nine process steps with varying characteristics and levels of complexity.

The content reviewed does not fully comply with WCAG 2.2 Levels A and AA.

In this sub-study, 30 success criteria were evaluated. Twenty-six of these 30 success criteria (87%) were met. Deviations were identified in 4 success criteria.

The pages reviewed are generally accessible. Headings, labels, link text, and interactive elements are used correctly and consistently.

The main issues relate to missing input instructions. For fields such as "Zip Code and City" and "Bride and Groom's Names," it is not clear to users exactly what is expected. Additionally, autofill support is not configured correctly on several forms. This particularly affects users with motor impairments or dyslexia.

In 2 out of 3 forms, the step title repeats the form’s name instead of describing the step’s content. This makes it difficult for users of screen readers to navigate using headings.

We recommend periodically reviewing content for recurring patterns of accessibility issues and ensuring accessibility is systematically incorporated into the management and publication process for forms.

About this study

A partial audit was conducted on the accessibility of the content in the Shift2 environment to determine the extent to which it complies with WCAG 2.2 Levels A and AA (EN 301 549).

This research report is valid for a maximum of three years. In the event of substantial changes to the content or the publication process, we recommend commissioning a supplementary or new study.

Scope of the sub-study

This sub-study focuses exclusively on the content of the forms within the Shift2 environment that the organization can enter or modify via the management system.

This study evaluated 30 of the 55 success criteria of WCAG 2.2 Levels A and AA.

The remaining 25 success criteria relate to the technical aspects of the forms and are evaluated in the separate technical sub-study.

Together, these two sub-studies constitute the complete assessment of the forms within the Shift2 environment.

Success criteria assessed in the technical sub-study

The following success criteria were not evaluated in this content study and are covered in the separate technical sub-study:

SCNameLevelReason for exclusion
3.3.1Error identificationAForm validation is handled entirely by the system
3.3.3Suggested correctionAAError suggestions are generated by the system
3.3.7Unnecessary importsAThe reuse of previously entered data within processes is technically enabled within the platform and is managed centrally.

Scope and Methodology

The study was conducted using a representative sample of forms within the Shift2 environment. Within this sample, the accessibility issues identified were described as specifically as possible, including references to the relevant form or form section. Where possible, recommendations were included to address the issues.

This study does not provide an exhaustive overview of all possible accessibility issues. The findings represent a snapshot of the situation at the time of the study.

What is WCAG?

WCAG (Web Content Accessibility Guidelines) are internationally recognized guidelines for digital accessibility, based on four principles: Perceivable, Operable, Understandable, and Robust. Measurable success criteria have been established within these principles.More information: WCAG 2.2 (Dutch translation)

Summary of results

The results are presented in two tables: by success criterion and by WCAG principle.

Results by success criterion

Success criterion

Level

Result

1.1.1 Non-textual content

A

Meets the requirements

1.2.1 Audio-only and video-only (pre-recorded)

A

Not available

1.1.1 Non-textual content

A

Meets the requirements

1.2.1 Audio-only and video-only (pre-recorded)

A

Not available

1.2.2 Captions for the deaf and hard of hearing (pre-recorded)

A

Not available

1.2.3 Audio description or media alternative (pre-recorded)

A

Not available

1.2.4 Captions for the Deaf and Hard of Hearing (live)

AA

Not available

1.2.5 Audio description (pre-recorded)

AA

Not available

1.3.1 Information and Relationships

A

Meets the requirements

1.3.2 Meaningful order

A

Meets the requirements

1.3.3 Sensory properties

A

Meets the requirements

1.3.5 Identify the purpose of the input

AA

Does not meet the requirements

1.4.1 Use of color

A

Meets the requirements

1.4.2 Sound Controls

A

Meets the requirements

1.4.3 Contrast (minimum)

AA

Meets the requirements

1.4.5 Images of text

AA

Meets the requirements

1.4.10 Reflow

AA

Meets the requirements

1.4.11 Contrast of non-textual content

AA

Meets the requirements

2.1.2 No keyboard drop

A

Meets the requirements

2.1.4 Single-character keyboard shortcuts

A

Not available

2.2.2 Pause, stop, or hide

A

Not available

2.3.1 Three flashes or below the threshold value

A

Meets the requirements

2.4.2 Page Title

A

Meets the requirements

2.4.4 Link target (in context)

A

Meets the requirements

2.4.6 Headings and labels

AA

Does not meet the requirements

2.5.3 Label in the name

A

Meets the requirements

2.5.8 Size of the selection area (minimum)

AA

Meets the requirements

3.1.1 Page Language

A

Meets the requirements

3.1.2 Language of components

AA

Meets the requirements

3.2.4 Consistent identification

AA

Meets the requirements

3.3.2 Labels or instructions

A

Does not meet the requirements

4.1.2 Name, role, and value

A

Does not meet the requirements

Research scores

The table below shows, for each WCAG principle and each WCAG level, how many success criteria were tested and how many of those were approved.

WCAG Principle

Level A

Level AA

Total

Observable

4 / 9

6 / 7

10 / 16

Operable

5 / 7

1 / 2

6 / 9

Understandable

1 / 2

2 / 2

3 / 4

Robust

0 / 1

0 / 0

0 / 1

Total

12 / 19

7 / 11

19/30

Findings

The identified issues are described below. For each issue, the location and a description of the problem are provided, followed by the impact on the user and a recommendation for resolving the issue.

1.3.5 Identify the purpose of the AA input

The purpose of form fields for personal information (e.g., your name) must be recognized by assistive technology.
1.3.5 Identify the purpose of the input

Result: Does not meet requirements

Finding 1 (SC 1.3.5)

On these pages, the "First Name" field has the value autocomplete="name". This is the wrong value: "name" refers to the full name, so when autofill is used, the browser fills in both the first name and the last name. This is a problem for people who rely on autofill, such as those with motor impairments or those who have difficulty typing.

Advice

In the "First Name" field, replace the "name" autocomplete attribute with "given-name".

 

Finding 2 (SC 1.3.5)

On this page, the "Address" field is missing the autocomplete attribute. As a result, the purpose of this field cannot be determined. This is a problem for people who rely on autofill, such as those with motor impairments or those who have difficulty typing.

Advice

Add the attribute `autocomplete="street-address"` to the "Address" field.

Finding 3 (SC 1.3.5)

Step 1 - Contact Form - Wedding Officiant Bert Groothengel / Contact Form - Wedding Officiant Bert Groothengel
https://www.wierden.nl/form/contactformulier-trouwambtenaar-bert-groothengel/contactformulier-trouwambtenaar-bert-groothengel-0

This page contains a form in which the "Applicant's Phone Number" field requests the user's own phone number. This field does not have an autocomplete attribute, which prevents the browser and assistive technology from programmatically determining the field’s purpose. As a result, autofill does not work for this field. This is a problem for people with cognitive disabilities, people with dyslexia, and people with motor disabilities, who specifically benefit from autofill to avoid errors and reduce the amount of typing required.

Advice

Add the attribute autocomplete="tel-national" to the phone number field.

2.4.6 Headings and Labels AA

Use clear headings and text labels that describe the subject or purpose.
2.4.6 Headings and Labels

Result: Does not meet requirements

Finding 1 (SC 2.4.6)

On these pages, the step title (h2) does not accurately describe the content of the step. The h2 repeats the name of the form, even though the step is about entering personal information and submitting a response. Users who navigate using headings—such as those who use a screen reader—cannot determine from this heading what is expected of them in this step.

Advice

Replace the h2 with a descriptive step title that explains what is required in that step. For example: "Your information and response."

3.3.2 Labels or instructions A

Input fields have clear text labels or instructions.
3.3.2 Labels or instructions

Result: Does not meet requirements

Finding 1 (SC 3.3.2)

Step 1 - Information (Sign up for Zenderink updates)
https://www.wierden.nl/form/aanmelden-updates-zenderink/gegevens-0-1

The page contains a form field labeled "Zip Code and City." This label is linked to a single text field. The field expects two separate pieces of information: a zip code and a city. There is no instruction regarding the expected input format. It is not clear to the user how the data should be entered: just the postal code, just the city, or both one after the other (and if so, in what order and with what separator). There is no placeholder or instructional text to clarify this. This is a problem for people who use assistive technology and for users who are unfamiliar with the expected input format.

Advice

Create two separate fields, each with its own label: "Zip Code" and "City."

Finding 2 (SC 3.3.2)

Step 1 - Contact Form - Wedding Officiant Bert Groothengel / Contact Form - Wedding Officiant Bert Groothengel
https://www.wierden.nl/form/contactformulier-trouwambtenaar-bert-groothengel/contactformulier-trouwambtenaar-bert-groothengel-0

The page contains a text field labeled "Bride and Groom's Names". The label does not indicate what input is expected. It is currently unclear whether the user should enter the full names of both partners separately, the combined married name, or some other format. Without instructions, the user must guess what the municipality intends. This is a problem for people with cognitive disabilities, but also for all other users who are not familiar with this type of form.

Advice

Add instructions directly below the label explaining what information is expected and in what format. For example: "Enter the first and last names of both partners, separated by 'and'"

4.1.2 Name, Role, and Value A

The software understands the name and role of elements. It can also determine the value, status, or properties of elements.
4.1.2 Name, role, and value

Result: Does not meet requirements

Finding 1 (SC 4.1.2)

Step 1 - Contact Form - Wedding Officiant Bert Groothengel / Contact Form - Wedding Officiant Bert Groothengel
https://www.wierden.nl/form/contactformulier-trouwambtenaar-bert-groothengel/contactformulier-trouwambtenaar-bert-groothengel-0

On the page, the "Applicant Phone Number" field has been created as a numeric field (type="number"). As a result, a screen reader announces the field as a countable number rather than a phone number. This is confusing for users who rely on a screen reader.

Advice

Replace the numeric field with the phone number field available in the form system. That field has type="tel" and also includes instructions on the expected format.

 

Comments

The comments are described below. For each comment, the location and a description of the problem are provided, followed by a recommendation.

1.3.3 Sensory properties A

Do not refer to shape, location, color, size, orientation, or sound.
1.3.3 Sensory characteristics

Result: Satisfactory , but with a comment

Note 1 (SC 1.3.3)

On these pages, the introductory text includes the sentence "Below is an overview of the current performance venues." However, this overview is not actually there. The form fields immediately follow the introductory text. As a result, all users are missing information that is intended to help them fill out the form correctly. The same problem occurs on the "Overview" page (step 2), where the exact same introductory text is used. This is not considered a violation because the reference "below" does not work for any user: the overview is completely missing. Consequently, there is no issue of unequal accessibility based on sensory characteristics.

Advice

Add the list of current performance venues to the page, immediately after the introductory text. If the list is located elsewhere, replace the reference with a link, for example: "View the list of current performance venues."

1.4.3 Contrast (minimum) AA

All text must have sufficient color contrast. Tip: Use the Color Contrast Analyzer to determine the color contrast.
1.4.3 Contrast (minimum)

Result: Satisfactory , but with a comment

Note 1 (SC 1.4.3)

Pages containing forms offer a high-contrast version. This can be enabled using a "contrast switch." This success criterion has been fully tested in high-contrast mode. The high-contrast version is considered an alternative to the standard version. As a result, there may be contrast issues in the standard version. These have not been further evaluated.

Advice

We recommend ensuring that the standard version also features sufficient color contrast in all text. This improves the website’s accessibility for visitors with visual impairments. Text with sufficient color contrast is also easier to read for all readers. As a result, reading is less taxing, requires less energy, and is (subconsciously) perceived as more pleasant. This makes the reader more likely to proceed to take action. The high-contrast version can then be used to provide "enhanced contrast," thereby meeting the WCAG 1.4.6 Enhanced Contrast success criterion (Level AAA).

 

1.4.11 Contrast of non-textual content AA

Non-text content on your website has sufficient color contrast (3.0:1). Examples include important images and form fields.
1.4.11 Contrast of non-text content

Result: Satisfactory , but with a comment

Note 1 (SC 1.4.11)

Pages containing forms include a high-contrast version. This can be enabled using a "contrast switch." This success criterion has been fully tested in high-contrast mode. The high-contrast version is considered an alternative to the standard version. As a result, there may be contrast issues in the standard version. These have not been further evaluated.

Advice

Ensure that the standard version also provides sufficient color contrast for all graphic elements. This improves the website’s accessibility for visitors with visual impairments. The high-contrast version can then be used to provide “enhanced contrast.”

 

Ensuring compliance and follow-up

Since the study was conducted using a sample, similar discrepancies may also exist in forms that were not examined. It is therefore advisable to check all online forms for similar patterns and to monitor them on an ongoing basis.

In addition, changes to the content of forms or to the publication process may introduce new accessibility risks. It is therefore essential to maintain a consistent focus on accessibility and to periodically review the forms.

Study Details

This chapter contains the research methodology: the scope and sample of the study, the methodology used, and the tools employed in the testing.

Sample

This study was conducted using a sample. The method used to determine the sample is specified in the WCAG-EM evaluation document. If a process was included in the study, all pages related to that process are also listed in the sample. See:https://www.digitoegankelijk.nl/aanpak/toegankelijkheidsonderzoek. 

Complete sample

Research Methods and Techniques

This study was conducted in accordance with the WCAG-EM evaluation method. This method is recommended by DigiToegankelijk (Logius). In conducting this study, it was assumed that all W3C techniques are supported and may therefore be used.

Test environment

The basic level of support includes common web browsers and assistive technologies. The study was conducted using:

  • Google Chrome 145 (primary);
  • Mozilla Firefox 147;
  • Microsoft Edge 145;
  • NVDA (Windows) in combination with Google Chrome;

Technologies

  • DOM
  • HTML
  • CSS