WCAG 2.2 AA Substudy: Website Content for GR JW

This report describes the results of the WCAG 2.2 AA sub-study on the accessibility of the content on the website www.grjw.nl, commissioned by the Joint Youth and WMO Arrangement of Midden-Holland.


 

GR JW Logo

Summary

This study was conducted by Shift2 between April 13, 2026, and April 28, 2026. For this sub-study, a representative sample was compiled consisting of 16 published web pages with various types of content.

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-one of these 30 success criteria (70%) were met.
Deviations were identified in 9 success criteria.

The GRJW website has a solid foundation. The pages are organized logically. Titles and headings are clear and help visitors quickly find what they’re looking for. This is important for people who use assistive technology to navigate the website, as they rely heavily on that structure. So the foundation is solid.

There are also a few areas for improvement. In several places, lists, headings, and emphasis in the text are clearly visible. Behind the scenes, however, the structure is incorrect. Additionally, several pages contain generic link text such as "Read more...," without making it clear where the link leads. In a few places within a PDF document, the color contrast between the text and the background is too low, making that text difficult to read for people with visual impairments. There is still room for improvement with the PDF documents by structuring them in a way that allows assistive software to convey the content effectively.

We recommend periodically reviewing content for recurring patterns of accessibility issues and embedding accessibility into the publication process.

About this study

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

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

Scope of the sub-study

This sub-study pertains exclusively to the content of the website that the organization can enter or modify via the content 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 website and are evaluated in the separate technical sub-study.

Together, these two sub-studies constitute the complete evaluation of the website.

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. Within this sample, the accessibility issues identified were described as specifically as possible. 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 criterionLevelResult
1.1.1 Non-textual contentADoes not meet the requirements
1.2.1 Audio-only and video-only (pre-recorded)Anot available
1.2.2 Captions for the deaf and hard of hearing (pre-recorded)Anot available
1.2.3 Audio description or media alternative (pre-recorded)Anot available
1.2.4 Captions for the Deaf and Hard of Hearing (live)AAnot available
1.2.5 Audio description (pre-recorded)AAnot available
1.3.1 Information and RelationshipsADoes not meet the requirements
1.3.2 Meaningful orderADoes not meet the requirements
1.3.3 Sensory propertiesAMeets the requirements
1.3.5 Identify the purpose of the importAADoes not meet the requirements
1.4.1 Use of colorAMeets the requirements
1.4.2 Sound ControlsAAnot available
1.4.3 Contrast (minimum)AADoes not meet the requirements
1.4.5 Images of textAAMeets the requirements
1.4.10 ReflowAAMeets the requirements
1.4.11 Contrast of non-textual contentAAMeets the requirements
2.1.2 No keyboard dropAMeets the requirements
2.1.4 Single-character keyboard shortcutsAMeets the requirements
2.2.2 Pause, stop, or hideAnot available
2.3.1 Three flashes or below the threshold valueAMeets the requirements
2.4.2 Page TitleADoes not meet the requirements
2.4.4 Link target (in context)ADoes not meet the requirements
2.4.6 Headings and labelsAAMeets the requirements
2.5.3 Label in the nameAMeets the requirements
2.5.8 Size of the selection area (minimum)AAMeets the requirements
3.1.1 Page LanguageADoes not meet the requirements
3.1.2 Language of componentsAAMeets the requirements
3.2.4 Consistent identificationAAMeets the requirements
3.3.2 Labels or instructionsAMeets the requirements
4.1.2 Name, role, and valueADoes 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 PrincipleLevel ALevel AATotal
Observable6 / 95/711 / 16
Operable5 / 72 / 27 / 9
Understandable1 / 22 / 23 / 4
Robust0 / 10 / 00 / 1
Total12 199 / 1121/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.1.1 Non-textual content A

Provide meaningful text alternatives for images and other non-text content.
Information about Success Criterion 1.1.1 Non-text Content

Result: Does not meet requirements

Finding 1 (SC 1.1.1)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

The PDF newsletter for the in-person meeting on October 6, 2025, contains many decorative elements, such as wave patterns and arrows. These elements are marked as images in the document but lack text alternatives. As a result, assistive technology repeatedly announces these images without providing any useful information to the user. Decorative elements do not add to the content and should be skipped by assistive technology.

Advice

Mark all purely decorative elements so that assistive software skips them. In Adobe Acrobat, you can do this using the tag panel: right-click on the image, select "Change Tag Type," and then choose "Artifact." Assistive software will then no longer read these elements aloud.

