Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://a11ysupport.io/tests/apg__menu-button-actions-active-descendant below:

Test: APG Actions Menu Button Example Using aria-activedescendant

Screen Reader support level: partial (98/117)

Voice Control support level: partial (15/30)

• About this test
• Age of results
• Test HTML
• Dates and Versions of tested combinations
• Summary of screen reader support by expectation
• Summary of voice control support by expectation
• Detailed support tables
• History
• Related features
• Contribute and Feedback

This example demonstrates how the menu button design pattern can be used to create a button that opens an actions menu. Note: not all features present in this example are tested, as they are tested elsewhere in this project.

Results in this test range from 4 years ago to 5 years ago. See detailed information about test dates and versions for more information.

Failing or partial results may be out of date. The oldest result is from 5 years ago. Consider running this test and contributing results.

* means that some support is hidden behind settings

* means that some support is hidden behind settings

* means that some support is hidden behind settings

This expectation is applied to the menu role. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-activedescendant attribute feature.

A screen reader user needs to be aware of which descendant is currently active

• Screen Readers: MUST
• Voice Control: NA

• When navigating to an element with this attribute, screen readers will also announce the referenced element

Just one of the listed commands must pass for the expectation to pass.

• Result: (pass)
  • Test Case: Use double tap (or alt+enter) (Activate button) to navigate forward to `*[role="menu"]`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menu"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: double tap (or alt+enter) (Activate button)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 1, menu item, expanded, double tap to activate"
  • Command Notes: activate the menu button, and focus will be sent to the target (menu)

These are less common combinations

• Result: (pass)
  • Test Case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menu"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Enter or Space (Activate Button)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "menu, Action 1, To move through items press up or down arrow."
  • Command Notes: activate the menu button, and focus will be sent to the target (menu)

This expectation is applied to the menu role. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-activedescendant attribute feature.

A screen reader user needs to be aware of which descendant is currently active

• Screen Readers: MUST
• Voice Control: NA

• When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes

All of the listed commands must pass for the expectation to pass.

• Result: (na)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `*[role="menuitem"]`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3, menu item, double tap to activate"

These are less common combinations

• Result: (pass)
  • Test Case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: <keyboard command> (Keyboard command while in forms or application mode)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3"
  • Command Notes: press up and down arrows to navigate menu items

This expectation is applied to the button element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-controls attribute feature.

The controlled element might not be close to the element with aria-controls and the user might find it convenient to jump directly to the controlled element.

• Screen Readers: MUST
• Voice Control: NA

Just one of the listed commands must pass for the expectation to pass.

• Result: (na)
  • Test Case: unknown
    1. Launch JAWS and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="true"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: target
       • Keyboard focus is: target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Insert + alt + M (Jump to controlled element)
       • After issuing the command, virtual focus should be: after target
    6. Record results for the relevant expectations
  • Output: ""
  • Command Notes: unable to navigate to the button with the menu expanded

• Result: (na)
  • Test Case: unknown
    1. Launch JAWS and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="true"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: target
       • Keyboard focus is: target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Insert + alt + M (Jump to controlled element)
       • After issuing the command, virtual focus should be: after target
    6. Record results for the relevant expectations
  • Output: ""
  • Command Notes: unable to navigate to the button with the menu expanded

