This is such an important reminder. It’s easy to treat semantics as optional when everything “works,” but the long-term cost (especially for accessibility) adds up quickly.
What’s interesting is how this extends beyond code quality into how we discover and use web apps too. A lot of tools are technically accessible, but still hard to find or revisit in a meaningful way.
Feels like there’s a broader gap between building things correctly and making them truly usable in practice. Some platforms are starting to explore that layer (like https://unstore.io), but it still feels early.
Really appreciated how clearly you broke this down.
Sara
This is such an important reminder. It’s easy to treat semantics as optional when everything “works,” but the long-term cost (especially for accessibility) adds up quickly. What’s interesting is how this extends beyond code quality into how we discover and use web apps too. A lot of tools are technically accessible, but still hard to find or revisit in a meaningful way. Feels like there’s a broader gap between building things correctly and making them truly usable in practice. Some platforms are starting to explore that layer (like https://unstore.io), but it still feels early. Really appreciated how clearly you broke this down.