Skip to content

🎨 Palette: Improve accessibility of filter buttons in coverage view#537

Draft
EffortlessSteven wants to merge 1 commit into
mainfrom
jules-12563686999770006565-6f46dd95
Draft

🎨 Palette: Improve accessibility of filter buttons in coverage view#537
EffortlessSteven wants to merge 1 commit into
mainfrom
jules-12563686999770006565-6f46dd95

Conversation

@EffortlessSteven

Copy link
Copy Markdown
Member

💡 What:
Added dynamic aria-pressed states to the "All", "Passing", "Failing", and "Unknown" filter buttons in the Acceptance Criteria Coverage view. Also improved the search input by changing its type to search and adding an aria-label. The changes were applied to both crates/app-http/src/platform/ui.rs and crates/http-platform/src/ui.rs to maintain consistency.

🎯 Why:
The filter buttons visually indicated their active state via a CSS class (.active), but this state was completely hidden from screen readers. By adding aria-pressed, assistive technologies can now accurately convey which filter is currently applied. The search input was also lacking an accessible name.

📸 Before/After:
(Visuals remain unchanged, screen reader experience significantly improved)

♿ Accessibility:

  • Filter buttons now communicate their toggle state via aria-pressed.
  • Screen readers will announce the active filter.
  • Search input is now properly identified as a search landmark with a clear label.
  • Logged learning regarding Maud's limitations with conditional boolean attributes in .jules/palette.md.

PR created automatically by Jules for task 12563686999770006565 started by @EffortlessSteven

- Add aria-pressed state to coverage filter buttons
- Dynamically update aria-pressed using JS
- Improve accessibility of search box with type="search" and aria-label
- Mirror changes across both UI component files
@google-labs-jules

Copy link
Copy Markdown

👋 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.

@coderabbitai

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@EffortlessSteven, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e899b371-131c-4dae-b466-7e2b660398ec

📥 Commits

Reviewing files that changed from the base of the PR and between 3debe49 and 68e8881.

📒 Files selected for processing (3)
  • .jules/palette.md
  • crates/app-http/src/platform/ui.rs
  • crates/http-platform/src/ui.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jules-12563686999770006565-6f46dd95

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Copy link
Copy Markdown

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 improves the accessibility of the Acceptance Criteria Coverage UI by adding aria-pressed attributes to the filter buttons, updating them dynamically via JavaScript, and adding an aria-label and type="search" to the search input. The feedback recommends adding safety checks to ensure that document.getElementById does not throw a runtime TypeError if it returns null when retrieving the active filter button.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment on lines +696 to +698
const activeBtn = document.getElementById('filter-' + status);
activeBtn.classList.add('active');
activeBtn.setAttribute('aria-pressed', 'true');

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

If document.getElementById returns null (e.g., due to an unexpected status or DOM state), calling classList.add or setAttribute directly on activeBtn will throw a runtime TypeError and halt subsequent JavaScript execution. Adding a safety check ensures the script fails gracefully.

Suggested change
const activeBtn = document.getElementById('filter-' + status);
activeBtn.classList.add('active');
activeBtn.setAttribute('aria-pressed', 'true');
const activeBtn = document.getElementById('filter-' + status);
if (activeBtn) {
activeBtn.classList.add('active');
activeBtn.setAttribute('aria-pressed', 'true');
}

Comment on lines +771 to +773
const activeBtn = document.getElementById('filter-' + status);
activeBtn.classList.add('active');
activeBtn.setAttribute('aria-pressed', 'true');

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

If document.getElementById returns null (e.g., due to an unexpected status or DOM state), calling classList.add or setAttribute directly on activeBtn will throw a runtime TypeError and halt subsequent JavaScript execution. Adding a safety check ensures the script fails gracefully.

Suggested change
const activeBtn = document.getElementById('filter-' + status);
activeBtn.classList.add('active');
activeBtn.setAttribute('aria-pressed', 'true');
const activeBtn = document.getElementById('filter-' + status);
if (activeBtn) {
activeBtn.classList.add('active');
activeBtn.setAttribute('aria-pressed', 'true');
}

@github-actions

Copy link
Copy Markdown

Test Results

283 tests   245 ✅  11m 49s ⏱️
 25 suites   38 💤
  1 files      0 ❌

Results for commit 68e8881.

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