Most software is designed on a large monitor by someone with good eyesight, steady hands and a fast connection. The people who then have to use it include a retired teacher reading without her glasses, a farmer holding a phone in bright sun, and a clerk who cannot use a mouse. Accessibility is the work of making one system serve all of them.
How many people this affects
Disability is far more common than most project plans assume. The World Health Organization estimates that 1.3 billion people, or 16 percent of the world's population, experience significant disability.1
The Philippine figures tell the same story. The National Disability Prevalence Survey found that in 2016 about 12 percent of Filipinos aged 15 and older experienced severe disability, 47 percent moderate disability and 23 percent mild disability. Only about one in five reported none. Almost one in three of those with severe disability were aged 60 or older.2
So this is not a small group with special needs. It is most adults at some level, and nearly everyone eventually. A public system that works only for the young and fully able shuts out a large share of the people it was paid for.
What the law already says
Republic Act No. 7277, the Magna Carta for Disabled Persons, approved in 1992, declares that disabled persons have the same rights as other people to take their proper place in society. It commits the State to remove social, cultural, economic, environmental and attitudinal barriers, and to work toward a barrier-free environment.3 The law was written before the web was in common use, but a government form that a blind person cannot fill in is a barrier of exactly the kind it describes.
For websites there is a specific rule. In 2017 the Department of Information and Communications Technology issued a memorandum circular prescribing the Philippine Web Accessibility Policy. It adopts the international standard ISO/IEC 40500:2012, which is the Web Content Accessibility Guidelines (WCAG) version 2.0, as the Philippine standard. It covers national agencies, state universities and colleges, government corporations and local government units, and it gave agencies with existing websites two years to conform.4
The guidelines have moved on since then. The current version, WCAG 2.2, is a recommendation of the World Wide Web Consortium, the body that sets web standards.5 Our approach is to build to the current version. The W3C states that content that conforms to WCAG 2.2 also conforms to WCAG 2.0, the version the circular names.5
Four basics anyone can understand
The guidelines are long, but their core ideas are simple: people must be able to perceive the content, operate the controls and understand what they find.5 A few specific rules do most of the work.
Contrast is the difference in brightness between text and its background. The guidelines ask for a ratio of at least 4.5 to 1 for ordinary text, which rules out pale gray words on a white page.5 Text size is the second rule: a user must be able to enlarge text to 200 percent without losing content or function.5
Keyboard use is the third. Everything that can be done with a mouse must also be possible with a keyboard, and the screen must show clearly which item is selected.5 This serves people who cannot use a mouse and people who use a screen reader, a program that reads the screen aloud.
Target size is the fourth. Anything meant to be tapped should be at least 24 by 24 CSS pixels, a unit meant to look about the same size on any screen. The rule exists so that people with tremors or limited movement, and anyone on a touchscreen, do not hit the wrong control.6
- Contrast: text stands out clearly from its background.
- Text size: enlarging the text does not break the page.
- Keyboard: every action works without a mouse, with a visible marker.
- Target size: buttons and links are large enough to tap accurately.
Why small screens are part of the same problem
We think of accessibility and phone use as one subject. A person reading a phone outdoors has low contrast. A person on a crowded jeepney has one free hand and an unsteady one. A person with an older phone has a small screen and slow responses. The fixes that help a user with a permanent disability help all of them.
This is why our approach is to design the phone layout first and treat the desktop layout as the roomier version of it. If a form can be completed with one thumb on a narrow screen, it will also be comfortable on a monitor. The reverse is rarely true.
How we build it in
Our own website is a working example. Its main buttons are at least 48 pixels tall, twice the minimum, because we expect most visitors to arrive on a phone. Every link and button shows a visible outline when reached by keyboard, and a visitor using a keyboard can skip past the menu straight to the page content.
The site has moving elements, and they stop for visitors whose device is set to reduce motion, a setting that many people who get dizzy or distracted by animation turn on. When a screen is small or zoomed in, the page scrolls. We do not shrink the text to make everything fit.
None of this was added after the design was finished. We set these as rules before building and check them on each change, with the keyboard and at phone width. Our view is that accessibility done at the start costs little, while accessibility added at the end means rebuilding screens that were already paid for.
Checks you can do in ten minutes
You do not need a specialist to see whether a system was built with care. Put the mouse aside and try to complete one task with only the Tab, Enter and arrow keys. Enlarge the text in the browser to 200 percent and see if anything disappears or overlaps. Open the system on the cheapest phone in the office and try to tap each button with a thumb.
Then take the phone outside and read it in daylight. If a vendor's system fails these checks during a demonstration, it will fail them for the public. Offices in the Bangsamoro can ask for conformance with the web accessibility guidelines in writing, and we think they should expect a supplier to show it, not only promise it.
Sources
- Disability. World Health Organization, 2023-03-07.
- Disability Spares No One: A New Perspective. Philippine Statistics Authority, 2019-05-03.
- Republic Act No. 7277, Magna Carta for Disabled Persons. The Lawphil Project, Arellano Law Foundation, 1992-03-24.
- Prescribing the Philippine Web Accessibility Policy and Adopting for this Purpose ISO/IEC 40500:2012 (DICT memorandum circular, 2017), text copy. Department of Information and Communications Technology, copy hosted by the Philippine Web Accessibility Group, 2017-05-12.
- Web Content Accessibility Guidelines (WCAG) 2.2. World Wide Web Consortium (W3C), 2024-12-12.
- Understanding Success Criterion 2.5.8: Target Size (Minimum). World Wide Web Consortium (W3C).