Finding 2 (SC 1.1.1)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

On page 3 of the PDF newsletter for the in-person meeting on October 6, 2025, the GR JW logo appears in the bottom right corner. This logo is not marked as an image in the document. As a result, a user reading the PDF with assistive software will not be informed that the GR JW logo is present here.

Advice

Select the logo as an image and provide a text alternative, such as "GR JW Logo." Assistive technology will then announce the logo, so the user knows who sent the newsletter.

1.3.1 Information and Relationships A

The information, structure, and relationships in the content that you can see must also be available in the code for assistive technology. 1.3.1 Information and relationships

Result: Does not meet requirements

Finding 1 (SC 1.3.1)

On several pages, headings have been further emphasized using a `strong` element (an HTML element used to emphasize text within body text). One example is the heading "Contract Management Notice" on the homepage. A heading is already a prominent element and does not need to be emphasized further. This results in users of assistive technology receiving incorrect information: the heading is read aloud as if it were emphasized, even though this is already evident from its heading level.

Advice

Remove the `strong` element from the headings. If you want the heading to stand out visually, use CSS instead of an extra `strong` element.

Finding 2 (SC 1.3.1)

https://www.grjw.nl/

On the homepage, under the heading "Important Topics" (H2), there are five topics listed side by side. Three of them (Physical Consultation Table, Regional Expert Team (RET), Policy & Regional Development) are formatted as H3. The other two (ETHOS Survey, Insight & Impact) are formatted as H2, even though they visually and in the code belong to the same section and should therefore be at the same level as the H3s. As a result, the hierarchy of the headings is incorrect, and users of assistive software cannot easily determine which topics belong together.

Advice

Make "ETHOS survey" and "Insight & impact" H3 headings so that all five topics in the "Key topics" section are at the same level.

Finding 3 (SC 1.3.1)

https://www.grjw.nl/

In the section under the heading "Contract Management Notification," the words "Care Notification" are italicized using an `em` element. This italicization is used to indicate the name of a button on the page. The `em` element is not intended for this purpose. It is intended to be used to place extra emphasis on a word within a running sentence, so that assistive software can read that word aloud with greater emphasis. Because it is used here on a button name, users of assistive software hear "care notification" as an emphasized word, even though it is merely a button name.

Advice

Remove the `em` element around "health notification". If you want the button name to stand out visually, do so using CSS or by turning the text into an actual link to the button.

Finding 4 (SC 1.3.1)

Several pages contain an empty heading. This occurs in areas where the page is laid out in two columns, and the empty heading is used to visually align the columns. An example can be found below the illustration next to the "Stay informed!" section on the "Physical meeting table" page. Anyone who has the website read aloud and navigates through the headings will hear a heading announced at those points that subsequently contains nothing.

Advice

Remove the empty header. If visual alignment is desired, choose a different solution that does not use a header.

Finding 5 (SC 1.3.1)

https://www.grjw.nl/over-ons

The "Job Openings" section of the page includes the text "Program Manager for Regional Transformation Projects". Visually, this appears as a subheading. In the code, however, it is not a heading but a regular line of text with the text emphasized using a `strong` element. People who use screen readers to have the website read aloud do not hear this text as a heading. As a result, they cannot quickly find the job opening via the list of headings on the page.

Advice

Make "Regional Transformation Projects Program Manager" a proper subheading (level 3) under the main heading "Job Openings".

Finding 6 (SC 1.3.1)

https://www.grjw.nl/over-ons

On the page, under "What will you be doing?" in the Jobs section, there is a list of five tasks. Visually, this list features green checkmarks next to each item. In the code, however, this is not formatted as a list, but as a single paragraph in which the items are on new lines, each preceded by a checkmark emoji. As a result, assistive software does not announce this as a list and does not mention the number of items. Furthermore, each checkmark emoji is read aloud as "white bold check mark," which distracts from the content.

Advice

Turn the bulleted list into an actual list in the code. Remove the checkmark emojis from the text itself. If you want the checkmarks to appear visually, style them using CSS.

Finding 7 (SC 1.3.1)

Several pages contain visual lists that are not formatted as lists. In the FAQ section on the Regional Expert Team page, the answer to "What are the functions of the RET?" includes four numbered items formatted as separate paragraphs rather than as a proper numbered list. On the Annual Report page, under "When do you need to submit this?", there are three deadlines listed in a single paragraph. Screen readers do not present these lists as lists. The number of items is not specified. As a result, the connection between the items is lost for people who have the website read aloud.

