Accessibility seems to be limited on Android

Aperta
  • Qualcosa non va?
#957 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
android, javascript, react-native
Ambito
accessibility, mobile

Direzione di ricerca

Start by tracing the Android imperative API's open function and how it passes accessibility props to the native modal; the report does not name source files or tests. Reproduce with the linked sample on Android with TalkBack enabled, then check whether the supplied aria-label is announced when the modal opens. The issue has had no comment for 358 days, so check the thread for prior findings before starting.

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

Descrizione

Bug report

Summary

Hello 👋 I was looking for a way to trigger talkback on Android when the modal opens. The accessibility parameters of the open function of the Android imperative API doesn't seem to work properly. Passing, aria-modal or aria-label doesn't seem to change anything when activating talkback on an Android device. I'm kinda new to accessibility on mobile apps but I think it should say the label out loud for example. Maybe I am doing something wrong or misunderstanding something ? I looked at the code of the imperative API and it doesn't seem to take the accessibility parameters into account.

Reproducible sample code

Steps to reproduce

  1. Clone this repo
  2. Install dependencies with Bun
  3. Run expo start and run on an Android emulator / device
  4. Make sure to activate talkback in accessibility settings of the device

Describe what you expected to happen:

  1. Talkback saying what I assigned to the aria-label prop

Environment info

Expo SDK 52.
npx react-native info output:

System:
  OS: macOS 15.2
  CPU: (8) arm64 Apple M1
  Memory: 115.47 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 23.6.0
    path: ~/.nvm/versions/node/v23.6.0/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.9.2
    path: ~/.nvm/versions/node/v23.6.0/bin/npm
  Watchman:
    version: 2024.12.02.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.0
      - iOS 18.0
      - macOS 15.0
      - tvOS 18.0
      - visionOS 2.0
      - watchOS 11.0
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23726.103.2422.12816248
  Xcode:
    version: 16.0/16A242d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.14
    path: /usr/bin/javac
  Ruby:
    version: 2.7.8
    path: /opt/homebrew/opt/[email protected]/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.3
    wanted: latest
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.7
    wanted: 0.76.7
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

datetimepicker version: 8.2.0

Android version : 12

Lingua principale
JavaScript
Stelle
2.9k
Fork
459
Merge medio
4g 16h
PR unite (30g)
5

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 react-native-datetimepicker/datetimepicker

Tutte le issue di react-native-datetimepicker/datetimepicker

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.