# When brand design undermines readability > Approved colors and typography make important text or controls difficult to use. Diagnose the cause, choose a bounded correction and verify critical reading and interaction paths passing appropriate checks. Source: https://saas-marketing.net/guides/brand-guidelines-have-no-accessibility-check/ Topic: SaaS Branding Type: guide Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/brand-guidelines-have-no-accessibility-check/ ## Short answer Approved colors and typography make important text or controls difficult to use. Start with this check: Inspect contrast, text scaling, focus visibility and narrow-screen behavior on real components. The corrective action is to define accessible combinations and test them in the actual interface rather than only a palette document. ## Key takeaways - Inspect contrast, text scaling, focus visibility and narrow-screen behavior on real components. - Define accessible combinations and test them in the actual interface rather than only a palette document. - Do not treat a visual review as a complete accessibility certification. - Review critical reading and interaction paths passing appropriate checks. --- Approved colors and typography make important text or controls difficult to use. The useful response is a diagnosis that changes a decision, not another report describing the symptom. Use this play with the brand owner and the teams applying the promise. The working evidence should include message hierarchy, proof register and approved asset rules, with private or sensitive details removed from any shared example. ## Confirm the problem in the actual workflow Inspect contrast, text scaling, focus visibility and narrow-screen behavior on real components. Start with one representative case and follow it from the original action to the reported outcome. Identify where the observed behavior first differs from the intended process. A screenshot of a final dashboard can be useful, but it may hide the source record, a delayed update or a decision made elsewhere. Keep the unit of analysis explicit: an intended audience’s understanding and recognition. The same label can conceal different populations or stages. Before comparing two results, check that they describe the same kind of work and have had a comparable chance to complete it. ## Separate the visible symptom from the cause Check whether the brand helps the audience recognize the product and understand its relevant promise. Consistency does not require identical copy in every context, but material claims should not contradict each other. Keep evidence, rights and accessibility requirements attached to the assets used. The symptom in this case is specific: approved colors and typography make important text or controls difficult to use. Ask which piece of evidence would distinguish an operating failure from a measurement failure or a mismatch in the original plan. If the evidence is unavailable, record the missing source and its owner instead of treating the preferred explanation as established fact. ## A situation to work through A consent note can match the brand palette and still be too faint or small to read comfortably on a phone. This is an illustrative situation, not a reported client case. Record the equivalent evidence and assumptions for your own workflow. ## Choose the smallest useful correction Define accessible combinations and test them in the actual interface rather than only a palette document. Keep the change narrow enough that the responsible people can implement and inspect it. If a correction changes several things at once, describe it as a combined operating change; do not later claim that one small element caused the whole result. Assign the correction to the brand owner and the teams applying the promise. Agree which artifact will show that the work is complete. An owner without an observable acceptance condition can close a task while leaving the original problem unresolved. A detailed checklist without an owner creates the opposite problem: the evidence requirement exists, but nobody is accountable for producing it. ## Preserve the important limitation Do not treat a visual review as a complete accessibility certification. This condition belongs beside the recommendation because it can change the decision. It should not disappear when the plan becomes a short presentation or a status update. A memorable campaign can still fail to communicate which product it represents. A consistent design can still be difficult to read. Review recognition, comprehension and usability as related but distinct questions rather than treating visual polish as proof of all three. ## Verification worksheet | Review item | What to record for this issue | Owner | Evidence | | --- | --- | --- | --- | | Observed symptom | Approved colors and typography make important text or controls difficult to use. | | | | Diagnostic test | Inspect contrast, text scaling, focus visibility and narrow-screen behavior on real components. | | | | Proposed correction | Define accessible combinations and test them in the actual interface rather than only a palette document. | | | | Guardrail | Do not treat a visual review as a complete accessibility certification. | | | | Review measure | Critical reading and interaction paths passing appropriate checks | | | Download a working copy and follow the [worksheet instructions](/resources/#using-worksheets). Keep unknown facts visible rather than filling gaps with guesses. ## Decide whether to keep, revise or stop the change Review critical reading and interaction paths passing appropriate checks after the agreed observation period. Keep the correction when the intended behavior is verified and the guardrail remains acceptable. Revise it when the diagnosis was useful but the intervention did not resolve the cause. Stop and reassess when new evidence shows that the original problem was framed incorrectly. Record what changed in message hierarchy, proof register and approved asset rules. This gives the next review a stable starting point and prevents a definition change from being mistaken for a performance improvement. ## Related methods and next steps - [Brand and performance budget planner](/calculators/brand-vs-performance-budget-split/) - [Brand vs performance marketing for SaaS](/comparisons/brand-marketing-vs-performance-marketing/) - [Rebrand vs brand refresh for SaaS](/comparisons/rebrand-vs-brand-refresh/) - [Category design: a worked decision review](/examples/category-design-teardowns/) Return to the [saas branding topic guide](/saas-branding/), browse its [complete resource collection](/topics/saas-branding/), or use the [working resource library](/resources/). The [primary reference](https://www.w3.org/WAI/fundamentals/accessibility-intro/) provides relevant platform or methodological context; the diagnosis and example here are original editorial guidance. ## Frequently asked questions ### What is the first diagnostic check? Inspect contrast, text scaling, focus visibility and narrow-screen behavior on real components. Inspect the actual working record or customer path rather than relying only on a summary report. ### What should change after the diagnosis? Define accessible combinations and test them in the actual interface rather than only a palette document. Record the owner and the evidence needed to verify the correction. ### What limit should the team keep visible? Do not treat a visual review as a complete accessibility certification. A local improvement does not establish a universal benchmark or guarantee a commercial result. ### How should the correction be evaluated? Review critical reading and interaction paths passing appropriate checks using a consistent unit and observation window. Keep the original evidence and record any measurement changes.