Report

About the Evaluation

Report Creator: Tom Schaek
Evaluation Commissioner: Omring
Evaluation date: Tue Nov 12 2024

Executive Summary

The website has been clearly developed with regard to accessibility. The main focus points are correct use of alt text, the correct use of semantics, keyboard navigation for the main menu and color contrast optimisations.

Scope of the Evaluation

Website name: Public website of Omring
Scope of the website: All 'thuiszorg' themed pages: Zorg thuis: https://www.omring.nl/zorg-thuis Thuiszorgteam: https://www.omring.nl/zorg-thuis/thuiszorgteam-zorg-behandeling-thuis Thuisbegeleiding: https://www.omring.nl/thuisbegeleiding Huishoudelijk hulp: https://www.omring.nl/hulpthuis Zorg of behandeling thuis: https://www.omring.nl/zorg-thuis/zorg-behandeling-thuis Dagbesteding: https://www.omring.nl/extra-diensten/dagbesteding Mantelzorg: https://omring.nl/mantelzorg Zorg per klacht: dementie: https://www.omring.nl/gezondheid/dementie
WCAG Version: 2.2
Conformance target: AA
Accessibility support baseline: See "Testing Methodologies" section (page 7) in the Quick Audit document.
Additional evaluation requirements: The report will include a description of the problem and repair suggestions for any errors listed.

Detailed Audit Results

Statistics

Impact

8 High priority
3 Warning
0 Best practice
44 No impact

Outcome

Conformance level A

12 Passed
7 Failed
0 Cannot tell
12 Not present
0 Not checked

Conformance level AA

15 Passed
4 Failed
0 Cannot tell
5 Not present
0 Not checked

POUR principles

Perceivable

We reported that 5 of the 20 (or 25%) relevant level A and AA criteria related to perceivability are not met, which means that a valuable segment of your target audience doesn’t have sufficient digital text alternatives that can be interpreted through their assistive technology (screen readers, braille devices, etc) and/or their visual ability.

11 Passed (55% rate)
5 Failed (25% rate)
0 Cannot tell (0% rate)
4 Not present (20% rate)
0 Not checked (0% rate)

Operable

We reported that 4 of the 20 (or 20%) relevant level A and AA criteria related to operability are not met, which means that a valuable segment of your target audience cannot interact with your website. Operability is considered support for keyboard and mouse interaction, providing sufficient time to fulfil certain tasks, and designing content in a way that is not causing seizures or physical reactions.

8 Passed (40% rate)
4 Failed (20% rate)
0 Cannot tell (0% rate)
8 Not present (40% rate)
0 Not checked (0% rate)

Understandable

We reported that 1 of the 13 (or 8%) relevant level A and AA criteria related to understandability are not met, which means that the minority of your target audience cannot understand the information shared on your website. Understanding means correct pronunciation and use of simple language, combined with consistent navigation and prevention of input errors through labelling, instructions, suggestions, and help.

7 Passed (54% rate)
1 Failed (8% rate)
0 Cannot tell (0% rate)
5 Not present (38% rate)
0 Not checked (0% rate)

Robust

We reported that 1 of the 2 (or 50%) relevant level A and AA criteria related to robustness are not met, which means that your website does not accommodate reliable access through a variety of user agents (browsers, assistive technology, etc). In addition to using different browsers (Chrome, Firefox, Microsoft Edge, etc), people with disabilities may rely on different types of assistive technologies. From screen readers and braille terminals to software for text magnification and speech recognition.

1 Passed (50% rate)
1 Failed (50% rate)
0 Cannot tell (0% rate)
0 Not present (0% rate)
0 Not checked (0% rate)

Summary

Reported on 55 of 55 WCAG 2.2 AA Success Criteria.

All Results

1 Perceivable

1.1 Text Alternatives

Success Criterion	Result	Impact	Observations
1.1.1: Non-text Content	Entire sample Result: Failed Zorg thuis Result: Failed	Entire sample Impact: High priority Zorg thuis Impact: High priority	Entire sample Observations: "Appropriate alt text" Problem: Not all images have appropriate alt texts. Solution: Evaluate alt texts for all images: If the image is not meaningful, it can be coded as decorative. Zorg thuis "Appropriate alt text" Problem: Hero banner has an alt text that is not descriptive. Solution: The hero banner has an alt text of "Thuiszorg", which does not describe the image. The image can also be coded as decorative by leaving the alt attribute empty (alt="", the alt attribute should always be present). Logo has an alt text of "Home", this can be improved by changing the alt text to "Omring home" or "Home" Evaluate alt texts for all images: If the image is not meaningful, it can be coded as decorative. Screenshot: Figure 13, Figure 14, Figure 15

