bug: ion-menu focuses its full-screen host on open and does not restore focus to ion-menu-button on close; ion-menu-button reads aria-label only once

Aperta
  • Qualcosa non va?
#31,620 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
accessibility, frontend

Direzione di ricerca

The issue identifies ion-menu focus handling and ion-menu-button label updates, but names no Ionic source files or tests. Start by locating those components and their existing accessibility tests, then reproduce the reported open, close, and runtime label changes. Done when focus moves to the visible menu on open, returns to the opener on close, and updated labels are reflected.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

type: bug
Prerequisites
Ionic Framework Version

v8.x

Current Behavior
  1. When an ion-menu is closed with the keyboard (Escape or a close button inside the menu),
    the menu blurs the focused element and does not return focus to the ion-menu-button that
    opened it. The focus lands on <body>; a keyboard or screen reader user has to start over
    from the top of the page. Measured on Android 14 (Chromium WebView) and iOS 26 (WKWebView).
  2. ion-menu-button reads its aria-label once (inheritAttributes on load). When the app
    changes the label at runtime (language switch), the button keeps the old name until the
    next page is rendered, while ion-menu itself picks up a new aria-label immediately.
  3. Without an app-provided label the button and the menu are announced with the English
    defaults ("menu", "Navigation. In menu") regardless of the document language.
  4. When the menu opens, ion-menu moves focus to its own host element (afterAnimation calls
    this.el.focus() with tabindex="0" set in beforeAnimation). The host has
    role="navigation" and covers the whole viewport (left/right/top/bottom: 0, backdrop
    included), so TalkBack draws its focus frame around the entire screen instead of the visible
    menu panel and announces only the landmark name. Measured on Android 14 (Chromium WebView,
    TalkBack): after opening, document.activeElement is the ion-menu host.

Verified with the reproduction on Ionic 8.8.5 (Chrome 154, page "2 ion-menu focus"): after closing the menu
document.activeElement is <body>; after changing the host aria-label to "Open menu" the inner button still
carries "Menü öffnen".

Expected Behavior
  • Closing the menu restores focus to the element that opened it, as ion-modal,
    ion-popover and ion-alert do.
  • aria-label changes on ion-menu-button are reflected.
  • Opening the menu focuses the visible menu panel (.menu-inner) or its first focusable
    element, so the screen reader focus matches what is visible.
Steps to Reproduce
  • Closing the menu restores focus to the element that opened it, as ion-modal,
    ion-popover and ion-alert do.
  • aria-label changes on ion-menu-button are reflected.
  • Opening the menu focuses the visible menu panel (.menu-inner) or its first focusable
    element, so the screen reader focus matches what is visible.
Code Reproduction URL

https://stackblitz.com/github/mrambow/starterApp/tree/a11y-repros (page /repro/menu)
GitHub: https://github.com/mrambow/starterApp/tree/a11y-repros (src/app/repros/menu.page.ts)

Code Reproduction URL

https://github.com/mrambow/starterApp/tree/a11y-repros

Ionic Info

Ionic 8.8.5, Angular 17.3, Capacitor 6 (reproduction); found in Ionic 8.8.5, Angular 21, Capacitor 8

Additional Information

No response

Lingua principale
TypeScript
Stelle
52.7k
Fork
13.3k
Merge medio
2g 21h
PR unite (30g)
65

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ionic-team/ionic-framework

Tutte le issue di ionic-team/ionic-framework

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.