---
title: "aria-expanded does not require a fallback"
url: https://daily.dev/posts/aria-expanded-does-not-require-a-fallback-eybkqzofx
source_url: https://hidde.blog/aria-expanded-does-not-require-a-fallback
type: article
source: "Hidde de Vries — hidde.blog"
published: 2026-05-31T07:49:02.582Z
updated: 2026-05-31T09:36:03.474Z
tags: ["webdev", "html", "accessibility"]
reading_time: 3
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# aria-expanded does not require a fallback

**[Hidde de Vries — hidde.blog](https://daily.dev/sources/hiddedevries)** · 3 min read · 0 upvotes · 0 comments

## Summary

Using aria-expanded without a fallback is the recommended approach for accessible toggle controls. Adding visually hidden text as a fallback introduces maintenance burden, inconsistent non-standard strings, no automatic localization, and redundant announcements for most screen reader users. Since aria-expanded is well supported across major assistive technologies (JAWS, NVDA, VoiceOver, Narrator), a fallback solves a problem for very few users while creating issues for the majority.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://hidde.blog/aria-expanded-does-not-require-a-fallback>

## Similar posts on daily.dev

- [Use cases for aria-expanded](https://daily.dev/posts/use-cases-for-aria-expanded-tgq9kcgth) · Piccalilli · 9 upvotes · 0 comments

---

Tags: [#webdev](https://daily.dev/tags/webdev), [#html](https://daily.dev/tags/html), [#accessibility](https://daily.dev/tags/accessibility)

[View this post on daily.dev](https://daily.dev/posts/aria-expanded-does-not-require-a-fallback-eybkqzofx)