Skip to content

[$20][MSFT-131] [Challenge Page] Prizes section is not readout by the screen reader #2828

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

Closed
veshu opened this issue Jul 17, 2019 · 51 comments
Closed

Comments

@veshu
Copy link
Contributor

veshu commented Jul 17, 2019

Steps to Reproduce

  1. Go to https://www.topcoder.com/challenges/30095032
  2. Switch on the screen reader
  3. Tap on the page header and press tab button until it reaches to the prizes section
  4. Listen

Expected Result
It should be read-out by the screen reader

Actual Result
Prizes section is not read out by the screen reader

Device: Desktop/Labtop
Operating System: Windows
Browser: Chrome

WCAG Category: 1. Perceivable
WCAG Level: A
WCAG Success Criterion: 1.3.1 Info and Relationships
Screen Reader Used: JAWS
Accessibility Audit Tool used: N/A

Attachment
https://topcodermsft-my.sharepoint.com/personal/pd-topcoder_topcodermsft_onmicrosoft_com/Documents/Forms/All.aspx?cid=6aa53cde%2D1eef%2D4bae%2Dbfe5%2Df5f5f79e9df4&FolderCTID=0x0120005C598A51049FC14CBA882E1AEE168F51&id=%2Fpersonal%2Fpd%2Dtopcoder%5Ftopcodermsft%5Fonmicrosoft%5Fcom%2FDocuments%2FMSFT%2DTeams%2DQA%2FJune%202019%2F29%20Jun%2FTest%20Results%2FBug%20Videos%20%26%20Log%20Files%2Fcodejam%2DAccessibility%2F41

@veshu veshu changed the title [MSFT-131] [Challenge Page] Prizes section is not readout by the screen reader [$10][MSFT-131] [Challenge Page] Prizes section is not readout by the screen reader Jul 18, 2019
@ThomasKranitsas
Copy link
Contributor

Contest https://www.topcoder.com/challenges/30095960 has been created for this ticket.

This is an automated message for thomaskranitsas via Topcoder X

@ThomasKranitsas
Copy link
Contributor

Contest https://www.topcoder.com/challenges/30095960 has been updated - the new changes has been updated for this ticket.

This is an automated message for thomaskranitsas via Topcoder X

@cwdcwd
Copy link
Contributor

cwdcwd commented Jul 18, 2019

Contest https://www.topcoder.com/challenges/30095960 has been updated - it has been assigned to PkDurlabhji.

This is an automated message for lazybaer via Topcoder X

@PrakashDurlabhji
Copy link
Contributor

@veshu PR #2949

@cwdcwd
Copy link
Contributor

cwdcwd commented Jul 25, 2019

[400]: Failed to create challenge. Detail: Operation failed in the contest service facade.

This is an automated message for lazybaer via Topcoder X

1 similar comment
@cwdcwd
Copy link
Contributor

cwdcwd commented Jul 25, 2019

[400]: Failed to create challenge. Detail: Operation failed in the contest service facade.

This is an automated message for lazybaer via Topcoder X

@tosha5252
Copy link

In prod, prize is still being read out twice using NVDA.

WIn10/Chrome

@tosha5252 tosha5252 added QA Failed on Prod Fail on Production and removed Ready for Prod QA labels Aug 15, 2019
@sushilshinde
Copy link
Collaborator

sushilshinde commented Aug 16, 2019

@crazyk07 @tosha5252 @lakshmiathreya

Same commit

https://github.com/topcoder-platform/community-app/pull/3196/files

is present on the production

https://github.com/topcoder-platform/community-app/blob/master/src/shared/components/challenge-detail/Header/Prizes.jsx#L35

@r0hit-gupta can you also confirm

@r0hit-gupta
Copy link
Collaborator

@sushilshinde yes, the code is present in the production. @tosha5252 it worked fine for you in dev env, right?

@tosha5252
Copy link

@r0hit-gupta yes, it worked in dev env

@r0hit-gupta r0hit-gupta mentioned this issue Aug 16, 2019
@r0hit-gupta r0hit-gupta added tcx_ReadyForReview and removed QA Failed on Prod Fail on Production labels Aug 16, 2019
@r0hit-gupta
Copy link
Collaborator

@tosha5252 @veshu @crazyk07 I have made some changes. Should now work with both JAWS & NVDA properly. Please review.

@lakshmiathreya
Copy link

Seems to be working fine with Win 10/Chrome/NVDA and MacOS/Chrome/Voice Over ... @tosha5252 @drasticdpk pls move to QA Pass after JAWS test is done ...

@tosha5252
Copy link

Working with Win10/Chome/JAWS

@tosha5252
Copy link

Verified working correctly in prod

Win/Chrome/JAWS

@crazyk07 crazyk07 added tcx_Paid and removed Accessibility Challenge Page P0 Critical (resolve within 4 hours) QA Pass in PROD Passed verification on Production labels Aug 23, 2019
@crazyk07
Copy link

Payment task has been updated: https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30097359

This is an automated message for crazyk via Topcoder X

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