Accessibility statement for Sage CRM

Updated: 26 October 2021


Sage CRM is a browser-based customer relationship management application that can be deployed on-premise or within the cloud. Sage CRM helps customers simplify the sales process, shorten sales cycles, and make the most of every sales opportunity. It is for medium-sized customers and is designed to integrate with Sage accounting products—find out more at

We want as many people as possible to be able to use Sage CRM. For example, that means you should be able to:

  • Use the web product on large screens without the need to scroll the page horizontally.
  • Use the web product on tablets with landscape (horizontal) orientation.
  • Navigate using consistent menus.
  • Simplify the menus, screens and captions based on individual user needs.
  • Zoom in to 150%, or change the size and spacing of text, without the text spilling off the screen.
  • Use the search feature to quickly access content.
  • Change any caption in the product. We have made the text in the product as simple as possible to understand.
  • Override the default theme with a high contrast visual theme for people with visual impairments.

AbilityNet also has advice on making your device easier to use if you have a disability.

Important notes: Sage CRM is currently updating the technology that it is built on. We’re bringing in improved accessibility support as we go, but not all features benefit from this technology yet. Sage CRM is a highly customizable, including by third party developers. Your implementation of Sage CRM may differ from this statement.

How accessible this product is

We know some parts of the product are not fully accessible.

  • When editing some content using the keyboard, sometimes people might become trapped and are unable to continue.
  • You may have difficulty interacting on some pages and buttons using the keyboard alone.
  • When using the tab button to move around, the sequence of movement is sometimes unusual.
  • If you use a screen reader, you may not be informed of error messages.
  • Error messages may not provide suggestions on how to correct the error.
  • Some fields or buttons may have poor visual contrast against the background.
  • There are some parts of the product which can only be navigated around by using menus
  • There are several other improvements we could make to our code to help the product work as well as it can for everyone.

Feedback and contact information

We know some parts of this product are not fully accessible.

If you need support, you find any problems not listed on this page, or if you think we’re not meeting accessibility requirements, please contact us:

We’ll consider any requests and get back to you as soon as possible.

Technical information about accessibility

Sage CRM is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-compliance with the accessibility guidelines

The content listed below is non-accessible for the following reasons.

Non-text content

We would like all elements on a page that have meaning to have a text alternative. However, text alternatives for some images are not available. We are working to define appropriate text alternatives for these images.

WCAG Reference 1.1.1

Identify input purpose

We would like the type of each field on the page to be apparent in code so fields can be presented in the most useful way to users, but sometimes this isn’t the case right now. To fix this, we’re working on updating the code for all fields. We would like to allow you to use ARIA landmarks to identify page regions, but these are missing. We will we’ll investigate adding the consistent use of ARIA landmarks going forward.

WCAG Reference 1.3.5

Contrast (minimum)

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

WCAG Reference 1.4.3

Non-text contrast

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, in some places, this isn’t the case. To fix this, we’re working on improved visual styles.

WCAG Reference 1.4.11


We would like everything that’s interactive to be accessible using the keyboard alone. However, our site navigation, tables, and some buttons aren’t yet keyboard accessible. To fix this, we’re working on new navigation, tables, and buttons.

WCAG Reference 2.1.1

No keyboard trap

We would like to avoid situations where you might get stuck if using the product with the keyboard alone. Right now, tabbing to the end of some message boxes means keyboard focus is lost and you need to press the Esc key to exit. To fix this, we’re rebuilding our message boxes.

WCAG Reference 2.1.2

Bypass blocks

We would like to allow you to bypass repeated blocks of content (such as skipping the navigation), as this may help people using assistive technologies. These features aren’t present in the application today, but we’ll investigate adding them.

WCAG Reference 2.4.1

Focus order

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.

WCAG Reference 2.4.3

Multiple ways

We would like to offer you more than one way to navigate around the application. Today we provide a navigation menu, action buttons in list views and search that covers most data. We’re investigating adding features like a sitemap or improved search.

WCAG Reference 2.4.5

Focus visible

We would like keyboard focus indicator to always be visible when using the application. Presently, we have some instances where scrollable regions do not show the focus. We are looking to address these.

WCAG Reference 2.4.7

Label in name

We would like the text we use for the labels of fields to be the same as the text we use for the field’s name in code to support speech input or text-to-speech users. While the code does contain the label text, it is combined with other content that makes it difficult to understand. To fix this, we’ll use different naming conventions.

WCAG Reference 2.5.3

Language of page

We would like to set the language of each page in code so content is always presented correctly. This code isn’t present in the product today, but we’ll plan to add it.

WCAG Reference 3.1.1

On input

We would like the behaviour of our application to be that when changing the setting of any user interface component, the context will not automatically be updated unless the user has been advised of the behaviour in advance. We would like our search components to tell you when the number of results has been updated after each keystroke.

WCAG Reference 3.2.2


We would like IDs in code to be unique, so the product works well for all users, but today some IDs are not unique. We’ve logged these cases to fix.

WCAG Reference 4.1.1

How we tested this application

  • The test was carried out internally by Sage employees.
  • Sage CRM is available globally and is localised to French, German, Spanish versions. Much of the user interface is the same, however, we tested the UK version specifically.
  • We tested all pages listed in the primary navigation of default system with Demo data.
  • We did not test plugins, extensions, or customisations.
  • Accessibility was last tested on Sage CRM 2021 R2 in October 2021.

    The test was conducted using:

    • Chrome version 95.0.4638.54 on Windows 10
    • Chrome version 95.0.4638.54 on Samsung Galaxy tablet S6
    • Edge version 95.0.1020.30 on Windows 10