-
Notifications
You must be signed in to change notification settings - Fork 29
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
Feedback: "Close a modal dialog in interaction mode" (Modal Dialog Example, Test 5) #720
Comments
The test case #4 for the modal dialog (Testing Task: Close a modal dialog in interaction mode) is flawed. A user can get different results depending on how many times they hit the escape key. Also, for this test when activating the "Run Test Setup" button, the dialog automatically opens. This is different behavior from tasks #1 and #2, but the same as #3. The inconsistency between tasks is very confusing. |
@jha11y The Community Group has previously reached consensus that in interaction mode, a screen reader should pass the Escape key through to the page. I know that this can be seen as subjective, but the test was written with this decision in mind. As such, please rerun the test, pressing Escape only once as instructed. If the results do not pass the assertions (which we know they wont), mark the assertions as failing. Note: there is a chance that if/when these tests are reviewed by NVAccess during a future phase, they will disagree with the test as it is currently written. If so, this decision may need to be revisited. |
@IsaDC I fine with that. I can update my results |
Out-of-date due to test plan refactor |
Description of Behavior
Test Setup
Review Conflicts for "Close a modal dialog in interaction mode"
Unexpected Behaviors for "Escape" Command
Assertion Results for "Escape" Command and "Role 'button' is conveyed" Assertion
Assertion Results for "Escape" Command and "Name 'Add Delivery Address' is conveyed" Assertion
The text was updated successfully, but these errors were encountered: