Scott O'Hara

Been meaning to respond to this issue for.... years now it appears. I've filed bugs against Chromium and Webkit because nested text fields within a summary will cause the details...

similarly, if an auto popup were opened on page load via a `showPopUp()`, then it should automatically be focused to mitigate what i outlined in my op

@tbondwilkinson I did mentioned that one resolution could be to ensure the `defaultopen` popup automatically receives focus. Requiring `autofocus` on a `defaultopen` `popup` is definitely a solution worth considering. But,...

>but the explainer I think says that no focus behavior is performed on show except when autofocus is used. right. that's why i raised this issue as i think this...

yeh, i hesitate to think that autofocus needs to happen 100% of the time (outside of if - as you mentioned - `autofocus` could be more of a true/false declaration),...

some follow up points / clarifications to your comment, @colbywhite. i hope they help. a `role=alert` would not be expected for exposing inline form error messages. It would be more...

i'd argue that this is a feature that you'd only want authors to add for very specific situations. if this were more commonly available, you'd see more instances of people...

per the example you provided, @mfreed7, that markup pattern would not return an accessible name for the option. An `alt` on the image, or a `role=presentation` on the svg element...

Being that someone using a screen reader would only be expected to interact with the `option`s of a listbox, while the markup you use @captainbrosset for this example would be...

Depending on the html element you are using to render the icon, it may very well be a misuse, as aria-label is only supposed to be used on html elements...