Accessibility Evaluation

Report:
Quick scan digital accessibility sunweb.dk


Evaluator
Mirjam, Swink
Date
18 February 2025
Commissioner
Sunweb Group Netherlands B.V.

Summary of the evaluation findings

The website Sunweb.dk does not comply to WCAG 2.1 level AA yet. 16 out of 50 success criteria contain one or more issues. This document describes to what extent the website meets the accessibility requirements captured in WCAG, the Web Content Accessibility Guidelines.

The website https://www.sunweb.nl has been audited between the 27th of Januari and the 18th of February 2025. For this inspection the WCAG-EM evaluation method has been followed as much as possible. During the inspection various discrepancies have been found. This document is a quick scan and cannot be used to claim an accessibility status based on the inspection alone: this would require a full audit. Due to the intrinsic nature of a quick scan, WCAG criterion have not been set to 'passed' as it cannot be confirmed that issues may arise elsewhere on the website.

During this quick scan multiple accessibility issues have been identified relating to various criteria. Notable issues include:

The audit focuses specifically on the accessibility of the website for people with a disability, such as people who are blind, deaf, low-literate or have other functional problems. For them it is important that the website is technically and substantively designed in such a way that the site is usable. Optimizing a website for accessibility has more advantages; it makes the website more usable for everyone (for example also for people who look at their mobile phone in a sunny environment) and it makes the site easier to find in search engines.

Scope of the evaluation

Website name Sunweb.dk
Scope of the website The scope of the audit includes:
  • All pages on sunweb.dk.
The scope of the audit excludes:
  • Sub-website(s) where the HTML and/or the system differs from sunweb.dk.
  • All external systems and websites that are linked to via sunweb.dk.
Conformance target WCAG 2.1 level AA
Accessibility support baseline Common browsers and assistive technologies.

Overview of audit results

Principle Passed Failed Can't tell
1 Perceivable 0 9 11
2 Operable 0 4 13
3 Understandable 0 2 8
4 Robust 0 1 2
Total 0 16 34

Reading Guide

This evaluation is a snapshot. The website might have been changed. The problems found are only examples. Therefore, check for any problem whether this also occurs in other places. This evaluation is just a sample of a few pages. As many different types of pages are included in the sample as possible to get the best impression of the accessibility. Pay attention! New problems may arise when making improvements or changes to the website/app. Success criteria marked with "Not present" are automatically approved. Success criteria marked with "Unknown" or "Can't tell" are not approved.

Detailed audit results


1. Perceivable

1.1 Text Alternatives

1.1.1 Non-text Content (Level A)

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.

Information about success criterion 1.1.1 Non-text Content

Outcome: Failed

Findings: A cookie consent banner appears when visiting https://www.sunweb.nl/ for the first time. The image with the Sunweb logo only contains the alternative text "CookieInfo". This does not describe what is seen on the image. For blind visitors of the website, it is important that assistive software such as a screenreader can read that this is a logo, and all the text that can be seen on the image. Because the image is in a link that leads to another website, it is also important this is described as such. To solve this, first remove the role="presentation" attribute from the image, than change the text of the alt-attribute. For example to 'Logo Sunweb, go to the website CookieInfo' (but than in Danish). See also succes criterion 2.4.4.

On the website there are several decorative images. These images have no alternative text, but are also not hidden for assistive software. This causes a problem for blind visitors, who know that there is an image here but do not know what image it is. An alternative text is not necessary for decorative images. Make sure that these images can be ignored by assistive software, by adding an empty alt-attribute to the img-elements. A few examples of images where this problem occurs:

  • The image in the heading of each page.
  • On https://www.sunweb.dk/ the image on the background of heading 'Solrige ferier sydpå hele året runt'.
  • On https://www.sunweb.dk/rejser the image on the background of heading 'Oplev den perfekte solferi i Tyrkiet'.

On page https://service.sunweb.com/da/support/home, the image that contains the Sunweb logo has an alternative text 'Freshworks Logo'. This does not describe the right logo. Change the text to solve this problem. Blind website visitors must be specifically alerted to the fact that this is a logo, and all the text that can be seen in the logo needs to be added to the alternative text. A good alternative text would be 'Sunweb Logo'. The image is in a link that leads to the homepage, so a text like 'go to homepage' (but in Danish) can be added.

On page https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/ in the footer several logo's can be found under heading-text 'Sunweb er tilknyttet'. These are formatted as one image in one link. The image and the link are missing an alternative text. Add an alternative text which contains the word 'Logo' and all the text from the logo's. Another solution would be to format this image and link as sereral images in several links, as is done on other pages. See also succes criterion 2.4.4.

On page https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/ there is an image of Camilla. This image has no alternative text. Add an alt-attribute and a text which describes who can be seen on the image.

On page https://www.sunweb.dk/rejser are a lot of images under 'Vores gæster på Instagram'. The alt-text does not describe what is seen on the images. For example the image with alt-text 'Foto av alexandra_staff.... offentliggjort på 30. november 2024'. Replace the text by a text that describes the image.


1.2 Time-based Media

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

For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:

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

Outcome: Can't tell

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


1.2.2 Captions (Prerecorded) (Level A)

Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

Information about success criterion 1.2.2 Captions (Prerecorded)

Outcome: Can't tell

Findings: 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)

An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

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

Outcome: Can't tell

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


1.2.4 Captions (Live) (Level AA)

Captions are provided for all live audio content in synchronized media.

Information about success criterion 1.2.4 Captions (Live)

Outcome: Can't tell

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


1.2.5 Audio Description (Prerecorded) (Level AA)

Audio description is provided for all prerecorded video content in synchronized media.

Information about success criterion 1.2.5 Audio Description (Prerecorded)

Outcome: Can't tell

Findings: 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, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Information about success criterion 1.3.1 Info and Relationships

Outcome: Failed

