Report:
Audit digital accessibility website Recharge.com
- Evaluator
- Sophie, Swink; Mirjam, Swink
- Date
- 23 July 2025
- Commissioner
- Recharge.com
Summary of the evaluation findings
The website Recharge.com does not comply to WCAG 2.1 level AA yet. 14 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 https://prd.recharge.services website was audited between 20 and 26th of June 2025. The audit was conducted using the WCAG-EM evaluation method. The aim of this report is to determine what improvements are needed to make this digital channel more accessible.
Some findings that were of note are:
- icons that should be marked as decorative
- alt-text that is not correct in some instances
- interactive elements that are not operable by keyboard, which causes impact on users with speech recognition software or screen readers
- colour combinations that have impact on low vision and/or colourblind users.
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 | Recharge.com |
---|---|
Scope of the website |
Within the scope of the audit are: - All pages on https://prd.recharge.services Outside the scope of the audit are:
|
Conformance target | WCAG 2.1 level AA |
Accessibility support baseline | Common browsers and assistive software. |
Overview of audit results
Principle | Passed | Failed | Can't tell |
---|---|---|---|
1 Perceivable | 13 | 7 | 0 |
2 Operable | 14 | 3 | 0 |
3 Understandable | 6 | 3 | 1 |
4 Robust | 2 | 1 | 0 |
Total | 35 | 14 | 1 |
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.
- Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)
- Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
- Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
- Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
- CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
- Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
Information about success criterion 1.1.1 Non-text Content
Outcome: Failed
Findings: On https://prd.recharge.services/en/us, there is a chevron used in the navigation bar in the header (with the categories button) and in the black buttons on the page. The chevron is an SVG-element that is not marked as decorative, and have an alternative text that is confusing for visitors with assistive technology. Remove the title-element in the SVG's, and use the attributes aria-hidden=true and focusable=false to mark them as decorative. This also occurs at https://prd.recharge.services/en/nl/paysafecard and https://prd.recharge.services/en/nl/lebara for example, with the FAQ-section.
On the top of every page at https://prd.recharge.services/en/us there are icons present with the sentences Certified reseller, Safe & secure payment and Instant digital delivery. An alt-text is provided. But in this case the icons are decorative and alt-text is not needed. Remove the alt-text, but make sure an empty alt-attribute is present in the code.
The logo of Recharge on every page of https://prd.recharge.services/en/us has insufficient alt-text. The alt-text should make clear it is a logo, and should also make it clear it will take you back to the homepage. Edit the alt-text to clarify this. This also counts for the logo in the footer on every page, but there it will be sufficient to just declare it is a logo, e.g. "Logo Recharge".
The images of the available products at https://prd.recharge.services/en/us are logo's of the brand, but the alt-text doesn't specify this. Edit the alt-text to clarify this, for example, "Logo LycaMobile" or "Logo Google Play". This also occurs on product pages as https://prd.recharge.services/en/nl/paysafecard for example and on https://prd.recharge.services/en/us/mobile-top-up.
On https://prd.recharge.services/en/nl/paysafecard underneath the product image, there are icons included with the text "Instant digital delivery" and "Safe & secure payment". And underneath the "Buy now" button, there is an icon next to the phrase "Certified reseller of PaysafeCard". An alt-text is provided. But in this case the icons are decorative and alt-text is not needed. Remove the alt-text, but make sure an empty alt-attribute is present in the code. This also occurs on https://prd.recharge.services/en/nl/lebara, https://prd.recharge.services/en/us/lycamobile and other product pages.
On https://prd.recharge.services/en/thank-you when the order has been delayed, the image of an envelope with a clock has the alt-text of "wait a minute icon". Since the image is decorative, this image can have an empty alt-attribute.
On https://prd.recharge.services/en/checkout, the images in the options for the payment methods when you are ready to pay have alt-text. They are decorative, so the images can have an empty alt-attribute here.
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:
- Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
- Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
Information about success criterion 1.2.1 Audio-only and Video-only (Prerecorded)
Outcome: Inapplicable
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: Inapplicable
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: Inapplicable
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: Inapplicable
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: Inapplicable
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: On https://prd.recharge.services/en/nl/paysafecard there is the phrase "By using this service, you consent to the terms and conditions of PaysafeCard." in the product description. The part "terms and conditions" is visually a link. But in the code, a button is used instead of a hyperlink. This is semantically not correct and can create confusion for speech recognition users or visitors with a screen reader. Change the button into a hyperlink. This also occurs on similar product pages.
On https://prd.recharge.services/en/nl/lebara in the block "How to recharge your Lebara phone?" the strong-element is used to mark up text as bold. This is not allowed, since the strong-element is only to be used to emphasize one or few words in a sentence. Use CSS to style sentences bold. But in this case, it looks an acts like a heading, so using a heading-element is the best way to solve this. In the block "How to check your Lebara balance?", CSS needs to be used for bold-styling. This also occurs on https://prd.recharge.services/en/nl/vodafone.
On https://prd.recharge.services/en/us/lycamobile there are lists not marked up as lists in the FAQ blocks "How do I recharge Lycamobile online?", "How do I check my Lycamobile balance?", "How do I recharge Lycamobile from abroad?" and "How do I contact Lycamobile?". Use the appropriate list element to mark up these lists. This also occurs on https://prd.recharge.services/en/us/at-t-prepaid, https://prd.recharge.services/en/nl/vodafone, https://prd.recharge.services/en/be/orange, https://prd.recharge.services/en/nl/kpn and https://prd.recharge.services/nl/nl/kpn.
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: Passed
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: Passed
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: Passed
1.3.5 Identify Input Purpose (Level AA)
The purpose of each input field collecting information about the user can be programmatically determined when:
- The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
- The content is implemented using technologies with support for identifying the expected meaning for form input data.
Information about success criterion 1.3.5 Identify Input Purpose
Outcome: Passed
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 this moment, the links in the cookie notice on https://prd.recharge.services/en/us are only discernible by colour. While WCAG allows links to be not underlined when the contrast between link, regular text and background colour is according to the minimal expected contrast ratio, we strongly advise underlining links. This makes them more discernible for visitors with low vision. This also counts for the blue links on product pages like https://prd.recharge.services/en/us/at-t-prepaid and https://prd.recharge.services/en/nl/paysafecard (in the FAQ-section).
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: Inapplicable
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:
- Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
- Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
- Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
Information about success criterion 1.4.3 Contrast (Minimum)
Outcome: Failed
Findings: The cookie notice on every page of https://prd.recharge.services/en/us contains an "I agree" button that is green (HEX #00B258) with white text. The contrast ratio of this colour combination is 2,8:1, while a minimum of 4,5:1 is expected. Use a darker green colour.
On https://prd.recharge.services/en/us, in the block Over 63,510 5-star reviews, the timestamp of the reviews (HEX #758C8D) don't have enough contrast with the background (HEX #F3F6F6). The contrast is 3,3:1, where it should be 4,5:1 at minimum. This block can also be found at product pages as https://prd.recharge.services/en/nl/paysafecard for example.
In the footer on every page of https://prd.recharge.services/en/us, the text "© 2025 Recharge.com International B.V. All rights reserved" and the links "Privacy Statement", "Cookie Statement" and "How it works" don't have enough contrast (text is HEX #738A8C) with the white background. The contrast ratio is 3,6:1, where a minimum of 4,5:1 is expected.
On https://prd.recharge.services/en/nl/paysafecard where a couple of payment methods are listed, there is the phrase "+ many more", in light grey (HEX #9CA3AF). The contrast ratio with the white background is 2,5:1 where it should be 4,5:1 at least. Use a darker grey. This also occurs on other product pages (for example https://prd.recharge.services/en/nl/lebara).
On https://prd.recharge.services/en/nl/paysafecard the grey (HEX #738A8C) phrase "By using this service, you consent to the terms and conditions of PaysafeCard." in the product description, does not have enough contrast with the white background. The contrast ratio is 3,6:1 where it should be 4,5:1 minimally. Use a darker grey or black. This also occurs on other product pages (for example https://prd.recharge.services/en/nl/lebara).
On https://prd.recharge.services/en/nl/lebara, when you make a choice of product (bundle, call credit, international), you can pick a specific one. For example "Lebara Online 500 MB". With all the options (in all categories), there is extra text present (for example "valid for 30 days" and "500MB 4G data"). This text (HEX #728A8B) doesn't contrast well with the background (HEX #F3F6F6). The contrast ratio is 3,4:1, where 4,5.1 is expected. Use a darker colour for the text. This occurs on similar product pages like https://prd.recharge.services/en/us/lycamobile as well.
On https://prd.recharge.services/en/checkout the placeholder in the e-mail field and the text "© 2025 Recharge.com International B.V." (both HEX #738A8C) don't have enough contrast with the white background. The contrast ratio is 3,6:1 where it should be 4,5:1 minimally. Use a darker grey or black.
On https://prd.recharge.services/en/checkout when selecting a payment method, the text "no extra fee" or the amount of extra fee (HEX #738A8C) doesn't have enough contrast. The contrast ratio is 3,6:1 where it should be 4,5:1 minimally. Use a darker grey or black.
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: When zooming in to 200%, there is a loss of functionality on pages that have the header bar: where you can view the category list and where you can change language, country and currency. Those interactive elements don't work anymore when zoomed in. Make sure all functionality works and can be activated when zoomed in.
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:
- Customizable: The image of text can be visually customized to the user's requirements;
- Essential: A particular presentation of text is essential to the information being conveyed.
Information about success criterion 1.4.5 Images of Text
Outcome: Passed
1.4.10 Reflow (Level AA)
Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:
- Vertical scrolling content at a width equivalent to 320 CSS pixels;
- Horizontal scrolling content at a height equivalent to 256 CSS pixels;
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: When zooming in to 400% and adjusting the browser window to a width of 1280 pixels, there is a loss of functionality on pages that have the header bar: where you can view the category list and where you can change language, country and currency. Those interactive elements don't work anymore when zoomed in. Make sure all functionality works and can be activated when zoomed in.
When zooming in to 400% and adjusting the browser window to a width of 1280 pixels, there is a horizontal scroll bar present on all pages. Make sure content adapts to the size of the browser window and size of the text.
When zooming in to 400% and adjusting the browser window to a width of 1280 pixels, on https://prd.recharge.services/en/nl/kpn, the text on the buy buttons is cut off. Make sure text is not cut off when the text size and browser window size are adjusted. This also occurs on other product pages.
When zooming in to 400% and adjusting the browser window to a width of 1280 pixels, the text of the payment methods in https://prd.recharge.services/nl/checkout becomes unreadable. Make sure text does not overlap when the text size and browser window size are adjusted.
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):
- User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
- Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
Information about success criterion 1.4.11 Non-text Contrast
Outcome: Failed
Findings: In the header on https://prd.recharge.services/en/us (and on every other page) there is a bar present with the logo, categories list, language picker and currency picker. The country list, language and currency picker get a light blue (HEX #B3D3F7) focus outline, when they receive focus. The contrast ratio against the white background of the bar is 1,5:1, where is a minimum of 3:1 is required. Choose a darker blue colour to solve this. The same outline is used for the black buttons on the homepage. For those buttons, pick an outline that contrasts both with the white background and the black colour of the button.
On https://prd.recharge.services/en/nl/paysafecard the button "Buy now" and the link "Terms and conditions" get a light blue (HEX #B3D3F7) focus outline, when they receive focus. The contrast ratio against the white background of the bar is 1,5:1, where is a minimum of 3:1 is required. Select a darker blue colour to solve this. Pick an outline that contrasts both with the white background and the black colour of the button. This also occurs on other product pages (for example https://prd.recharge.services/en/nl/lebara).
In the header on https://prd.recharge.services/en/us (and on every other page) there is a bar present with the logo, categories list, language picker and currency picker. The categories select list gets a green (HEX #05E27E) focus outline, when it receives focus. The contrast ratio against the white background of the bar is 1,7:1, where is a minimum of 3:1 is required. Decide on a darker green colour to solve this.
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:
- Line height (line spacing) to at least 1.5 times the font size;
- Spacing following paragraphs to at least 2 times the font size;
- Letter spacing (tracking) to at least 0.12 times the font size;
- Word spacing to at least 0.16 times the font size.
Information about success criterion 1.4.12 Text Spacing
Outcome: Passed
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:
- Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
- Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
- Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Information about success criterion 1.4.13 Content on Hover or Focus
Outcome: Passed
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: On https://prd.recharge.services/en/nl/paysafecard you can select a value for which you want to top up. The first option receives focus and can be selected. The other options are not reachable and operable by keyboard. This is because the tabindex attribute with a negative value is used. A solution is to turn the options in radio buttons. Keep in mind that the radio buttons need to be labelled and grouped with fieldset and legend. Also: don't use hidden or display:none in CSS when styling the radio buttons and labels.
On https://prd.recharge.services/en/nl/lebara)/ you can select what you want to buy: call credit, bundle. data or international. The first option receives focus and can be selected. The other options are not reachable and operable by keyboard. This is because the tabindex attribute with a negative value is used. A solution is to turn the options in radio buttons. Keep in mind that the radio buttons need to be labelled and grouped with fieldset and legend. Also: don't use hidden or display:none in CSS when styling the radio buttons and labels. The same problem occurs at https://prd.recharge.services/en/us/lycamobile and other pages this component is used.
When changing the region in the header bar on every page, or when changing the redeemable country on product pages as https://prd.recharge.services/en/nl/paysafecard, a modal opens. You can't navigate to the options, not even when you performed a search. This is because of removing the radio buttons at each country option with display:none in the CSS. This is not allowed. Remove the CSS property. If you want to keep on using the current style, you will need to move the real radio buttons visually off-screen (instead of removing or hiding). Check that visually the faux radio buttons get a focus outline and that with picking an option (or navigating between the options), the real ones off-screen will be activated.
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: Passed
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:
- Turn off: A mechanism is available to turn the shortcut off;
- Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
- Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.
Information about success criterion 2.1.4 Character Key Shortcuts
Outcome: Inapplicable
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:
- Turn off: The user is allowed to turn off the time limit before encountering it; or
- Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
- Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
- Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
- Essential Exception: The time limit is essential and extending it would invalidate the activity; or
- 20 Hour Exception: The time limit is longer than 20 hours.
Information about success criterion 2.2.1 Timing Adjustable
Outcome: Inapplicable
2.2.2 Pause, Stop, Hide (Level A)
For moving, blinking, scrolling, or auto-updating information, all of the following are true:
- Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Information about success criterion 2.2.2 Pause, Stop, Hide
Outcome: Passed
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: Passed
2.4 Navigable
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: On the site there are no skip links available. Skip links are especially helpful for people using a screen reader, since they can directly jump to the main content of the page. Add a skip link to solve this, and make sure the skip link is the first item that receives focus on the page (when the cookie notice is no longer present). If the skip link is used, it should take the user to the main content, and when the user continues tabbing through the page, focus should continue from the main content.
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: Passed
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: On https://prd.recharge.services/en/us, there is a cookie notice present when you first visit the site. When navigating by keyboard, this cookie notice is the last to receive focus. This should be the first item on the page that receives focus.
In the header on https://prd.recharge.services/en/us (and on every other page) there is a bar present with the logo, categories list, language picker and currency picker. The "Help" link receives visible focus twice, because there is a button nested in a hyperlink. This can be confusing for visitors using assistive technology. Use only the hyperlink and remove the button.
2.4.4 Link Purpose (In Context) (Level A)
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: Passed
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: Passed
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: Passed
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: Passed
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: Inapplicable
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:
- No Down-Event: The down-event of the pointer is not used to execute any part of the function;
- Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
- Up Reversal: The up-event reverses any outcome of the preceding down-event;
- Essential: Completing the function on the down-event is essential.
Information about success criterion 2.5.2 Pointer Cancellation
Outcome: Inapplicable
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: Passed
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:
- Supported Interface: The motion is used to operate functionality through an accessibility supported interface;
- Essential: The motion is essential for the function and doing so would invalidate the activity.
Information about success criterion 2.5.4 Motion Actuation
Outcome: Inapplicable
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: Failed
Findings: The page https://prd.recharge.services/en/us/woops does not have a lang-attribute in the HTML-element. Setting the language of the page is important for screen readers, so they will use the right voice (accent, cadence, etc.). Add this attribute to the HTML-element and set the correct language as the value.
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: Passed
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: Passed
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: Passed
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: Passed
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: Passed
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: Not tested
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 https://prd.recharge.services/en/checkout, when you just selected a product from the product page, you get presented with a field to enter your e-mail address. You can also provide a discount code. These fields are not labelled, it only provides a placeholder (which is not enough to pass this criterion). Ensure they have a label.
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: Failed
Findings: On https://prd.recharge.services/en/checkout, when you just selected a product from the product page, you get presented with a field to enter your e-mail address. When you provide an invalid e-mail address (with a comma instead of a period), there is no error suggestion along with the error message. Provide a suggestion on how to solve this issue.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
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:
- Reversible: Submissions are reversible.
- Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
- 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: Passed
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: Passed
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: In the header on https://prd.recharge.services/en/us (and on every other page) there is a bar present with the logo, categories list, language picker and currency picker. The "Help" link is a button nested in a hyperlink, with the hyperlink being hidden with aria-hidden. Nesting focusable elements in elements that are hidden for assistive technology is not allowed. Remove the aria-hidden attribute.
On https://prd.recharge.services/en/nl/lebara, the selection lists you get when selecting the amount of a product don't have a label. In the code, they are comboboxes. But since there is no field to type or search, they are not really comboboxes. Use a native select-element instead, and make sure it has a label. This also occurs on similar product pages.
On https://prd.recharge.services/en/checkout the URL stays the same during the process. Changed or updated content is not announced by assistive technology. This can be solved by using different URL's for every step in the check-out process and/or using live regions.
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: Passed
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
- https://prd.recharge.services/en/us
- https://prd.recharge.services/en/us/woops
- https://prd.recharge.services/en/nl/paysafecard
- https://prd.recharge.services/en/nl/lebara
- https://prd.recharge.services/en/us/lycamobile
- https://prd.recharge.services/en/us/at-t-prepaid
- https://prd.recharge.services/en/checkout
- https://prd.recharge.services/en/thank-you
- https://prd.recharge.services/en/us/mobile-top-up
- https://prd.recharge.services/en/nl/vodafone
- https://prd.recharge.services/en/be/orange
- https://prd.recharge.services/en/nl/kpn
- https://prd.recharge.services/nl/nl/kpn
Relied upon techniques
Web browsers (User Agents) and other software
The following software was used in this evaluation:- Chrome, version 137
- Safari, version 18.3.1
- VoiceOver
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.