Skip to content

🎨 Palette: Improve screen reader accessibility for layout and decorative elements - #150

Open
NITISH-R-G wants to merge 1 commit into
mainfrom
palette/improve-a11y-readme-10107819504642098085
Open

NITISH-R-G wants to merge 1 commit into
mainfrom
palette/improve-a11y-readme-10107819504642098085

Conversation

@NITISH-R-G

@NITISH-R-G NITISH-R-G commented Aug 10, 2026

Copy link
Copy Markdown
Owner

💡 What: Added role="presentation" to purely visual <table> elements and converted decorative markdown images to <img> tags with alt="" aria-hidden="true".
🎯 Why: To improve accessibility. Using <table> for visual layout grids in Markdown causes screen readers to incorrectly announce them as tabular data. Decorative images without proper aria-hidden attributes create unnecessary noise for visually impaired users.
📸 Before/After: (Visual appearance is unchanged, but DOM is semantically different)
Accessibility: Prevents layout tables and decorative images from polluting the screen reader experience.


PR created automatically by Jules for task 10107819504642098085 started by @NITISH-R-G

Summary by Sourcery

Improve screen reader accessibility by marking layout tables as presentational and converting decorative markdown images to hidden, non-announced HTML images.

Enhancements:

  • Add role="presentation" to visual layout tables in the README to prevent them being announced as data tables by screen readers.
  • Convert decorative markdown images in the README to <img> elements with empty alt text and aria-hidden="true" so they are ignored by assistive technologies.
  • Extend the Jules palette documentation with a new accessibility learning and action item around using presentational roles for layout tables in Markdown.

- Add `role="presentation"` to `<table>` elements used for layout grids to prevent them from being announced as tabular data.
- Convert purely decorative Markdown images to HTML `<img>` tags with `alt=""` and `aria-hidden="true"` to remove screen reader noise.

Co-authored-by: NITISH-R-G <225521762+NITISH-R-G@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.

@sourcery-ai

sourcery-ai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR improves screen reader accessibility by marking layout tables as presentational and converting decorative markdown images into hidden <img> tags, and documents these accessibility guidelines in the internal palette notes.

File-Level Changes

Change Details Files
Convert decorative markdown images to semantic tags that are ignored by screen readers.
  • Replaced top decorative markdown image syntax with including empty alt and aria-hidden attributes.
  • Replaced centered header markdown image with equivalent tag marked decorative.
  • Replaced bottom decorative markdown image markdown syntax with decorative tag.
README.md
Mark layout tables as presentational to avoid being announced as data tables by screen readers.
  • Added role="presentation" to the 'Featured Builds' layout table.
  • Added role="presentation" to the 'Now' layout table.
README.md
Document new accessibility guidelines related to layout tables and decorative images.
  • Added a new learning entry describing screen reader noise from layout tables in markdown.
  • Documented an action guideline to always add role="presentation" to purely visual elements.
    .Jules/palette.md

    Tips and commands

    Interacting with Sourcery

    • Trigger a new review: Comment @sourcery-ai review on the pull request.
    • Continue discussions: Reply directly to Sourcery's review comments.
    • Generate a GitHub issue from a review comment: Ask Sourcery to create an
      issue from a review comment by replying to it. You can also reply to a
      review comment with @sourcery-ai issue to create an issue from it.
    • Generate a pull request title: Write @sourcery-ai anywhere in the pull
      request title to generate a title at any time. You can also comment
      @sourcery-ai title on the pull request to (re-)generate the title at any time.
    • Generate a pull request summary: Write @sourcery-ai summary anywhere in
      the pull request body to generate a PR summary at any time exactly where you
      want it. You can also comment @sourcery-ai summary on the pull request to
      (re-)generate the summary at any time.
    • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
      request to (re-)generate the reviewer's guide at any time.
    • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
      pull request to resolve all Sourcery comments. Useful if you've already
      addressed all the comments and don't want to see them anymore.
    • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
      request to dismiss all existing Sourcery reviews. Especially useful if you
      want to start fresh with a new review - don't forget to comment
      @sourcery-ai review to trigger a new review!

    Customizing Your Experience

    Access your dashboard to:

    • Enable or disable review features such as the Sourcery-generated pull request
      summary, the reviewer's guide, and others.
    • Change the review language.
    • Add, remove or edit custom review instructions.
    • Adjust other review settings.

    Getting Help

