Accessibility Is a Design Skill You Already Have

Accessibility scores went backwards in 2026. WebAIM’s annual crawl of one million homepages found errors on 95.9% of them — up from the year before, snapping a six-year streak of slow improvement. The average page now carries 56 detectable barriers.

The uncomfortable part is not the number. It’s the list of failures causing it.

The Six Failures That Haven’t Changed in Seven Years

According to WebAIM’s 2026 report, the most common accessibility errors are: low colour contrast, missing form labels, empty links and buttons, missing image alt text, absent document language declarations, and missing input labels. Read that list slowly. There is nothing on it that requires specialist knowledge. Contrast is a visual design decision. Labels are copywriting. Alt text is content strategy. Document language is a single HTML attribute.

As Hope Turner argues in UX Design, the framing of accessibility as a compliance specialism — something handed off to a separate team — is precisely what keeps these same six failures appearing year after year. Designers already make contrast decisions every day. They already write button copy. The skill gap is not technical. It is attentional: teams are not applying what they know to every element, every time.

For Southeast Asian markets, the stakes are compounded. Screen reader usage is growing across the region’s aging demographics, and government accessibility mandates in Singapore, Thailand, and Malaysia are tightening. Failing here is not just an ethical miss — it is a regulatory and commercial exposure.

Accessibility as Conversion Infrastructure

Here is where I find it useful to reframe the conversation for stakeholders who budget by outcome, not principle. The six failure types are not just accessibility problems. They are conversion problems wearing a different label.

Low colour contrast on a CTA button does not just disadvantage users with low vision — it reduces click-through for everyone scanning a screen in bright sunlight on a mobile commute, which describes most of your audience in Bangkok, Jakarta, or Ho Chi Minh City. Missing form labels do not just disorient screen reader users — they increase form abandonment. Empty link text confuses Google’s crawler as much as it confuses assistive technology.

Shopee’s mobile UI is instructive here. Their product cards use high-contrast price typography and explicit, redundant labelling on interactive elements — not because their design team is particularly accessibility-conscious, but because their conversion data told them that ambiguity kills tap rates. Accessible design and high-converting design are solving the same underlying problem: reducing cognitive load and friction for users who are not giving you their full attention.

Implementation implication: audit your five highest-traffic pages using WebAIM’s WAVE tool or Axe DevTools. Prioritise contrast and label fixes first — they are highest-frequency failures with the lowest engineering effort required.

---

The Ownership Problem Behind the Execution Gap

If the fixes are this knowable, why do the numbers move in the wrong direction? NNG’s Evan Sunwall offers a useful diagnostic through the lens of psychological ownership. Teams tend to develop strong ownership over outputs they can directly control — visual aesthetics, brand expression, animation polish — and weak ownership over systemic properties like accessibility compliance, which feel shared, diffuse, or someone else’s responsibility.

Misplaced ownership is particularly acute in agencies and in-house teams operating under sprint pressure. A designer who owns a component’s visual identity but not its functional completeness will make very different tradeoff decisions under deadline. The result is polished interfaces that fail at the structural level — precisely the pattern WebAIM’s data describes.

The organisational fix is not a new process. It is a tighter ownership contract. Accessibility criteria — contrast ratios, label requirements, alt text — belong inside the definition of done for every component, not appended as a QA pass at the end. Design systems are the most scalable enforcement mechanism here: bake compliant defaults into your component library and the right behaviour becomes the path of least resistance. Teams at Grab have operationalised this at scale, embedding WCAG 2.2 AA standards into their design token system so compliant colour pairs are the only options surfaced to designers by default.

Scaling Fixes Across Multi-Language, Multi-Platform Contexts

For brands operating across Southeast Asia’s linguistic diversity, accessibility has an additional dimension that rarely appears in Western design discourse: multi-language interface integrity. A Thai or Bahasa Indonesia label that is visually present but not properly tagged in the HTML document language will fail screen readers regardless of how well it is translated. This is a failure mode that compounds — accessibility debt plus localisation debt in a single element.

Practical guidance: when building or auditing a design system for multilingual deployment, treat lang attribute tagging as a localisation requirement, not an afterthought. Establish a component-level QA checklist that links language declaration to translation handoff, so the two tasks are completed together. On mobile — where over 70% of Southeast Asian e-commerce traffic originates — also pressure-test touch target sizes against WCAG’s 24×24px minimum, since many localised components inherit desktop sizing assumptions that fail at smaller viewport scales.

Timeline reality: a focused accessibility audit and remediation sprint for a mid-sized marketing site typically runs four to six weeks of combined design and front-end effort. The business case writes itself when framed as conversion infrastructure rather than compliance overhead.

---

Key Takeaways

• Run WebAIM WAVE or Axe DevTools on your five highest-traffic pages this week — contrast and label failures are fixable in days, not sprints.
• Embed WCAG AA contrast ratios and label requirements as non-negotiable defaults in your design system’s component library, so compliance is the path of least resistance.
• In multilingual Southeast Asian deployments, link HTML lang attribute tagging to translation handoff as a single quality gate — do not treat them as separate workstreams.

The uncomfortable question sitting underneath all of this: if the six most common accessibility failures have not changed in seven years of measurement, what does that tell us about how the industry actually prioritises design quality versus design aesthetics? And if those two things are drifting apart in your organisation, what is it costing you in conversions you cannot see?

---

At grzzly, we help marketing teams across Southeast Asia build design systems and UX frameworks that treat accessibility and conversion as the same problem — because they are. If your team is carrying accessibility debt that you suspect is quietly bleeding performance, we would enjoy the conversation. Let’s talk