• Result: (pass)
  • Test Case: unknown
    1. Launch JAWS and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="true"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: target
       • Keyboard focus is: target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Insert + alt + M (Jump to controlled element)
       • After issuing the command, virtual focus should be: after target
    6. Record results for the relevant expectations
  • Output: "move to controlled element, action 1, menu"
  • Command Notes: tab to the button with it expanded, then execute this command

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch Narrator and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, subMenu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, subMenu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, submenu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch Orca and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, push button, focus mode"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Swipe Right (Next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch VoiceOver (iOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe Right (Next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button, menu popup"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch VoiceOver (macOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu popup button"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

These are less common combinations

• Result: (pass)
  • Test Case: unknown
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="true"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: target
       • Keyboard focus is: target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Insert + alt + M (Jump to controlled element)
       • After issuing the command, virtual focus should be: after target
    6. Record results for the relevant expectations
  • Output: "move to controlled element, action 1, menu"
  • Command Notes: tab to the button with it expanded, then execute this command

This expectation is applied to the button element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-controls attribute feature.

Users need to be aware that an element has aria-controls functionality. If the presence of the attribute is not explicitly conveyed, then users may not be aware of the functionality. However, some screen readers may choose to not convey the presence by default since the controlled element is usually directly after the controlling element in the reading order and easily findable. In these situations, explicitly conveying the presence could be unnecessarily verbose.

• Screen Readers: SHOULD
• Voice Control: NA

• When supported, screen readers will often hint that an element controls another element, and may even announce the keyboard shortcut to jump to the controlled element
• Most screen readers either do not support this attribute or the setting to convey the presence is turned off by default. This is because in the vast majority of cases, the controlled element is adjacent to the element with aria-controls, and thus announcing the presence is redundant and add extra verbosity.

Just one of the listed commands must pass for the expectation to pass.

This is not a MUST requirement, because the functionality could still be discoverable via the screen reader's command to jump to the controlled element. If the command fails, the attribute is not present.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch Narrator and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, subMenu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, subMenu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, submenu"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch Orca and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, push button, focus mode"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Swipe Right (Next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch VoiceOver (iOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe Right (Next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button, menu popup"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch VoiceOver (macOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu popup button"
  • Command Notes: tab to the button with it collapsed
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

These are less common combinations

• Result: (fail)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action button, menu"
  • Command Notes: tab to the button with it collapsed

This expectation is applied to the button element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the aria-haspopup attribute feature.

• Screen Readers: MUST
• Voice Control: NA

Just one of the listed commands must pass for the expectation to pass.

Since ARIA 1.1, the "true" value must be conveyed as the "menu" value. In ARIA 1.0, the "true" value simply conveys that a popup is available (not the type of popup). If applied to an ARIA 1.0 combobox, this should pass if the screen reader conveys that there is a popup.

• Result: (partial)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button"
  • Command Notes: tab to the button with it collapsed
  • Result Notes: not announced as a menu popup

These are less common combinations

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action button, menu"
  • Command Notes: tab to the button with it collapsed

This expectation is from the menu role feature.

A screen reader user needs to be aware of the name of menu

• Screen Readers: MUST
• Voice Control: NA

• The accessible name of the menu is announced when entering the menu.

Just one of the listed commands must pass for the expectation to pass.

• Result: (pass)
  • Test Case: Use double tap (or alt+enter) (Activate button) to navigate forward to `*[role="menu"]`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menu"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: double tap (or alt+enter) (Activate button)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 1, menu item, expanded, double tap to activate"
  • Command Notes: activate the menu button, and focus will be sent to the target (menu)

These are less common combinations

• Result: (fail)
  • Test Case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menu"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Enter or Space (Activate Button)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "menu, Action 1, To move through items press up or down arrow."
  • Command Notes: activate the menu button, and focus will be sent to the target (menu)

This expectation is from the menu role feature.

A screen reader user needs to be aware that elements are within a menu

• Screen Readers: MUST
• Voice Control: NA

• Some screen readers will explicitly convey the menu role as something like "<name> menu"
• The role may be implied by the presence of menuitem children

Just one of the listed commands must pass for the expectation to pass.

• Result: (pass)
  • Test Case: Use double tap (or alt+enter) (Activate button) to navigate forward to `*[role="menu"]`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menu"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: double tap (or alt+enter) (Activate button)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 1, menu item, expanded, double tap to activate"
  • Command Notes: activate the menu button, and focus will be sent to the target (menu)

These are less common combinations

• Result: (pass)
  • Test Case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menu"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Enter or Space (Activate Button)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "menu, Action 1, To move through items press up or down arrow."
  • Command Notes: activate the menu button, and focus will be sent to the target (menu)

This expectation is from the menu role feature.

A screen reader user needs to be aware when they enter and exit a menu

• Screen Readers: MUST
• Voice Control: NA

• Boundaries may be implied by posinset information
• Boundaries may be implied by no longer conveying the menu item role (if the role is explicitly conveyed)
• Boundaries may be implied by looping back to the top of the menu
• Boundaries may be explicitly conveyed by announcing something like "<name> menu" when entering and "exiting menu" when leaving

All of the listed commands must pass for the expectation to pass.

• Result: (pass)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forwards out of `ul[role="menu"]`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:ul[role="menu"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: within target
       • Keyboard focus is: within target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: after target
    6. Record results for the relevant expectations
  • Output: The next element was announced
  • Command Notes: swipe to the element after the open menu
  • Result Notes: implied by navigating to an element that is not announced as a menu item

These are less common combinations

• Result: (pass)
  • Test Case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: <keyboard command> (Keyboard command while in forms or application mode)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3"
  • Command Notes: press up and down arrows to navigate menu items
  • Result Notes: Implied by looping back to the first item

This expectation is from the menuitem role feature.

A screen reader user needs to know what the menu item does

• Screen Readers: MUST
• Voice Control: MUST

Just one of the listed commands must pass for the expectation to pass.

• Result: (pass)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `*[role="menuitem"]`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3, menu item, double tap to activate"

• Result: (pass)
  • Test Case: Use "Tap <text>" or just "<text>" (Activate item by name)
    1. Launch Voice Access (Android) and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Tap <text>" or just "<text>" (Activate item by name)
    5. Record results for the relevant expectations
  • Output: button was activated
  • Command Notes: said "tap action 3"

These are less common combinations

• Result: (pass)
  • Test Case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: <keyboard command> (Keyboard command while in forms or application mode)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3"
  • Command Notes: press up and down arrows to navigate menu items

This expectation is from the menuitem role feature.

A screen reader user needs to be aware that they are interacting with a menu item

• Screen Readers: MUST
• Voice Control: MUST

• The role may be explicitly conveyed as something like "menu item"
• The role may be implied by the announcement of a menu context

Just one of the listed commands must pass for the expectation to pass.

• Result: (pass)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `*[role="menuitem"]`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3, menu item, double tap to activate"

• Result: (pass)
  • Test Case: Use "Show numbers" (Turn on the numbers overlay)
    1. Launch Voice Access (Android) and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Show numbers" (Turn on the numbers overlay)
    5. Record results for the relevant expectations
  • Output: items were flagged

These are less common combinations

• Result: (pass)
  • Test Case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: <keyboard command> (Keyboard command while in forms or application mode)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3"
  • Command Notes: press up and down arrows to navigate menu items
  • Result Notes: implied by menu context

This expectation is from the menuitem role feature.

The user should be able to determine how many options are in the list and where they are in the list

• Screen Readers: MAY
• Voice Control: NA

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu

Just one of the listed commands must pass for the expectation to pass.

• Result: (fail)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `*[role="menuitem"]`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3, menu item, double tap to activate"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

These are less common combinations

• Result: (fail)
  • Test Case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: <keyboard command> (Keyboard command while in forms or application mode)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action 3"
  • Command Notes: press up and down arrows to navigate menu items

This expectation is from the button element feature.

A screen reader user needs to know what to enter.

• Screen Readers: MUST
• Voice Control: MUST

• A screen reader might announce the button as something like "<name>, button".
• Voice control software will let the user say something like "click <name>" to activate the control.

Just one of the listed commands must pass for the expectation to pass.

• Result: (pass)
  • Test Case: Use "Click <text>" (Activate item by name)
    1. Launch Dragon Naturally Speaking and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Click <text>" (Activate item by name)
    5. Record results for the relevant expectations
  • Output: button was activated and command was recognized. However, the menu opened and then immediately closed. This appears to be a bug with the example.
  • Command Notes: said "click actions"

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch Narrator and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, subMenu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, subMenu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, submenu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch Orca and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, push button, focus mode"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use "Tap <text>" or just "<text>" (Activate item by name)
    1. Launch Voice Access (Android) and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Tap <text>" or just "<text>" (Activate item by name)
    5. Record results for the relevant expectations
  • Output: button was activated
  • Command Notes: said "tap actions"

• Result: (pass)
  • Test Case: Use "Tap <text>" (Activate item by name)
    1. Launch Voice Control (iOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Tap <text>" (Activate item by name)
    5. Record results for the relevant expectations
  • Output: button was activated
  • Command Notes: said "tap actions"

• Result: (fail)
  • Test Case: Use "Click <text>" (Activate item by name)
    1. Launch Voice Control (MacOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Click <text>" (Activate item by name)
    5. Record results for the relevant expectations
  • Output: Other links on the page were clicked. Could not get it to click the button
  • Command Notes: said "click actions"
  • Grading note: This command may be expected to fail. This result simply indicates that it did not yield support.

• Result: (pass)
  • Test Case: Use Swipe Right (Next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch VoiceOver (iOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe Right (Next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button, menu popup"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch VoiceOver (macOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu popup button"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use "Click <text>" (Activate item by name)
    1. Launch Windows Speech Recognition and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Click <text>" (Activate item by name)
    5. Record results for the relevant expectations
  • Output: "button was activated and command was recognized. However, the menu opened and then immediately closed. This appears to be a bug with the example."
  • Command Notes: said "click actions"

These are less common combinations

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action button, menu"
  • Command Notes: tab to the button with it collapsed

This expectation is from the button element feature.

A screen reader user needs to know how they can interact with the element. Voice control software might use the role to help users activate controls that do not have a visible name.

• Screen Readers: MUST
• Voice Control: MUST

• A screen reader might be announce the role as something like "button".
• Voice control software will let the user say something like "click button".

Just one of the listed commands must pass for the expectation to pass.

• Result: (pass)
  • Test Case: Use Click <role> (Click Type)
    1. Launch Dragon Naturally Speaking and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: Click <role> (Click Type)
    5. Record results for the relevant expectations
  • Output: button was activated and command was recognized. However, the menu opened and then immediately closed. This appears to be a bug with the example.
  • Command Notes: said "click button"

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button, menu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch Narrator and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, button"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, subMenu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Edge.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, subMenu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch NVDA and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu button, submenu"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch Orca and Firefox.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, push button, focus mode"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch TalkBack and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe right (or alt+right arrow) (Read next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use "Show numbers" (Turn on the numbers overlay)
    1. Launch Voice Access (Android) and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Show numbers" (Turn on the numbers overlay)
    5. Record results for the relevant expectations
  • Output: items were flagged

• Result: (pass)
  • Test Case: Use "Show numbers" (Turn on the numbers overlay)
    1. Launch Voice Control (MacOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Show numbers" (Turn on the numbers overlay)
    5. Record results for the relevant expectations
  • Output: button was flagged, but when the menu was opened, nothing was flagged

• Result: (pass)
  • Test Case: Use Swipe Right (Next item) to navigate forward to `button:not([aria-expanded])`
    1. Launch VoiceOver (iOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Swipe Right (Next item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, popup button, menu popup"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch VoiceOver (macOS) and Safari.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "actions, menu popup button"
  • Command Notes: tab to the button with it collapsed

• Result: (pass)
  • Test Case: Use "Show numbers" (Turn on the numbers overlay)
    1. Launch Windows Speech Recognition and Chrome.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:*[role="menuitem"]
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Issue the command: "Show numbers" (Turn on the numbers overlay)
    5. Record results for the relevant expectations
  • Output: menu items were flagged with numbers

These are less common combinations

• Result: (pass)
  • Test Case: Use Tab (Read next focusable item) to navigate forward to `button:not([aria-expanded])`
    1. Launch JAWS and IE.
    2. Navigate to the test page.
    3. Find the target element(s) that you will test against. Identify all elements that match this selector:button:not([aria-expanded])
       • If multiple elements match the selector, repeat this test for all instances. However, choose a single instance to report against. If you feel that the selector should be more specific, please open a GitHub Issue.
    4. Position and configure the screen reader so that the following conditions are met
       • Virtual focus is: before target
       • Keyboard focus is: before target
       • Mode is: auto (do not explicitly change the mode)
    5. Issue the command: Tab (Read next focusable item)
       • After issuing the command, virtual focus should be: target
    6. Record results for the relevant expectations
  • Output: "action button, menu"
  • Command Notes: tab to the button with it collapsed

• 2020-03-30 Draft test
• 2020-11-09 Update JAWS support for aria-controls. JAWS 2020 no longer has a setting to convey the presence of the attribute.
• 2021-08-07 Added Narrator results for NVDA and JAWS, updated NVDA+Chrome results.
• 2021-11-10 Retested with VoiceOver. No major changes.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4