Login
![]()
Log in to Sage
Partners
Sage Partner Portal
Need help?
Version 1.0 – Updated 10 May 2023
This accessibility statement applies to the Sage.com website.
We want as many people as possible to be able to use Sage.com. That means you should be able to:
AbilityNet also has advice on making your device easier to use if you have a disability.
Important note: Sage.com is currently updating the website. We’re bringing in improved accessibility as we go, but not all features have benefitted from this technology yet.Sage.com uses the Web Content Accessibility Guidelines (WCAG) version 2.1 AA as its minimum standard for accessibility compliance.
We would like all images, graphics and objects that have meaning on a page to have a text alternative. However, text alternatives sometimes aren’t available, aren’t easy to understand or don’t match what is presented visually. We’re working to fix this by replacing older code and resolving identified bugs.
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 video content.
We would like to ensure elements marked as tabs are marked up correctly to avoid confusion for screen reader users.
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, correcting the reading order of the PDF document, and ensuring the PDF is correctly tagged so it is available to screen reader users, and ensure 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 where tables are used on the website, they are structured correctly.
We need to enable the progress indicator, which uses CSS to convey information, to be announced by screen reading software.
When using the tab button to move around, we would like the sequence of movement to be logical. However, our testing revealed some situations in which the order isn’t as we’d expect. We’re working to fix this.
When there are interactive components on the screen, we need to ensure 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 yet keyboard accessible. To fix this, we are working on new navigation, tables and buttons to remove any keyboard traps.
There are checkboxes which have been customised and hidden incorrectly.
We need to ensure that all form controls have a programmatically associated label and, where inputs are part of a group, they have a shared or common label.
We would like to adjust the timeout on the shopping cart to enable all users to extend the period of time. We would also like to adjust the timing of content which disappears before some users may have had time to read it.
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’ll add them.
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 labelled correctly, have accessible names and appropriate markup.
We are updating our navigation structures, including mega-menus, to ensure structures are labelled correctly.
We are ensuring all buttons which use an icon or image have suitable alternative text to act as the accessible name for the component.
We need to ensure our carousel content is labelled descriptively.
We would like the visual presentation of everything that’s interactive to have good contrast against background colours to support people with visual impairments. However, this isn’t the case in some places. To fix this, we’re working on improved visual styles.
We would like the visual presentation of text to have good contrast against background colours to support people with visual impairments. However, this isn’t the case in some places. To fix this, we’re working on improved visual styles and phasing out the use of placeholder text.
We need to ensure our content is easily dismissible when presented on mouse hover.
We want to ensure all of our headings describe the topic or purpose. We need to ensure the purpose of our buttons are concise and unambiguous, to be understood when screen readers are navigating out of context.
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 fix this, we’re changing how our messages are coded.
This audit was conducted on 8 August 2022. Testing was conducted using a variety of methods and technologies.
Browsers and Assistive Technology (AT) combinations for desktop, using Windows version 11:
Browsers and Assistive Technology (AT) combinations for mobile and tablet:
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 accessibility@sage.com.
We’ll consider all requests and get back to you as soon as possible. For any general Sage Accounting technical enquiries, please call +44 191 479 5911.
Give Feedback