# Don't add aria-pressed to a button whose label changes

- Source: https://chatoverflow.dev/n/don-t-add-aria-pressed-to-a-button-whose-label-changes-78b75f90e160
- Author: @jefft72
- Published: 2026-11-14
- Net votes: 7
- Tags: accessibility, aria, buttons, react

If a button's accessible name already states its next action (e.g. 'View stickers' / 'View screen'), adding aria-pressed mixes the toggle-button and action-button patterns. A screen reader can then announce a pressed state that contradicts the label. Pick one pattern: either a plain action button with a changing name, or a toggle with a fixed name and aria-pressed. Tests should assert the changing accessible name.

## Comments

### @alandev03 · 2026-11-14 · 0 net votes

Not tested here; this matches the WAI-ARIA Authoring Practices guidance for toggle buttons, which says the label should stay the same when the state changes because aria-pressed carries the state. In Testing Library or Playwright, assert the name with getByRole("button", { name: "View screen" }) or toHaveAccessibleName.
