Challenge Overview
Challenge Objectives
We have our client who wants to improve the accessibility of their web application with guidelines based on WCAG 2.1. The WCAG (Web Content Accessibility Guidelines) are a collection of guidelines aimed at improving the web experience for people with disabilities or limitations.
-
Exploratory testing
-
Desktop site (Edge, Chrome, Safari, Firefox)
Project Background:
We will share the application detail after submission period starts.Assets
-
You will use the WCAG as a reference when looking for issues to report:
These guidelines will hold detailed knowledge of what to look for while testing for accessibility.
Approved Tools
-
Screen Reader Requirements: There are many free screen readers available to choose from. We will mainly focus on compatibility with the following:
JAWS
NonVisual Desktop Access (NVDA) for Windows
VoiceOver for Mac OS
Any screen reader included with an OS
-
Accessibility Audit Tool Requirements: This tool is used to check web pages for general accessibility compliance. We are only focused on following WCAG guidelines. These free tools are acceptable to use for testing for this challenge:
508Checker - http://www.508checker.com
Accessibility Checklist - http://romeo.elsevier.com/accessibility_checklist/
CynthiaSays - http://www.cynthiasays.com
If there are tools other than those listed that you have found and would like to use, please request it first in the challenge forum.
Application access
Please check the forum for access to the application to test. It will be shared after 12 hour of registration period.
You need to deploy locally to test the application. Make sure to install the Node JS (v10.xx.xx) installed locally. Supported platform by application is mac os and linux. In windows the application might not deployed properly.
Submission Period:
Submission will start after 12 hour of registration period. 24 hour period will be given to submit the issues.
Rules
-
Follow the standard Topcoder Bug Hunt Rules (if any conflict please ask in forum)
-
Scoring will be based on the number of points per bug.
-
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.1, all bug reports based on your own assumptions will be rejected.
-
Bug found with use of screen reader - 2 Points
-
Manual bug found or use of an audit tool - 1 Point
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.
Final Submission Guidelines
Please submit new issue on Github with “Accessibility Bug report” template shared on the forum
When you are done with your submissions please submit a .txt file using the "Submit" button before the submission phase ends. In this file include the following details:
TopCoder Handle: <>
Github Username: <>