Popover API Accessibility Issue

[TrentHawke]

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Popover_API

What specific section or headline is this issue about?

Browser Compatibility

What information was incorrect, unhelpful, or incomplete?

There seems to be an Accessibility Issue with the HTML Popover API. This might just be a new Bug but if an HTML Popover contains an input of type date then it causes unexpected focus changes when navigating through other elements with the Tab Key.

What did you expect to see?

I was expecting to see some kind of indication that it is a known issue

Do you have any supporting links, references, or citations?

I did test this using the following HTML Markup

<div>
  <button popovertarget="examplePopover">Open Popover</button>
</div>
<div id="examplePopover" popover>
  <div>
    <input type="date" />
  </div>
  <div>
    <input type="text" />
  </div>
</div>

Then clicking on the "Open Popover" button, once the Popover opens, pressing the Tab Key will move the focus to the input date correctly but then pressing the Tab Key again will not move the focus to the next segment of the input date. The input date seems to effect other subsequent focusable elements as well, being unable to tab past the input date and onto other elements in the Popover.

Do you have anything more you want to share?

No response

MDN metadata

Page report details

• Folder: en-us/web/api/popover_api
• MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/Popover_API
• GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/api/popover_api/index.md
• Last commit: e2ac6a9
• Document last modified: 2024-11-22T01:13:24.000Z

[Josh-Cena]

Have you reported it as a bug to the browsers? Is it common across all browsers?

[TrentHawke]

I've reported it to both Chrome and Firefox, both have recognized it as a bug and are taking a look. The bug in Edge is the same as in Chrome but is very slightly different between Chrome and Firefox but I haven't been able to test on Safari.

Chrome Issue Report
Firefox Issue Report

[Josh-Cena]

I'm going to merge this into #37465. We would either add a note when we create the new "Accessibility" section, or we just add a note in the browser compat table. We'll see how the browser bugs go. Thanks for the info!