Success Criterion

Result

Impact

Observations

1.1.1: Non-text Content

Entire sample

Result: Failed

Zorg thuis

Result: Failed

Entire sample

Impact: High priority

Zorg thuis

Impact: High priority

Entire sample

Observations:

"Appropriate alt text"

Problem: Not all images have appropriate alt texts.

Solution: Evaluate alt texts for all images: If the image is not meaningful, it can be coded as decorative.

Zorg thuis

"Appropriate alt text"

Problem: Hero banner has an alt text that is not descriptive.

Solution: The hero banner has an alt text of "Thuiszorg", which does not describe the image. The image can also be coded as decorative by leaving the alt attribute empty (alt="", the alt attribute should always be present). Logo has an alt text of "Home", this can be improved by changing the alt text to "Omring home" or "Home" Evaluate alt texts for all images: If the image is not meaningful, it can be coded as decorative.

Screenshot: Figure 13, Figure 14, Figure 15

1.2 Time-based Media

Success Criterion	Result	Impact	Observations
1.2.1: Audio-only and Video-only (Prerecorded)	Entire sample Result: Not present	Entire sample Impact: No impact
1.2.2: Captions (Prerecorded)	Entire sample Result: Passed	Entire sample Impact: No impact Dagbesteding Impact: No impact	Entire sample Observations: Note: Videos use closed captions (baked into the video). An improvement would be to use open captions (can be turned on or off, styled and has support for assisted technology)
1.2.3: Audio Description or Media Alternative (Prerecorded)	Entire sample Result: Not present	Entire sample Impact: No impact	Entire sample Observations: Note: No audio description needed for this type of video content. The visual content is not needed to understand the video.
1.2.4: Captions (Live)	Entire sample Result: Not present	Entire sample Impact: No impact
1.2.5: Audio Description (Prerecorded)	Entire sample Result: Passed	Entire sample Impact: No impact	Entire sample Observations: Note: No audio description needed for this type of video content. The visual content is not needed to understand the video.

Success Criterion

Result

Impact

Observations

1.2.1: Audio-only and Video-only (Prerecorded)

Entire sample

Result: Not present

Entire sample

Impact: No impact

1.2.2: Captions (Prerecorded)

Entire sample

Result: Passed

Entire sample

Impact: No impact

Dagbesteding

Impact: No impact

Entire sample

Observations:

Note: Videos use closed captions (baked into the video). An improvement would be to use open captions (can be turned on or off, styled and has support for assisted technology)

1.2.3: Audio Description or Media Alternative (Prerecorded)

Entire sample

Result: Not present

Entire sample

Impact: No impact

Entire sample

Observations:

Note: No audio description needed for this type of video content. The visual content is not needed to understand the video.

1.2.4: Captions (Live)

Entire sample

Result: Not present

Entire sample

Impact: No impact

1.2.5: Audio Description (Prerecorded)

Entire sample

Result: Passed

Entire sample

Impact: No impact

Entire sample

Observations:

Note: No audio description needed for this type of video content. The visual content is not needed to understand the video.

1.3 Adaptable

Success Criterion	Result	Impact	Observations
1.3.1: Info and Relationships	Entire sample Result: Failed Zorg thuis Result: Failed	Entire sample Impact: Warning Zorg thuis Impact: Warning	Entire sample Observations: "Missing landmark" Problem: Search bar is missing the search landmark. Solution: Add role="search" to the form Screenshot: Figure 5 Zorg thuis "Empty landmark" Problem: Page contains a 'Complementary' landmark that has no content Solution: Remove the 'complementary' landmark when it has no content Screenshot: figure 4 "Heading level" Problem: Lower-level headings should be more prominent than higher-level headings. Headings of the same level should have the same font style. Solution: Make a visual distinction between H2 and H3 headings. H2 should have a larger font-size than the H3 heading. Also check if headings of the same level have the same font style. Screenshot: Figure 7 "No heading text" Problem: The heading is empty or lacks meaningful content. Solution: Provide content for the headings or remove them. Screenshot: Figure 18
1.3.2: Meaningful Sequence	Entire sample Result: Passed	Entire sample Impact: No impact
1.3.3: Sensory Characteristics	Entire sample Result: Passed	Entire sample Impact: No impact
1.3.4: Orientation	Entire sample Result: Passed	Entire sample Impact: No impact
1.3.5: Identify Input Purpose	Entire sample Result: Passed	Entire sample Impact: No impact

