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

[Medium] Chrome+JAWS: Status is not announced by Screen Reader #9452

Closed
SumitDiyora opened this issue Jun 14, 2022 · 1 comment
Closed

[Medium] Chrome+JAWS: Status is not announced by Screen Reader #9452

SumitDiyora opened this issue Jun 14, 2022 · 1 comment

Comments

@SumitDiyora
Copy link

SumitDiyora commented Jun 14, 2022

Action Performed:

  1. Open Expensify account on Web.
  2. Select any chat room in your list.
  3. Tap the NEW (green plus) button on the bottom left of the screen.
  4. Open the folder with the desired file on your computer.
  5. Drag a photo from the folder to the chat room.
  6. Notice that opened menu closed and user can drop file to the chat.
  7. Observe the status of file sent is not announced by Screen Reader.

Expected Result:

File sent/uploaded information should be announced by Screen Reader

Actual Result:

File sent/uploaded information is not announced by Screen Reader

Workaround:

Yes

Area issue was found in:

Chat Section

Failed WCAG checkpoints

4.1.3

User impact:

When status messages are not programmatically indicated, users of assistive technology, such as screen readers, may be unaware of the status change.

Suggested resolution:

Assign appropriate roles or properties to status messages so that the new content is spoken by screen readers.
The aria-live property can be used to notify assistive technology when messages are injected into a live region container. Special case live region roles, such as role="alert", role="status", role="progressbar", role="log" etc., can also be used instead of applying live region properties directly. Developers should avoid the use of role="alert" or aria-live="assertive" as it may interrupt the user's text-to-speech.

Refer:
https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA22.html

Platform:

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number:v1.1.76-2
**Reproducible in staging?:Yes
**Reproducible in production?:Yes
**Issue reported by:Sumit

status.of.file.sent.mp4
@melvin-bot
Copy link

melvin-bot bot commented Aug 30, 2022

@SumitDiyora, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant