Accessibility
We sell readable colour, so it would be odd not to say where our own site stands. Here it is, including the parts we have not finished.
The standard we aim at
We aim for WCAG 2.2 Level AA on this site and in the customizer. It is the current version of the standard, and it includes everything in WCAG 2.1 AA, which is the benchmark US courts use under the Americans with Disabilities Act and the one European law points to.
What that means in the product
We do not check contrast at the end. We build it in. Every theme runs through every pair on our list (26 text and background pairs SuiteCRM draws), and almost all of them are moved automatically until they clear 4.5 to 1 before we build the file. One pair, for brands where the maths genuinely cannot satisfy two different backgrounds with the same colour, cannot always be fixed; when that happens it is reported on the export screen before you pay, not hidden. You see the full contrast report either way, and the home page runs the same arithmetic in front of you each time you pick one of the sample brands.
So you cannot hand your team a CRM they struggle to read just because your brand colour is a tricky one. That is the usual problem with a hand-made theme.
What we have done on this site
- You can reach and use every button and link with a keyboard, and you can see where you are.
- A “Skip to content” link is the first thing on every page.
- Buttons and links are at least 24 pixels tall, or spaced so they are easy to hit.
- When a panel closes or a step changes, your place moves with it, and a screen reader is told what happened.
- Form fields say what is wrong in words, on the field itself, and never only in red.
- Colour is never the only clue. Status badges have words on them too.
- The sample app is marked as decoration, so a screen reader does not read out a table of made-up records.
- Text drops to one column on a phone with no sideways scrolling.
- While the cookie notice is open, the page leaves room for it at the bottom, so a control you move to is scrolled clear of it rather than hidden behind it.
- There is very little movement, and we turn it off if your device asks us to.
What we know is not there yet
- We have not tested the colour picker with a screen reader. It is operable from the keyboard, and every colour it sets is also typeable as a hex value in the field beside it, which is the route we are confident in.
- The six-screen preview is something you compare by eye. The contrast report beside it is the non-visual equivalent, and it names every pair and its ratio, but there is no way to hear what a screen looks like.
- Nobody outside the company has audited us yet. When that happens, we will put what they find, and when we plan to fix it, on this page.
The themes we generate, and the CRM around them
We can promise the colour contrast of a theme we make. We cannot make the whole CRM accessible, because we did not build it. Missing labels, keyboard traps, and heading problems in the app itself are not something a colour theme can fix. Anyone selling you a theme who says otherwise is not being straight with you.
Telling us about a barrier
If something here or in the customizer does not work for you, email support@brandtint.app. Tell us what you were trying to do. We aim to reply within five working days. If it is stopping you buying something, say so and we will find another way to get it to you.
Last reviewed October 15, 2026. See also our privacy notice and terms.