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

Offen
  • Stimmt etwas nicht?
#31,620 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
accessibility, frontend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
TypeScript
Sterne
52.7k
Forks
13.3k
Ø Merge
2 T. 21 Std.
Gemergte PRs (30 T.)
65

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ionic-team/ionic-framework

Alle Issues in ionic-team/ionic-framework

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.