docs: add a worked modal example to defect priority - #910
Open
MuslumYilmaz wants to merge 1 commit into
Open
Conversation
Connect the priority guidance to a concrete modal accessibility incident and regression check.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add one worked modal example before the accessibility defect-priority table.
Why
The introduction explains that severity can change with the affected workflow and that new patterns may be added. This example connects technical findings with user impact and priority, including keyboard and screen-reader evidence and a behavioral regression check.
Disclosure
I’m affiliated with FrontendAtlas, which maintains the linked free, account-free exercise.
Validation
Documentation-only change; the rendered Markdown link and live destination were checked.