Findings: The menu (for example on https://www.sunweb.dk/) contains several menu-items. These are links on which the 'role="menuitem"' attribute is placed. For this attribute it is required that there is also an aria-parent role, such as 'role="menu"'. If used correctly, this conveys information about the structure of the menu to users of assistive software. In this case, the use of this attribute does not give the right information. The role can be removed from the Sunweb-logo (link to homepage). For the other menu-items the 'role="menuitem"' can be removed, as the list elements are correctly used. It is also important to remove the 'role="none" from the list-items. This way the structure of the menu can be understood correctly.

Under the header on https://www.sunweb.dk/ are three list-items (e.g. 'Prisgaranti', 'Fleksibel ombooking'). The li-element is used for this list-items. For list-items it is required that they are nested in a list (ol or ul). Otherwise, the structure of the list cannot be understood by screenreader users. Make sure to make up the list correctly.

Advice: The heading structure is not properly formatted on several pages. For visitors using assistive software such as a screen reader, a heading structure is important because it is posible to navigate by retrieving a list of headings. It will fail this succes criterion if the heading structure is not well constructed, but improving it ensures that the structure of the content can be better interpreted. Provide a good heading structure, starting with a heading level h1 for the most important heading (title of the page), heading level h2 for the headings, heading level h3 for the intermediate headings, and so on. Do not skip any headings in the process.

Some examples of an incorrect heading structure are:


1.3.2 Meaningful Sequence (Level A)

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Information about success criterion 1.3.2 Meaningful Sequence

Outcome: Can't tell

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


1.3.3 Sensory Characteristics (Level A)

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

Information about success criterion 1.3.3 Sensory Characteristics

Outcome: Can't tell

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


1.3.4 Orientation (Level AA)

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.

Information about success criterion 1.3.4 Orientation

Outcome: Can't tell

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


1.3.5 Identify Input Purpose (Level AA)

The purpose of each input field collecting information about the user can be programmatically determined when:

Information about success criterion 1.3.5 Identify Input Purpose

Outcome: Failed

Findings: The form on https://www.sunweb.dk/login?returnUrl=/mit-sunweb 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 there is an autocomplete attribute, but this is set to 'off'. Change this to 'email'. 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)

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Information about success criterion 1.4.1 Use of Color

Outcome: Failed

Findings: On page https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/, the footer contains the links 'her' and 'kontakt'. Only color is used to make clear that these are links, but it is difficult to see the difference with normal text. Make sure color is not the only way to convey information (that these are links). The best solution would be to underline the linktext if they are in a sentence like here.


1.4.2 Audio Control (Level A)

If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

Information about success criterion 1.4.2 Audio Control

Outcome: Can't tell

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


1.4.3 Contrast (Minimum) (Level AA)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:

Information about success criterion 1.4.3 Contrast (Minimum)

Outcome: Failed

Findings: The cookie banner that appears when visiting https://www.sunweb.dk/ for the first time, contains the red (HEX #ED2924) button 'Tillad cookies'. The red color does not have enough contrast to the white text. The contrast ratio is 4.2:1. According to this succes criterion, the minimal contrast ratio should be 4.5:1.

On the homepage https://www.sunweb.dk/ a lot of white heading-texts are placed on an image that contains several colors. If a visitor zooms in on the page, the text is placed on different background colors. On several places contrast-issues occur. For example the heading-tekst 'Last minute-tilbud: Skiferier fra 1.999,- per person..'. A shadow is added to the white text, the darkest point is grey (HEX #959193). The contrastratio to almost white (HEX #F1F0F5) background is too low, it is 2.7:1 where a minimum of 4.5:1 is required. The same problem occurs on more pages, for example https://www.sunweb.dk/rejser 'Fantastiske messetilbud med store rabatter'.

On homepage https://www.sunweb.dk/ there is grey (HEX #928D8B) text on a white background. For example the text 'Vinterferie under solen fra 2.999,-'. The contrastratio is too low, it is 3.2:1 where this should be a minimum of 4.5:1.

On the homepage are a lot of red (HEX FF333F) buttons which contain white text. For example 'Vis 1477 Rejser' and 'Se tilbud'. The contrastratio is 3.6:1, this should be a minimum of 4.5:1. This color combination also applies to the button 'Sol' in the header. The same color combination can also be found on other pages, for example on https://www.sunweb.dk/rejser/sog?Country%5B0%5D=12&Duration%5B0%5D=8-8&Participants%5B0%5D%5B0%5D=1994-03-20&Participants%5B0%5D%5B1%5D=1994-03-20&ParticipantsDistribution=1%7C2&TransportType=Flight.

On page https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/ the links 'Spørgsmål og kontakt'and 'Mit Sunweb' do not have enough contrast to the background. The dark grey (HEX #7A7776) text has a contrastratio of 4.2:1 to the light grey (HEX #FAFAFA) background. A minimum contrast ratio of 4.5:1 is required.

On page https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/ there are links in the text. For example 'Camilla' and 'Les Trois Vallées'. The contrast between the red (HEX #F05451) text and the white background is too low. The contrast ratio is 3.4:1, where it should be minimal 4.5:1.

On https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/ there is a button with the white text 'Tilbage'. The contrastratio to the red (HEX #ED2426) background is too low, it is 4.3:1 where a minimum of 4.5:1 is required.

On page https://www.sunweb.dk/rejser/sog?Country%5B0%5D=12&Duration%5B0%5D=8-8&Participants%5B0%5D%5B0%5D=1994-03-20&Participants%5B0%5D%5B1%5D=1994-03-20&ParticipantsDistribution=1%7C2&TransportType=Flight there labels on the images. These contain the white text 'Selections' on an orange (HEX #F66E20) background. The contrastratio is 2.9:1 where this should be a minimum of 4.5:1.

On page https://www.sunweb.dk/rejser/sog?Country%5B0%5D=12&Duration%5B0%5D=8-8&Participants%5B0%5D%5B0%5D=1994-03-20&Participants%5B0%5D%5B1%5D=1994-03-20&ParticipantsDistribution=1%7C2&TransportType=Flight a lot of grey colored text are used on several places. These text can be hard to read for some visitors, as the contrastratio is too low. An example: the grey (HEX #928D2B) numbers on light-grey (HEX #FBF9F6) background, next to the checkbox-labels under 'Forplejning'.


1.4.4 Resize text (Level AA)

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

Information about success criterion 1.4.4 Resize text

Outcome: Failed

Findings: 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)

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:

Information about success criterion 1.4.5 Images of Text

Outcome: Can't tell

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


1.4.10 Reflow (Level AA)

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

Except for parts of the content which require two-dimensional layout for usage or meaning.

Information about success criterion 1.4.10 Reflow

Outcome: Failed

Findings: 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.11 Non-text Contrast (Level AA)

The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):

Information about success criterion 1.4.11 Non-text Contrast

Outcome: Failed

Findings: On several pages icons that convey information can be found. The colors used for this icons do not have enough contrast to the background, which can make it difficult to see them for some visitors. An example is on page https://www.sunweb.dk/rejser/sog?Country%5B0%5D=12&Duration%5B0%5D=8-8&Participants%5B0%5D%5B0%5D=1994-03-20&Participants%5B0%5D%5B1%5D=1994-03-20&ParticipantsDistribution=1%7C2&TransportType=Flight the info-button '?' behind the text 'Hvad mener vi med popularitet'. The grey (HEX #B5B0AB) color has a contrastratio of 2.1:1, where this should be a minimum of 3:1. Another example on this page is the close-icon ('x') on the label 'Spanien x', which is browngrey (HEX #A07E68) and has a contrastratio of 2.8:1 to the grey (HEX #E7E0D7) background. Make sure all non-text items that convey essential information have a contrastratio of minimum 3:1.


1.4.12 Text Spacing (Level AA)

In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:

Information about success criterion 1.4.12 Text Spacing

Outcome: Can't tell

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


1.4.13 Content on Hover or Focus (Level AA)

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

Information about success criterion 1.4.13 Content on Hover or Focus

Outcome: Failed

Findings: On https://www.sunweb.dk/, a visitor can select a date in the field 'Afrejsedato'. If the focus is brought to this field using the keyboard, a calendar unfolds. This calendar stays unfolded, even if the focus is brought to another element on the website. Make sure the calendar can be closed, for example by using the escape key. The same problem, with the same field, occurs on page https://www.sunweb.dk/rejser/sog?Country%5B0%5D=12&Duration%5B0%5D=8-8&Participants%5B0%5D%5B0%5D=1994-03-20&Participants%5B0%5D%5B1%5D=1994-03-20&ParticipantsDistribution=1%7C2&TransportType=Flight.


2. Operable

2.1 Keyboard Accessible

2.1.1 Keyboard (Level A)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

Information about success criterion 2.1.1 Keyboard

Outcome: Failed

Findings: A cookie consent banner appears when visiting https://www.sunweb.nl/ for the first time. The Sunweb logo is a link to the CookieInfo website. This link can not easily be reached by using the tab-key on the keyboard, because 'tabindex="-1"' is added to the link. Remove this attribute.


2.1.2 No Keyboard Trap (Level A)

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

Information about success criterion 2.1.2 No Keyboard Trap

Outcome: Can't tell

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


2.1.4 Character Key Shortcuts (Level A)

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

Information about success criterion 2.1.4 Character Key Shortcuts

Outcome: Can't tell

Findings: 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)

For each time limit that is set by the content, at least one of the following is true:

Information about success criterion 2.2.1 Timing Adjustable

Outcome: Can't tell

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


2.2.2 Pause, Stop, Hide (Level A)

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

Information about success criterion 2.2.2 Pause, Stop, Hide

Outcome: Can't tell

Findings: 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)

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

