Skip to main content

Enterprise Systems Multi-Tenant Architecture & Accessibility

Enterprise White-Label Theme Generator: Balancing Custom Branding with Strict WCAG 2.1 AA Accessibility

My Role
UX/UI Designer
Team
1 Lead Designer, 1 Senior UX Designer, 1 UX/UI Designer (myself), Product Owners, QA Engineers, Frontend & Backend Engineering Team
Duration
October 2020 - December 2022 (2 years 2 months)
Domain
Multi-Tenant Enterprise / Healthcare / Public Sector
Key Outcome
Automated label and state colours for white-label tenant themes, so custom themes keep WCAG 2.1 AA contrast and admins can brand the portal themselves instead of filing engineering tickets.

Executive Summary

The Context

The platform is an enterprise data governance tool deployed across multi-tenant environments, including healthcare organisations and public sector agencies.

The Problem

Changing a tenant’s branding took custom CSS or an engineering ticket. To support institutional white-labelling, executive management proposed an open colour picker allowing administrators to freely rebrand the user interface. However, unrestricted customisation posed a severe usability risk: non-designer admins could unintentionally choose low-contrast colour combinations, making dense data views unreadable and violating mandatory accessibility requirements (WCAG 2.1 AA).

The Core Problem: Management Assumption vs. Usability Reality

The Assumption

Give client administrators complete freedom to apply their corporate brand colours to any interface component.

The Reality

  • High risk of human error: Untrained admins pairing light text with pastel buttons or dark cards on dark backgrounds.
  • Accessibility compliance failures: Failing mandatory WCAG 2.1 AA contrast requirements (4.5:1 for body text, 3:1 for large text and interface components).
  • Illegible critical data: Low-contrast palettes making system status badges, table data, and interactive actions difficult to read for everyday users.

The Solution: Governed White-Label Theming & Accessibility

