Issues:
Quick scan digital accessibility sunweb.nl

(Issues only)

Scope of the evaluation

Detailed audit results

1. Perceivable

1.1 Text Alternatives

1.1.1 Non-text Content (Level A)

Information about success criterion 1.1.1 Non-text Content

Finding 1: A cookie consent banner appears when visiting https://www.sunweb.nl/ for the first time/if you have not consented yet. The Sunweb logo only contains the alternative text "CookieInfo", which does not describe the function/features of this image. Blind website visitors must be specifically alerted to the fact that this is a logo, and since it also serves as a link to the homepage it should be described as such. Change the text, for example to "Logo Sunweb - Ga naar de website van CookieInfo".

Finding 2: The header on https://www.sunweb.nl/vakantie/zoeken contains the Sunweb logo as an SVG. The image visually conveys meaning, but lacks a text alternative. Describe the function/features of this image. Blind website visitors must be specifically alerted to the fact that this is a logo, and since it also serves as a link to the homepage it should be described as such. A solution would be to add role=img and a title element containing the text alternative as the first child element of the SVG.

Finding 3: The page https://www.sunweb.nl/ features a background image behind the headings "Vakanties om van te houden" (h1) and "Boek nu tijdelijk met hoge kortingen" (h2). The image has no text alternative, which is not necessary for decorative images. It does however require an empty alt attribute (alt=""), so all forms of assistive technology can ignore it.

Finding 4: The page https://www.sunweb.nl/ contains an image which visually features the text "Nu tot €400 vroegboekkorting per persoon". This image contains the text alternative "Early booking", and does not convey (all) the information provided. Make sure the text is present for all visitors, including the visually impaired. By amending the text alternative for example, or by placing the same information on the page a different way and adding and empty alt attribute (alt="") tot he image. The image also serves as a link, so it should also contain information about the target page. A good text could be "Nu tot €400 vroegboekkorting per persoon: Boek jouw zomervakantie 2025 nu extra voordelig, naar pagina vroegboekkorting".

1.2 Time-based Media

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Information about success criterion 1.2.1 Audio-only and Video-only (Prerecorded)

Finding 5: This criterion has not been (fully) researched for the purposes of this quick scan.

1.2.2 Captions (Prerecorded) (Level A)

Information about success criterion 1.2.2 Captions (Prerecorded)

Finding 6: This criterion has not been (fully) researched for the purposes of this quick scan.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Information about success criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)

Finding 7: This criterion has not been (fully) researched for the purposes of this quick scan.

1.2.4 Captions (Live) (Level AA)

Information about success criterion 1.2.4 Captions (Live)

Finding 8: This criterion has not been (fully) researched for the purposes of this quick scan.

1.2.5 Audio Description (Prerecorded) (Level AA)

Information about success criterion 1.2.5 Audio Description (Prerecorded)

Finding 9: This criterion has not been (fully) researched for the purposes of this quick scan.

1.3 Adaptable

1.3.1 Info and Relationships (Level A)

Information about success criterion 1.3.1 Info and Relationships

Finding 10: The Sunweb logo on https://www.sunweb.nl/ is placed in a link element (a) which contains aria role="menuitem" in it's parent. This aria role is used in combination with menu, menubar or group, which allows assistive technology to convey certain structures to its' users. Remove this role from the link element, as it does not serve such a purpose. This is also the case for the buttons in the main menu ("Ons aanbod", "Vroegboekkorting" and "Last minutes" amongst others).

Finding 11: The main menu items on https://www.sunweb.nl/ have been placed in list items (li), in turn nested in an unordered list (ul). The list items contain the attribute role="none", which is not allowed on such an element. This occurs throughout the website, including the heart-shaped favorites icon and the "Mijn Sunweb" item.

1.3.2 Meaningful Sequence (Level A)

Information about success criterion 1.3.2 Meaningful Sequence

Finding 12: This criterion has not been (fully) researched for the purposes of this quick scan.

1.3.3 Sensory Characteristics (Level A)

Information about success criterion 1.3.3 Sensory Characteristics

Finding 13: This criterion has not been (fully) researched for the purposes of this quick scan.

1.3.4 Orientation (Level AA)

Information about success criterion 1.3.4 Orientation

