The Digital Experience team uses a standard form to input all accessibility issues. The form content is added to the accessibility tracker.
Here are the fields captured:
- Product or Service: A dropdown value with all the products currently owned by the President's Office. This field in the form is used behind the scenes to display the issue on the related Product page.
- Interface Tested: A lookup field with only two values - Back End/Administrative Interface and Front End/Customer-Facing Interface.
- Issue Title: A text field to provide a short description of the issue.
- Detailed Description of Issue: A long text field with formatting options (bullets, headings, etc.) that provides ample room for providing as much detail as possible around the issue.
- Video Recording: A link field that provides a link to a video recording of the issue. We store all video recordings on Dropbox, not directly in the database so that we can provide captions and a transcript for the video.
- Page or Location of Issue: A text field to provide either the exact page name or a navigation path to the content depending the product.
- Impact: A text field that provides how a disabled person would be impacted if the issue is not resolved.
- Impacted Disabilities: A multi-select list with the following values.
- Blind
- Colorblind
- Deaf
- Deafblind
- Epilepsy, Vestibular Disorder, or Motion Sensitivity
- Hard of Hearing
- Low Vision
- Mobility
- Neurodivergent
- Associated WCAG Success Criteria: A multi-select list with all the WCAG success criteria listed as selection options and a not applicable option for issues that do not align with a specific WCAG criteria but create usability issues for the disability community.
- Manual Testing Used: A multi-select list with the following values.
- Browser Zoom
- Dark Mode
- Dragon Naturally Speaking
- High Contrast Mode
- JAWS
- Keyboard Only
- Manual Video Review
- NVDA
- Reduced Motion Mode
- Text-to-Speech Software
- Voice Control
- VoiceOver
- Automated Testing Used (If Applicable): A dropdown field with the following values.
- Adobe Accessibility Checker
- axe Dev Tools
- Color Contrast Analyzer
- DubBot
- Priority: A dropdown field with the following two values.
- Blocker: User can not complete the process or is significantly hindered from completing the process. When to fix: Must be fixed prior to go live. However, if an application wasn't reviewed prior to go live, issues should be fixed within three to six months.
- Weakness: A weakness is considered an issue with the content or functionality that is still considered an issue by accessibility standards, but the user can complete the process. Deemed frustrating or annoying. When to fix: If the issue is complex to address, the recommendation would be to wait until all blockers are fixed. If it's a quick change, as soon as possible to reduce overall frustration.
- Expected Outcome: A text field for entering in detailed information about the expected outcome.
- Recommended Fix: A long text field with formatting for entering in either a high level recommended fix or detailed code fix recommendations.
- Status: A dropdown field with the following values.
- Identified
- Submitted to Vendor
- Submitted to Internal Team
- Vendor Working on Fix
- Internal Team Working on a Fix
- Vendor Declined to Fix
- Vendor to review for future remediation project
- Internal Workaround in Place until Vendor Fix
- Escalated to Legal
- Fix Applied
- Fix Validated
- Canceled - Functionality Being Retired
- Reporter: A dropdown field with the following values.
- Accessibility Specialist
- Developer
- DubBot Report
- End User
- Vendor
- Associated Case Number (if applicable): This is a text field that we use for capturing case numbers provided by vendors that have case management systems.
- Comments: This field is available for anyone with access to the tracker to submit a comment on an issue.