To prevent unrestricted branding from breaking usability, I designed a governed theming workflow. We gave client administrators control over key brand touchpoints, while embedding clear WCAG 2.1 AA guardrails, luminance rules, and validation checks to protect readability across enterprise workflows.

  1. Configurable Surfaces & Inline Guidance

    A focused theme editor letting administrators rebrand key touchpoints while preserving data readability.

    • Scoped Brand Surfaces: Limited customisation to a few named surfaces - the header bar, action buttons, navigation sidebar and table selection - while table text and canvas areas stay on neutral system colours.
    • Contextual Guidance: Every colour field shows its contrast rating and a short note on what it affects, and a live preview updates as admins edit, before anything reaches users.
    • Structured Theme Editor: Grouped the settings into clear sections - General, Header bar, Navigation sidebar, Content & tables and Custom CSS - with drafts and autosave, to reduce setup errors for non-technical administrators.
  2. Automated Component States from One Base Colour

    A simple system rule for developers: administrators pick one base colour, and every interactive state is calculated from it.

    • No Manual State Tuning: Instead of asking admins for separate hover, pressed and disabled colours, the system mixes the base colour: +30% black for hover, +30% white for pressed and 40% opacity for disabled.
    • Automatic Label Contrast: Labels and icons switch between white and near-black (#12141A), whichever contrasts more with the background, so text stays readable on any brand colour.
    • Navigation Tabs: The selected tab lifts with +35% white on dark header backgrounds and deepens with +8% black on light ones.
  3. Sidebar and Table Selection Rules

    Extending the same logic to navigation drawers and dense data tables.

    • Clear Selection States: The active sidebar item and selected table row use the full chosen colour, hover uses a 35% tint, and pressed adds 8% black, so dense records stay easy to scan.
    • Readable Text in Every State: Text colour is recalculated for each state, so a light or dark brand colour never hides the row or item label.
    • One Reusable Function: Engineers implement the rules once as a shared stylesheet function that works for any palette, instead of maintaining hundreds of hand-picked hex values.
  4. Advocating for Accessibility in Team Reviews

    A visual comparison matrix I presented during a team meeting to demonstrate why colour guardrails were critical for real users.

    • Demonstrating Real Usability Risks: Prepared side-by-side screens showing how custom brand themes, such as a bold red healthcare theme, change under Protanopia, Deuteranopia, and Tritanopia.
    • Highlighting Broken Interactions: Showed the team that without safeguards, primary buttons could look disabled or unclickable, while urgent alerts stopped standing out.
    • Aligning the Team on Accessibility: Used this practical comparison to convince stakeholders and developers that we needed built-in contrast rules, and status colours that always come with an icon and a text label, not an unconstrained colour picker.
  5. Colour-Vision Accessibility Preview (Phase 2)

    A designed preview in the theme’s details panel to help administrators see the impact of their colour choices before publishing.

    • Accessibility Tab: An “Accessibility” tab lets admins switch the theme preview between typical vision, Protanopia, Deuteranopia and Tritanopia, next to the theme’s contrast checks.
    • Showing Real Usability Issues: Side-by-side previews show admins how colours that look distinct to them can blur together for other users.
    • Moved to Phase 2: To launch the MVP on time with the core contrast rules, we saved this interactive preview for the next product release.

Error Prevention & Deployment Safeguards

Changing visual themes in an enterprise multi-tenant tool directly affects active users across organisations. To prevent critical mistakes and broken layouts, I designed 3 clear safety mechanisms into the publishing workflow.

  • Protecting the Default System Theme

    Preventing critical system errors by locking the baseline theme.

    • No Editing or Deleting the Default Theme: The core system theme is read-only, ensuring the application always has a stable, accessible fallback.
    • Duplicate to Customize: Admins create new themes by duplicating an existing one, making it easy to test changes without risking the baseline setup.
  • Clear Warnings Before Applying Changes

    Explaining the immediate impact of publishing a theme to active users.

    • Explicit Confirmation Step: Before a theme goes live, a confirmation dialog shows the current and new theme side by side and states that signed-in users will see it on their next page refresh.
    • Reducing Accidental Publishing: Prevents administrators from unintentionally altering the live interface during working hours without prior notice, and reminds them that the previous theme can be republished.
  • Optional CSS Field with Maintenance Warnings

    Keeping custom CSS as a secondary fallback for technical teams, not the primary tool.

    • Secondary Add-on: Placed the optional CSS editor last among the theme sections and marked it Advanced, so users rely on the visual controls first.
    • Clear Warning Notice: An inline warning explains that custom CSS can break layouts during monthly platform updates, suggests requesting a layout change instead, and asks admins to confirm they will re-test after each release.

MVP Delivery & Phased Roadmap

To launch quickly while keeping enterprise standards high, our team prioritised core functionality for the MVP and moved advanced educational tools to the next release.

  1. Shipped · MVP

    Self-Service Theming

    Launched the administrative customiser, allowing enterprise clients to rebrand key portal areas on their own without filing custom engineering tickets.

    • Enterprise
    • Healthcare
    • Public Sector
  2. Shipped · MVP

    Automated Contrast & State Rules

    Integrated baseline WCAG 2.1 AA contrast checks, automatic label colours (white or near-black) and state colours calculated from one base colour, so components stay accessible by default.

    • #FFFFFF
    • #12141A
  3. Shipped · MVP

    Publishing Safeguards

    The default system theme stays locked, and a confirmation step warns admins before a new theme reaches active users.

    • Locked system theme
    • Duplicate to customize
    • Publish confirmation
  4. Phase 2 · Roadmap

    Colour-Vision Accessibility Preview

    While the contrast rules launched in the MVP, the interactive preview simulating colour blindness was documented as a Phase 2 feature for future sprints.

    MVP Contrast & state rules
    Phase 2 Colour-vision preview

Developer Handoff & Technical Collaboration

Since this project was designed in Adobe XD before native design token plugins were widespread, maintaining consistency required clear and simple handoff documentation.

  1. 05

    A Short Rule Set Instead of Endless Hex Codes

    Documented every state as a rule on the base colour: +30% black for hover, +30% white for pressed and 40% opacity for disabled; the selected sidebar item or table row uses the full colour, with a 35% tint on hover and +8% black when pressed; labels switch to white or near-black, whichever contrasts more.

    • Base base
    • Hover +30% #000
    • Pressed +30% #FFF
    • Disabled 40% opacity
  2. 06

    Collaborative Implementation

    Worked closely with frontend developers so they could turn these rules into one shared stylesheet function, keeping component behaviour consistent across any client palette.

    --selected: var(--brand);
    --hover: color-mix(in srgb, var(--brand) 35%, var(--surface));
    --pressed: color-mix(in srgb, var(--brand), #000 8%);
    --on-brand: contrast-pick(var(--brand), #FFF, #12141A);
    

Key Takeaways & Retrospective

  1. Guardrails Protect Real Usability

    In enterprise tools, unlimited user freedom often leads to broken interfaces. Designing sensible boundaries - like locking core text contrast and restricting brand customisation to key areas - protects legibility without frustrating administrators.

  2. Designing for High-Impact Mistakes

    When an administrative change affects hundreds of daily users, UX safety is essential. Adding confirmation warnings and locking the default system theme guards against critical mistakes while keeping the configuration workflow straightforward.