Skip to content

🎨 Palette: Improve README.md accessibility with presentation roles and hidden decorative images - #152

Open
NITISH-R-G wants to merge 1 commit into
mainfrom
palette/readme-accessibility-11496072763914008391
Open

NITISH-R-G wants to merge 1 commit into
mainfrom
palette/readme-accessibility-11496072763914008391

Conversation

@NITISH-R-G

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

Copy link
Copy Markdown
Owner

💡 What: Converted decorative markdown images to HTML <img> tags with alt="" aria-hidden="true" and added role="presentation" to <table> elements used for multi-column layout.
🎯 Why: Screen readers would previously announce purely visual tables as complex data tables and read out the decorative SVG assets, causing auditory noise and confusion.
♿ Accessibility: Improves the screen reader experience by hiding decorative elements and telling assistive tech to treat layout tables as presentation rather than structured tabular data.
📝 Journaled the learning in .Jules/palette.md.


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

Summary by Sourcery

Improve README accessibility by marking layout tables as presentational and hiding decorative SVG images from assistive technologies.

Enhancements:

  • Replace decorative markdown images in the README with HTML image tags configured as non-announced decorative content for screen readers.
  • Mark HTML tables used for multi-column layout in the README with presentational roles to avoid them being treated as data tables.
  • Document accessibility learnings and conventions for using layout tables and decorative dividers in markdown within .Jules/palette.md.

Documentation:

  • Extend .Jules/palette.md with guidance on accessible use of layout tables and decorative elements in markdown-based profiles.

…d hidden decorative images

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.

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

@sourcery-ai

sourcery-ai Bot commented Aug 11, 2026

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

Reviewer's Guide

This PR improves accessibility of the profile README by converting decorative markdown images to hidden HTML img tags and marking layout tables as presentational, and it updates the Jules journal with the accessibility guideline learned.

File-Level Changes

Change Details Files
Make decorative images in the README inaccessible to screen readers while retaining their visual appearance.
  • Replaced top markdown image syntax with an HTML img tag including empty alt text and aria-hidden="true".
  • Replaced bottom markdown image syntax with an HTML img tag including empty alt text and aria-hidden="true".
README.md
Explicitly mark layout tables in the README as presentational for assistive technologies.
  • Added role="presentation" to the Featured Builds HTML table used for layout.
  • Added role="presentation" to the Now HTML table used for layout.
README.md
Document accessibility learnings and actions around using tables for layout in markdown.
  • Appended a new dated entry describing how multi-column layout tables affect screen readers.
  • Recorded an explicit action item to always add role="presentation" to layout tables in markdown.
.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

@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Accessibility
    • Improved screen reader behavior by marking decorative images as hidden from assistive technologies.
    • Identified layout-only tables so they are not interpreted as data tables.
  • Documentation
    • Added accessibility guidance for using presentation roles with Markdown tables.
    • Updated README examples to reflect accessible image and table markup.

Walkthrough

The README now marks decorative images and layout-only tables for assistive technologies. .Jules/palette.md documents the corresponding accessibility guidance.

Changes

Accessibility markup

Layer / File(s) Summary
README presentation markup
README.md
Decorative images now use empty alt text and aria-hidden="true". The Featured Builds and Now tables now use role="presentation".
Accessibility guidance
.Jules/palette.md
Added guidance for using role="presentation" on visual multi-column layouts.

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

Possibly related PRs

Poem

A rabbit hops through tables bright,
And hides the art from ears of night.
Presentational roles guide the way,
While empty alt text clears the hay.
Accessibility blooms today!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the README accessibility changes and the use of presentation roles and hidden decorative images.
Description check ✅ Passed The description directly explains the README accessibility changes and documents the related learning.
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/readme-accessibility-11496072763914008391

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 left some high level feedback:

  • The new 2024-05-19 entry in .Jules/palette.md is largely duplicative of the existing 2026-06-07 section and appears out of chronological order; consider consolidating the guidance into a single entry or reordering/merging them to avoid repetition.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new 2024-05-19 entry in `.Jules/palette.md` is largely duplicative of the existing 2026-06-07 section and appears out of chronological order; consider consolidating the guidance into a single entry or reordering/merging them to avoid repetition.

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: 2

🤖 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 4-6: Add one blank line before and one blank line after the
heading “2024-05-19 - Adding Accessible Multi-Column Layouts in Markdown” in the
palette documentation, preserving the surrounding content.

In `@README.md`:
- Line 1: Add a top-level Markdown heading containing the README document title
before the decorative Bottom_up.svg image, ensuring the image remains below the
heading and markdownlint MD041 passes.
🪄 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: f94ffc47-0c1f-4f51-88ca-b9a307bc5eba

📥 Commits

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

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

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

(MD022, blanks-around-headings)


[warning] 4-4: 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 (2)
README.md (2)

52-52: LGTM!

Also applies to: 94-94


137-137: LGTM!

Comment thread .Jules/palette.md
Comment on lines +4 to +6
## 2024-05-19 - Adding Accessible Multi-Column Layouts in Markdown
**Learning:** Purely visual `<table>` elements used for multi-column layouts in markdown files (like profile READMEs) can be read as tabular data by screen readers, creating a confusing experience.
**Action:** Always add `role="presentation"` to `<table>` elements that are used purely for layout/presentation purposes to prevent screen readers from announcing them as data tables.

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 blank lines around the new heading.

## 2024-05-19 - Adding Accessible Multi-Column Layouts in Markdown requires one blank line before and after it. markdownlint MD022 reports both missing blank lines.

🧰 Tools
🪛 markdownlint-cli2 (0.23.2)

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

(MD022, blanks-around-headings)


[warning] 4-4: 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 4 - 6, Add one blank line before and one
blank line after the heading “2024-05-19 - Adding Accessible Multi-Column
Layouts in Markdown” in the palette documentation, preserving the surrounding
content.

Source: Linters/SAST tools

Comment thread README.md
@@ -1,4 +1,4 @@
![](assets/Bottom_up.svg)
<img src="assets/Bottom_up.svg" alt="" aria-hidden="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.

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

Add a top-level heading before the decorative image.

README.md starts with an <img> element, so markdownlint MD041 reports that the first line is not a top-level heading. Add the document title before this image, or configure an explicit exception if the banner must remain first.

🧰 Tools
🪛 markdownlint-cli2 (0.23.2)

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

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

🤖 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 `@README.md` at line 1, Add a top-level Markdown heading containing the README
document title before the decorative Bottom_up.svg image, ensuring the image
remains below the heading and markdownlint MD041 passes.

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