Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #4739 Talkback does not read the expected text #5152

Merged
merged 41 commits into from
Oct 19, 2023

Conversation

Vishwajith-Shettigar
Copy link
Collaborator

@Vishwajith-Shettigar Vishwajith-Shettigar commented Sep 15, 2023

Explanation

Fix #4739, edittext requesting focus only when reader is off will resolve this issue.

Essential Checklist

  • The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
  • Any changes to scripts/assets files have their rationale included in the PR explanation.
  • The PR follows the style guide.
  • The PR does not contain any unnecessary code changes from Android Studio (reference).
  • The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
  • The PR is assigned to the appropriate reviewers (reference).

For UI-specific PRs only

Before fix

before.mp4

After fix

Talkback On

on.mp4

Talkback Off

off.mp4

If your PR includes UI-related changes, then:

  • Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes
  • For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see RTL guide)
  • Add a video showing the full UX flow with a screen reader enabled (see accessibility guide)
  • Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing

@Vishwajith-Shettigar
Copy link
Collaborator Author

@adhiamboperes PTAL

Copy link
Collaborator

@adhiamboperes adhiamboperes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Vishwajith-Shettigar. Please add a talkback screen recording to your PR description. You also need to add tests as mentioned in the issue discussion.

@oppiabot
Copy link

oppiabot bot commented Sep 15, 2023

Unassigning @adhiamboperes since the review is done.

@oppiabot
Copy link

oppiabot bot commented Sep 15, 2023

Hi @Vishwajith-Shettigar, it looks like some changes were requested on this pull request by @adhiamboperes. PTAL. Thanks!

@Vishwajith-Shettigar
Copy link
Collaborator Author

Thanks @Vishwajith-Shettigar. Please add a talkback screen recording to your PR description. You also need to add tests as mentioned in the issue discussion.

@adhiamboperes,PTAL I have attached screen recordings. Thank you

@oppiabot
Copy link

oppiabot bot commented Sep 16, 2023

Unassigning @Vishwajith-Shettigar since a re-review was requested. @Vishwajith-Shettigar, please make sure you have addressed all review comments. Thanks!

Copy link
Collaborator

@adhiamboperes adhiamboperes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Vishwajith-Shettigar.

So the "after" video you added does not fully illustrate that the problem has been solved. Instead of interrupting talkback, could you please let it read out the full text? I expect all the text on the screen to be read until the edittext. If you find that the textviews are not being read then it means that they have no content description, and you shoukd add some.

@Vishwajith-Shettigar
Copy link
Collaborator Author

Thanks @Vishwajith-Shettigar.

So the "after" video you added does not fully illustrate that the problem has been solved. Instead of interrupting talkback, could you please let it read out the full text? I expect all the text on the screen to be read until the edittext. If you find that the textviews are not being read then it means that they have no content description, and you shoukd add some.

I thought textviews text should be read only when user click on them . So you are saying when we enter activity, talk back should read all the text in the textviews automatically until edit text, am i right ? please let me know if there is any issue with what i'm actually thinking.

@adhiamboperes
Copy link
Collaborator

Thanks @Vishwajith-Shettigar.
So the "after" video you added does not fully illustrate that the problem has been solved. Instead of interrupting talkback, could you please let it read out the full text? I expect all the text on the screen to be read until the edittext. If you find that the textviews are not being read then it means that they have no content description, and you shoukd add some.

I thought textviews text should be read only when user click on them . So you are saying when we enter activity, talk back should read all the text in the textviews automatically until edit text, am i right ? please let me know if there is any issue with what i'm actually thinking.

Technically yes, the swipe gestures that gets them in focus. In your video demo, I did not see that.

@Vishwajith-Shettigar
Copy link
Collaborator Author

Thanks @Vishwajith-Shettigar.
So the "after" video you added does not fully illustrate that the problem has been solved. Instead of interrupting talkback, could you please let it read out the full text? I expect all the text on the screen to be read until the edittext. If you find that the textviews are not being read then it means that they have no content description, and you shoukd add some.

I thought textviews text should be read only when user click on them . So you are saying when we enter activity, talk back should read all the text in the textviews automatically until edit text, am i right ? please let me know if there is any issue with what i'm actually thinking.