Information about success criterion 2.3.1 Three Flashes or Below Threshold

Outcome: Can't tell

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


2.4.1 Bypass Blocks (Level A)

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Information about success criterion 2.4.1 Bypass Blocks

Outcome: Failed

Findings: Every page lacks a mechanism to skip repetitious content (a skiplink). Visitors who use the keyboard to navigate (which includes visitors who use assistive software) 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 first unique content on the page. The link should be the first focusable link on the page. It may be visually hidden, but must become visible upon keyboard initiation.

Advice: The carousel on https://www.sunweb.dk/rejser (under 'Gæsternes favoritter') contains a lot of focusable elements. It is not required for this succes criterium, but it would be better to add a way in which the visitor can skip this carousel. That would make navigation more efficient for visitor who use the keyboard to do this.


2.4.2 Page Titled (Level A)

Web pages have titles that describe topic or purpose.

Information about success criterion 2.4.2 Page Titled

Outcome: Can't tell

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


2.4.3 Focus Order (Level A)

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

Information about success criterion 2.4.3 Focus Order

Outcome: Failed

Findings: The menu (for example on https://www.sunweb.dk/) contains a menu-item that can be expanded, 'Vores tilbud'. If expanded, it is possible to leave the submenu by using the tab-key, without the submenu being folded in again. The submenu hides elements of the pages at that moment, so visitors who navigate using the keyboard but are able to see cannot see where the focus is. Make sure the focus can only leave the submenu after folding this submenu in.

On page https://www.sunweb.dk/, after zooming in the menu is found under a menu-button. After unfolding the menu, de focus order is not correct. the submenu-items that belong to menu-item 'Vores tilbud' are skipped, and it is possible to leave the menu and focus on elements on the page that are currently hidden by the menu. Make sure al focusable items in the menu can be reached, and that the focus can leave the menu only after closing it.

The menu (for example on https://www.sunweb.dk/) contains a submenu under menu-item 'Vores tilbud'. Visitors who use the keyboard to navigate, can go through the whole menu correctly. But after the last menu-item (Mit Sunweb), the focus goes to all the items of the submenu. Even if this is folded in at that moment. For visitors who can see it is not clear where the focus is at that moment. For visitors who cannot see, it is not clear they are in a submenu now. Make sure the focus cannot be brought to elements that are not visible on the site at that moment.

A cookie banner appears when visiting https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/ for the first time. This element is almost the last in the focus order. Visitors who use the keyboard to navigate, need to go through the whole page to be able to consent. Until than, the cookie banner hides other elements on the site. For users who need to zoom in on the page this is even a bigger problem. Therefore it is important that the cookie banner is the first element in the focus order. Another solution would be to remove this cookie banner, because there is also another cookie banner which does appear first in the focus order.

On page https://www.sunweb.dk/rejser a dialog window can be opened by clicking on the button 'Sponsoreret'. Is this window is opened, the visitor can move the focus to elements that are hidden by the window. Make sure the focus can only leave the dialog window after it is closed.


The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

Information about success criterion 2.4.4 Link Purpose (In Context)

Outcome: Failed

Findings: The image with the Sunweb logo only contains the alternative text "CookieInfo". This should serve as a description of the link purpose, but because the role="presentation" attribute is added to the image element this can not be read by a screenreader. Remove this attribute and change the text of the alt-attribute, so visitors who use a screenreader know which logo can be seen on the image and know what the link purpose is. See also succes criterion 1.1.1.

The Sunweb logo that serves as a link to the homepage, does not have a clear description of the role of the link and of the link purpose. Remove the role="menuitem" so the link can be recognized as link, and change the text of the alt-attribute in the img-element. For example to 'Sunweb logo, go to homepage' (but than in Danish).

In the footer of all pages, for example https://www.sunweb.dk/, there are two links under 'Hent vores app'. These links have no name. Therefore the linkpurpose is not clear for visitors who use assistive software such as a screenreader. See also succes criterion 4.1.2.

On several pages there can be found div-elements which contain a link, an image and a heading-text. For example on the homepage https://www.sunweb.dk/ the heading-text 'Solrige ferier sydpå hele året rundt'. The div contains more than one link (with the same link purpose), and one of these links has no name. This can be confusing for visitors who use assistive software such as a screenreader. Make sure that there is only one link in the div-element, and give this link a clear name. This also prevents the problem that keyboard-users have more than one tab-stops in this div-element. The clickable area of the link can be enlarged using the CSS or Javascript. The same problem occurs on for example page https://www.sunweb.dk/rejser ('Fantastiske messetilbud med store rabatter'). See also succes criterion 4.1.2.

On all pages a link with a heart-icon can be found in the menu. Assistive software like a screenreader recognizes that there is a link here, but the name of the link is read as '0' (if there are no likes yet). For visitors who cannot see, this does not describe the link purpose enough. Add a name which describes the link purpose, and also the number of likes (0 in this case).

On page https://service.sunweb.com/da/support/home, icons that are links that have no name can be found. For example under heading-text 'Skriv till os på WhatsApp eller ring til os!', the link to WhatsApp. Assistive software such as a screenreader can in some cases read out (a part of) the URL, which does not make the link purpose clear. Add a name to solve this problem. See also succes criterion 4.1.2.

On page https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/ in the footer several logo's can be found under heading-text 'Sunweb er tilknyttet'. These are formatted as one image in one link. This link has no name. This can be solved in several ways. The image in the link can be given an alternative text which contains all the information from the logo's, but this would be a long text. A better solution would be to replace the link by several links, one for each logo. Each logo needs an alternative text. On other pages it is done like this. See also succes criterion 1.1.1.


2.4.5 Multiple Ways (Level AA)

More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.

Information about success criterion 2.4.5 Multiple Ways

Outcome: Can't tell

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


2.4.6 Headings and Labels (Level AA)

Headings and labels describe topic or purpose.

Information about success criterion 2.4.6 Headings and Labels

Outcome: Can't tell


2.4.7 Focus Visible (Level AA)

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Information about success criterion 2.4.7 Focus Visible

Outcome: Can't tell


2.5 Input Modalities

2.5.1 Pointer Gestures (Level A)

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

Information about success criterion 2.5.1 Pointer Gestures

Outcome: Can't tell

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


2.5.2 Pointer Cancellation (Level A)

For functionality that can be operated using a single pointer, at least one of the following is true:

Information about success criterion 2.5.2 Pointer Cancellation

Outcome: Can't tell

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


2.5.3 Label in Name (Level A)

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

Information about success criterion 2.5.3 Label in Name

Outcome: Can't tell

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


2.5.4 Motion Actuation (Level A)

Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:

Information about success criterion 2.5.4 Motion Actuation

Outcome: Can't tell

Findings: 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)

The default human language of each Web page can be programmatically determined.

Information about success criterion 3.1.1 Language of Page

Outcome: Can't tell

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


3.1.2 Language of Parts (Level AA)

The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

Information about success criterion 3.1.2 Language of Parts

Outcome: Failed

Findings: The menu on each page contains a nav-element which by assistive software is read as 'Main menu'. The language of the website is Danish, so this English text might be difficult to understand. Also, it cannot be read out with the right pronunciation. Change the text of the aria-label to a Danish text.

On page https://www.sunweb.dk/ there is a h2-heading 'It's a Sunweb holiday! #creatingmemories'. Because the language of the page is set to Danish, this text cannot be read out with the right pronunciation. To solve this, add a lang-attribute (lang="en") to the h2-element.

On page https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/, after scrolling down on the page, a link 'Go to Top' appears. This English text cannot be read out the correct way, which can cause confusion for visitors who cannot see. Solve this by translating the screen-reader text in the link to Danish.

On https://www.sunweb.dk/blog/alperne-eller-skandinavien-paa-din-naeste-skiferie/ a dialog modal can be found, with a 'Last minute-tilbud'. This contains a close-button which has a Dutch text, 'Sluiten'. Translate this to a Danish text. This also occurs on the same place on page https://www.sunweb.dk/rejser.

On page https://www.sunweb.dk/rejser there is a carousel under 'Gæsternes favoritter'. The buttons under the carousel have been named by an aria-label, for example 'Carousel Page 1 (Current Slide)'. Because the language of the page is set to Danish, this text cannot be read with the right pronunciation. For some visitors who do not speak English, it can also be difficult to understand this text. Solve this by translating the text of the aria-labels to Danish.


3.2 Predictable

3.2.1 On Focus (Level A)

When any component receives focus, it does not initiate a change of context.

Information about success criterion 3.2.1 On Focus

Outcome: Can't tell

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


3.2.2 On Input (Level A)

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

Information about success criterion 3.2.2 On Input

Outcome: Can't tell

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


3.2.3 Consistent Navigation (Level AA)

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

Information about success criterion 3.2.3 Consistent Navigation

Outcome: Can't tell

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


3.2.4 Consistent Identification (Level AA)

Components that have the same functionality within a set of Web pages are identified consistently.

Information about success criterion 3.2.4 Consistent Identification

Outcome: Can't tell

Findings: 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)

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

Information about success criterion 3.3.1 Error Identification

Outcome: Can't tell

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


3.3.2 Labels or Instructions (Level A)

Labels or instructions are provided when content requires user input.

Information about success criterion 3.3.2 Labels or Instructions

Outcome: Failed

Findings: On page https://service.sunweb.com/da/support/home there is a search field. This field does not contain a label that stays visible when the visitor starts typing. This can cause confusion for some visitors. Place the placeholdertext (that dissapears when typing) outside of the field so it stays visible, or add a search-icon in a search-button. Give this button a clear name.


3.3.3 Error Suggestion (Level AA)

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

Information about success criterion 3.3.3 Error Suggestion

Outcome: Can't tell

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


For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

  1. Reversible: Submissions are reversible.
  2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

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

Outcome: Can't tell

Findings: 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)

In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

Information about success criterion 4.1.1 Parsing

Outcome: Can't tell

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


4.1.2 Name, Role, Value (Level A)

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Information about success criterion 4.1.2 Name, Role, Value

Outcome: Failed

Findings: On all pages, for example the homepage https://www.sunweb.dk/, there is a 'Mit Sunweb' button. An aria-attribute (aria-expanded="false") is placed on the div-element, which is not allowed en does not function. This aria-attribute is important, but make sure to add it to the right element, in this case the button-element (Mit Sunweb).

