Test cases for Dragon Naturally Speaking + Chrome Test case: Use "Click <text>" (Activate item by name) Launch Dragon Naturally Speaking and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes Test case: Use Click <role> (Click Type) Launch Dragon Naturally Speaking and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: Click <role> (Click Type) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes Test cases for Dragon Naturally Speaking + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Dragon Naturally Speaking + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for JAWS + Chrome Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch JAWS and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch JAWS and Chrome. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) on the target of `button[aria-expanded]` Launch JAWS and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for JAWS + Edge Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch JAWS and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch JAWS and Edge. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) on the target of `button[aria-expanded]` Launch JAWS and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for JAWS + Firefox Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch JAWS and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch JAWS and Firefox. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) on the target of `button[aria-expanded]` Launch JAWS and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for JAWS + IE Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch JAWS and IE. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) on the target of `button[aria-expanded]` Launch JAWS and IE. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for Narrator + Edge Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch Narrator and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch Narrator and Edge. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space Bar (Activate Item (primary action)) on the target of `button[aria-expanded]` Launch Narrator and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space Bar (Activate Item (primary action)) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for Narrator + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Narrator + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for NVDA + Chrome Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch NVDA and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch NVDA and Chrome. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) on the target of `button[aria-expanded]` Launch NVDA and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for NVDA + Edge Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch NVDA and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch NVDA and Edge. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) on the target of `button[aria-expanded]` Launch NVDA and Edge. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for NVDA + Firefox Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch NVDA and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch NVDA and Firefox. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) on the target of `button[aria-expanded]` Launch NVDA and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for NVDA + IE The test has not been configured for this combination. Please open a GitHub issue.
Test cases for TalkBack + Chrome Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `button[aria-expanded="false"]` Launch TalkBack and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe right (or alt+right arrow) (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `button[aria-expanded="true"]` Launch TalkBack and Chrome. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe right (or alt+right arrow) (Read next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use double tap (or alt+enter) (Activate button) on the target of `button[aria-expanded]` Launch TalkBack and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: double tap (or alt+enter) (Activate button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for TalkBack + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Access (Android) + Chrome Test case: Use "Tap <text>" or just "<text>" (Activate item by name) Launch Voice Access (Android) and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: "Tap <text>" or just "<text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Voice Access (Android) and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes Test cases for Voice Access (Android) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (iOS) + Safari Test case: Use Swipe Right (Next item) to navigate forward to `button[aria-expanded="false"]` Launch VoiceOver (iOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe Right (Next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Swipe Right (Next item) to navigate forward to `button[aria-expanded="true"]` Launch VoiceOver (iOS) and Safari. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Swipe Right (Next item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Double tap (Activate Button) on the target of `button[aria-expanded]` Launch VoiceOver (iOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Double tap (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for VoiceOver (iOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (macOS) + Safari Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch VoiceOver (macOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch VoiceOver (macOS) and Safari. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use VO + space (Activate Button) on the target of `button[aria-expanded]` Launch VoiceOver (macOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: VO + space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for VoiceOver (macOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for VoiceOver (macOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Orca + Firefox Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="false"]` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[aria-expanded="false"]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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes aria-expanded attribute, MUST convey the "false" value, applied to button element Examples:
Most screen readers will announce the state as "collapsed" Resultunknown pass fail partial
Notes Test case: Use Tab (Read next focusable item) to navigate forward to `button[aria-expanded="true"]` Launch Orca and Firefox. Navigate to the test page . 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. Position and configure the screen reader so that the following conditions are metVirtual focus is: before target Keyboard focus is: before target Mode is: auto (do not explicitly change the mode) Issue the command: Tab (Read next focusable item) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey the "true" value, applied to button element Examples:
Most screen readers will announce the state as "expanded" Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) on the target of `button[aria-expanded]` Launch Orca and Firefox. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:button[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. Position and configure the screen reader so that the following conditions are metVirtual focus is: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Enter or Space (Activate Button) After issuing the command, virtual focus should be: target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-expanded attribute, MUST convey change in value, applied to button element Examples:
If the element with aria-expanded has focus when its expanded state changes, the new state value will be announced (either "expanded" or "collapsed"). Some screen readers will re-announce the entire element, including name, role, and other properties and states. Resultunknown pass fail partial
Notes Test cases for Orca + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (iOS) + Safari Test case: Use "Tap <text>" (Activate item by name) Launch Voice Control (iOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: "Tap <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes Test cases for Voice Control (MacOS) + Safari Test case: Use "Click <text>" (Activate item by name) Launch Voice Control (MacOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Voice Control (MacOS) and Safari. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes Test cases for Voice Control (MacOS) + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Voice Control (MacOS) + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Speech Recognition + Chrome Test case: Use "Click <text>" (Activate item by name) Launch Windows Speech Recognition and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: "Click <text>" (Activate item by name) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its name Examples:
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. Resultunknown pass fail partial
Notes Test case: Use "Show numbers" (Turn on the numbers overlay) Launch Windows Speech Recognition and Chrome. Navigate to the test page . Find the target element(s) that you will test against. Identify all elements that match this selector:buttonIf 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. Issue the command: "Show numbers" (Turn on the numbers overlay) Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting button element, MUST convey its role Examples:
A screen reader might be announce the role as something like "button". Voice control software will let the user say something like "click button". Resultunknown pass fail partial
Notes Test cases for Windows Voice Access + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Voice Access + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Windows Keyboard + Edge The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Mac Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.
Test cases for iOS Keyboard + Safari The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Chrome The test has not been configured for this combination. Please open a GitHub issue.
Test cases for Android Keyboard + Firefox The test has not been configured for this combination. Please open a GitHub issue.