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 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:*[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. 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 menuitem role, MUST convey the name 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:*[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. 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 menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context 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:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes Test case: unknown 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: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Insert + alt + M (Jump to controlled element) After issuing the command, virtual focus should be: after target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 Resultunknown pass fail partial
Notes Test cases for JAWS + Edge Test case: Use Tab (Read next focusable item) to navigate forward to `button:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes Test case: unknown 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: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Insert + alt + M (Jump to controlled element) After issuing the command, virtual focus should be: after target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 Resultunknown pass fail partial
Notes Test cases for JAWS + Firefox Test case: Use Tab (Read next focusable item) to navigate forward to `button:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes Test case: unknown 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: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Insert + alt + M (Jump to controlled element) After issuing the command, virtual focus should be: after target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 Resultunknown pass fail partial
Notes Test cases for JAWS + IE Test case: Use Tab (Read next focusable item) to navigate forward to `button:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes Test case: unknown 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: target Keyboard focus is: target Mode is: auto (do not explicitly change the mode) Issue the command: Insert + alt + M (Jump to controlled element) After issuing the command, virtual focus should be: after target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 Resultunknown pass fail partial
Notes Test cases for Narrator + Edge Test case: Use Tab (Read next focusable item) to navigate forward to `button:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space Bar (Activate Item (primary action)) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 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:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 Resultunknown pass fail partial
Notes Test cases for NVDA + Edge Test case: Use Tab (Read next focusable item) to navigate forward to `button:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 Resultunknown pass fail partial
Notes Test cases for NVDA + Firefox Test case: Use Tab (Read next focusable item) to navigate forward to `button:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 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:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use double tap (or alt+enter) (Activate button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forward to `*[role="menuitem"]` 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:*[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. 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes Test case: Use Swipe right (or alt+right arrow) (Read next item) to navigate forwards out of `ul[role="menu"]` 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: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. Position and configure the screen reader so that the following conditions are metVirtual focus is: within target Keyboard focus is: within 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: after target Record results for the relevant expectations Output Notes If support is hidden behind non-default settings, briefly describe that setting menu role, MUST convey the boundaries of the menu Examples:
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 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 "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:*[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. 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 menuitem role, MUST convey the name 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:*[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. 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 menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context 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:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Double tap (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use Swipe Right (Next item) to navigate forward to `*[role="menuitem"]` 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:*[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. 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 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:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use VO + space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 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:not([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: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. 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-haspopup attribute, MUST convey the "true" value (see note), applied to button element Resultunknown pass fail partial
Notes aria-controls attribute, SHOULD convey the presence of the aria-controls attribute, applied to button element Examples:
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. Resultunknown pass fail partial
Notes aria-controls attribute, MUST allow the user to jump to the controlled element, applied to button element Resultunknown pass fail partial
Notes Test case: Use Enter or Space (Activate Button) to navigate forward to `*[role="menu"]` 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:*[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. 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: 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 menu role, MUST convey the name if named Examples:
The accessible name of the menu is announced when entering the menu. Resultunknown pass fail partial
Notes menu role, MUST convey its role Examples:
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 Resultunknown pass fail partial
Notes aria-activedescendant attribute, MUST convey the referenced element as active, applied to menu role Examples:
When navigating to an element with this attribute, screen readers will also announce the referenced element Resultunknown pass fail partial
Notes Test case: Use <keyboard command> (Keyboard command while in forms or application mode) to navigate forward to `*[role="menuitem"]` 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:*[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. 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: <keyboard command> (Keyboard command while in forms or application mode) 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-activedescendant attribute, MUST convey when the referenced element changes, applied to menu role Examples:
When navigating within an element with this attribute, screen readers will also announce the referenced element as the reference changes Resultunknown pass fail partial
Notes menuitem role, MUST convey the name Resultunknown pass fail partial
Notes menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context Resultunknown pass fail partial
Notes menuitem role, MAY convey information about the position the menu item in the menu Examples:
A screen reader might announce "<name> <role> <2 of 10>" when navigating through a menu Resultunknown pass fail partial
Notes menu role, MUST convey the boundaries of the menu Examples:
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 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 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:*[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. 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 menuitem role, MUST convey the name 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 "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:*[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. 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 menuitem role, MUST convey the name 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:*[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. 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 menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context 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 "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:*[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. 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 menuitem role, MUST convey the name 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:*[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. 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 menuitem role, MUST convey its role Examples:
The role may be explicitly conveyed as something like "menu item" The role may be implied by the announcement of a menu context 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.