Carlos Lastres
Carlos Lastres1,434 words

Japan's Government Ships a Better Design System Than Most of Its Exporters

Japan's Digital Agency publishes a design system. It is on version 2.17.0 as of 5 August 2026. It has design tokens, a Figma library, HTML and React component code, an icon and illustration set, written accessibility guidance, and three separate public changelogs for documentation, design data and everything else.

The tokens and the reference components are on GitHub under the MIT licence.

I have worked with Japanese companies with revenues in the billions of dollars whose design system is a PDF from 2019 that nobody can find the source file for.

The thing I did not expect

The standard story about government technology is that it lags the private sector by a decade. In Japan the story is usually told with feeling, because most people here have filed something on a government website.

On this one specific axis, it is no longer true, and I think it stopped being true without most of the industry noticing.

Go and look at design.digital.go.jp. The Digital Agency defines its design system as three things: a design language covering styling, UI components covering visual representation and interaction, and guidelines for design and implementation grounded in usability and accessibility. It is scoped to central government, local authorities and public bodies, and it is framed against the agency's stated mission of digitalisation that leaves nobody behind.

Then look at the changelog, which is where you find out whether a design system is alive. The entry for 5 August 2026 revises typography and the colour foundations. On 27 May 2026 the global menu was renamed to the horizontal menu across the header and menu components, which is the kind of tedious naming correction that only gets made by people who have to answer support questions about it.

My favourite entry is 22 July 2026, which revised the disclosure and accordion components and added a line of guidance: do not use a disclosure when the content is important to most users.

That is not a styling rule. It is somebody who has watched a form get filled in badly, worked out that the reason was a collapsed section, and written the finding down where the next team will hit it. Institutional learning, in a public changelog, on a government website.

Semantic versioning on a government design system is a smaller detail that tells you the same thing. It means somebody decided that consumers of this thing need to know whether an update will break them. That is a maturity signal you cannot fake.

There is a standard behind it, with a level and a deadline

The part the private sector genuinely does not have is the accountability layer underneath.

The Ministry of Internal Affairs and Communications publishes the Public Site Operation Guideline, 2024 edition. It tells public bodies, in plain language, what to do about accessibility depending on where they currently stand. Sites already conforming to JIS X 8341-3:2016 level AA should continue and extend the work. Sites not conforming should promptly publish an accessibility policy and work towards level AA. New builds should conform at construction time, with the conformance test carried out and published.

JIS X 8341-3:2016 is Japan's national web accessibility standard and it is aligned with WCAG 2.0. Level A is 25 success criteria. Level AA adds 13 more. AAA takes the full set to 61, and the guideline explicitly does not ask for AAA, which is the right call and one a lot of well meaning private policies get wrong.

So a Japanese public body has a named standard, a named level, a requirement to publish its own policy, and a requirement to publish its test results.

The Digital Agency also publishes a web accessibility introduction guidebook, written deliberately for designers and managers rather than engineers, with the jargon stripped out and diagrams in place of specification language. On 16 October 2025 it was incorporated into the Digital Society Promotion Standard Guidelines as a reference document, which is the bureaucratic way of saying it is now part of how government projects are supposed to be run.

What the private sector has instead

A duty with no standard attached.

On 1 April 2024, Japan's revised Act on the Elimination of Discrimination against Persons with Disabilities made reasonable accommodation a legal obligation for private businesses rather than a matter of effort. That was a real change and I wrote about it at the time.

What it did not come with is a level, a test, a publication requirement or a reference implementation. A Japanese company that wants to comply has a legal duty, no defined target, and no shared component library to start from.

Which is exactly the situation in which nothing happens, and I want to be fair about why. It is not indifference. I have sat with Japanese teams who genuinely wanted to do this and could not get past the first question, which is what done looks like. Without a level, every accessibility conversation becomes an unbounded one, and unbounded conversations do not survive contact with a quarterly plan.

The obvious move nobody is making

The standard is public. The guidebook is public and written for non specialists. The tokens and reference components are MIT licensed on GitHub, in the digital-go-jp organisation: design-tokens, design-system-example-components-html and design-system-example-components-react.

MIT means you can use them commercially, modify them and ship them, with attribution of the licence. There is no negotiation and no procurement process. A Japanese company could adopt the government's accessibility baseline this quarter, for free, and be measurably ahead of most of its competitors.

I would not tell anyone to adopt the government's visual language. That would be a mistake, and not for the reason people assume. The type, the colour and the component shapes are tuned for a public service that has to look institutional and trustworthy to a hundred and twenty three million people, which is the correct goal for a tax filing service and the wrong goal for almost any product.

The parts worth taking are the parts underneath the appearance. The token structure, which is a decision about how a system is organised rather than how it looks. The component inventory, which is a list of the interactive problems a real service actually has and is a better checklist than anything you will assemble from scratch. The accessibility guidance, which is the same regardless of your brand. And the versioning discipline.

Take the skeleton, throw away the skin.

Why a government builds one and a company does not

This is the part I find genuinely interesting, because it is not about budget.

A design system is an institutional memory device. Its actual function is to hold decisions in a form that survives the departure of the person who made them.

Japanese central government rotates staff on a fixed cycle. Nobody owns a service for a decade. So the institution cannot rely on anyone remembering why the error message is worded that way, and it has to write the decision down in an executable form or lose it. Constraint produced the system.

A Japanese company with lifetime employment and slow internal movement has the opposite situation. The person who decided is still in the building, so you can go and ask them. Which works, right up to the day they retire, and then twenty years of undocumented judgement leaves with them.

Design systems in companies get sold on efficiency. Fewer duplicated buttons, faster handoff, consistency across platforms. Those are real and they are not why the important ones exist. The important ones exist because someone worked out that the knowledge in individual heads was a liability on the balance sheet.

Japan's demographics make that liability come due on a schedule you can read off a chart. There are people whose judgement is holding up entire product lines and who are five years from retirement, and in most of the companies I have seen, nobody has started writing it down.

The government did, because it had to. That is the whole difference, and it is available to copy.

Sources

← All posts