search icon

Accessibility statement for


Version 1.0 - Updated May 10, 2023

This accessibility statement applies to the website.

We want as many people as possible to be able to use That means you should be able to:

  • Use the web product on small screen devices without the need to scroll the page horizontally.
  • You can zoom in by 200% and even change the size or spacing of the text — all without any of the text running off the screen.
  • Use only your keyboard to navigate.
  • Listen to and interact with the website using a screen reader, such as Apple’s VoiceOver.

AbilityNet also has advice on making your device easier to use if you have accessibility needs.

Important note: is currently updating the website. We’re bringing in improved accessibility support as we go, aiming to ensure that all features benefit from this technology yet.

Technical information about accessibility uses the Web Content Accessibility Guidelines (WCAG) version 2.1 AA as its minimum standard for accessibility compliance.

Non-text Content

We would like all relevant images, graphics, and objects on a page to have a text alternative. However, sometimes text alternatives aren’t available and easily understandable or match what is presented visually. We’re working to fix this by replacing older code and resolving identified bugs.

Time-based media

We would like to provide captions for time-based media. We would also like to provide audio description tracks or a text alternative (transcript) to allow users who are visually impaired or blind to fully understand the content of the video.


We would like to ensure elements marked as tabs are marked correctly to avoid confusion for screen reader users.

Custom elements

We would like to ensure where custom controls have been used on the website that these controls are accessible for all users.


We would like PDFs to be accessible. This includes correcting the reading order of the PDF document, ensuring the PDF is correctly tagged so that it is available to screen reader users, and that all PDFs have a title that describes the topic.


We would like to update the website where content is visually grouped together as lists so that the corresponding relationships are programmatically available to screen reader users.


We would like to ensure that the tables used on the website are structured correctly.

Breadcrumb trail

We need to enable the progress indicator that uses CSS to convey information to be announced by screen reading software.

Keyboard focus

When using the tab button to move around, we would like the sequence of movement to be logical. However, our testing has revealed some instances in which the order isn’t as we’d expect. We’re working to repair this.

When there are interactive components on the screen, we need to ensure that there is a visible focus state indicator.


We would like everything that’s interactive to be accessible using the keyboard alone. However, there are elements which cannot be accessed using a keyboard only. Our site navigation, tables, and some buttons are not keyboard accessible yet. To fix this, we are working on new navigation, tables, and buttons to remove any keyboard traps.

Hidden checkboxes

There are checkboxes which have been customized and hidden incorrectly.

Form controls – labels and groups

We need to ensure all form controls have a programmatically associated label and, where inputs are part of a group, that they have a shared or common label.


We would like to adjust the timing on the timeout of the shopping cart to enable all users an opportunity to extend the time period. We would also like to adjust the timing of content that disappears before some users may have had time to read it.

Bypass blocks

We would like to provide features to allow users to bypass repeated blocks of content, for example, navigation that appears on every page, as this may help some users. These features are not present in the product today, but we will add them.

Page titles

We would like to ensure all page titles are descriptive.


We need to ensure all our modals are accessible and do not trap users’ focus.


We need to ensure all our links are labeled correctly, have accessible names, and have appropriate markup.

Navigation semantics

We are updating our navigation structures, including mega-menus, to ensure the structures are labeled correctly.

Buttons – accessible name

We are ensuring all buttons which use an icon or image have suitable alternative text which will act as the accessible name for the component.

Confusing labels on carousel

We need to ensure our carousel content is labeled descriptively.


We would like the visual presentation of everything interactive to have good contrast against background colors to support people with visual impairments. However, in some places this isn’t the case. To repair this, we’re working on improved visual styles.

We would like the visual presentation of text to have good contrast against background colors to support people with visual impairments. However, in some places this isn’t the case. To repair this, we’re working on improved visual styles and phasing out the use of placeholder text.

Content on hover or focus

We need to ensure our content is easily dismissible when presented on mouse hover.

Non-descriptive headings and labels

We want to ensure all of our headings describe the topic or purpose. We need to ensure the purpose of our buttons is concise and unambiguous, to be understood when screen readers are navigating out of context.

Status message (including errors)

If a status message appears, we would like it to be clear to all users. Right now, messages aren’t coded in a way that users of some assistive technologies would notice. To repair this, we’re developing how our messages are coded.


How we tested this product

This audit was conducted on August 8, 2022. Testing was conducted using a variety of methods and technologies.


Browsers and Assistive Technology (AT) combinations for desktop using Windows version 11:

  • JAWS 2019 using Chrome and Edge browser (Version 104).
  • NVDA 2022.2 using Chrome browser (Version 104).
  • Dragon Voice Activation v15 using Chrome browser (Version 104).
  • Keyboard using Chrome browser (Version 104).
  • Screen Magnification (Reflow, Text Spacing) using Chrome browser (Version 104).
  • Windows Magnifier using Chrome browser (Version 104).
  • ZoomText using Edge browser (Version 104).
  • System inverted colors using Edge browser (Version 104).


Browsers and Assistive Technology (AT) combinations for mobile and tablet:

  • VoiceOver on iOS using Safari browser (Version 14.1.2).
  • Talk Back / Voice Assistant on Android using Chrome browser (Version 104).
  • Magnification on Android using Chrome browser (Version 104).
  • Pinch to Zoom on iOS using Safari browser (Version 14.1.2).
  • System inverted colors for iOS and Android using Safari browser (Version 14.1.2).

Feedback and contact information

If you need support, find problems not listed on this page, or if you believe we are not meeting accessibility requirements, please contact us at


We will read all requests and get back to you as soon as possible. For any general Sage Accounting technical inquiries please call +44 191 479 5911.

Give Feedback