1.4 Distinguishable

Success Criterion	Result	Impact	Observations
1.4.1: Use of Color	Entire sample Result: Passed	Entire sample Impact: No impact
1.4.2: Audio Control	Entire sample Result: Not present	Entire sample Impact: No impact
1.4.3: Contrast (Minimum)	Entire sample Result: Failed Thuiszorgteam Result: Failed	Entire sample Impact: High priority Thuiszorgteam Impact: High priority	Entire sample Observations: "Insufficient normal text contrast (4 occurrences)" Problem: There is insufficient color contrast between the foreground and background of normal text content. Solution: Footer items: Use foreground color: #d7ffff and the original background color: #007b85 to meet a contrast ratio of 4.71:1 Chat box: Use foreground color: #727272 and the original background color: #ffffff to meet a contrast ratio of 4.81:1 Screenshot: Figure 1 Thuiszorgteam "Insufficient large text contrast (1 occurrence)" Problem: The active pagination link does not provide sufficient color contrast between the foreground and background of large text content. Solution: Change background color from #3fcfd5 to #2b9da1, or choose a different color combination that has a contrast ratio of at least 3:1 Screenshot: Figure 21
1.4.4: Resize text	Entire sample Result: Passed	Entire sample Impact: No impact
1.4.5: Images of Text	Entire sample Result: Passed	Entire sample Impact: No impact
1.4.10: Reflow	Entire sample Result: Passed	Entire sample Impact: No impact
1.4.11: Non-text Contrast	Entire sample Result: Failed	Entire sample Impact: High priority	Entire sample Observations: "Insufficient color contrast for meaningful visual cue" Problem: The search box is surrounded by a box-shadow, which does not provide the required 3:1 contrast ratio Solution: Adding a border with color #949494 for the search box would provide sufficient color contrast. Screenshot: Figure 25
1.4.12: Text Spacing	Entire sample Result: Passed	Entire sample Impact: No impact
1.4.13: Content on Hover or Focus	Entire sample Result: Failed	Entire sample Impact: Warning	Entire sample Observations: "Content on hover is not dismissible" Problem: The main menu reveals a sub menu when hovering over the main menu items, but this submenu is not dismissible by pressing the Esc key. Solution: Allow users to dismiss the submenu by pressing the Esc key. This can be implemented with javascript.

Success Criterion

Result

Impact

Observations

1.4.1: Use of Color

Entire sample

Result: Passed

Entire sample

Impact: No impact

1.4.2: Audio Control

Entire sample

Result: Not present

Entire sample

Impact: No impact

1.4.3: Contrast (Minimum)

Entire sample

Result: Failed

Thuiszorgteam

Result: Failed

Entire sample

Impact: High priority

Thuiszorgteam

Impact: High priority

Entire sample

Observations:

"Insufficient normal text contrast (4 occurrences)"

Problem: There is insufficient color contrast between the foreground and background of normal text content.

Solution: Footer items: Use foreground color: #d7ffff and the original background color: #007b85 to meet a contrast ratio of 4.71:1 Chat box: Use foreground color: #727272 and the original background color: #ffffff to meet a contrast ratio of 4.81:1

Screenshot: Figure 1

Thuiszorgteam

"Insufficient large text contrast (1 occurrence)"

Problem: The active pagination link does not provide sufficient color contrast between the foreground and background of large text content.

Solution: Change background color from #3fcfd5 to #2b9da1, or choose a different color combination that has a contrast ratio of at least 3:1

Screenshot: Figure 21

1.4.4: Resize text

Entire sample

Result: Passed

Entire sample

Impact: No impact

1.4.5: Images of Text

Entire sample

Result: Passed

Entire sample

Impact: No impact

1.4.10: Reflow

Entire sample

Result: Passed

Entire sample

Impact: No impact

1.4.11: Non-text Contrast

Entire sample

Result: Failed

Entire sample

Impact: High priority

Entire sample

Observations:

"Insufficient color contrast for meaningful visual cue"

Problem: The search box is surrounded by a box-shadow, which does not provide the required 3:1 contrast ratio

Solution: Adding a border with color #949494 for the search box would provide sufficient color contrast.

Screenshot: Figure 25

1.4.12: Text Spacing

Entire sample

Result: Passed

Entire sample

Impact: No impact

1.4.13: Content on Hover or Focus

Entire sample

Result: Failed

Entire sample

Impact: Warning

Entire sample

Observations:

"Content on hover is not dismissible"

Problem: The main menu reveals a sub menu when hovering over the main menu items, but this submenu is not dismissible by pressing the Esc key.

Solution: Allow users to dismiss the submenu by pressing the Esc key. This can be implemented with javascript.

2 Operable

2.1 Keyboard Accessible

Success Criterion	Result	Impact	Observations
2.1.1: Keyboard	Entire sample Result: Failed Zorg thuis Result: Failed Thuiszorgteam Result: Failed Thuisbegeleiding Result: Not present Huishoudelijk hulp Result: Failed Zorg of behandeling thuis Result: Failed Dagbesteding Result: Not present Mantelzorg Result: Not present Zorg per klacht: dementie Result: Not present	Entire sample Impact: High priority Zorg thuis Impact: High priority Thuiszorgteam Impact: High priority Thuisbegeleiding Impact: No impact Huishoudelijk hulp Impact: High priority Zorg of behandeling thuis Impact: High priority Dagbesteding Impact: No impact Mantelzorg Impact: No impact Zorg per klacht: dementie Impact: No impact	Entire sample Observations: "Keyboard navigation" Problem: Submenu items on the main menu can't be expanded with the keyboard (only on mouse hover) Solution: Expand the subitems on the main menu when the main menu item receives focus. Additionally, it is advised to add a visual cue (for instance: chevron down icon) so users know there are subitems present in the main menu. Screenshot: Figure 2 "Missing href" Problem: The <a> element is missing an href="..." attribute. Solution: This element serves as the destination for the 'Skip to main content link'. Semantically this should be a <div> element instead of an <a> element Screenshot: Figure 20 Zorg thuis "Keyboard navigation" Problem: The 'Nu chatten' cta is not accessible with keyboard navigation. Solution: The button is <a> element and is missing the href attribute. Semantically, an element like this should be implemented as <button> Screenshot: Figure 3 Thuiszorgteam "Keyboard navigation" Problem: The 'Nu chatten' cta is not accessible with keyboard navigation. Solution: The button is <a> element and is missing the href attribute. Semantically, an element like this should be implemented as <button> Screenshot: Figure 3 Thuisbegeleiding No observations added Huishoudelijk hulp "Keyboard navigation" Problem: The 'Nu chatten' cta is not accessible with keyboard navigation. Solution: The button is <a> element and is missing the href attribute. Semantically, an element like this should be implemented as <button> Screenshot: Figure 3 Zorg of behandeling thuis "Keyboard navigation" Problem: The 'Nu chatten' cta is not accessible with keyboard navigation. Solution: The button is <a> element and is missing the href attribute. Semantically, an element like this should be implemented as <button> Screenshot: Figure 3 Dagbesteding No observations added Mantelzorg No observations added Zorg per klacht: dementie No observations added
2.1.2: No Keyboard Trap	Entire sample Result: Passed	Entire sample Impact: No impact
2.1.4: Character Key Shortcuts	Entire sample Result: Not present	Entire sample Impact: No impact

Success Criterion

Result

Impact

Observations

2.1.1: Keyboard

Entire sample

Result: Failed

Zorg thuis

Result: Failed

Thuiszorgteam

Result: Failed

Thuisbegeleiding

Result: Not present

Huishoudelijk hulp

Result: Failed

Zorg of behandeling thuis

Result: Failed

Dagbesteding

Result: Not present

Mantelzorg

Result: Not present

Zorg per klacht: dementie

