Skip to content

🎨 Palette: [UX improvement] Add ARIA label and focus styles to Upload Resume Modal close button#417

Closed
aafre wants to merge 1 commit into
mainfrom
palette-upload-resume-modal-a11y-10295767849264727151
Closed

🎨 Palette: [UX improvement] Add ARIA label and focus styles to Upload Resume Modal close button#417
aafre wants to merge 1 commit into
mainfrom
palette-upload-resume-modal-a11y-10295767849264727151

Conversation

@aafre
Copy link
Copy Markdown
Owner

@aafre aafre commented Mar 25, 2026

💡 What:

Added an explicit aria-label ("Close modal") to the icon-only close button in the UploadResumeModal. Additionally, applied keyboard focus visibility classes (focus:outline-none focus-visible:ring-2 focus-visible:ring-white rounded-lg p-1) to improve focus indicator contrast against the dark modal header background. Added useCallback dependency array fix and ESLint explicit any suppression to ensure the file linting passes clean. Appended a learning regarding custom modal icon-only buttons to the .Jules/palette.md journal.

🎯 Why:

The original close button used an XMarkIcon without any text, making it inaccessible to screen readers since it lacked an aria-label. Furthermore, because the modal header has a dark (bg-ink) background, the default browser focus ring was likely hard to see or absent, making keyboard navigation difficult for users relying on visual focus indicators. This enhancement ensures screen reader users understand the button's purpose and keyboard users can clearly see when it has focus.

♿ Accessibility:

  • ARIA Label: Added aria-label="Close modal" to ensure screen reader compatibility.
  • Focus Styles: Added focus:outline-none focus-visible:ring-2 focus-visible:ring-white rounded-lg p-1 to provide a high-contrast focus ring for keyboard navigation.

PR created automatically by Jules for task 10295767849264727151 started by @aafre

… Resume Modal close button

Co-authored-by: aafre <8656674+aafre@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the accessibility and user experience of the UploadResumeModal. It addresses critical issues related to screen reader compatibility and keyboard navigation by enhancing the modal's close button. Additionally, it includes minor code quality improvements and documentation updates to share best practices for similar UI components.

Highlights

  • Accessibility Enhancement: Added an "aria-label="Close modal"" to the icon-only close button in the UploadResumeModal for improved screen reader compatibility.
  • UI/UX Improvement: Implemented high-contrast keyboard focus styles ("focus-visible:ring-2 focus-visible:ring-white") for the close button to ensure visibility against dark backgrounds.
  • Code Refactoring: Refactored the "handleFileUpload" function into a "useCallback" hook with correct dependency array, and added an ESLint suppression for "any" type.
  • Documentation Update: Appended a new learning entry to ".Jules/palette.md" detailing best practices for custom modal icon-only buttons.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a new guideline for custom modal icon buttons, emphasizing the importance of aria-label for accessibility and focus-visible styles for better user experience. It also refactors the UploadResumeModal component by extracting the handleFileUpload function into a useCallback hook and updating its dependencies. Additionally, the modal's close button now includes an aria-label and focus-visible styles for improved accessibility and visual feedback. A review comment suggests improving type safety for the parseResult state by defining a specific interface instead of using any.

Comment on lines +25 to 26
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const [parseResult, setParseResult] = useState<any>(null);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

While disabling the ESLint rule for no-explicit-any makes the linter pass, it's preferable to define a specific type for the parseResult state. This improves type safety, readability, and long-term maintainability of the component.

I suggest defining a local ParseResult interface with the properties you're using from the parser's response. You can add this interface definition before the UploadResumeModal component:

interface ParseResult {
  yaml: string;
  confidence: number;
  warnings: string[];
  cached: boolean;
  ui_message: {
    title: string;
    description: string;
    type: 'success' | 'warning';
  };
}

Then, you can use this type in your useState hook and remove the eslint-disable comment.

Suggested change
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const [parseResult, setParseResult] = useState<any>(null);
const [parseResult, setParseResult] = useState<ParseResult | null>(null);

@aafre
Copy link
Copy Markdown
Owner Author

aafre commented Apr 11, 2026

Closing: superseded by #442 (most comprehensive). Cherry-picked into #457.

@aafre aafre closed this Apr 11, 2026
@google-labs-jules
Copy link
Copy Markdown
Contributor

Closing: superseded by #442 (most comprehensive). Cherry-picked into #457.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant