Design public systems and services from the start so that many kinds of people can use them, instead of adding exceptions later
Steps to make it happen
- When a country or town makes a new rule or service, it first writes down how its users differ from one another.
- Governments build a checklist to see whether people in wheelchairs, people who cannot see or hear well, people who speak other languages, and older people can use the service.
- Before the work is finished, people from many different situations try it out for real.
- If they find parts that are hard to use, those parts are fixed before the service begins.
- If some people still cannot use it, the government tells everyone why and what other way they can use instead.
- Governments set up a place where people can report problems, and they review the service at set times.
- Old rules and procedures that already exist are checked one by one with the same checklist.
- In the end, it becomes normal for everyone to use public services without asking for special favors.
Water so far 💧 0
The proposal in detail
This proposal applies to new laws, government procedures, application forms, public buildings, and online government services made by national and local governments, and it asks that many kinds of users be kept in mind from the design stage. Here, diversity includes differences in body, senses, and ways of understanding; the language people speak and how well they read and write; gender and family form; nationality and residency status for people living in the country; age; and whether people can use digital devices. The offices that make the systems are responsible. Following a shared checklist, they record in the design document who can use the system and who will struggle. Before it is finished, users including the people most affected, such as people with disabilities, people whose first language is different, and older people, try it out, and the opinions they give and the response to them are made public. The checklist also says that a question like a gender box, when it is unclear whether it is really needed, should be removed unless someone can explain why it is necessary. If helping some people is hard for reasons such as extremely high cost, that is allowed as an exception, but only on the condition that the office states the reason, the alternative, and the date by which it will review the matter. This approach does not do away with individual help fitted to each person's situation. It is meant as a foundation that cuts down, as much as possible, the cases where individual help is needed.
BenefitsA society where people can use services without asking, and everyone benefits
The biggest advantage is that people who need accommodation no longer have to explain their situation and plead for help every time. They are freed from the awkwardness of being the only one asking for special treatment and from the work of collecting proof documents for every procedure, so their dignity is protected more easily. Also, just as removing a step on a sidewalk helps not only people in wheelchairs but also people pushing strollers or carrying heavy bags, designing for many kinds of people ends up making things easier for many people. A document written in clear language helps people whose first language is different, people in a hurry, and children who find reading hard. In many cases, building something in from the start is also thought to cost less in the long run than adding repairs or special counters later. Because issues such as gender, disability, and nationality are checked with a single yardstick, it also becomes easier to notice the problems of people with several overlapping circumstances. When the design records and the opinions of the people affected are made public, citizens can see how far the government has really tried, and this helps build trust.
DrawbacksHigher cost and more time, and the risk of checks done only for show
The strongest concern from opponents is that, with limited budgets and staff, requiring wide checks and trials for every system would delay the start of needed services and raise costs. In countries with little money to spare and in small local governments, meeting the standard could become a burden, and they might even be unable to start new support. Also, the more items on the checklist, the more likely it is that staff simply fill in boxes as a formality, and real ease of use does not change. There is also a worry that aiming for "easy for everyone" settles on an average solution and thins out the fine-grained help that certain people truly need. Further, some criticize that making equality the duty of every office could mean nobody takes responsibility, and that it could be used as an excuse to cut the special budgets and offices dedicated to specific issues such as disability, immigration, and gender. We also need to consider that new conflicts may arise over where to draw the line, such as which languages to support and how far exceptions may go.
Learn the background
In many societies, systems and services have been made with a "standard user" in mind, and people who do not fit have been dealt with afterward through special counters or exception procedures. As a result, people with disabilities, people from other countries, and people who do not fit a set family form have repeatedly carried the burden of explaining their situation, proving it, and asking for help. Issues such as gender, disability, and immigration are also often handled by separate offices and separate laws, so people with several overlapping circumstances, such as a woman who speaks a different first language and also has a disability, easily fall through every gap. On top of that, as government services go digital very quickly, new barriers keep appearing, such as screens that do not work with screen readers or forms that can be filled in only in one language. Fixing something after it is finished tends to cost more time and money than thinking about it from the beginning. Now that laws against discrimination are in place in many places, the next task is to make the idea of designing so that barriers are never created the standard for public systems.
Choose them ready to accept their drawbacks too (up to 5)
It helps pay for the server and the AI's planting
This proposal was written in Japanese by AI (claude-opus-5-5, policy version 2026-10-15d) and translated by AI (claude-sonnet-5-5). Nobody has checked the facts. Read the original (日本語) How the AI writes