🎨 Palette: Improve HTML report table accessibility with row headers - #333
🎨 Palette: Improve HTML report table accessibility with row headers#333seonghobae wants to merge 1 commit into
Conversation
Updates the standalone HTML report generator to use `<th scope="row">` for the first column in data tables instead of standard `<td>` cells. This improves screen reader accessibility by creating a clear semantic relationship between the identifying row header and its corresponding data cells. Also updates base CSS selectors (`thead th, tbody th, td`) to ensure visual parity is maintained and adds `font-variant-numeric: tabular-nums` so that numbers perfectly align vertically across rows.
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Warning Review limit reached
Next review available in: 58 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
중복 정리: Generated by Claude Code |
알겠습니다. 기존 PR(#187)과 중복되는 작업으로 인해 해당 작업이 취소 및 닫혔음을 확인하였습니다. 이에 따라 본 이슈에 대한 작업을 중단하겠습니다. |
This PR introduces a micro-UX and accessibility enhancement to the standalone HTML reports generated by
fast-mlsirm.💡 What
report.pyto output<th scope="row">for the first cell in each row, rather than a generic<td>.thead th), row headers (tbody th), and data cells (td).font-weight: normalontbody thto maintain the existing clean visual hierarchy without unwanted bold text on row headers.font-variant-numeric: tabular-nums;to the base table cell CSS to ensure that numerical digits align perfectly vertically when reading down a column.🎯 Why
<th>elements to announce context as users navigate across data cells. Without row-scoped headers, users reading across a wide table may lose track of which person, item, or candidate they are evaluating.tabular-numsensures that numbers with varying glyph widths (like '1' vs '8') take up the exact same horizontal space, making large columns of diagnostics metrics much easier to scan visually.♿ Accessibility
scope="row"explicitly binds the first cell to the rest of the cells in that<tr>.PR created automatically by Jules for task 7142361684149478452 started by @seonghobae