...
Replicate and Document the Issue
We should attempt Attempt to replicate validate the reported issue before moving forward. Follow this process for each reported or newly discovered barrier:
Document error reproduction pathway.
Take screenshots and/or screen captures where needed.
Include alternative text.
Insert template here; fields:
Reported issue
Can replicate/no
Replication pathway
Comments
Screenshot
WCAG violation
Responsible party (in-house/vendor/vendor with in-house workaround)
Generate detailed notes and record them in an internal comment in the original ticket.
Determine if the issue is solvable by the system administrator or if it must be referred to the vendor.
In-House Remediation
The in-house system admin(s) should attempt to remediate using accessibility best practices.
Try to resolve any reported issues on your own, if you can.
Note what you did to fix it, if it was your configuration that caused the issue, or if it was a bug that you worked around that should be reported to the vendor.
If you can’t fix it, move to the next step.
In-House Remediation and Vendor Report
Vendor Report
Issues that cannot be solved by us , determine the extent and severity of the associated accessibility barrier(s), and assign remediation and response to the appropriate responsible party.
In-House Remediation and Response
If the responsible party is the systems administrator or an internal content contributor, the issue should be resolved in house. Please refer to the follow resources for guidance and consultation as necessary:
Vendor Remediation and Response
Issues that cannot be solved in house must be escalated to the vendor for resolution. It’s important to be thorough in documenting everything from previous steps so the vendor knows exactly what must be done to remediate. Even if you are able to work around a bug that was causing the original issue, it is important to inform the vendor as it may affect others.
...