Image Button inconsistency from empty naming attribute

[WilcoFiers]

Accessibility support

The input type="image" Accessible Name Computation algorithm uses the first defined attribute, even if the attribute has an empty value. In contrast, some user agents and assistive technologies ignore empty attributes.

ACT Rules

• Image button has non-empty accessible name - 59796f

Test cases

Test case 1

Testing image button accessible name computation across different naming methods

TODO

Test instructions

TODO

External links

Test results

Please report test results in a comment below. Please use the following format:

## Test case 1

- Date: ...
- Operating system: ..., version ...
- Browser: ..., version ...
- Screen reader: ..., version ...
- Test result: Passed / Failed (if failed, how was it different from expected?)

[shunguoy]

1. based on the acc name calculation spec, an aria-label or aria-labbeledby attribute will be ignored in the acc name calculation if its value is undefined or empty string when trimmed of whitespace.
2. The last resort (step 5) of an acc name for an input image button is from an implementation defined string, which is "Submit" for Chrome regardless of the existence of the image src, and "Submit Query" for FF only if the src image doesn't exist.
   The descriptions for each of the three Failed examples state that each button has an accessible name “Submit Query” (from the default internal implementation), however, they still fail without explanations of why.