Figma Colour System Cleanup - WCAG 2.2 AA Compliance

Figma Colour System Cleanup - WCAG 2.2 AA Compliance We have a completed set of Figma designs for a web application. The layouts, structure, and overall visual direction are settled and we're happy with them — this is not a redesign. What we need is a focused pass over the colour palette, contrast ratios, and small styling inconsistencies so the designs meet WCAG 2.2 AA and feel more polished and coherent. Scope of work: • Audit the existing designs against WCAG 2.2 AA contrast requirements (4.5:1 for body text, 3:1 for large text, icons, and interactive UI components) • Adjust the colour palette where needed to hit those ratios while staying true to the current look and brand feel • Check and correct colour usage across all interaction states — default, hover, focus, active, disabled, error, success, warning • Ensure meaning is never conveyed by colour alone (e.g. error states, status indicators, chart keys, required fields) • Review focus indicators for visibility and consistency • Tidy minor styling inconsistencies encountered along the way — spacing drift, mismatched border radii, inconsistent shadows, one-off type sizes • Consolidate colours into a clean, well-named set of Figma variables / styles (semantic tokens preferred, e.g. surface/primary, text/muted, border/subtle) • Sanity-check the palette for common colour vision deficiencies (deuteranopia, protanopia, tritanopia) Deliverables 1. Updated Figma file with corrected colours and styles applied across all screens and components 2. A documented colour token set (Figma variables/styles) ready for developer handoff 3. A short summary of what changed and why — including a before/after contrast table for the key combinations 4. A flagged list of anything you'd recommend changing that falls outside this scope, so we can decide separately Explicitly out of scope • Layout, IA, or navigation changes • New screens or new components • Full brand identity work • Wholesale reinterpretation of the visual direction If you think something structural is holding the design back, flag it — but don't action it without agreement first. What we're looking for: • Demonstrable UI design experience with accessibility as a genuine specialism, not an afterthought • Strong, fluent Figma skills — components, variants, variables/modes, and design-system hygiene • Working knowledge of WCAG 2.2 AA (bonus if you've worked to AAA or against a formal accessibility audit) • Restraint. The ability to improve something without redesigning it is the core skill for this job. • Clear written English and a responsive, low-friction communication style Nice to have: • Experience preparing design tokens for a front-end implementation • Familiarity with light/dark mode token structures • Some front-end awareness (how these tokens actually land in code) To apply Please include: 1. Portfolio examples where accessibility or contrast was a stated part of the brief — links to live work or case studies preferred 2. A brief note on your approach: how you'd tackle an existing palette that fails contrast without losing the original character 3. One specific observation. [Optional — attach 1–2 sample screens.] Tell us one contrast or colour issue you can spot and how you'd fix it. Applications that engage with the actual work go to the top of the pile. 4. Your availability and estimated hours Generic proposals and AI-generated boilerplate will be ignored. A few specific sentences beat three paragraphs of preamble.