Advice

Turn the visual lists into a proper list. Use a numbered list if the order is important. Use a bulleted list if the order doesn't matter.

Finding 8 (SC 1.3.1)

https://www.grjw.nl/jaarverantwoording

On the Annual Report page, under the subheading "What do you need to submit?", the text reads "Random checks on production up to €200,000." Visually, this appears as a subheading. In the code, however, it is not a heading but rather text emphasized using a `strong` element. People who use a screen reader to have the website read aloud do not hear this text as a heading. As a result, they cannot quickly find this topic using the list of headings on the page.

Advice

Make "Random inspections during production up to €200,000" a proper subheading at the correct level. Remove the `strong` element. The visual formatting can be controlled using CSS.

Finding 9 (SC 1.3.1)

https://www.grjw.nl/jaarverantwoording

On the Annual Report page, the text "The deadlines at a glance:" is displayed in italics using an `em` element. This text serves as an introductory sentence above the list of deadlines. The `em` element is not intended for that purpose. It is intended to be used to place extra emphasis on a specific word within a running sentence, so that assistive technology can read that word aloud with greater emphasis. Because it appears here in an introductory sentence, users of assistive technology read "The deadlines at a glance:" with extra emphasis, even though there is no word that needs that emphasis.

Advice

Remove the `em` element around "The deadlines at a glance:". If you want the text to appear italicized, use CSS to achieve that.

Finding 10 (SC 1.3.1)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

In the PDF newsletter for the in-person consultation meeting on October 6, 2025, the heading structure is incorrect. Headings at the lowest level appear directly under the main title, without any intermediate levels. This occurs, for example, under "How is GR JW doing?" and "What is an in-person consultation meeting?". On page 3, under "Save the date," there are three lines of text marked as level 4 headings, even though they are simply paragraphs. As a result, people who have the PDF read aloud and navigate using the headings will hear an illogical structure. This makes it more difficult to distinguish main points from side issues.

Advice

Use headings in a logical order, without skipping any levels. Mark only actual headings as headings, and regular text as paragraphs.

Finding 11 (SC 1.3.1)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

On page 1 of the PDF newsletter for the in-person consultation meeting on October 6, 2025, there is a table of contents in the upper right corner under the heading "Contents." Visually, this appears as a list, but within the document, the topics are presented as separate paragraphs one below the other. As a result, screen readers do not announce the table of contents and do not mention the number of items.

Advice

Mark the topics under "Contents" as a single table of contents, rather than as separate paragraphs. In Adobe Acrobat, you can do this via the Tags panel by marking the block as a table of contents. Screen readers will then announce the block as a table of contents, including the number of items.

Finding 12 (SC 1.3.1)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

On page 2 of the PDF newsletter for the in-person meeting on October 6, 2025, there are three numbered tiles (1, 2, 3) side by side under the heading "Did you know...". Visually, this is a numbered list, but in the document, the three tiles are presented as separate paragraphs and headings. As a result, assistive software does not recognize it as a list and does not mention the number of items.

Advice

Modify the source file so that the three tiles are included as a single numbered list when exported to PDF.

Finding 13 (SC 1.3.1)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/20260224%20Overzicht%20contractmanagers%20en%20zorgaanbieders_0.pdf?cb=lXRChgTP

The PDF document "Overview of Contract Managers and Healthcare Providers" contains a table with four columns: Healthcare Provider, Contract Manager, Contract Manager's Email Address, and Contract Manager's Phone Number. The first row appears to be a header row, but it is not formatted as such in the document. Screen readers read only the content of each cell without indicating which column it belongs to. Furthermore, this row is repeated as a regular row on every new page. As a result, assistive software reads the column headers over and over again, in the middle of the data.

Advice

Set the first row in the source file as the header row, and make sure this header row appears only once in the table. Then export the PDF again.

1.3.2 Meaningful Order A

Make sure all content is in a "logical" order and that assistive technology can also determine this order.
1.3.2 Meaningful order

Result: Does not meet requirements

Finding 1 (SC 1.3.2)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

On page 2 of the PDF newsletter for the in-person consultation meeting on October 6, 2025, there are two sections in two columns side by side: "Breakout Session: Day Services" and "Breakout Session: Externalizing Behavior in Open Youth Services." Visually, the text directly below each heading corresponds to it. However, screen readers first read the two headings one after the other, and only then the two texts. It is then unclear which text belongs to which heading.

Advice

Adjust the source file so that each heading appears directly above its corresponding text in the order in which it is read aloud.

