total_score

score_foundations

People search and replace values manually across design files and code. It takes weeks and things get missed.

Values are defined centrally in design or in code, but not connected. Someone updates both by hand.

It's changed in one place and flows automatically to both design and code.

It would be a multi-month project touching most screens.

Possible, but with a lot of manual work and one-off exceptions.

It's mostly configuration. We have it already or could add it in weeks.

They build their own. We have several versions of the same thing in production.

They start from the shared library but often copy and modify it for their case.

They use the shared component as-is, or extend it through an agreed process.

Not really. Accessibility is fixed case by case, usually after a complaint or audit.

Some components are checked, but it's inconsistent and not tested regularly.

Accessibility is built into shared components and tested, so teams get it for free.

Somewhere between a third and two thirds.

It's seen as a blocker. Teams work around it to hit deadlines.

Useful, but teams often wait on it or find it missing what they need.

It's the default. Using it is faster than not using it.

Noticeably different. Engineers treat designs as a rough suggestion.

Mostly the same, but details drift (states, spacing, naming).

Same components, same names, same options. Differences get caught and fixed.

Long threads, lots of back-and-forth, engineers guess values.

Engineers inspect designs themselves, with some clarifying questions per feature.

Designs reference existing components directly. Engineers rarely need to ask about specs.