Test Cases Passed Passed Example 1 Open in a new tab This button element has an accessible
name because of its text content.
Passed Example 2 Open in a new tab This input element has an accessible name because of its
value attribute.
Passed Example 3 Open in a new tab This button element has an accessible name because of its
aria-label attribute.
Passed Example 4 Open in a new tab This element with a button role has an accessible name
because of its aria-label attribute.
Passed Example 5 Open in a new tab This button element with the disabled attribute has an
accessible name because of its text content.
Passed Example 6 Open in a new tab This off screen button element has an accessible name
because of its text content.
Passed Example 7 Open in a new tab This input element has an accessible name because of the
default accessible name for an input element with a type attribute set to reset.
Failed Failed Example 1 Open in a new tab This button element has no accessible name because
it has no content or attribute that can provide it.
Failed Example 2 Open in a new tab This button element has no accessible name. The value
attribute does not provide an accessible name for button elements, only when an input
element's state of the type attribute is button, submit or reset.
Failed Example 3 Open in a new tab This element with the button role has no accessible name
because it has no content or attribute that can provide it.
Failed Example 4 Open in a new tab This off screen button element has no accessible name
because it has no content or attribute that can provide it.
Failed Example 5 Open in a new tab This button element has an explicit role of none.
However, it is focusable (by default). Thus it has a semantic role of button due to
Presentational Roles Conflict Resolution. It has an empty accessible name.
Inapplicable Inapplicable Example 1 Open in a new tab This input element has a type
attribute set to image. These images are tested in a separate rule which also tests success
criterion 1.1.1 Non-text Content.
Inapplicable Example 2 Open in a new tab This button element does not need an accessible
name because it is not included in the accessibility tree.
Inapplicable Example 3 Open in a new tab This button element has a link role. Links are
tested in a separate rule which also tests success criterion 2.4.4 Link Purpose (In
Context).
Inapplicable Example 4 Open in a new tab There is no element with a semantic role of button.
Press Here
Inapplicable Example 5 Open in a new tab This button element has an explicit role of none;
it is not focusable because it is disabled. Thus it has a semantic role of none.
MybuttonMybutton