1.3.5 Identify the purpose of the input AA

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 the "Healthcare Provider Information" and "Resident Information" sections of the reporting form, information must be entered about a person other than the reporter. An autocomplete attribute is available for several input fields (last name, ZIP code, street name, city, email address, and phone number). The autocomplete attribute ensures that browsers and assistive software can provide assistance with filling out the form, for example by suggesting the user’s own information. In this case, however, the fields do not pertain to the user themselves, but to a third party. Therefore, the autocomplete attribute on these fields is incorrect.

Advice

Remove the autocomplete attribute from the input fields on the "Healthcare Provider Information" and "Resident Information" steps. On the step where the reporter enters their own contact information, the attribute should remain as it is now.

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: Does not meet requirements

Finding 1 (SC 1.4.3)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

In several places in the PDF newsletter for the in-person consultation meeting on October 6, 2025, the contrast between the text and the background is too low. At the top of each page, the blue header bar displays the date "10/30/2025" and the text "Physical Consultation Table Newsletter" in dark gray (#3B474F) on a blue background (#5A90CC). The contrast ratio is 2.9:1, while a minimum of 4.5:1 is required for normal text. At the bottom of page 3, the "Save the date" block appears in white text (#FFFFFF) on turquoise (#10B9A8). The contrast ratio is 2.5:1. A minimum of 3:1 is required for the large "Save the date" headline, and a minimum of 4.5:1 for the explanatory text below it. Neither standard is met. As a result, this text is difficult to read for people with visual impairments, such as the visually impaired or those with reduced contrast sensitivity.

Advice

Increase the contrast in both areas to meet the requirements: at least 3:1 for large headings and at least 4.5:1 for body text. Make these adjustments in the source file and re-export the PDF.

2.4.2 Page Title A

All pages have a clear title that describes the topic.
2.4.2 Page Title

Result: Does not meet requirements

Finding 1 (SC 2.4.2)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/20260224%20Overzicht%20contractmanagers%20en%20zorgaanbieders_0.pdf?cb=lXRChgTP

In the PDF document "Overview of Contract Managers and Healthcare Providers," no title has been entered in the file properties. As a result, PDF readers display the file name (20260224 Overview of Contract Managers and Healthcare Providers_0.pdf) in the title bar and tab of the window. People who have the PDF read aloud will hear the file name instead of a meaningful title.

Advice

In the source file, enter a descriptive title, such as "Overview of Contract Managers and Healthcare Providers." Then export the PDF again. In the PDF itself, also set it so that the document title is displayed instead of the file name. In Adobe Acrobat, you can do this by going to File > Properties > Initial View tab: under "Show," select the "Document Title" option.

2.4.4 Link target (in context) A

Provide clear text for links so that users know what will happen when they click on them.
2.4.4 Link target (in context)
 

Result: Does not meet requirements

Finding 1 (SC 2.4.4)

Several pages contain links with the text "Read more..." in a separate paragraph, without any descriptive context in the same sentence or paragraph. An example is the "Read more..." link under "Physical conference table" on the homepage. The link text alone does not make it clear where the link leads. Assistive software that reads a list of links aloud will read "Read more..." multiple times without distinction.

Advice

Make the link text specific, for example, "Read more about the Physical Conference Table." Alternatively, you can place the link in the same paragraph as the descriptive text. Assistive technology can then use that surrounding text as context, so the user still knows what the link is about.

Finding 2 (SC 2.4.4)

Several pages contain links whose text appears to be an email address, but the web address behind the link does not point to an email address. Instead, the user remains on the same page. An example is the link "contact@grjw.nl" in the footer of the homepage. Anyone who clicks this link expects the email program to open, but that does not happen. The link text promises something different from what the link actually does.

Advice

Replace the web address in these links with the correct email address, in the format "mailto:contact@grjw.nl". Clicking the link will then open the user's email program with the email address already filled in.

3.1.1 Page Language A

Assistive software must be able to determine the language of the page so that, for example, the correct voice and intonation can be used.
3.1.1 Language of the page
 

Result: Does not meet requirements

Finding 1 (SC 3.1.1)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

The PDF newsletter for the in-person consultation meeting on October 6, 2025, is written in Dutch, but the document properties are set to English. As a result, screen readers read the Dutch text aloud using an English pronunciation. This makes the content more difficult to follow for people who use screen readers to have the PDF read aloud.

Advice

Set the document language to Dutch. In Adobe Acrobat, you can do this by going to File > Properties > the Advanced tab, and then under Reading Options at the bottom: select "Dutch" under Language. Assistive technology will then read the text aloud with the correct pronunciation.

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)

