Presently, Chrome does not follow the "children presentation" rule on buttons. Instead, everything in a button is exposed to the accessibility APIs. So, chrome explicitly does not follow the ARIA spec here.
Since this kind of markup is found on the web, do we want to change the spec, or add a new exception in the handling author's error section?
One option is do do as Chrome does expose all the content of the button. Or, expose the content if there is interactive content in it. @dtsengchromium wonders specifically if instead we should not expose the button as a button when there is interactive content.
Also, I'm sure this has been discussed before, I wonder if anyone can find links as to where? :)
Presently, Chrome does not follow the "children presentation" rule on buttons. Instead, everything in a button is exposed to the accessibility APIs. So, chrome explicitly does not follow the ARIA spec here.
Since this kind of markup is found on the web, do we want to change the spec, or add a new exception in the handling author's error section?
One option is do do as Chrome does expose all the content of the button. Or, expose the content if there is interactive content in it. @dtsengchromium wonders specifically if instead we should not expose the button as a button when there is interactive content.
Also, I'm sure this has been discussed before, I wonder if anyone can find links as to where? :)