Finding 14: This criterion has not been (fully) researched for the purposes of this quick scan.

1.3.5 Identify Input Purpose (Level AA)

Information about success criterion 1.3.5 Identify Input Purpose

Finding 15: The form on https://www.sunweb.nl/login allows users to fill out their own e-mail address and password. The purpose of these and other similar fields must be programmatically determinable, meaning author-supplied data should be recognised by user agents including assistive technologies. A user should be able to have the aforementioned fields filled out automatically, or be given extra aid during input. In this case that can be achieved by for example using the attribute autocomplete="email" for the corresponding field. An overview of where the autocomplete can be applied and the possible attribute values can be found on the page: https://www.w3.org/tr/wcag21/#input-purposes.

1.4 Distinguishable

1.4.1 Use of Color (Level A)

Information about success criterion 1.4.1 Use of Color

Finding 16: This criterion has not been (fully) researched for the purposes of this quick scan.

1.4.2 Audio Control (Level A)

Information about success criterion 1.4.2 Audio Control

Finding 17: This criterion has not been (fully) researched for the purposes of this quick scan.

1.4.3 Contrast (Minimum) (Level AA)

Information about success criterion 1.4.3 Contrast (Minimum)

Finding 18: A cookie consent banner appears when visiting https://www.sunweb.nl/ for the first time/if you have not consented yet. The red button (HEX #ED2924) for cookie acceptance has a 4.2:1 contrast ratio with the white text, where 4.5:1 is the minimal standard set by this criterion. Contrast below this standard poses a problem for people with poor eyesight and color blindness. Use a color combination with sufficient contrast.

Finding 19: The buttons "Zon","Wintersport" and "Cruises" under the h2 heading "Boek nu tijdelijk met hoge kortingen" on https://www.sunweb.nl/ do not meet the minimum contrast ratio when a button is active. "Zon" for example, results in red text and contour (HEX #FF333F) which has a 3.6:1 contrast ratio with the white background, where 4.5:1 is the minimal standard set by this criterion. Contrast below this standard poses a problem for people with poor eyesight and color blindness. Use a color combination with sufficient contrast.

Finding 20: Four images with underlying tekst under the h2 heading "It's a Sunweb holiday! #creatingmemories" on https://www.sunweb.nl/ pose color contrast issues. The grey text (HEX #928D8B) under the h5 heading "1e kind gratis verblijf" has a contrast ratio of 3.2:1 with the white background, where 4.5:1 is the minimal standard set by this criterion. Contrast below this standard poses a problem for people with poor eyesight and color blindness. Use a color combination with sufficient contrast.
Similar contrast issues are present on the same page, for example under the h5 heading "Verzekeringen regelen" and hotel locations in the cards under the h2 heading "Bekijk onze unieke toplocaties".