Result: Not present

Entire sample

Impact: High priority

Zorg thuis

Impact: High priority

Thuiszorgteam

Impact: High priority

Thuisbegeleiding

Impact: No impact

Huishoudelijk hulp

Impact: High priority

Zorg of behandeling thuis

Impact: High priority

Dagbesteding

Impact: No impact

Mantelzorg

Impact: No impact

Zorg per klacht: dementie

Impact: No impact

Entire sample

Observations:

"Keyboard navigation"

Problem: Submenu items on the main menu can't be expanded with the keyboard (only on mouse hover)

Solution: Expand the subitems on the main menu when the main menu item receives focus. Additionally, it is advised to add a visual cue (for instance: chevron down icon) so users know there are subitems present in the main menu.

Screenshot: Figure 2

"Missing href"

Problem: The <a> element is missing an href="..." attribute.

Solution: This element serves as the destination for the 'Skip to main content link'. Semantically this should be a <div> element instead of an <a> element

Screenshot: Figure 20

Zorg thuis

"Keyboard navigation"

Problem: The 'Nu chatten' cta is not accessible with keyboard navigation.

Solution: The button is <a> element and is missing the href attribute. Semantically, an element like this should be implemented as <button>

Screenshot: Figure 3

Thuiszorgteam

"Keyboard navigation"

Problem: The 'Nu chatten' cta is not accessible with keyboard navigation.

Solution: The button is <a> element and is missing the href attribute. Semantically, an element like this should be implemented as <button>

Screenshot: Figure 3

Thuisbegeleiding

No observations added

Huishoudelijk hulp

"Keyboard navigation"

Problem: The 'Nu chatten' cta is not accessible with keyboard navigation.

Solution: The button is <a> element and is missing the href attribute. Semantically, an element like this should be implemented as <button>

Screenshot: Figure 3

Zorg of behandeling thuis

"Keyboard navigation"

Problem: The 'Nu chatten' cta is not accessible with keyboard navigation.

Solution: The button is <a> element and is missing the href attribute. Semantically, an element like this should be implemented as <button>

Screenshot: Figure 3

Dagbesteding

No observations added

Mantelzorg

No observations added

Zorg per klacht: dementie

No observations added

2.1.2: No Keyboard Trap

Entire sample

Result: Passed

Entire sample

Impact: No impact

2.1.4: Character Key Shortcuts

Entire sample

Result: Not present

Entire sample

Impact: No impact

2.2 Enough Time

Success Criterion	Result	Impact	Observations
2.2.1: Timing Adjustable	Entire sample Result: Not present	Entire sample Impact: No impact
2.2.2: Pause, Stop, Hide	Entire sample Result: Not present	Entire sample Impact: No impact

Success Criterion

Result

Impact

Observations

2.2.1: Timing Adjustable

Entire sample

Result: Not present

Entire sample

Impact: No impact

2.2.2: Pause, Stop, Hide

Entire sample

Result: Not present

Entire sample

Impact: No impact

2.3 Seizures and Physical Reactions

Success Criterion	Result	Impact	Observations
2.3.1: Three Flashes or Below Threshold	Entire sample Result: Not present	Entire sample Impact: No impact

Success Criterion

Result

Impact

Observations

2.3.1: Three Flashes or Below Threshold

Entire sample

Result: Not present

Entire sample

Impact: No impact

2.4 Navigable

