Brand Strategy
Accessible Brand Identity: What to Ask Your Branding Studio For
Updated
A founder approves a new identity with a soft yellow palette. Two weeks later the web team asks to change the primary button. White text looked fine on the presentation slide, but on a phone the label disappears into the yellow. The founder sees another round of design. The web team sees a button people need to read before they can buy.
An accessible brand identity gives both teams a better starting point. It sets rules for how colour, typography and visual cues work in the places people use them. If you are hiring a branding studio, put those requirements into the brief and agree how you will evaluate the concept before approving it.
Cover photograph by Fiona Murray-deGraaff on Unsplash.
Brief the decisions customers need to make
Start with three to five places where confusion would cost a customer time or stop a purchase. For a food brand, that might mean choosing a flavour from a mobile product grid, reading preparation instructions on a pack and spotting a required field at checkout. For a service business, it might mean comparing plans and submitting an enquiry by keyboard. Give your studio the actual wording, screenshots and templates. If you are assembling the wider project scope, add these examples to your branding brief.
Turn each example into an approval question. Can someone tell the flavours apart when the thumbnails are small? Does the form say which entry needs fixing? Can the customer tell where keyboard focus is as they move through the page? These questions give the studio and the implementation team a shared definition of what the design has to do.
Ask for colour pairings with specific jobs
A palette shows the colours a brand owns. A pairing guide tells the team what to put on each colour and when to use it. Ask the studio to specify approved combinations for everyday text, links, primary buttons, form messages and any dark surfaces in scope. Include the background and the foreground in every entry. Contrast describes the relationship between two colours, so a swatch on its own tells the developer very little.
For web content, WCAG 2.2 Level AA sets a minimum contrast of 4.5:1 for most text and 3:1 for large text as defined by the standard. Logo text is exempt from that particular criterion. A checkout button label or delivery note still needs to be evaluated as text. The non-text contrast criterion also sets a 3:1 minimum for visual information needed to identify certain controls and states, and for relevant parts of graphics, subject to its exceptions.
For example, white text on a soft yellow such as #FFD76A has a contrast ratio of about 1.4:1. Using dark #1A1A1A text on the same yellow gives about 12.6:1. The studio can keep yellow prominent and give the label a readable pairing. Ask for a rule for text over photography too. If the image can change in the CMS, a solid backing for copy may be easier to maintain than testing every image crop.
Give every important colour cue a second signal
Colour can help people scan. Pair it with a cue that carries the same meaning. Put the flavour name on the product thumbnail, give the current step a label such as “Step 2 of 3,” and put “Enter a valid email address” next to the relevant field. A red outline can support that message. The text tells the customer how to recover. WCAG 2.2’s Use of Color criterion covers this principle for web content.
Ask your studio for one example that your team is likely to copy. For a subscription business, show the selected plan and the rest of the options within the real card layout. For a multi-flavour food brand, review two similar packs together and then check whether the product names survive in the retailer’s thumbnail crop. For print, review legibility on the physical sample under the lighting customers are likely to encounter.
Review type with the copy people will actually read
Ask to see the longest product name, a price, a delivery note and a full paragraph in the proposed type system. Open them on a narrow mobile screen and review them at the sizes the team intends to use. A distinctive display font can work well for headlines while a different cut or family serves instructions and product details. If you sell across languages, bring realistic examples with longer phrases, different character sets or accents into this review.
For a digital template, also check what happens when a visitor zooms or increases text size. Fixed-height cards and clipped labels are implementation problems the team can catch before launch. Agree who checks the finished experience and include those responsibilities in the brand guidelines handoff.
Agree on what the studio delivers and who tests the build
Ask for a shortlist of approved colour pairings with their roles and contrast ratios, type styles shown in context, examples of key states and a few reusable templates. Put those items in the scope so the client, studio and web team can quote and plan against the same deliverables.
Give the implementation team responsibility for checking the running site, including visible keyboard focus, form behaviour and page structure. If you need a formal WCAG evaluation, define its scope and who conducts it up front. The identity can make accessible choices easier to repeat. The final accessibility of a site depends on how those choices are implemented and how content is added over time.
If you are commissioning a new identity or replacing one your team keeps working around, tell us where it needs to work first. Explore UNDOUBT STUDIO’s branding packages and bring those applications into your project brief.
Source notes. The web guidance references the W3C WCAG 2.2 Recommendation. The colour example uses WCAG relative luminance for solid sRGB colours. Both editorial photographs are available under the Unsplash License.
Found this useful?
Views —