1.1.1 Non-text Content - Check #380

Passed Passed Example 1 Open in a new tab The image button has an accessible name through the alt attribute. Passed Example 2 Open in a new tab The image button has an accessible name through the aria-label attribute. Passed Example 3 Open in a new tab The image button has an accessible name through the title attribute. note: The title attribute may not always be accessibility supported. Passed Example 4 Open in a new tab The image button has an accessible name through the aria-labelledby attribute.
Search
Failed Failed Example 1 Open in a new tab The image button element has an accessible name equal to the default "Submit Query". The name attribute can not be used to provide an accessible name. Failed Example 2 Open in a new tab The image button has an empty alt attribute, and no other attributes that can give it an accessible name, hence its name is the default "Submit Query". Failed Example 3 Open in a new tab The image button has an aria-labelledby attribute, but the referenced element does not exist. This gives the button the default accessible name of "Submit Query". Inapplicable Inapplicable Example 1 Open in a new tab The button element is not an image button. Success Criterion 1.1.1 Non-text Content can not fail text buttons. Only non-text content is applicable. Inapplicable Example 2 Open in a new tab The input element with the type attribute value of button is not an image button. Success Criterion 1.1.1 Non-text Content can not fail text buttons. Only non-text content is applicable. Inapplicable Example 3 Open in a new tab The button element is tested separately from the img element. Success Criterion 4.1.2 Name, Role, Value is applied to the button, whereas the image is tested under Success Criterion 1.1.1 Non-text Content Inapplicable Example 4 Open in a new tab The img element is not a user interface component, and so is not tested for Success Criterion 4.1.2 Name, Role, Value. W3C logo Inapplicable Example 5 Open in a new tab The image button is ignored by assistive technologies because it is not included in the accessibility tree. These are not required to have an accessible name. If at some future state of the page the element gets included in the accessibility tree, an accessible name will be necessary.
Passed Shadow DOM Test 1
Passed Shadow DOM Test 2
Passed Shadow DOM Test 3
Passed Shadow DOM Test 4
Failed Shadow DOM Test 1
Failed Shadow DOM Test 2
Failed Shadow DOM Test 3
Inapplicable Shadow DOM Test 1
Inapplicable Shadow DOM Test 2
Inapplicable Shadow DOM Test 3
Inapplicable Shadow DOM Test 4
Inapplicable Shadow DOM Test 5