Success Criterion	Result	Impact	Observations
2.4.1: Bypass Blocks	Entire sample Result: Failed	Entire sample Impact: High priority	Entire sample Observations: "Skip link is not fully functional" Problem: There's 'skip link' method in place to bypass the navigation, but the link is not visible when it receives focus. Solution: The 'skip to main content' element has visually-hidden class but the element is obscured but the main menu. Adjust the visually-hidden so that the element becomes visible (z-index). "Multiple footer landmarks" Problem: The page contains two or more HTML <footer> elements. Solution: Replace the inner footer element with a <div> Screenshot: FIgure 19
2.4.2: Page Titled	Entire sample Result: Passed	Entire sample Impact: No impact
2.4.3: Focus Order	Entire sample Result: Passed	Entire sample Impact: No impact
2.4.4: Link Purpose (In Context)	Entire sample Result: Failed Thuiszorgteam Result: Failed	Entire sample Impact: Warning Thuiszorgteam Impact: Warning	Entire sample Observations: "Links to the same page have different labels (3 occurrences)" Problem: Three links to this page https://www.zorgkaartnederland.nl/zorginstelling/wijkverpleging-omring-thuiszorg-hoorn-741 have a different label text. Links with the same destination should have the same link text. Solution: Only use the link on one part of the text or try to link labels to different parts of the destination page by using anchors. Screenshot: Figure 10 Thuiszorgteam "Link is missing href" Problem: Link with an emailaddress as text has no href Solution: Add href="mailto:..." attribute to the <a> element Screenshot: Figure 22
2.4.5: Multiple Ways	Entire sample Result: Passed	Entire sample Impact: No impact
2.4.6: Headings and Labels	Entire sample Result: Failed	Entire sample Impact: High priority	Entire sample Observations: "Link element coded as heading" Problem: the link "Chat met een medewerker" is coded is a heading but is a cta and doesn't serve as a descriptive label for a section that follows it. Solution: Code the element with a <a> tag. Screenshot: Figure 6 "Elements are missing appropriately descriptive labels" Problem: The input field and button for the search widget are missing descriptive labels that define the function of the element. When using a screen reader the input field reads "Text box", and the button reads "Button". Solution: Provide a descriptive label for each element. For instance: when adding an aria-label="Zoek" to the submit button, a screen reader would read "Button - Zoek", making the function clear to the user. "Breadcrumb is missing accessible text" Problem: The breadcrumb has no accessible text, screen reader users will not know the purpose for this list of links. Solution: Add aria-label="Breadcrumb" to the <nav> element, or fix the issue with aria-labelledby="system-breadcrumb" reported in 4.1.2: Name, Role, Value
2.4.7: Focus Visible	Entire sample Result: Passed	Entire sample Impact: No impact
2.4.11: Focus Not Obscured (Minimum)	Entire sample Result: Passed	Entire sample Impact: No impact

Success Criterion

Result

Impact

Observations

2.4.1: Bypass Blocks

Entire sample

Result: Failed

Entire sample

Impact: High priority

Entire sample

Observations:

"Skip link is not fully functional"

Problem: There's 'skip link' method in place to bypass the navigation, but the link is not visible when it receives focus.

Solution: The 'skip to main content' element has visually-hidden class but the element is obscured but the main menu. Adjust the visually-hidden so that the element becomes visible (z-index).

"Multiple footer landmarks"

Problem: The page contains two or more HTML <footer> elements.

Solution: Replace the inner footer element with a <div>

Screenshot: FIgure 19

2.4.2: Page Titled

Entire sample

Result: Passed

Entire sample

Impact: No impact

2.4.3: Focus Order

Entire sample

Result: Passed

Entire sample

Impact: No impact

2.4.4: Link Purpose (In Context)

Entire sample

Result: Failed

Thuiszorgteam

Result: Failed

Entire sample

Impact: Warning

Thuiszorgteam

Impact: Warning

Entire sample

Observations:

"Links to the same page have different labels (3 occurrences)"

Problem: Three links to this page https://www.zorgkaartnederland.nl/zorginstelling/wijkverpleging-omring-thuiszorg-hoorn-741 have a different label text. Links with the same destination should have the same link text.

Solution: Only use the link on one part of the text or try to link labels to different parts of the destination page by using anchors.

Screenshot: Figure 10

Thuiszorgteam

"Link is missing href"

Problem: Link with an emailaddress as text has no href

Solution: Add href="mailto:..." attribute to the <a> element

Screenshot: Figure 22

2.4.5: Multiple Ways

Entire sample

Result: Passed

Entire sample

Impact: No impact

2.4.6: Headings and Labels

Entire sample

Result: Failed

Entire sample

Impact: High priority

Entire sample

Observations:

"Link element coded as heading"

Problem: the link "Chat met een medewerker" is coded is a heading but is a cta and doesn't serve as a descriptive label for a section that follows it.

Solution: Code the element with a <a> tag.

Screenshot: Figure 6

"Elements are missing appropriately descriptive labels"

Problem: The input field and button for the search widget are missing descriptive labels that define the function of the element. When using a screen reader the input field reads "Text box", and the button reads "Button".

