Website Accessibility in Singapore: WCAG 2.2 for Business Sites
Short answer: Singapore has no law that requires a private business website to meet an accessibility standard. Government digital services must meet WCAG Level AA under GovTech's Digital Service Standards, and the Enabling Masterplan 2030 targets every high-traffic government site conforming by 2030. For a business site the practical standard is WCAG 2.2 AA, GovTech's free Oobee scanner finds most failures, and fixing a typical 10-page site takes 1 to 3 days.
Sources are MDDI, GovTech, MSF, the W3C, WebAIM and Google, checked 18 October 2026.
What does Singapore require and what does it recommend?
Facts, with dates.
- Government services: required. GovTech's Digital Service Standards, last updated 26 March 2026, incorporate WCAG Levels A and AA and apply to agencies and the industry partners that build their services. MDDI's parliamentary reply of 12 November 2024 names the target: all high-traffic government websites conforming to WCAG 2.1 AA by 2030.
- The Enabling Masterplan 2030. MSF's EMP2030, the 2022 to 2030 plan, sets the goal of all high-traffic government websites being fully accessible by 2030, up from 61% at the time. It has 29 recommendations; none places a legal duty on private websites.
- Private sector: recommended, not mandated. MDDI's reply of 5 December 2024 describes engagement with private firms, a May 2024 Co-Creation Lab with over 90 participants, and the release of Oobee, GovTech's open-source accessibility tester, free for any organisation.
- The PDPA and the Building Control Regulations govern data and buildings, not web content.
What this means for a business: no fine and no complaint mechanism specific to websites. The reasons to meet the standard are practical. Customers over 50, customers with low vision or limited dexterity and screen reader users are part of every Singapore market. Government tenders and large clients ask for WCAG conformance. Most fixes also improve mobile use and search indexing.
What does WCAG 2.2 AA mean in plain terms?
WCAG 2.2 was published by the W3C as a Recommendation on 5 October 2023 and updated 12 December 2024. Level AA is the level governments and procurement specify. The W3C summary of what is new lists 9 added criteria and one removed, 4.1.1 Parsing.
The criteria group under four principles. For a business site they reduce to:
- Perceivable. Every image has a text alternative. Text has a contrast ratio of at least 4.5:1, or 3:1 for text of 18 point or 14 point bold. Content works at 200% zoom and on a 320 pixel wide screen. Video has captions.
- Operable. Everything works with a keyboard alone. Focus is visible and not hidden behind a sticky header (new in 2.2). Buttons and links are at least 24 by 24 CSS pixels or spaced apart (new in 2.2). Anything done by dragging can also be done by tapping (new in 2.2). Nothing flashes more than three times a second.
- Understandable. The page language is declared. Form fields have visible labels, errors name the field and the fix, and information already entered is not asked for again (new in 2.2). Help, such as the contact link, sits in the same place on every page (new in 2.2). Logins do not depend on memory or puzzles (new in 2.2).
- Compatible with assistive technology. Custom controls expose their name, role and state so a screen reader can announce them.
12 checks on a business site
Run these on the homepage, one service page and the contact page. Automated tools catch about half; the rest need a person.
| # | Check | How | Tool |
|---|---|---|---|
| 1 | Text contrast at least 4.5:1 | Scan | Oobee, Lighthouse |
| 2 | Every informative image has alt text; decorative images have empty alt | Scan, then read | Oobee |
| 3 | Every form field has a visible label tied to the input | Scan | Oobee, Lighthouse |
| 4 | No empty links or buttons: icon-only controls without a name | Scan | Oobee |
| 5 | Page language set on the HTML element | Scan | Lighthouse |
| 6 | Headings in order: one H1, then H2, then H3 | Scan | Lighthouse |
| 7 | Tab through the page: every control reachable, in visual order, focus visible | Keyboard | Person |
| 8 | Focus never hidden under a sticky header or cookie bar | Keyboard | Person |
| 9 | Tap targets at least 24 by 24 pixels, including the WhatsApp button and menu | Measure | Person |
| 10 | Page usable at 200% zoom and 320 pixels wide, no horizontal scroll | Resize | Person |
| 11 | Form errors name the field and say how to fix it | Submit empty | Person |
| 12 | Captions on any video; no autoplay with sound | Watch | Person |
The first six match the failures WebAIM finds most. Its 2026 WebAIM Million analysis of 1,000,000 home pages, February 2026, found detectable WCAG 2 failures on 95.9% of pages, an average of 56.1 errors per page, and six issue types making up 96% of errors: low contrast text (83.9% of pages), missing alt text (53.1%), missing form labels (51%), empty links (46.3%), empty buttons (30.6%) and missing document language (13.5%).
Tools, all free:
- Oobee, GovTech's scanner, MIT licensed, built on axe-core, reports Must Fix and Good to Fix findings against WCAG 2.2.
- Lighthouse in Chrome, whose accessibility score is a weighted average of axe-core audits. Its own documentation lists what it cannot test: keyboard order, focus traps, custom controls, visual meaning.
- A keyboard and a phone, for checks 7 to 12.
A Lighthouse score of 100 means the automated checks passed, not that the site is accessible. Checks 7 to 12 are the ones that stop a real visitor. The wider audit method is in website audit checklist.
What does it cost to fix a typical 10-page site?
Estimates, for a site on a modern stack where the developer can edit the templates.
| Work | Typical scope | Time (estimate) |
|---|---|---|
| Contrast and colour tokens | Change 2 to 4 colours in the stylesheet | 1 to 2 hours |
| Alt text | 30 to 80 images | 2 to 4 hours |
| Form labels and error messages | 1 to 3 forms | 2 to 4 hours |
| Keyboard focus, skip link, focus styles | Site template | 2 to 4 hours |
| Heading order, page language, button names | Site template and 10 pages | 2 to 4 hours |
| Target size and sticky header fixes | Site template | 1 to 2 hours |
| Re-scan and manual checks | 3 pages | 2 hours |
Total: 1 to 3 working days where templates are editable. On a builder or a theme with locked components, some items cannot be fixed, and the cost becomes the rebuild. A rebuild on Next.js from a fixed-price studio starts at S$2,000; accessibility is then a build requirement rather than a retrofit, because colours, forms and focus styles are set once in the template and inherited by every page. The hosting and security side of that stack is described at website infrastructure.
Accessibility checklist
- Colours pass 4.5:1 for body text and 3:1 for large text and interface borders.
- Alt text on every informative image; empty alt on decorative ones.
- Visible labels on every field; errors name the field and the fix; no repeated entry.
- One H1 per page, headings in order, page language declared.
- Keyboard: skip link, visible focus, logical order, nothing hidden under sticky elements.
- Targets 24 by 24 pixels or spaced.
- No drag-only interactions; no login puzzles.
- Captions on video; no autoplay with sound; nothing flashing.
- Help and contact in the same place on every page.
- Scanned with Oobee and Lighthouse, then checked by a person on a keyboard and a phone.
- Re-checked after every design change.
What cense does
cense builds sites in Next.js, hosted on Vercel or Google Cloud with HTTPS, security headers and no plugins, and the client owns the domain, code, hosting and data. Website from S$2,000, first draft 14 days after one call. See website infrastructure.
Is website accessibility required by law in Singapore?+
Not for private business websites. Government digital services must meet WCAG Level AA under GovTech's Digital Service Standards, and MDDI's 12 November 2024 reply targets all high-traffic government sites at WCAG 2.1 AA by 2030. MDDI's 5 December 2024 reply describes private-sector engagement, not a mandate.
What is WCAG 2.2 AA?+
The W3C's Web Content Accessibility Guidelines version 2.2, published 5 October 2023, at the middle of three conformance levels. It adds 9 criteria to 2.1, including 24 by 24 pixel tap targets, visible focus not hidden by sticky headers and no login puzzles, and removes 4.1.1 Parsing.
What are the most common accessibility failures?+
WebAIM's February 2026 scan of 1,000,000 home pages found failures on 95.9%, averaging 56.1 per page. Low contrast text was on 83.9% of pages, missing alt text 53.1%, missing form labels 51%, empty links 46.3%, empty buttons 30.6% and missing page language 13.5%.
Is there a free accessibility checker?+
Yes. Oobee is GovTech's open-source scanner, MIT licensed, built on axe-core, reporting against WCAG 2.2. Lighthouse in Chrome uses the same engine. Neither can test keyboard order, focus traps or custom controls; a person does those.
How much does it cost to make a 10-page site accessible?+
On a site with editable templates, 1 to 3 working days, estimate: colours, alt text, form labels, focus styles, heading order and target sizes. On a locked builder theme some items cannot be fixed, and the cost becomes a rebuild from S$2,000.



