Accessibility Law

For years, the fact that a disabled user could not use a product was not filed as the builder's problem. It was treated as an unfortunate situation, something to handle once there was room in the schedule. When a screen reader — software that speaks the contents of a screen aloud — failed to announce what a button did, nothing was logged as broken, so nobody was assigned to fix it.

Prioritization meetings kept landing in the same place. Someone would ask when the accessibility work was happening, the answer was next quarter if there's room, and next quarter something more urgent took the slot.

Accessibility law exists to reorder that list from outside the team. It treats a product built so that some people cannot use it as discrimination, and attaches a cost to leaving it that way. Once a nice-to-have becomes something that hurts when skipped, the work moves out of the goodwill column and into the list of things checked before release. Accessibility is a question of how you design a screen; accessibility law is what pins down by when and to what standard.

The reach also differs from its neighbors. The E-commerce Act and consumer protection rules attach to a transaction, so they bite around checkout. Accessibility law covers every screen a user can reach, including a marketing page that sells nothing.

No regulator inspects your screens directly. Three layers stack up: a law creates the duty, technical guidelines turn that duty into items someone can judge, and contracts or disputes apply pressure.

1. The law states only what must happen. In Korea that role belongs to the Act on the Prohibition of Discrimination Against Persons with Disabilities, in force since 2008, which requires providers of information and communication services to offer reasonable accommodation. The covered set started with public institutions and large companies and widened in stages. The United States and the European Union have their own statutes filling the same slot.
2. Guidelines restate the duty in the language of a screen. No statute says "give your buttons names," so the judging is done against the Web Content Accessibility Guidelines (WCAG), written by the web standards body, where every item carries an A, AA, or AAA grade. Law and contracts almost always ask for the middle grade, AA. Korea maintains a localized edition, and the state-run web accessibility certification audits against it.
3. Enforcement arrives by three routes: a complaint to the national human rights body that ends in a correction recommendation, a discrimination claim argued in court, or a clause written into a contract that stops you at a vendor review. The third route is the one most teams meet first, because a buyer checks before a regulator does.

A button drawn as an icon alone reads out as just "button" to a screen reader and fails; give it a name so it reads "share button" and it passes. An image with empty alt text fails, and one labeled "third-quarter revenue chart" passes. Not being able to reach the payment button using the keyboard alone, without a mouse, fails as well.

In practice this law usually turns up inside a contract. Being asked about it by a customer is far more common than receiving an order from a regulator.

Selling to public institutions, or B2G, makes it most visible. Tender notices routinely list the web accessibility certification as an eligibility requirement, and without the certificate there is no chance to submit a proposal at all. The audit runs for weeks, so a team that starts preparing when the notice appears has already missed it.

Large enterprise customers bring the same items. Their vendor review packet carries roughly ten accessibility questions sitting next to the security ones. These buyers usually want the current state item by item rather than a certificate, so writing down the lines that fail today with a date attached passes more often than claiming everything is clean. A reviewer who finds one false claim stops trusting the rest of the sheet, and the deal slows down while someone verifies it line by line.

The decision to open a new market drags it along too. An online service sold into the European Union has to meet accessibility requirements, and in the United States thousands of website discrimination suits are filed every year. A condition that never applied while you sold at home arrives the day you widen the map.

"This public tender lists the accessibility certification as an eligibility requirement. No certificate, no proposal."

The law has landed as a condition of the contract, so this is now a question about bidding rather than about the product.

"This isn't a courtesy thing. It falls under the disability discrimination act."

Ending a priority argument by moving it onto the question of legal coverage.

"Happy to open Europe, but let me check the accessibility requirements before we set a date."

Putting the regulatory check ahead of the expansion decision.

At Pagedeck the subject first came up seriously the day Sofia walked in with a public tender notice. The eligibility box asked for the certification, nobody had ever applied for it, and that year's tender had to be skipped. Grace decided to give up the deal and get certified before the end of the next quarter.

Theo started by writing down the current state item by item. Of the two dozen or so lines, seventeen already passed, and the failures clustered in the document editor and the file upload screen. Mia put fixing those two screens on the quarterly plan as a line item so it competed for order against every other feature.

The most common mistake is reading this as a rule that applies only to public institutions. Certification and tenders come up together so often that private services assume they are out of scope. But the covered set has widened in stages, most companies running a service now fall inside it, and the duty stands whether or not anyone applies for a certificate. Certification confirms the duty; it does not define who has one. Push it aside and the first enterprise vendor review hands you months of work in a single afternoon.

The other mistake is reading the legal bar as perfect accessibility. What gets asked for is usually AA, written as checkable values like a color contrast ratio of 4.5 to 1. Nor does all of it have to be true today: the document that passes a review is not the one claiming every line is met, but the one that names the failing lines and says when each will be fixed. Aim at perfect and you arrive at the review with nothing started.