@greptile-apps greptile-apps 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.

Your trial has ended. Reactivate Greptile to resume code reviews.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Accessibility
    • Improved screen-reader behavior by marking decorative images and layout tables as presentational.
    • Updated README image markup with explicit paths and empty alternative text for decorative images.
  • Documentation
    • Added guidance for identifying and addressing screen-reader noise caused by purely visual Markdown tables.

Walkthrough

The README now marks decorative images as hidden from assistive technologies and marks visual layout tables as presentation-only. The palette adds guidance for using role="presentation" on visual Markdown tables.

Changes

Accessibility markup

Layer / File(s) Summary
Decorative image semantics
.Jules/palette.md, README.md
README decorative images use HTML <img> elements with explicit paths, empty alt text, and hidden semantics.
Presentation table semantics
README.md, .Jules/palette.md
The Featured Builds and Now tables use role="presentation". The palette documents this accessibility guidance.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

Poem

A rabbit hops through markup bright,
With hidden images out of sight.
The tables wear a clearer role,
While guidance helps the pages whole.
Hop, hop—accessibility takes flight!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main accessibility changes for screen readers, layout tables, and decorative elements.
Description check ✅ Passed The description directly explains the README accessibility changes and their purpose.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch palette/improve-a11y-readme-10107819504642098085

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.

@sonarqubecloud

Copy link
Copy Markdown

@sourcery-ai sourcery-ai 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.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@coderabbitai coderabbitai 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.Jules/palette.md:
- Around line 5-6: Insert a blank line after the new dated heading in the
Markdown section before the “Learning:” paragraph to satisfy the MD022
heading-spacing requirement.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4231047c-11be-4634-875e-1fb8bdf2e4ca

📥 Commits

Reviewing files that changed from the base of the PR and between f25f98b and 08b29d8.

📒 Files selected for processing (2)
  • .Jules/palette.md
  • README.md
📜 Review details
🧰 Additional context used
🪛 markdownlint-cli2 (0.23.2)
.Jules/palette.md

[warning] 5-5: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

README.md

[warning] 1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🔇 Additional comments (3)
README.md (3)

1-1: 📐 Maintainability & Code Quality

Resolve or document the first-line heading warning.

markdownlint-cli2 reports MD041 because README.md starts with an image instead of a top-level heading. If this rule is enforced, add a top-level heading before the image. Otherwise, document an exception so the intentional visual layout remains unchanged.

Source: Linters/SAST tools


3-5: LGTM!

Also applies to: 137-137


52-52: LGTM!

Also applies to: 94-94

Comment thread .Jules/palette.md
Comment on lines +5 to +6
## 2026-08-10 - Screen Reader Noise from Layout Tables in Markdown
**Learning:** Using `<table>` elements for visual layout grids in Markdown causes screen readers to announce them as tabular data, creating significant noise for visually impaired users.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add a blank line after the new heading.

markdownlint-cli2 reports MD022 because Line 5 is immediately followed by the **Learning:** paragraph on Line 6.

Proposed fix
 ## 2026-08-10 - Screen Reader Noise from Layout Tables in Markdown
+
 **Learning:** Using `<table>` elements for visual layout grids in Markdown causes screen readers to announce them as tabular data, creating significant noise for visually impaired users.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## 2026-08-10 - Screen Reader Noise from Layout Tables in Markdown
**Learning:** Using `<table>` elements for visual layout grids in Markdown causes screen readers to announce them as tabular data, creating significant noise for visually impaired users.
## 2026-08-10 - Screen Reader Noise from Layout Tables in Markdown
**Learning:** Using `<table>` elements for visual layout grids in Markdown causes screen readers to announce them as tabular data, creating significant noise for visually impaired users.
🧰 Tools
🪛 markdownlint-cli2 (0.23.2)

[warning] 5-5: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.Jules/palette.md around lines 5 - 6, Insert a blank line after the new
dated heading in the Markdown section before the “Learning:” paragraph to
satisfy the MD022 heading-spacing requirement.

Source: Linters/SAST tools

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