Skip to content
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

Allow Test Admin to provide contextual information about conflict resolution #426

Open
jscholes opened this issue May 26, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request UI

Comments

@jscholes
Copy link
Contributor

Description

At present, it is only possible for the Test Admin to resolve conflicts on a per-result basis, without providing any test-level documentation or context about decisions that were made during the resolution process.

Impact

  1. When decisions are made (e.g. in a CG meeting) that have an impact on conflict resolution for a test, the Test Admin cannot record this context in a way that carries forward to published reports. As such, it is non-obvious (or impossible) for an assistive technology vendor or other interested party to track the reasoning for those decisions.

  2. Once the functionality in issue Allow testers to provide an explanation of the undesirable behaviours they experience #425 has been implemented, individual testers will be able to provide an explanation of the undesirable behaviour(s) that they experienced. But the wording of these explanations will undoubtedly differ across results, and it is not a tester's responsibility to investigate the reasoning for an undesirable behaviour, nor to provide a concise description for AT vendors.

    One of the roles fulfilled by the Test Admin, with CG and other input, is to write that description instead. But such content cannot currently be recorded within the app.

Suggested Solution

Provide a new text input, scoped to the entire result set for a single test. The Test Admin will use this field to provide any pertinent facts that may assist an interested party in understanding decisions that were taken.

CC @richnoah, @s3ththompson and @mcking65

@jscholes jscholes added enhancement New feature or request UI labels May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request UI
Projects
None yet
Development

No branches or pull requests

2 participants