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.
Non-compliance with the accessibility guidelines
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 aren’t available, aren’t easy to understand or they don’t match what is visually presented. We’re working to fix this by replacing older code and resolving identified bugs.
WCAG Reference 1.1.1
Information and relationships
We would like to make sure that information and relationships implied by visual formatting are clear to people using assistive technologies. However, headings are not correctly marked up in code. We will review our code to make improvements.
WCAG Reference 1.3.1
Where the sequence of content on a page is important, we will make sure 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 occurrences.
WCAG Reference 1.3.2
Identify input purpose
We use ARIA landmarks to identify page regions, but some might be missing. We will work to ensure the consistent use of ARIA landmarks going forward.
WCAG Reference 1.3.5
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 fix this, we’re working on improved visual styles and phasing out the use of placeholder text.
WCAG Reference 1.4.3
We would like everything interactive to be accessible using only the keyboard. 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.
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, users can escape from a table using the escape key, but there’s no way for them to know this ahead of time. Going forward, we will rebuild our tables to fix this.
WCAG Reference 2.1.2
We would like to provide features in code to allow users to bypass repeated blocks of content as this may help some users. For example, navigation that appears on every page. These features aren't present in the product today, but we are adding them.
WCAG Reference 2.4.1
Headings and labels
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.
WCAG Reference 2.4.6
We would like to set the language of each page in code so that content is always presented correctly. This code isn’t present in the product today, but we plan to add it.
WCAG Reference 3.1.1
Users may encounter situations where interacting with items causes unexpected behavior. We’re working on resolving these occurrences.
WCAG Reference 3.2.2
We would like people to receive appropriate suggestions to correct an error if possible. However, some error messages are worded broadly and many don’t include specific suggestions for correction. We will review our error message content.
WCAG Reference 3.3.3
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 as well as 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