-
Notifications
You must be signed in to change notification settings - Fork 212
[$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
Comments
Contest https://www.topcoder.com/challenges/30095960 has been created for this ticket. |
Contest https://www.topcoder.com/challenges/30095960 has been updated - the new changes has been updated for this ticket. |
Contest https://www.topcoder.com/challenges/30095960 has been updated - it has been assigned to PkDurlabhji. |
[400]: Failed to create challenge. Detail: Operation failed in the contest service facade. |
1 similar comment
[400]: Failed to create challenge. Detail: Operation failed in the contest service facade. |
In prod, prize is still being read out twice using NVDA. WIn10/Chrome |
@crazyk07 @tosha5252 @lakshmiathreya Same commit
is present on the production
@r0hit-gupta can you also confirm |
@sushilshinde yes, the code is present in the production. @tosha5252 it worked fine for you in dev env, right? |
@r0hit-gupta yes, it worked in dev env |
@tosha5252 @veshu @crazyk07 I have made some changes. Should now work with both JAWS & NVDA properly. Please review. |
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 ... |
Working with Win10/Chome/JAWS |
Verified working correctly in prod Win/Chrome/JAWS |
Payment task has been updated: https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30097359 |
Steps to Reproduce
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
The text was updated successfully, but these errors were encountered: