What's the chocolate cake analogy for accessibility?

The chocolate cake analogy says accessibility is like the cocoa, eggs and flour - a core ingredient mixed in from the start, not icing added at the end. Bolting accessibility on after launch is far harder, more expensive and produces a worse result than baking it into design, build and content from day one.

Why can't accessibility be added at the end of a project?

Adding accessibility at the end usually means rebuilding decisions made earlier - components, navigation, content structure, third-party widgets - at much higher cost than getting them right initially. Late-stage remediation also tends to produce surface-level fixes that pass automated checks but still fail real users. Cost-of-rework studies consistently show late accessibility work is several times more expensive than designing it in.

What ingredients does an accessibility programme need?

A working accessibility programme needs five ingredients: standards (WCAG 2.2 as the recipe), capability (trained design, dev and content people who know the standard), governance (someone accountable, definition of done that includes accessibility), tooling (testing and validation built into the workflow), and lived-experience input (user research with people with disabilities, not just expert review).

Can accessibility overlay widgets fix an inaccessible site?

No - overlay widgets do not deliver real accessibility. They cannot fix the underlying code, frequently interfere with users' own assistive technology, and have been the subject of many complaints from disability communities. Accessibility requires fixing the source, not adding a widget on top. Treat overlays as a red flag, not a solution.

The Chocolate Cake Accessibility Analogy

Why accessibility and usability should be baked in, not added on

Imagine you're craving a rich chocolate cake. You gather the finest cocoa, premium chocolate, and all the ingredients needed to ensure every bite delivers pure chocolate bliss. The result? A cake that's rich, cohesive, and exactly what you wanted.

Now, imagine starting with a vanilla cake instead. Halfway through, you realise you wanted chocolate. So, you cover it with chocolate icing and maybe even inject some chocolate syrup inside. Sure, it looks chocolatey on the outside, and it might taste close, but it's not quite the same as a true chocolate cake.

This analogy perfectly illustrates the difference between designing with usability, accessibility, and universal design in mind from the outset versus trying to retrofit these principles later. The end result might seem similar on the surface, but the experience and the cost will tell a different story.

Upfront vs. Retrospective Design: The Pros and Cons

1. Cost Efficiency

Upfront: Building accessibility and usability from the beginning saves significant costs. Design decisions are intentional, and costly rework is avoided.
Retrospective: Retrofitting accessibility features often requires reworking designs, rewriting code, and rethinking workflows, all of which are costly and time-consuming.

2. Time to Delivery

Upfront: Projects stay on schedule as accessibility and usability are part of the initial scope.
Retrospective: Redesigning to address accessibility issues can delay timelines, sometimes significantly, especially if third-party audits uncover non-compliance.

3. User Experience

Upfront: A product designed with universal design principles delivers a seamless and enjoyable experience for all users.
Retrospective: Patchwork fixes may address functional gaps but often leave the overall experience feeling disjointed.

4. Brand Reputation and Compliance

Upfront: Proactive accessibility design enhances brand reputation, reduces legal risks, and ensures compliance with regulations.
Retrospective: Addressing compliance only after issues arise can result in reputational damage, legal challenges, and loss of user trust.

5. Testing and Validation

Upfront: Usability and accessibility testing are part of the standard development cycle, allowing early identification and correction of issues.
Retrospective: External audits and retroactive testing often reveal deep-rooted problems that require extensive redesign and validation.

The Lesson: Try to Build It Right from the Start

Whether designing documents, websites, or apps, the principle remains the same: building with accessibility, usability, and universal design in mind from the start creates a stronger, more effective product. Like a well-made chocolate cake, everything aligns perfectly, delivering satisfaction without unnecessary rework.

On the other hand, retrofitting accessibility after the fact may result in a product that looks correct but doesn't fully deliver on usability or inclusivity.

At ExceedAbility, we believe in baking accessibility into every stage of design and development. Whether you're working on a document, website, or app, starting with the right ingredients ensures your end product isn't just 'good enough': it's exceptional.

Ready to create a seamless experience for all users from the start?

Get in Touch