Technically yes, the swipe gestures that gets them in focus. In your video demo, I did not see that.

Okay i got it, basically talk back should read toolbar close button first automatically without user interaction, and when user click or use gesture on textview then only textview should be read.

Copy link
Collaborator

@adhiamboperes adhiamboperes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once you have make the suggested change, please add a test for the edittext being focussed/unfocussed when screen reader is on/off. See TopicFragmentTest in this PR for reference:

Copy link
Collaborator

@adhiamboperes adhiamboperes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Vishwajith-Shettigar, just some minor corrections. See in-line.

@Vishwajith-Shettigar
Copy link
Collaborator Author

@adhiamboperes, PTAL.
Thank you.

@oppiabot
Copy link

oppiabot bot commented Oct 19, 2023

Unassigning @Vishwajith-Shettigar since a re-review was requested. @Vishwajith-Shettigar, please make sure you have addressed all review comments. Thanks!

Copy link
Collaborator

@adhiamboperes adhiamboperes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @Vishwajith-Shettigar!

@oppiabot
Copy link

oppiabot bot commented Oct 19, 2023

Unassigning @adhiamboperes since they have already approved the PR.

@oppiabot oppiabot bot added the PR: LGTM label Oct 19, 2023
@oppiabot
Copy link

oppiabot bot commented Oct 19, 2023

Hi @Vishwajith-Shettigar, this PR is ready to be merged. Please address any remaining comments prior to merging, and feel free to ask someone to merge your PR once the CI checks pass and you're happy with it. Thanks!

@adhiamboperes adhiamboperes enabled auto-merge (squash) October 19, 2023 11:07
@adhiamboperes adhiamboperes merged commit 4fb9b58 into oppia:develop Oct 19, 2023
36 checks passed
Rd4dev pushed a commit to Rd4dev/oppia-android that referenced this pull request Oct 31, 2023
<!-- READ ME FIRST: Please fill in the explanation section below and
check off every point from the Essential Checklist! -->
## Explanation
Fix oppia#4739, edittext requesting focus only when reader is off will
resolve this issue.
<!--
- Explain what your PR does. If this PR fixes an existing bug, please
include
- "Fixes #bugnum:" in the explanation so that GitHub can auto-close the
issue
  - when this PR is merged.
  -->

## Essential Checklist
<!-- Please tick the relevant boxes by putting an "x" in them. -->
- [x] The PR title and explanation each start with "Fix #bugnum: " (If
this PR fixes part of an issue, prefix the title with "Fix part of
#bugnum: ...".)
- [x] Any changes to
[scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets)
files have their rationale included in the PR explanation.
- [x] The PR follows the [style
guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide).
- [x] The PR does not contain any unnecessary code changes from Android
Studio
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)).
- [x] The PR is made from a branch that's **not** called "develop" and
is up-to-date with "develop".
- [x] The PR is **assigned** to the appropriate reviewers
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)).

## For UI-specific PRs only
Before fix


https://github.com/oppia/oppia-android/assets/76042077/41bc96b4-3fe1-4688-a77b-02bfdbd22782


After fix

  Talkback On


https://github.com/oppia/oppia-android/assets/76042077/a01da3dc-8848-4632-a8c0-17ce3e409beb


Talkback Off



https://github.com/oppia/oppia-android/assets/76042077/beac309e-16d8-496f-bc09-af8de634536b





 

<!-- Delete these section if this PR does not include UI-related
changes. -->
If your PR includes UI-related changes, then:
- Add screenshots for portrait/landscape for both a tablet & phone of
the before & after UI changes
- For the screenshots above, include both English and pseudo-localized
(RTL) screenshots (see [RTL
guide](https://github.com/oppia/oppia-android/wiki/RTL-Guidelines))
- Add a video showing the full UX flow with a screen reader enabled (see
[accessibility
guide](https://github.com/oppia/oppia-android/wiki/Accessibility-A11y-Guide))
- Add a screenshot demonstrating that you ran affected Espresso tests
locally & that they're passing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Talkback does not read the expected text
2 participants