Version 1.1 – Updated 5 November 2020
This accessibility statement applies to Sage Business Cloud X3, Enterprise Management ERP (Enterprise Resource Planning) software for medium to large business owners – find out more on the Sage Business Cloud X3 website.
We want as many people as possible to be able to use Sage X3. For example, that means you should be able to:
AbilityNet also has advice on making your device easier to use if you have a disability.
We know some parts of this product are not fully accessible.
There are several other improvements we could make to our code to help the product work as well as it can for everyone.
If you need support, find any problems not listed on this page, or if you think we’re not meeting accessibility requirements, please contact us:
We will consider any requests and get back to you as soon as possible.
Sage Business Cloud Accounting is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons.
We would like all objects on a page that have meaning to have a text alternative. However, sometimes text alternatives are not available, they are not easy to understand, or they do not match what is presented visually. We are working to fix this by replacing older code and resolving identified bugs.
We would like to ensure that information and relationships implied by visual formatting are clear to people using assistive technologies. However, headings are not marked up correctly in the code. We will review our code to make improvements.
Where the sequence of content on a page is important, we will ensure that the sequence is preserved for users of assistive technologies like screen readers. If CSS is disabled, some content may be read by assistive technologies in the wrong sequence. We will fix these instances.
We use ARIA landmarks to identify page regions but some may be missing. We will work to ensure the consistent use of ARIA landmarks going forward.
We would like the visual presentation of the text to have good contrast against background colours to assist people with visual impairments. However, in some places, this is not the case. To fix this, we are working on improved visual styles and phasing out the use of placeholder text.
We would like everything that is interactive to be accessible using the keyboard alone. However, sometimes pages may be difficult to navigate with the keyboard. We plan to allow users to set their own keyboard shortcuts to help with this.
We would like to avoid situations where you might get stuck if using the product with the keyboard alone. Right now, users can exit from a table using the escape key, but there’s no way for them to know this up front. Going forward, we will rebuild our tables to fix this.
We would like to provide features in the code 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 aren't present in the product today, but we’ll add them.
We provide concise and meaningful descriptive headings but some are missing or unclear. In some cases, there is only one label for several fields, or read-only fields are used as labels. We will resolve these cases when we update or replace pages.
We would like to set the language of each page in the code so that the content is always presented correctly. This code is not present in the product today, but we plan to add it.
Users may encounter situations where interacting with items causes unexpected behaviour. We are working on resolving these situations.
If possible, we would like people to receive appropriate suggestions for the correction of an error. However, some error messages are worded broadly, and many don’t include specific suggestions for correction. We will review our error message content.
We would like each field on the page to be associated with a label in the code however, in some situations, this is not the case (for example, checkboxes indicating table row selection, or fields in tables). To fix this, we are working on updating how cases like this are coded.
We would also like all icons to have text descriptions in the code so that it is clear to all users what they do. We found some that do not have descriptions, and we have logged them for fixing.
It is possible to use the web product on tablets with landscape (horizontal) orientation and on larger screens than this, without the need to scroll the page horizontally. (Separate mobile apps are available which will be covered by their own accessibility statements).
However, if you use the product on tablets with portrait (vertical) orientation or on smaller screens such as smartphones, you will need to scroll horizontally to see all the content.
All pages of the product would need to be fixed, including many pages with large tables of data. This would be costly as it is often difficult to offer responsive variants of large tables without losing meaning, and some WCAG guidance suggests that a ‘two-dimensional layout for usage or meaning’ may be acceptable.
We believe that offering support for smaller screens would be a disproportionate burden within the meaning of the accessibility regulations. We will make regular further assessments.
Sage X3 is a complex product containing more than 3 000 features that have one or several pages each.
We believe that resolving all the issues above across all legacy X3 pages due to be replaced would be a disproportionate burden within the meaning of the accessibility regulations. We will make regular further assessments.
Nevertheless, Sage X3 is currently refreshing the technology it relies on, and we will deliver the best value improvements that we can, given their benefit to users.