Version 1.0 — Updated June 30, 2020
Sage Intacct is a cloud accounting application for businesses, which provides core accounting capabilities supplemented by solutions to automate complex revenue and billing processes, financial and budgeting capabilities, integrations with third-party software products, reporting, and additional advanced modules for financial management.
This accessibility statement relates to a specific instance of Sage Intacct provisioned for accessibility testing in the UK locale. Results for other locales, including Canada, cannot be inferred from this statement.
We want as many people as possible to be able to use Sage Intacct. For example, that means you should be able to:
- Use the web product on large screens without the need to scroll the page horizontally (separate mobile apps are available, which will be covered by their own accessibility statements)
- Navigate using consistent menus or a visual process map.
- 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.
AbilityNet also has advice on making your device easier to use if you have a disability.
- Sage Intacct 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 Intacct is highly customizable, including by third party developers. Your implementation of Sage Intacct may differ from this statement.
If you need support, find any problems not listed on this page, or think we’re not meeting accessibility requirements, please contact us:
We’ll consider any requests and get back to you as soon as possible.
We would like all objects on a page that have meaning to have a text alternative.
WCAG Reference 1.1.1
Info and relationships
We would like to make sure that information and relationships implied by visual formatting are clear to people using assistive technologies.
WCAG Reference 1.3.1
Use of colour
We would like to make sure that colour is not used as the only visual means of conveying information.
WCAG Reference 1.4.1
We would like the visual presentation of text to have good contrast against background colours to support people with visual impairments.
WCAG Reference 1.4.3
We would like the visual presentation of everything that’s interactive to have good contrast against background colours to support people with visual impairments.
WCAG Reference 1.4.11
We would like everything that’s interactive to be accessible using the keyboard alone.
WCAG Reference 2.1.1
We would like to provide features in code to allow users to bypass repeated blocks of content (for example, navigation that appears on every page), as this may help some users.
WCAG Reference 2.4.1
We would like each page to have a title in code that identifies its contents.
WCAG Reference 2.4.2
When using the tab button to move around, we would like the sequence of movement to be logical.
WCAG Reference 2.4.3
Headings and labels
We would like all pages to provide clearer and more descriptive titles, and for all pages to have a "Heading 1" in code.
WCAG Reference 2.4.6
We would like to help people know which item has keyboard focus.
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 in order to support speech input or text-to-speech users.
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.
WCAG Reference 3.1.1
We would like people to receive appropriate suggestions for the correction of an error if possible.
WCAG Reference 3.3.3
We would like IDs in code to be unique, so that 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
Name, role, value
We would like each field on the page to be associated with a label in code; however in some situations this isn’t the case (for example, checkboxes indicating table row selection or fields in tables). To fix this, we’re working on updating how cases like this are coded.
We would also like all icons to have text descriptions in code so it’s clear to all users what they do. We found some that don’t have descriptions, and we’ve logged them to fix.
WCAG Reference 4.1.2
If a message appears, we would like it to be clear to all users.
WCAG Reference 4.1.3
Without the need to scroll the page horizontally, it is possible to use the web product on large screens. (Separate mobile apps are available, which will be covered by their own accessibility statements.)
However, if you use the product on screens below 1930 pixels wide, you’ll need to scroll horizontally to see some 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’s 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.
WCAG Reference 1.4.10