🎨 Palette: Add ARIA labels to dynamic matrix grids - #4389
Conversation
Added descriptive `aria-label` attributes to the matrix and vector input fields in `ReferenceFrameConverter.tsx` and `RotationConverter.tsx` to provide necessary context for screen reader users, as standard `<label>` elements are impractical for dense matrix layouts. Co-authored-by: dieterolson <198168927+dieterolson@users.noreply.github.com>
|
👋 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. |
💡 What: Added dynamic
aria-labelattributes to the matrix and vector input fields inReferenceFrameConverter.tsxandRotationConverter.tsx.🎯 Why: Dynamic input grids are completely inaccessible to screen reader users without explicit labels for each cell. Because standard
<label>elements are impractical for dense matrix layouts,aria-labelprovides the necessary context.📸 Before/After: Inputs for matrices and vectors had no screen reader announcements. Now they clearly announce their mathematical component (e.g. "Transform matrix row 1, column 1", "Twist component ωx", or "Quaternion component W").
♿ Accessibility: Significantly improves screen reader navigation by explicitly associating matrix cells and vector elements with their contextual meaning.
PR created automatically by Jules for task 3953280844180552522 started by @dieterolson