- Who else accessibility features help
- Five low-cost fixes to start with
- Contrast targets for text and background
- Where Japan's rules and standards sit
The short answer
Accessibility is not a bolt-on for one group of users. Reading aloud, voice input, larger text, high contrast and keyboard-only operation are things any of us need as soon as the circumstances change. The order of work is not complicated either. Start with text size and contrast, then keyboard operation, then alternative routes to reach you. None of the three is expensive, and all three widen who can actually use what you built.
The same feature, a different day
| Feature | Who it is usually built for | Who else it rescues |
|---|---|---|
| Reading aloud | People with low vision | Anyone driving, commuting, or reading at the end of a long day |
| Voice input | People with limited hand movement | Anyone whose hands are full, or wearing gloves on site |
| Larger text | People with partial sight | Older customers, bright sunlight, a small phone |
| High contrast | People who perceive colour differently | Outdoors, an old screen, a dark room |
| Captions | People who are hard of hearing | A noisy shop, a train where you cannot play sound |
| Keyboard operation | People who cannot use a mouse | Wrist strain, a dead mouse, anyone who works fast |
| Simple flows | People with cognitive load | First-time users, people in a hurry, people who are tired |
Written out like that, the right-hand column is everyone. Break an arm and you are using one hand; carry a child and your hands are full. Permanent and temporary situations differ in duration, not in what they need from the screen.
What to fix first
- Let people change the text size, then check that nothing is clipped or overlapping when they do.
- Get real separation between text and background. Pale grey text reads fine on a new screen indoors and disappears outdoors.
- Try operating the site without a mouse. Can the Tab key reach every field and the submit button, and can you see where the focus is?
- Describe your images. Screen readers get the meaning, and so does anyone whose images failed to load.
- Offer more than one route for the same request. A form plus a phone number plus an email address loses fewer people than a form alone.
For text and background, the W3C's Web Content Accessibility Guidelines (WCAG 2.2) give a usable target: 4.5:1 for normal text and 3:1 for large text, where large means at least 18 point, or 14 point bold, or the equivalent size for Chinese, Japanese and Korean typefaces.
Where voice and AI widen the door
Asking a question out loud and hearing the answer removes reading and typing from the equation at once. It helps when you cannot look at a screen, cannot type, or find following text tiring, which are three different groups of people having the same problem. Translation works the same way: for someone who struggles with the language your notices are written in, converting them on the spot does the same job as magnification.
Some of the products APOUL plans to release deal with spoken answers and translation. Both are built as features anyone reaches for when the situation calls for it, rather than as assistive extras kept off to one side.
Where the rules sit
Someone will eventually ask what obliges you to do any of this. In Japan, the guidance from the Cabinet Office states that the revised Act on the Elimination of Discrimination against Persons with Disabilities came into force on 1 April 2024, turning the provision of reasonable accommodation by businesses from an effort obligation into a legal duty. The Cabinet Office describes reasonable accommodation as taking necessary and reasonable steps to remove a social barrier when a person with a disability indicates that they need it, provided the burden is not excessive, and stresses working out the response together through dialogue.
The same guidance calls advance improvements aimed at people with disabilities in general — revising manuals, staff training, making facilities barrier-free — "improving the environment", and treats that as an effort obligation. What any of this means in a given situation varies, so read the Cabinet Office's own guidance rather than a summary.
On the technical side, alongside the W3C guidelines, Japan has the JIS X 8341-3 standard, and the Ministry of Internal Affairs and Communications publishes an operations guideline for public sector websites, most recently a 2024 edition, which the ministry describes as a handbook explaining the steps public bodies should take based on JIS X 8341-3. Matching every clause is a lot for a small private company to take on, but it helps to know where to look when a judgement call comes up.
Where it goes wrong
Treating accessibility as a list of features to add can make things worse. Alternative text written as a paragraph exhausts the listener before the point arrives. Image descriptions that merely repeat the nearby heading add nothing. Judge by whether it makes sense when heard, not by whether the attribute is present.
The same thinking applies off the web. Do not print your notices in pale ink, do not run a contact route that exists only by telephone, and keep instructions to one idea per sentence. Most real difficulty shows up at the point where someone is trying to get in touch or sign up.
Finally, do not rely on automated checks alone. A tool can measure contrast and heading structure. It cannot tell you that the third step is confusing. Ask a colleague to use the site for five minutes with the mouse unplugged; it is the fastest test you have.
In short
Accessibility is not special treatment for someone else. It is what keeps a product usable when your own circumstances change. Start with text size, contrast, keyboard operation, image descriptions and a second way to get in touch. None of it costs much, and each step helps widen the door.
APOUL ANSER VOICE
APOUL Translator