Run Test: APG Actions Menu Button Example Using aria-activedescendant

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.

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".

Examples:

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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

Examples:

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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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".

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.

Examples:

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

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

Examples:

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

Examples:

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

Examples:

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

Examples:

• A screen reader might announce "<name> <role> <2 of 10>" when navigating through a 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

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.

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.

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".

Examples:

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

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.

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".

Examples:

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