Skip to content

Add modal-window accessibility testing resource - #3911

Open
Müslüm Yılmaz (MuslumYilmaz) wants to merge 4 commits into
MicrosoftDocs:mainfrom
MuslumYilmaz:docs/modal-accessibility-testing-resource
Open

Add modal-window accessibility testing resource#3911
Müslüm Yılmaz (MuslumYilmaz) wants to merge 4 commits into
MicrosoftDocs:mainfrom
MuslumYilmaz:docs/modal-accessibility-testing-resource

Conversation

@MuslumYilmaz

@MuslumYilmaz Müslüm Yılmaz (MuslumYilmaz) commented Aug 20, 2026

Copy link
Copy Markdown

Fixes #3909

Rendered article section for review:


Incidental files

AB#63675935


Summary

This PR adds a public, guided modal accessibility debugging scenario to the article section External articles and websites in the article Resources for accessibility testing.

The scenario complements the article’s manual-testing guidance by covering:

  • Dialog naming
  • Keyboard focus containment
  • Background isolation
  • Focus restoration
  • Behavior-based regression testing.

No screenshots or other third-party assets are added.

Validation

  • Confirmed that the link uses the canonical HTTPS URL and the destination’s page title.
  • Confirmed that the scenario is public and doesn’t require sign-in.
  • Checked the Markdown preview, and verified that the diff changes only microsoft-edge/accessibility/test.md.
    • (In this PR, I added a local TOC in two other articles, to look for the previously problematic section that listed external tools. - M.H.)
  • The automated Microsoft Learn build and staged preview will be reviewed when posted.

Addresses #3909.

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

@mikehoffms Michael Hoffman (mikehoffms) changed the title Add modal accessibility testing resource Add modal-window accessibility testing resource Aug 20, 2026
@mikehoffms

Michael Hoffman (mikehoffms) commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

I am looking around the docset trying to find which section was problematic b/c turned into a list of non-Microsoft tools.

It was a list of tools from various companies.

The section became too high-maintenance, w/ too many non-Microsoft companies trying to list and advertise/promote too many tools; not sustainable.

Toward that search for the old section (listing external tools), in this PR, in a related article (or two), added a local TOC.

Patrick Brosset (@captainbrosset)

Found the previously problematic article section:
https://learn.microsoft.com/microsoft-edge/devtools/device-mode/testing-other-browsers#cloud-based-emulators-and-simulators
The maint. problem was solved there by replacing the list of non-Microsoft products by an MDN link.

mikehoffms

This comment was marked as outdated.

@mikehoffms

Michael Hoffman (mikehoffms) commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

IMO, Müslüm Yılmaz (@MuslumYilmaz), this PR, so far as it goes, is not problematic.
But, we can't promise to retain the Modal entry, if this section becomes problematic to maintain b/c too many companies try to list a product here.
I recommend / Approve this PR, w/ caveat that any non-Microsoft product/tool mentions, are subject to deletion at any time (to reduce Maint. overhead).

The problematic past section that I'm looking for, at one point, added a note that no further additions of tools will be made, and that this is just a suggestive list.

Found the previously problematic article section:
https://learn.microsoft.com/microsoft-edge/devtools/device-mode/testing-other-browsers#cloud-based-emulators-and-simulators
The maint. problem was solved there by replacing the list of non-Microsoft products by an MDN link.

@MuslumYilmaz

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@MuslumYilmaz

Copy link
Copy Markdown
Author

Thanks for the clarification and for approving the PR, Michael Hoffman (@mikehoffms). I understand that non-Microsoft resource entries may be removed if this section becomes difficult to maintain, and that caveat is completely reasonable. The intent here is simply to contribute a focused, freely accessible accessibility-testing scenario, not to establish a permanent product listing.

add local toc; section of interest is Cloud-based...
mikehoffms

This comment was marked as outdated.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - Writer/Editor

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 653fb55:

✅ Validation status: passed

File Status Preview URL Details
microsoft-edge/accessibility/build/index.md ✅Succeeded View
microsoft-edge/accessibility/test.md ✅Succeeded View
microsoft-edge/devtools/device-mode/testing-other-browsers.md ✅Succeeded View

For more details, please refer to the build report.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: consider an applied modal accessibility testing example

2 participants