Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[ui/accessibility] Update web-accessibility.md for Flutter 3.50 WCAG 2.1 AA improvements and fix duplicated sentence

Aperta
  • Qualcosa non va?
#13,963 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à
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
65/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
dart, flutter, markdown
Ambito
accessibility, documentation

Direzione di ricerca

Start with sites/docs/src/content/ui/accessibility/web-accessibility.md and sites/docs/src/content/ui/accessibility/accessibility-testing.md, then verify the Flutter 3.50 behavior against the linked Flutter pull requests. Remove the duplicated sentence, document the listed web accessibility changes, and add the debugShowSemanticsNodes guidance. Done when both pages reflect the requested updates and the documentation checks pass.

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

Descrizione

a.rn.release-notes d.enhancement e1-hours fix.typo from.team p2-medium t.a11y target.web
Page URL
Describe the problem

sites/docs/src/content/ui/accessibility/web-accessibility.md and sites/docs/src/content/ui/accessibility/accessibility-testing.md need a copy fix and updates for the Flutter 3.50 Web accessibility (WCAG 2.1 AA) improvements (cc @parlough @sfshaza2):

  1. Duplicated sentence in web-accessibility.md: web-accessibility.md#L49-L50 repeats "to users. For example, a role can indicate if/whether a widget is a button, a link," on two consecutive lines.
  2. Missing Flutter 3.50 Web accessibility & SemanticsRole improvements: web-accessibility.md#L64-L80 and accessibility-testing.md#L103-L115 can be expanded to cover SemanticsRole.slider, multi-view semantics placeholder scoping, browser zoom support, and debugShowSemanticsNodes.
Detailed page breakdown & affected targets (AI-assisted)
Expected fix
1. sites/docs/src/content/ui/accessibility/web-accessibility.md (https://docs.flutter.dev/ui/accessibility/web-accessibility)
  • Fix duplicated line (L49-L51): Remove line 49 (to users. For example, a role can indicate if a widget is a button, a link,) and keep line 50.
  • Expand ### Using SemanticsRole in Flutter for web (L64-L80) and Web Accessibility behavior:
    • SemanticsRole.slider: Slider and RangeSlider automatically assign SemanticsRole.slider (flutter/flutter#193324, flutter/flutter#192964), exposing an accessible <input type="range"> element in the web semantics DOM.
    • Landmark & menu ARIA roles: Named routes with scopesRoute: true and a non-empty namesRoute label emit role="region" landmarks (flutter/flutter#192965).
    • Focus preservation & keyboard navigation: The web engine now preserves DOM focus across semantic role changes using Element.moveBefore (flutter/flutter#192963), restores focus properly when dialogs/modals close in WidgetsApp.router apps (flutter/flutter#192601), and dismisses visible Tooltips when pressing Escape (flutter/flutter#193192).
    • Browser zoom & multi-view scoping: Note that Flutter Web's <meta flt-viewport> supports browser pinch-to-zoom up to maximum-scale=5.0 (flutter/flutter#182047), prevents unintended iOS Safari auto-zoom on text inputs (flutter/flutter#192328), and scopes the Enable accessibility <flt-semantics-placeholder> button inside each <flutter-view> in embedded/multi-view apps (flutter/flutter#190856).
2. sites/docs/src/content/ui/accessibility/accessibility-testing.md (https://docs.flutter.dev/ui/accessibility/accessibility-testing)
  • Under ## Testing accessibility on the web (L103-L115), mention that developers can also enable semantic node visualization at runtime in flutter_bootstrap.js via debugShowSemanticsNodes: true in _flutter.loader.load({ config: { debugShowSemanticsNodes: true } }) (linking to /platform-integration/web/initialization).
Lingua principale
Dart
Stelle
3.1k
Fork
3.5k
Merge medio
2g 45m
PR unite (30g)
53

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 flutter/website

Tutte le issue di flutter/website

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.