Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Non-modal dialog is not accessible with Voice Control on iOS & Safari #3403

Open
@mihkeleidast

Description

@mihkeleidast

Describe the bug

When using floating-ui to create a non-modal dialog (popover essentially), the contents of it are not accessible when using Voice Control on iOS with Safari.

To Reproduce

Reproduction:https://codesandbox.io/p/sandbox/festive-hamilton-ztmqn7

Steps to reproduce the behavior:

  1. Go to (iOS, Safari, Voice Control enabled)https://ztmqn7.csb.app/
  2. Click on "my trigger"
  3. Say "show names" / "show numbers" to surface accessible elements
  4. See that the contents of the popover do not get numbers/names assigned to it.

Expected behavior

Non-modal dialog contents should be accessible when using Voice Control.

Screenshots

Current behavior:

Image

Expected behavior:

Image

The expected behavior can be achieved by either:

  • removingheight: 1px; inline style and reseting the names ("hide names", then "show names" again
  • completely removing thearia-owns element

Context:

  • OS: iOS 26
  • Browser: Safari 26

Note: behaved the same with iOS/Safari v18

Additional context

Arguably, this is a iOS/Safari/WebKit bug, so I've also reported it there:https://bugs.webkit.org/show_bug.cgi?id=300224

However, perhaps this can also be remediated in floating-ui? Options:

  1. Folks in the a11y Slack were curious as to why this non-modal dialog pattern needs aria-owns at all. I could not find a specific reason as to why it was added. I get that it moves contents of the dialog in the accessibility tree to the "correct place", but I don't quite understand if it has any practical implications as well. Could we remove the aria-owns element?
  2. The root cause seems to come from the HIDDEN_STYLES applied on the owner span element. Given that the span never has any content of its own, perhaps applying a smaller subset of the visually hidden styles would work just as well?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp