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

Feedback: "Navigate backwards to a button" (Command Button Example, Test 6) #736

Closed
IsaDC opened this issue May 25, 2022 · 4 comments
Closed
Labels
Agenda+Community Group To discuss in the next workstream summary meeting (usually the last teleconference of the month)

Comments

@IsaDC
Copy link
Contributor

IsaDC commented May 25, 2022

Description of Behavior

As I see it, we have two options:

  1. Mark the output as failing or
  2. Ask the tester to press the command sequence twice.

Test Setup

Review Conflicts for "Navigate backwards to a button"

  1. Unexpected Behaviors for "Shift+Control+Option+Command+J" Command

    • Tester louis4533 recorded output "Run Test Setup dimmed button " and noted "2 presses of Shift+Control+Option+Command+J were necessary to achieve the desired output. First press navigated forward and placed focus on the last element on the page (dimmed Run Test Setup button.) Second press correctly navigated backwards and placed focus on the previous control (Print Page button).".
    • Tester IsaDC recorded output "Run Test Setup dimmed button You are currently on a button. This item is dimmed. " and noted "After pressing the command sequence, VoiceOver jumps to the "Run Test Setup" button.".
@IsaDC
Copy link
Contributor Author

IsaDC commented May 26, 2022

@louis4533 As the test only instructs that the command should be pressed once, you have correctly indicated that upon doing so, VoiceOver fails against the assertions. To resolve result conflicts, we will remove your indication of unexpected behavior because it relates to pressing the command multiple times which is not in scope.

@IsaDC IsaDC added the Agenda+Community Group To discuss in the next workstream summary meeting (usually the last teleconference of the month) label Jun 2, 2022
@jscholes
Copy link
Contributor

jscholes commented Jun 9, 2022

@s3ththompson to look into why the app raised this as a conflict. We will then revisit. Note the related issues, #738 and #740.

@s3ththompson
Copy link
Member

@jscholes I opened an issue here to answer this question and document the behavior: w3c/aria-at-app#435

@IsaDC
Copy link
Contributor Author

IsaDC commented Jun 23, 2022

Assertions have been unified and undesirable behaviours have been removed.

@IsaDC IsaDC closed this as completed Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agenda+Community Group To discuss in the next workstream summary meeting (usually the last teleconference of the month)
Projects
None yet
Development

No branches or pull requests

3 participants