-
Notifications
You must be signed in to change notification settings - Fork 15
🎨 Palette: [UX improvement] Add ARIA label and focus styles to Upload Resume Modal close button #417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
🎨 Palette: [UX improvement] Add ARIA label and focus styles to Upload Resume Modal close button #417
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,6 @@ | ||
| ## 2025-02-14 - ResponsiveConfirmDialog for Destructive Actions | ||
| **Learning:** Destructive actions (like Delete) implemented with custom hardcoded modals lack standard accessibility attributes (`role="dialog"`, `aria-modal`, etc.) and mobile responsiveness (like bottom sheets). This app has a `ResponsiveConfirmDialog` component designed specifically for this purpose, but it was not being utilized uniformly. | ||
| **Action:** Always use `ResponsiveConfirmDialog` for destructive confirmation prompts (such as `DeleteResumeModal`) to ensure a consistent, accessible, and mobile-friendly UX that prevents accidental data loss. | ||
| ## 2026-03-25 - Custom Modal Icon Buttons | ||
| **Learning:** Custom modals often implement manual close buttons (e.g., `XMarkIcon`) that lack native `aria-label`s and `focus-visible` styles against dark backgrounds. | ||
| **Action:** Always verify that all icon-only buttons in custom modal headers receive explicit `aria-label`s and `focus-visible:ring-white` (or contrasting color) combined with `focus:outline-none`. |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While disabling the ESLint rule for
no-explicit-anymakes the linter pass, it's preferable to define a specific type for theparseResultstate. This improves type safety, readability, and long-term maintainability of the component.I suggest defining a local
ParseResultinterface with the properties you're using from the parser's response. You can add this interface definition before theUploadResumeModalcomponent:Then, you can use this type in your
useStatehook and remove theeslint-disablecomment.