---
title: "Discussion on \"Accessible Web Apps: A Div Is Not a Button\" | Hashnode"
description: "Discussion on \"Accessible Web Apps: A Div Is Not a Button\". Stop rebuilding browser functionality and use native controls"
url: "https://hashnode.com/posts/a-div-is-not-a-button/6a1e43d281824da877de3c6b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Accessible Web Apps: A Div Is Not a Button](https://peralov.hashnode.dev/a-div-is-not-a-button?utm_source=hashnode&utm_medium=feed)

Stop rebuilding browser functionality and use native controls

Jun 2 · 6 min read · peralov.hashnode.dev  
Read the article

-   [#button](https://hashnode.com/tag/button)
-   [#html5](https://hashnode.com/tag/html5)
-   [#wcag](https://hashnode.com/tag/wcag)
-   [#accessibility](https://hashnode.com/tag/accessibility)
-   [#angular-2](https://hashnode.com/tag/angular-2)
-   [#web-app-development](https://hashnode.com/tag/web-app-development)
-   [#typescript](https://hashnode.com/tag/typescript)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#vuejs](https://hashnode.com/tag/vuejs)

## Written by

[Filip Peralov](https://hashnode.com/@peralov)

@peralov · Skopje

  
[View profile](https://hashnode.com/@peralov)

Senior Frontend Engineer | Design Systems, Accessibility & Scalable Web Apps

I unpack complex frontend architecture, actionable web accessibility (a11y), HTML5 optimizations, and how to scale enterprise-grade UIs without inheriting massive technical debt.

## Responses 1

Markdown supported · ⌘↵ to post

[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.
