---
title: "Comment by Sara on \"Accessible Web Apps: A Div Is Not a Button\" | Hashnode"
description: "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"
url: "https://hashnode.com/posts/a-div-is-not-a-button/6a1e43d281824da877de3c6b/comment/6a1f0e798a27b35074b42449"
---

[Discussion](https://hashnode.com/posts/a-div-is-not-a-button/6a1e43d281824da877de3c6b)

Comment [Accessible Web Apps: A Div Is Not a Button](https://hashnode.com/posts/a-div-is-not-a-button/6a1e43d281824da877de3c6b)

[Sara](https://hashnode.com/@sar-a-a-a-a)

[Jun 2](https://hashnode.com/posts/a-div-is-not-a-button/6a1e43d281824da877de3c6b/comment/6a1f0e798a27b35074b42449)

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](https://unstore.io/)), but it still feels early. Really appreciated how clearly you broke this down.
