Why This Is Suddenly on SME Radars
For years, web accessibility was a government-sector concern — something GovTech mandated for public agency websites under the Web Content Accessibility Guidelines (WCAG). Most SMEs reasonably assumed it didn’t apply to them. Three things have shifted that: enterprise clients now routinely require accessibility compliance from vendors and suppliers as part of procurement, tender documents for government-linked contracts increasingly cascade WCAG requirements down the supply chain, and Singapore’s ageing population means a growing share of customers genuinely need larger text, working keyboard navigation, and screen-reader-compatible pages to use a website at all.
None of this means an SME site needs a compliance certificate. It does mean accessibility has quietly moved from “nice to have” to “will get asked about” for a meaningful number of businesses, especially those selling B2B or bidding on institutional contracts.
What WCAG 2.1 AA Actually Asks For
The standard sounds intimidating but breaks down into concrete, buildable requirements:
- Every image needs meaningful alt text — not “image123.jpg”, but a description that conveys what a sighted user would understand.
- Text must have sufficient colour contrast against its background (a pale grey font on white, common in “minimalist” templates, usually fails outright).
- Every interactive element — buttons, forms, menus — must be operable using a keyboard alone, not just a mouse or touchscreen.
- Forms need properly associated labels so screen readers can announce what each field is for.
- Video content needs captions or a transcript.
None of these are exotic engineering problems. Most are copywriting and CSS fixes, not rebuilds.
The Audit That Takes an Afternoon
Before commissioning anything, run a free automated check: WAVE (wave.webaim.org) and Google Lighthouse’s accessibility tab (built into Chrome DevTools) will both flag the majority of common issues — missing alt text, contrast failures, unlabelled form fields — in minutes, for free. These tools won’t catch everything (they can’t judge whether alt text is actually meaningful, or test real screen-reader flow), but they’ll surface 70-80% of typical issues and give you a prioritised list to work through.
What Actually Needs Fixing First
Not every WCAG criterion carries equal weight for a typical SME site. We’d prioritise in this order:
- Contrast and font size issues — highest impact, lowest effort, affects the most visitors including simply older users on mobile in bright sunlight.
- Keyboard navigation through your main conversion path (menu, product or service pages, contact form, checkout) — test it yourself by unplugging your mouse for ten minutes.
- Alt text on product images and key visuals, written properly rather than auto-generated.
- Form labels and error messages that are announced clearly, not just shown in red text.
Where This Fits With PDPA and Procurement
Accessibility isn’t a PDPA requirement, but the two increasingly appear in the same vendor due-diligence checklists, alongside data security questions. If you’re pursuing government-linked tenders, enterprise clients, or education-sector contracts, expect an accessibility question in the RFP at some point in the next few years, if it hasn’t appeared already. Getting the fundamentals right now, while it’s still a competitive advantage rather than table stakes, costs far less than retrofitting a site under deadline pressure once a client makes it a contractual requirement.