Child components of ActionBar not accessibility friendly.

Open
#3,746 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, typescript
Domain
accessibility, mobile

Research direction

Start by reproducing the Android behavior with Appium and UiAutomatorViewer, focusing on ActionBar children such as ActionItem and NavigationButton. Trace where AutomationText is exposed for these components and verify how the Android accessibility metadata is generated. Done means the child components expose usable AutomationText and are no longer marked NAF for accessibility and UI automation.

Written by the indexing model from the issue text.

Description

action-bar enhancement feature good first issue ux

Please, provide the details below:

Tell us about the problem

While trying to create UI automated tests with Appium we've noticed that the child components of ActionBar, such as ActionItem and NavigationButton don't have a property for AutomationText. When running UiAutomatorViewer, these objects are marked as NAF (Not Accessibility Friendly). This prevents us from allowing any accessibility features for the navigation buttons that we have in our app, as well as not allowing UI automation to be possible for those features. Is it possible to have the AutomationText property added to the child components of ActionBar? If not, what are some other UI automation strategies to handle situations like these?

Which platform(s) does your issue occur on?

Only confirmed for Android.

Please provide the following version numbers that your issue occurs with:
  • CLI: 2.5.0
  • Cross-platform modules: 2.5.1
  • Runtime(s): Android: 2.5.0

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Dominant language
TypeScript
Stars
25.7k
Forks
1.7k
Avg merge
1d 5h
Merged PRs (30d)
35

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NativeScript/NativeScript

All issues in NativeScript/NativeScript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.