We are committed to providing a website that is accessible to the widest possible audience.
We routinely check web pages – when amendments are made to existing pages and when new pages are added - to ensure that they meet accessibility requirements, and we respond positively to feedback regarding the accessibility of any of our pages and services.

Web Content Accessibility Guidelines

This site has been developed with the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines (WCAG) 2.1 in mind.
These guidelines are the internationally recognised benchmark for building accessible websites, which explain how to make them more accessible for people with disabilities.
Conformity to these guidelines also makes websites more user-friendly for all users, regardless of ability.
This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.1 AA standard, due to the non-compliances listed below.

Non Compliance With the Accessibility Regulations

We know some parts of this website aren’t fully accessible yet:

  • Charts. This page cannot be accessed on mobile devices (i.e. those with a screen width less than 768px), as it would be unusable.
  • Links styled as buttons. Various links are styled to look like buttons. Users of voice recognition software should be aware of this when looking to identify and mark links and buttons on a page.
  • Documentation. Our included documentation contains a number of screenshots and videos, which were recorded using a standard desktop device and browser. These therefore may not appear the same to users who use assistive technologies in their browser, or might normally change their browser settings to increase font size, for example.
  • Payment Gateways' Hosted Payment Pages. Some of the customer journey may take place on a Hosted Payment Page provided by the vendor's Payment Gateway, to which we redirect the customer to enter card details. As this is hosted by a Payment Gateway, it is outside of our control and may not conform to accessibility requirements.
  • Card Issuer's 3D Secure Pages. Where a transaction requires challenge authentication, an authentication page will be displayed. As this is hosted by the Card Issuer, it is outside of our control and may not conform to accessibility requirements.

Disproportionate Burden

  • Charts. These are generated by a third-party plugin, bundled within a framework which we use. To use a different plugin, or to change the framework, would create a disproportionate burden. We will keep the version of the framework up to date, so that future enhancements to the plugin are made available.

Reporting Accessibility Problems

If you find any problems that are not listed on this page or think we are not meeting accessibility requirements, contact us at support@svlsecurepay.com.


Technical Information About This Website’s Accessibility


WAI-ARIA Landmarks

The WAI ARIA specification defines a set of specialised "landmark" roles, which provide a method to programmatically identify commonly found sections of webpage content in a consistent way.
We use these landmarks within this site, which allows assistive technologies to provide users with features which they can use to identify and navigate to sections of page content more easily.

Colour Contrast

We have checked text and background colour combinations to ensure that the contrast is sufficient and we have also ensured that information is not referenced by colour alone.

Text Size

You can vary the text size by using your browser’s text resize option: in many web browsers this can be accessed by selecting “View” -> “Text Size” or on desktop devices by pressing 'Ctrl' and '+' to zoom in or 'Ctrl' and '-' to zoom out.

Browsers

This site has been built using code compliant with W3C standards for HTML and CSS.
It should display correctly in the current and at least the previous major version of the following browsers: Firefox, Chrome, Edge, Safari, and Opera.
Note that Internet Explorer is not supported, as the last major version (11) was released in 2013 and falls short of current web standards. Edge, which was released in 2015, effectively superseded Internet Explorer.

Screen Sizes

This website can dynamically adapt to the screens of the modern mobile devices such as iPhone, iPad, or Android phones (in portrait or landscape rotation), in addition to desktop-size screens.
The minimum recommended display width is 414px, which is the display resolution of the iPhone 6 Plus.

HTTPS/SSL

This site uses HTTPS (also commonly known as SSL), which securely encrypts any communication between your browser and this site.
HTTPS uses a combination of a protocol and a cipher suite to establish and secure each connection.
At the time of writing, the most secure and widely-used protocol is TLS 1.2, which must be enabled in the browser to establish communication with this site.
Older protocols such as TLS 1.1, TLS 1.0, SSL 3 and SSL 2 are no longer supported.
TLS 1.3 will also be supported in the near future.
This site is required to conform to current PCI-DSS requirements, which state that as of June 30th 2018, all websites will need to be on TLS 1.1 or higher in order to be compliant.
This site is regularly evaluated against industry standards (which may exceed PCI-DSS), to ensure that only protocols and cipher suites which are considered secure are enabled.
Therefore any older Operating Systems and browsers which do not support these current standards will not be able to access this site.
Examples include Android prior to version 5, Internet Explorer prior to version 10 and Safari prior to version 7.

Future Improvements

We undertook a significant redesign of this site in 2019, with accessibility considerations as one of the primary drivers. We will continue to review this site for additional improvements, as part of our continuous development cycle.

This statement was prepared on 26/06/2019. It was last updated on 11/11/2020.