Docs: consider an applied modal accessibility exercise in Additional resources

[MuslumYilmaz]

Prerequisites

• I have searched for duplicate or closed feature requests
• I have read the contributing guidelines

Proposal

The current Accessibility overview explains that accessible outcomes still depend on an author’s markup and JavaScript, while its Additional resources section mainly points to standards, reference documentation, and audit tools. Would you consider adding this short behavioral exercise?

https://frontendatlas.com/incidents/modal-screen-reader-failure

Suggested copy:

• FrontendAtlas: Modal opens visually but fails screen-reader users — A 15-minute diagnostic scenario covering dialog naming, keyboard focus containment, background isolation, focus restoration, and behavioral regression tests.

I am FrontendAtlas’s founder and maintainer. The linked scenario is public; separate exercises on the site may be optional premium. The scenario uses a custom React portal rather than Bootstrap’s modal implementation, so I am proposing it only as a general authoring exercise.

Motivation and context

It reinforces the page’s point that visually correct components can still fail because of application-level semantics and focus behavior. It also complements static audit-tool links with a behavior-focused learning scenario. If framework-neutral exercises are outside the scope of this list, no change is needed.