Solution: Provide a descriptive label for each element. For instance: when adding an aria-label="Zoek" to the submit button, a screen reader would read "Button - Zoek", making the function clear to the user.

"Breadcrumb is missing accessible text"

Problem: The breadcrumb has no accessible text, screen reader users will not know the purpose for this list of links.

Solution: Add aria-label="Breadcrumb" to the <nav> element, or fix the issue with aria-labelledby="system-breadcrumb" reported in 4.1.2: Name, Role, Value

2.4.7: Focus Visible

Entire sample

Result: Passed

Entire sample

Impact: No impact

2.4.11: Focus Not Obscured (Minimum)

Entire sample

Result: Passed

Entire sample

Impact: No impact

2.5 Input Modalities

Success Criterion	Result	Impact
2.5.1: Pointer Gestures	Entire sample Result: Not present	Entire sample Impact: No impact
2.5.2: Pointer Cancellation	Entire sample Result: Not present	Entire sample Impact: No impact
2.5.3: Label in Name	Entire sample Result: Passed	Entire sample Impact: No impact
2.5.4: Motion Actuation	Entire sample Result: Not present	Entire sample Impact: No impact
2.5.7: Dragging Movements	Entire sample Result: Not present	Entire sample Impact: No impact
2.5.8: Target Size (Minimum)	Entire sample Result: Passed	Entire sample Impact: No impact

3 Understandable

3.1 Readable

Success Criterion	Result	Impact	Observations
3.1.1: Language of Page	Entire sample Result: Passed	Entire sample Impact: No impact
3.1.2: Language of Parts	Entire sample Result: Passed	Entire sample Impact: No impact

Success Criterion

Result

Impact

Observations

3.1.1: Language of Page

Entire sample

Result: Passed

Entire sample

Impact: No impact

3.1.2: Language of Parts

Entire sample

Result: Passed

Entire sample

Impact: No impact

3.2 Predictable

Success Criterion	Result	Impact
3.2.1: On Focus	Entire sample Result: Passed	Entire sample Impact: No impact
3.2.2: On Input	Entire sample Result: Passed	Entire sample Impact: No impact
3.2.3: Consistent Navigation	Entire sample Result: Passed	Entire sample Impact: No impact
3.2.4: Consistent Identification	Entire sample Result: Passed	Entire sample Impact: No impact
3.2.6: Consistent Help	Entire sample Result: Passed	Entire sample Impact: No impact

3.3 Input Assistance

Success Criterion	Result	Impact	Observations
3.3.1: Error Identification	Entire sample Result: Not present	Entire sample Impact: No impact
3.3.2: Labels or Instructions	Entire sample Result: Failed	Entire sample Impact: High priority	Entire sample Observations: "Accessible labels" Problem: Widget has an accessible label but does not describe its purpose. Solution: for the chat widget, the Close button has an accessible name of "x", this should be replaced by "Close chat". The icon that links to the chat window has an accessible name of "Group", this should be "Open chat". Screenshot: Figure 11 "Duplicate labels" Problem: The search widget has the same label text for the input (placeholder) and submit button (value text) Solution: Change the placeholder for the input to "Zoeken naar" Screenshot : Figure 12 "Placeholder used for label Problem: The form control only uses placeholder="..." to provide a visible label. Solution: The input field does not have an associated label, a placeholder is not sufficient for users that rely on a screen reader. Add an associated label, it can be visually hidden and still be functional for screen readers. Screenshot: Figure 12
3.3.3: Error Suggestion	Entire sample Result: Not present	Entire sample Impact: No impact
3.3.4: Error Prevention (Legal, Financial, Data)	Entire sample Result: Not present	Entire sample Impact: No impact
3.3.7: Redundant Entry	Entire sample Result: Not present	Entire sample Impact: No impact
3.3.8: Accessible Authentication (Minimum)	Entire sample Result: Not present	Entire sample Impact: No impact

4 Robust

4.1 Compatible

Success Criterion	Result	Impact	Observations
4.1.2: Name, Role, Value	Entire sample Result: Failed Zorg thuis Result: Failed Dagbesteding Result: Failed	Entire sample Impact: High priority Zorg thuis Impact: High priority Dagbesteding Impact: High priority	Entire sample Observations: "Invalid aria-labeledby" Problem: The element's aria-labelledby="system-breadcrumb" attribute is pointing to an invalid or non-existent id. Solution: Provide an existing element with id="system-breadcrumb", that provides the label for the breadcrumb. Or replace the aria-labelledby with aria-label="Breadcrumb" Screenshot: Figure 15 "Active SVG missing aria-label" Problem: The <svg> element is the sole content of an actionable element (such as a link or button) but neither the <svg> nor the actionable element has an accessible name. Solution: Add an aria-label tot he SVG element. Screenshot: Figure 16 "Duplicate id's (8 occurrences)" Problem: There are multiple id="..." attributes with the same value. These are all provides by the SVG Solution: Rename or remove duplicate id's inside SVG elements Zorg thuis "Link function: cta is missing href" Problem: The element is coded as <a> without an href Solution: Code this element as a <button> Screenshot: Figure 9 Dagbesteding "Iframe has no title" Problem: The <iframe> for the youtube video is missing the title="..." attribute. Solution: Add the title attribute to the iframe. Screenshot: Figure 23 "Aria-hidden on parent of focusable" Problem: aria-hidden="true" is used on an element that contains one or more focusable child elements, making the element inaccessible to screen reader users. Solution: Do not use aria-hidden="true" on focusable elements. Remove the attribute. The fix for this issue depends on a third party (Youtube). Screenshot: Figure 24
4.1.3: Status Messages	Entire sample Result: Passed	Entire sample Impact: No impact

Success Criterion

Result

Impact

Observations

4.1.2: Name, Role, Value

Entire sample

Result: Failed

Zorg thuis

Result: Failed

Dagbesteding

Result: Failed

Entire sample

Impact: High priority

Zorg thuis

Impact: High priority

Dagbesteding

Impact: High priority

Entire sample

Observations:

"Invalid aria-labeledby"

Problem: The element's aria-labelledby="system-breadcrumb" attribute is pointing to an invalid or non-existent id.

Solution: Provide an existing element with id="system-breadcrumb", that provides the label for the breadcrumb. Or replace the aria-labelledby with aria-label="Breadcrumb"

Screenshot: Figure 15

"Active SVG missing aria-label"

Problem: The <svg> element is the sole content of an actionable element (such as a link or button) but neither the <svg> nor the actionable element has an accessible name.

Solution: Add an aria-label tot he SVG element.

Screenshot: Figure 16

"Duplicate id's (8 occurrences)"

Problem: There are multiple id="..." attributes with the same value. These are all provides by the SVG

Solution: Rename or remove duplicate id's inside SVG elements

Zorg thuis

"Link function: cta is missing href"

Problem: The element is coded as <a> without an href

Solution: Code this element as a <button>

Screenshot: Figure 9

Dagbesteding

"Iframe has no title"

Problem: The <iframe> for the youtube video is missing the title="..." attribute.

Solution: Add the title attribute to the iframe.

Screenshot: Figure 23

"Aria-hidden on parent of focusable"

Problem: aria-hidden="true" is used on an element that contains one or more focusable child elements, making the element inaccessible to screen reader users.

Solution: Do not use aria-hidden="true" on focusable elements. Remove the attribute. The fix for this issue depends on a third party (Youtube).

Screenshot: Figure 24

4.1.3: Status Messages

Entire sample

Result: Passed

Entire sample

Impact: No impact

Sample of Audited Web Pages

Zorg thuis - https://www.omring.nl/zorg-thuis
Thuiszorgteam - https://www.omring.nl/zorg-thuis/thuiszorgteam-zorg-behandeling-thuis
Thuisbegeleiding - https://www.omring.nl/thuisbegeleiding
Huishoudelijk hulp - https://www.omring.nl/hulpthuis
Zorg of behandeling thuis - https://www.omring.nl/zorg-thuis/zorg-behandeling-thuis
Dagbesteding - https://www.omring.nl/extra-diensten/dagbesteding
Mantelzorg - https://omring.nl/mantelzorg
Zorg per klacht: dementie - https://www.omring.nl/gezondheid/dementie

Web Technology

HTML,CSS,WAI-ARIA,JavaScript,SVG

Recording of Evaluation Specifics

Not provided