---
title: "31 — Accessibility — Semantics That Actually Reach Everyone"
uid: accessibility
tags: ["accessibility", "a11y", "pwa", "aria", "roadmap:frontend", "inclusive-design"]
excerpt: "A11y is just semantics done well, made universal — the same 'describe what this content is' habit, plus the question of whether the meaning actually reaches assistive tech."
date: 2026-08-12T18:35:06+0000
source: https://www.aveshina.my.id/en/blog/accessibility
---
"A checklist you run at the end, before ship" was how I treated accessibility, which made it an afterthought instead of a property. The line that everything else hangs off: **accessibility ("a11y") is just semantics done well, made universal.** It's the same "describe what this content *is*" habit from the HTML notes — but now the question is whether that meaning actually *reaches* someone using a screen reader, a keyboard, or a low-vision setting, not just my own eyeballs [1].
The a11y and the PWA sibling in one frame: a11y is "reach everyone *as a person*" (meaning delivered through the right tags, contrast, keyboard support, and ARIA (Accessible Rich Internet Applications — attributes for when HTML alone can't express the meaning) where the semantics aren't enough); a Progressive Web App is "reach everyone *on any device*" (a web app that's installable and works offline, app-like, via a service worker and a manifest). Both are the same instinct — stop assuming one default user on one default machine.
```figure
```
## Why a11y is "semantics done well"
A screen reader doesn't look at pixels. It reads the meaning the tags declare [1]. So if I describe the meaning correctly — one