https://cuatro.sim-cdn.nl/grjwb466a1/uploads/Nieuwsbrief%20fysieke%20overlegtafel%206%20oktober%202025%20(1).pdf?cb=_Nzi_zUb

The PDF newsletter for the in-person consultation meeting on October 6, 2025, contains clickable links in several places, such as the email address contact@grjw.nl on page 2 and the link www.nji.nl on page 3. These links are not marked as links within the document. As a result, screen readers do not announce the text as a link.

Advice

Modify the source file so that clickable text is included as a link when exported to PDF.

Comments

The comments below do not result in a rejection, but contain suggestions that could further improve accessibility or user-friendliness.

1.1.1 Non-textual content A

Provide meaningful text alternatives for images and other non-text content.
Information about Success Criterion 1.1.1 Non-text Content

Result: Satisfactory , but with a comment

Note 1 (SC 1.1.1)

https://www.grjw.nl/over-ons

The page displays the GR JW logo. In addition to the logo and the caption, the text alternative also includes a description of the logo itself ("The logo consists of the letters 'GR' in blue and 'JW' in green."). Colors and placement do not add any information. For people who use screen readers, this is simply distracting.

Advice

Remove the description of the letter colors from the text alternative. The text alternative will then contain only "GR JW" (logo) and the caption.

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)

The website offers 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.

This may cause contrast issues in the standard version. These issues have not been further evaluated.

Advice

We recommend ensuring that the standard version also includes sufficient color contrast in all text. This improves the website’s accessibility for visitors with visual impairments.

Texts with sufficient color contrast are also easier for all readers to read. This makes reading less taxing, requires less energy, and is (subconsciously) perceived as more enjoyable. As a result, readers are more likely 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)

A high-contrast version is available on the website. It 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 with graphic elements in the standard version. These have not been further evaluated.

Advice

We recommend ensuring that the standard version also provides sufficient contrast for graphic elements, such as icons, buttons, and form fields. This improves the website’s accessibility for visitors with visual impairments.
The high-contrast version can then be used to provide “enhanced contrast.”

2.4.4 Link target (in context) A

Provide clear text for links so that users know what will happen when they click on them.
2.4.4 Link target (in context)

Result: Satisfactory , but with a comment

Note 1 (SC 2.4.4)

https://www.grjw.nl/voor-gemeenten

The page contains three links with the anchor text "Start Point" that lead to two different destinations. Two of them link to the external website aanbod.zorgverkeer.nl. The third link jumps from the table of contents to the "Start Point" section further down the page. Screen readers that read out a list of links will read "Start Point" three times without distinguishing between the destinations.

Advice

We recommend avoiding identical link text when links lead to different destinations. You can do this by making the link text in the table of contents more specific (for example, "Go to the 'Starting Point' section on this page") or by giving the external link its own descriptive text (for example, "Starting Point: Overview of Healthcare Providers").

Ensuring compliance and follow-up

Since the study was conducted using a sample, similar issues may also exist on pages that were not examined. It is therefore advisable to check the entire website for similar patterns and to monitor them on an ongoing basis.

In addition, changes to the content or the publication process may introduce new accessibility risks. Therefore, a consistent focus on accessibility and periodic reassessment remain essential.

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.

Scope

The URL indicates the reason why a particular section was or was not included. This is in accordance with the rules for determining the scope in the WCAG-EM evaluation method.

https://www.grjw.nl (URI base)

 

Additional scope information

The following content falls outside the scope of this study pursuant to the Accessibility Act:

  • Not online maps and mapping services, unless they are intended for navigation (legal exception for government agencies)
  • Not office files created before September 23, 2018, unless they are part of an administrative process (legal exception for the government).
  • Not the live videos (legal exception for the government)
  • Excluding audio and video files uploaded to the digital channel before September 23, 2020 (legal exception for the government)
  • Content not provided by third parties (legal exception for the government)
  • Not the contents of archives (legal exception for the government)
  • Not the content behind a login
     

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, version 143 (primary)
  • Mozilla Firefox, version 146
  • Microsoft Edge, version 143
  • Adobe Acrobat Pro
  • PDF Accessibility Checker (PAC)
  • Color Contrast Analyzer
  • NVDA (Windows) in combination with Google Chrome

Technologies

  • DOM
  • HTML
  • CSS
  • SVG
  • PDF