Finding 21: The color contrast ratio between grey footer (#B5B0AB) on https://www.sunweb.nl/ and the white text it contains (Over Sunweb, Contact, Vacature etc) does not meet the 4.5:1 minimal standard set by this criterion. The contrast should be significantly raised from 2.1:1 as it poses a problem for people with poor eyesight and color blindness. Use a color combination with sufficient contrast.

Finding 22: The form field "Wanneer" on https://www.sunweb.nl/vakantie/zoeken contains the placeholder text "Vertrekdatum toevoegen", which has a 3.2:1 contrast with the background, where it ought to meet a minimum of 4,5:1 as set by this criterion.
Similar contrast issues can be found on the same page regarding the visual labels and placeholder texts "Luchthaven toevoegen" and "Bestemming". Also note issues concerning the hotel search results under the text "2328 zonvakanties".

Finding 23: A list of hotels is present under the text "2328 zonvakanties" on https://www.sunweb.nl/vakantie/zoeken. The images of some results contain a red label (HEX #FF333F) with white text, for example "Vroegboek Topsellers" ont he first result. The color contrast ratio is 3.6:1 where it ought to meet a minimum of 4,5:1 as set by this criterion. Contrast below this standard poses a problem for people with poor eyesight and color blindness. Use a color combination with sufficient contrast.

Finding 24: A list of hotels is present under the text "2328 zonvakanties" on https://www.sunweb.nl/vakantie/zoeken. Some of the hotels have been reduced in price, made visible with a pink label (HEX #FAFAC9) containing a red percentage value (HEX #ED2924), for example "14%" on the first search result. The contrast between the text and the background is 2.9:1 while the minimum set by this criterion is 4.5:1. Contrast below this standard poses a problem for people with poor eyesight and color blindness. Use a color combination with sufficient contrast.

1.4.4 Resize text (Level AA)

Information about success criterion 1.4.4 Resize text

Finding 25: Every page contains the settings "maximum-scale=1.0" en "user-scalable=no" under meta name="viewport" in the HTML-code. The consequence of these settings include that in some cases visitors of the website cannot use zoom. Refrain from using such settings, to make sure the website is scalable. See SC 1.4.10 as well for the same issues.

1.4.5 Images of Text (Level AA)

Information about success criterion 1.4.5 Images of Text

Finding 26: This criterion has not been (fully) researched for the purposes of this quick scan.

1.4.10 Reflow (Level AA)

Information about success criterion 1.4.10 Reflow

Finding 27: Every page contains the settings "maximum-scale=1.0" en "user-scalable=no" under meta name="viewport" in the HTML-code. The consequence of these settings include that in some cases visitors of the website cannot use zoom. Refrain from using such settings, to make sure the website is scalable. See SC 1.4.4 as well for the same issues.

1.4.11 Non-text Contrast (Level AA)

Information about success criterion 1.4.11 Non-text Contrast

Finding 28: This criterion has not been (fully) researched for the purposes of this quick scan.

1.4.12 Text Spacing (Level AA)

Information about success criterion 1.4.12 Text Spacing

Finding 29: This criterion has not been (fully) researched for the purposes of this quick scan.

1.4.13 Content on Hover or Focus (Level AA)

Information about success criterion 1.4.13 Content on Hover or Focus

Finding 30: This criterion has not been (fully) researched for the purposes of this quick scan.

2. Operable

2.1 Keyboard Accessible

2.1.1 Keyboard (Level A)

Information about success criterion 2.1.1 Keyboard

Finding 31: This criterion has not been (fully) researched for the purposes of this quick scan.

2.1.2 No Keyboard Trap (Level A)

Information about success criterion 2.1.2 No Keyboard Trap

Finding 32: This criterion has not been (fully) researched for the purposes of this quick scan.

2.1.4 Character Key Shortcuts (Level A)

Information about success criterion 2.1.4 Character Key Shortcuts

Finding 33: This criterion has not been (fully) researched for the purposes of this quick scan.

2.2 Enough Time

2.2.1 Timing Adjustable (Level A)

Information about success criterion 2.2.1 Timing Adjustable

Finding 34: This criterion has not been (fully) researched for the purposes of this quick scan.

2.2.2 Pause, Stop, Hide (Level A)

Information about success criterion 2.2.2 Pause, Stop, Hide

Finding 35: This criterion has not been (fully) researched for the purposes of this quick scan.

2.3 Seizures and Physical Reactions

2.3.1 Three Flashes or Below Threshold (Level A)

Information about success criterion 2.3.1 Three Flashes or Below Threshold

Finding 36: This criterion has not been (fully) researched for the purposes of this quick scan.

2.4 Navigable

2.4.1 Bypass Blocks (Level A)

Information about success criterion 2.4.1 Bypass Blocks

Finding 37: Every page lacks a mechanism to skip repetitious content. Keyboard/assistive technology users should be able to reach the unique page content without having to pass the same menu items, login sections etc. that are featured on each page. This can be achieved by adding one or several skiplinks to a page, which redirects the focus to the aforementioned content. The link should be the first focusable link on the page. It may be visually hidden, but must become visible upon keyboard initiation.

2.4.2 Page Titled (Level A)

Information about success criterion 2.4.2 Page Titled

Finding 38: This criterion has not been (fully) researched for the purposes of this quick scan.

Finding 39: Advice: The website does not use a consistent title structure. The homepage is named "Vakantie boeken | ❤️ vakantie met Sunweb", the search page "Zoekpagina - Sunweb Zonvakanties" and the user environment "Mijn Sunweb | Al jouw boekingsgegevens". It is advisable to use a good short descriptor of the specific page, followed by the website name. Visitors will know which website they are visiting, and what the contents of the specific page/tab is. This is beneficial to optimize navigation.

2.4.3 Focus Order (Level A)

Information about success criterion 2.4.3 Focus Order

Finding 40: This criterion has not been (fully) researched for the purposes of this quick scan.

2.4.4 Link Purpose (In Context) (Level A)

Information about success criterion 2.4.4 Link Purpose (In Context)

Finding 41: This criterion has not been (fully) researched for the purposes of this quick scan.

2.4.5 Multiple Ways (Level AA)

Information about success criterion 2.4.5 Multiple Ways

Finding 42: This criterion has not been (fully) researched for the purposes of this quick scan.

2.4.6 Headings and Labels (Level AA)

Information about success criterion 2.4.6 Headings and Labels

Finding 43: The text fields "E-mailadres" and "Wachtwoord" on https://www.sunweb.nl/login are not visually labelled (placeholders disappear once input is commenced). Consequently visitors will not always know what to fill in (the icons remain visible, but their contrast may be an issue for the colour-blind). Provide visual labels for the fields and associate them in HTML. See SC 3.3.2. for placeholders specifically.

2.4.7 Focus Visible (Level AA)

Information about success criterion 2.4.7 Focus Visible

Finding 44: Navigational focus is not always visible for keyboard users on https://www.sunweb.nl/. Some elements are provided focus indicator with a black boundary, others are red and some do not have a clear one at all. Make sure that the entire boundary of focus indicators is clearly visible. Also see https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance-minimum.html for tips regarding good visibility.

Finding 45: It is not always clear to those who rely on their keyboard to navigate, what they focus is on in the drop down navigation under "Ons aanbod" on https://www.sunweb.nl/. Optically there is no focus indicator present in traditional sense: it is set apart from the other items by means of a marginally different grey teint. This cannot be observed by all visitors, specifically impacting the color-blind and those with low vision. Make the distinction in focus more visible to solve this problem.

2.5 Input Modalities

2.5.1 Pointer Gestures (Level A)

Information about success criterion 2.5.1 Pointer Gestures

Finding 46: This criterion has not been (fully) researched for the purposes of this quick scan.

2.5.2 Pointer Cancellation (Level A)

Information about success criterion 2.5.2 Pointer Cancellation

Finding 47: This criterion has not been (fully) researched for the purposes of this quick scan.

2.5.3 Label in Name (Level A)

Information about success criterion 2.5.3 Label in Name

Finding 48: This criterion has not been (fully) researched for the purposes of this quick scan.

2.5.4 Motion Actuation (Level A)

Information about success criterion 2.5.4 Motion Actuation

Finding 49: This criterion has not been (fully) researched for the purposes of this quick scan.

3. Understandable

3.1 Readable

3.1.1 Language of Page (Level A)

Information about success criterion 3.1.1 Language of Page

Finding 50: This criterion has not been (fully) researched for the purposes of this quick scan.

3.1.2 Language of Parts (Level AA)

Information about success criterion 3.1.2 Language of Parts

Finding 51: The Sunweb logo and menu items on https://www.sunweb.nl/ are contained in a nav element. Screenreader users hear the English aria-label "Main menu" announced, whilst the language of the page is set to Dutch. Make sure all aria-labels are also translated to Dutch, in order for assistive technology to pronounce words correctly.
Similar issues can be found throughout the site, on the menu bar for example ("menubar-navigation") and on the favorites & "Mijn Sunweb" buttons ("menubar-action-items"). Translate texts where needed.

3.2 Predictable

3.2.1 On Focus (Level A)

Information about success criterion 3.2.1 On Focus

Finding 52: This criterion has not been (fully) researched for the purposes of this quick scan.

3.2.2 On Input (Level A)

Information about success criterion 3.2.2 On Input

Finding 53: This criterion has not been (fully) researched for the purposes of this quick scan.

3.2.3 Consistent Navigation (Level AA)

Information about success criterion 3.2.3 Consistent Navigation

Finding 54: This criterion has not been (fully) researched for the purposes of this quick scan.

3.2.4 Consistent Identification (Level AA)

Information about success criterion 3.2.4 Consistent Identification

Finding 55: This criterion has not been (fully) researched for the purposes of this quick scan.

3.3 Input Assistance

3.3.1 Error Identification (Level A)

Information about success criterion 3.3.1 Error Identification

Finding 56: Should visitors leave a text field empty or enter incorrect information, error messages appear under the fields. For example "Er moet een e-mailadres worden ingevuld'" (an e-mail address must be provided). A good error identifier mentions what mistake is made and where. For example 'the field e-mail address has not been filled in'. There is a distinction between an error identifier and an error suggestion. The latter, stating a field is mandatory, is covered by SC 3.3.3.

3.3.2 Labels or Instructions (Level A)

Information about success criterion 3.3.2 Labels or Instructions

Finding 57: The text fields "E-mailadres" and "Wachtwoord" on https://www.sunweb.nl/login have a placeholder text but no visible label. The placeholder text does not suffice, as it disappears once a visitor starts typing. For some people it can be difficult to remember what they need to fill out, especially if there are multiple fields. Add a label that always remains visible (perhaps a placeholder that relocates into the focus indicator) to solve this issue.

3.3.3 Error Suggestion (Level AA)

Information about success criterion 3.3.3 Error Suggestion

Finding 58: All text forms on https://www.sunweb.nl/login are mandatory (this might seem obvious, but poses a potential issue should more fields be added). Under this criterion such fields must be clearly marked, for example with the use of an asterisk and a legend.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Information about success criterion 3.3.4 Error Prevention (Legal, Financial, Data)

Finding 59: This criterion has not been (fully) researched for the purposes of this quick scan.

4. Robust

4.1 Compatible

4.1.1 Parsing (Level A)

Information about success criterion 4.1.1 Parsing

Finding 60: This criterion has not been (fully) researched for the purposes of this quick scan.

4.1.2 Name, Role, Value (Level A)

Information about success criterion 4.1.2 Name, Role, Value

Finding 61: One can search for a vacation on https://www.sunweb.nl/ by means of various filters: "Vertrekdatum", "Met wie & hoeveel kamers?", "Aantal dagen" and "Bestemming". These fields aren't associated with accessible labels. The placeholders function as visual labels, but that does not suffice for this criterion. There are various issues regarding placeholders: the ones used disappear once input is initiated and placeholders in general are not always announced by all forms of assistive technology. Make sure the fields have a label that remains on the page so visitors are aware of the required input at all times.
A similar issue can be found on https://www.sunweb.nl/login. Also see SC 3.3.2 for this topic.

Finding 62: One can search for a vacation on https://www.sunweb.nl/ by means of various filters: "Vertrekdatum", "Met wie & hoeveel kamers?", "Aantal dagen" and "Bestemming". Once an option is chosen, the field that requires the number of vacation days contains the choice and an 'x' to remove the choice. This icon has the function of a button but does not have an accessible name. Users of assistive technology such as screenreaders will not be informed what the button does. Make sure all such interactive components have accessible names.

4.1.3 Status Messages (Level AA)

Information about success criterion 4.1.3 Status Messages

Finding 63: This criterion has not been (fully) researched for the purposes of this quick scan.

Basis for this evaluation

The audit was conducted based on the evaluation method of the W3C, WCAG-EM. This is largely done manually by taking a sample. For a quickscan we use parts of this methodology. Despite all the researcher's care and experience, it is possible that a problem has not been identified. Keep in mind that in a next audit certain parts could be assessed differently because of further development of techniques and assistive software. Tools are used in the manual audit.

Sample of audited web pages

• homepage:
  https://www.sunweb.nl/
• login area:
  https://www.sunweb.nl/login
• search results:
  https://www.sunweb.nl/vakantie/zoeken
• specific search result:
  https://www.sunweb.nl/vakantie/egypte/rode-zee/el-gouna/hotel-three-corners-rihana-resort-rihana-inn
• Mijn Sunweb environment:
  https://www.sunweb.nl/mijn-sunweb

Relied upon techniques

• HTML5
• CSS
• WAI-ARIA
• ECMAScript 5
• DOM
• SVG

Resources:

• Website Accessibility Conformance Evaluation Methodology (WCAG-EM)
  www.w3.org/WAI/eval/conformance
• Web Content Accessibility Guidelines (WCAG)
  www.w3.org/WAI/intro/wcag
• How to Meet WCAG 2.1 Quick Reference
  www.w3.org/WAI/WCAG21/quickref/

This report is mainly created with the online W3C report tool.