GSAR - Test For Accessibility Series -2

Welcome to the GSAR - Test For Accessibility Series -2 challenge. All you need is to explore the given app and report the web accessibility issue based on WCAG 2.0 Guidelines. The WCAG (Web Content Accessibility Guidelines) are a collection of guidelines aimed at improving the web experience for people with disabilities or limitations.

Persons with vision impairment and other differently abled people are encouraged and very welcome to compete.  

Issue reporting will open 24 hrs after the challenge starts.  Please do not report any issues in JIRA until then. They will not be accepted. 

The announcement will be made in the forum when the time comes.  So, please watch the forum.

Assets

• Application Testing URL  : Will post on forum once registration period is over.

• You will use the WCAG 2.0 Rules  as a reference when looking for issues to report:

OTHER DETAILS

• Browsers: Use latest or minimum versions specified below for each browser.

Chrome:

 Windows, macOS, Linux 79.0.3945.117

 Android 79.0.3945.93

 iOS 79.0.3945.73

Internet Explorer:

 Windows 11.0.165 Microsoft 

Edge:

Windows 10 44.18362.449.0

 Windows 10 Mobile 40.15254.369

 Android 42.0.4.3892

 iOS 44.8.0

 Firefox:

Standard: 72.0

 Extended Support Release

Safari:

macOS 13

 iOS 13

 

• Device: Desktop/Mobile/Tablet 

• Operating System: 

           Android/Mobile Phone/Tablet

iOS/Mobile Phone/ Ipad

Windows 10

Linux

MacOS

• Assistive Technology : JAWS, NVDA 

• Accessibility Audit Tool:  WAVE

Note: Please only report the issue which falls under WCAG 2.0 Level A and AA. Level AAA is out of scope. And Audit Tool WAVE, Screen Reader JAWS & NVDA are in Scope.

How to Participate

 

•  Jira: Please request access to Jira in the forums if you have not received an email invite.  

• Report  the bug with below guidelines.
   

  Issue Weights and Scoring

• Scoring will be based on the number of points per bug.

• Bug found with use of screen reader                        - 2 Points

• Manual bug found or use of an audit tool                  - 1 Point

• Only verified issues will be counted.  Tickets created for enhancements or that are not bugs will not be counted. Duplicate issues will be closed and not counted. Log issues according to the guidelines above. Issues that do not follow these guidelines may be rejected due to lack of information.

• For challenge scoring, the user with the most verified points will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.

• Please focus on accessibility testing based on the requirements of the WCAG 2.0 Rules, all bug reports based on your own assumptions will be rejected.

• Submitters that do not take 1st, 2nd or 3rd place will be paid $5 for each non-duplicate and verified issue up to a maximum of the 3rd place prize. 

  Important Notice

• Follow the standard topcoder Bug Hunt Rules.

• If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. If you submit the same bug in multiple areas/pages, (for instance, Same validation issue of a form can be found in different pages/sections) you will likely get credit for the original bug report only. The others will all be closed as duplicates.

• Important Notes:

• DON'T use any other link to create new issues or submit as a document, they won't count and won't be paid.

• DON'T use youtube or public shared location for uploading your Testing collateral.

• - ALL THE SUBMISSIONS WITHOUT ABOVE INFORMATION WILL BE REJECTED AND WON’T BE PAID.

  - IMPORTANT: Submit the above details before the Submission Phase ends. If you can't submit due to technical difficulties within the Submission Phase please email your submission with above details to support@topcoder.com.

  - Participants who haven't submitted will not be paid.

   

• Please don’t make adjustments or change labels of existing issues logged by other competitors.   

• DON'T RE-OPEN the issues in the review phase and anyone who RE-OPENS a ticket will be disqualified from the challenge.

• DON'T create the same issue on different platforms; instead, merge them into one; All the others will be marked as Duplicate.

• If you see multiple broken links on the same page, combine them into one ticket. Others will be marked as DUPLICATE.

• You must not edit the bug report once created, so make sure you enter all the details at the time you create the issue. If you really need to edit an issue you must use the comments section for this (i.e. add a comment to describe any changes you want to make to the issue).

• You must specify the test data you have used in the 'Reproduction Steps', All the issues will be marked as 'Incomplete', if the correct test data is not provided.

• Keep an eye on the issues being submitted by other participants to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.

• There will be no appeals phase. The decision of PM/Copilot for validity and severity of each filled issue will be final.

Final Submission Guidelines

For each report of a limitation or bug, we need the following information:

• Device: The type of device used.  

• Operating System: OS you are using. 

• Browser:  Used browser.

• AT (Assistive Technology): JAWS, NVDA

• Steps to reproduce, including any additional information (Must list all the steps that need to reproduce the bug, DON'T list only the URL)

• Actual result: What actually happens

• Expected results: What should happen

• WCAG Category 

• WCAG Success Criterion

• WCAG Level

• Testing collateral: In Google Drive,  upload the

1. Voice Recording*, and/or

2. Screenshot(s)

3. Screenshot of OS version

4. Screenshot of browser version

5. Any other supporting documents to the Google Drive link listed in the forum
   Be sure to put the Google Drive link in the appropriate field in JIRA.
   ***A duplicate report for the same bug on a different browser is not allowed.*** 

When you are done with your reporting, please submit a .txt file in Direct using the "Submit" button before the submission phase ends. In this file please include the following details:

• TopCoder Handle: <>

• Jira Username: <>