On page https://www.sunweb.dk/, after zooming in the menu is found under a menu-button. This button has no name. For visitors who cannot see, it is unclear where the menu can be found. Add a name to the button to solve this. This also applies to the button next to the menu-button, 'Mit Sunweb'.

In the footer of all pages, for example https://www.sunweb.dk/, there are two links under 'Hent vores app'. These links have no name. For this succes criterion it is required that the name of every link can be programmatically determined. Add a name to solve this problem. See also succes criterion 2.4.4.

Under the header on https://www.sunweb.dk/ are three list-items (e.g. 'Prisgaranti', 'Fleksibel ombooking'). Some list items are placed in a div-element on which an aria-hidden="true" and tabindex="-1" attribute is added. For exampel 'Flexibel ombooking'. This can cause problems for visitors who navigate using the keyboard, and/or use assistive software like a screenreader. They may not be able to reach, focus and use the links. Make sure focusable items such as links are not placed in an element that is hidden.

On several pages there can be found div-elements which contain a link, an image and a heading-text. For example on the homepage https://www.sunweb.dk/ the heading-text 'Solrige ferier sydpå hele året rundt'. The div contains more than one link (with the same link purpose), and one of these links has no name. Therefore the name of this link can not be programmatically determined. Make sure that there is only one link in the div-element, and give this link a clear name. This also prevents the problem that keyboard-users have more than one tab-stops in this div-element. The clickable area of the link can be enlarged using the CSS or Javascript. The same problem occurs on for example page https://www.sunweb.dk/rejser ('Fantastiske messetilbud med store rabatter'). See also succes criterion 2.4.4.

On page https://service.sunweb.com/da/support/home, icons that are links that have no name can be found. For example under heading-text 'Skriv till os på WhatsApp eller ring til os!', the link to WhatsApp. Assistive software such as a screenreader can in some cases read out (a part of) the URL, which does not make the link purpose clear. Add a name to solve this problem. See also succes criterion 2.4.4.

On page https://service.sunweb.com/da/support/home there are several 'Vis flere' links. These can be unfolded to see more options. These links are not formatted correctly, which causes several problems. The links are not focusable, and therefore difficult to reach for visitors who use the keyboard to navigate. An aria-expanded attribute is added to the links, but this attribute is not allowed on a link. Solve this for example by formatting this element as a button and add the aria-expanded attribute to this button.

On several pages, for example the homepage https://www.sunweb.dk/, the searchfield '2 personer i 1 værelser' can be expanded. Several buttons ('-' and '+') are visible. These buttons do not have a name. For visitors who cannot see, it is not clear what these buttons can be used for. Add a name to solve this problem.

On page https://www.sunweb.dk/rejser there is a search-button. This button is not formatted correctly, and it has no name. To solve this, remove the role="menuitem" from the button-element and add a name to make the purpose of the button clear.


4.1.3 Status Messages (Level AA)

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Information about success criterion 4.1.3 Status Messages

Outcome: Can't tell

Findings: 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

Relied upon techniques

Web browsers (User Agents) and other software

The following software was used in this evaluation:

Resources:

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

Source: toegankelijkheidsrapport.swink.nl/sunweb.dk/audit/
Printed: 2025-03-09 15:51:04 v2.4-011