Skip to content

Docs: consider an applied modal accessibility testing example #3909

Description

Link to the documentation page

https://learn.microsoft.com/en-us/microsoft-edge/accessibility/test

Description of the issue

The page explains that automated tools cannot find every accessibility problem and recommends keyboard and screen-reader testing. The “External articles and websites” section links to tools and reference material, but not to a hands-on example of failures that emerge during interaction.

Would this public applied example fit that section?

FrontendAtlas: Modal opens visually but fails screen-reader users
https://frontendatlas.com/incidents/modal-screen-reader-failure

It asks readers to diagnose a missing dialog name, focus escaping behind the modal, background interaction, and focus restoration. It is not a Microsoft Edge or DevTools integration; it would only illustrate the manual-testing gap described on the page.

Disclosure: I’m FrontendAtlas’s founder and maintainer. The linked scenario is public and free; some separate exercises elsewhere on the site are optional premium.

I have not opened a PR. If this scope fits the page, I can prepare the smallest documentation change for review.

Screenshots

Not applicable.

Microsoft Edge version

Not version-specific.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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