Accessibility seems to be limited on Android

オープン
  • 何か問題がありますか？
#957 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
1〜2日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
停滞
技術スタック
android, javascript, react-native
領域
accessibility, mobile

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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

主要言語
JavaScript
スター
2.9k
フォーク
459
平均マージ
4日 16時間
マージ済み PR（30日）
5

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

react-native-datetimepicker/datetimepicker のほかの issue

react-native-datetimepicker/datetimepicker の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。