Skip to content

🎨 Palette: Fix heading hierarchy in nested UI cards#84

Open
NickJLange wants to merge 1 commit intomainfrom
palette-heading-hierarchy-14610081192161817067
Open

🎨 Palette: Fix heading hierarchy in nested UI cards#84
NickJLange wants to merge 1 commit intomainfrom
palette-heading-hierarchy-14610081192161817067

Conversation

@NickJLange
Copy link
Copy Markdown
Contributor

@NickJLange NickJLange commented Mar 29, 2026

💡 What: Changed the <h3> wrapping the post title inside the "Latest Update" card to an <h4> in src/components/HomepageContent/index.js.
🎯 Why: To improve semantic heading hierarchy. The "Latest Update" section itself is an <h3>. Nesting another <h3> immediately inside it for the card title disrupts the logical document outline, making it confusing for screen reader users navigating by headings.
Accessibility: This directly improves accessibility by ensuring heading levels correctly increment, allowing screen readers to accurately represent the relationship between the section and its contents.
📝 Journal Entry: A new critical learning regarding heading hierarchy in nested UI components was added to .Jules/palette.md.


PR created automatically by Jules for task 14610081192161817067 started by @NickJLange


Summary by cubic

Fixed the heading hierarchy in the “Latest Update” card by changing the post title from h3 to h4. This keeps the outline under the section’s h3 and improves screen reader navigation.

Written for commit 6e26451. Summary will update on new commits.

- Changed the `<h3>` wrapping the post title in the "Latest Update" card to an `<h4>`.
- This fixes an accessibility issue where nested cards were using the same heading level as their parent section, disrupting the logical document outline for screen reader users.
- Added a new entry to the `.Jules/palette.md` journal detailing this learning.

Co-authored-by: NickJLange <1529105+NickJLange@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.

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

No issues found across 2 files

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