Skip to content

🎨 Palette: Fix semantic heading hierarchy in Latest Post card#79

Open
NickJLange wants to merge 1 commit intomainfrom
palette-fix-semantic-heading-922177666261906777
Open

🎨 Palette: Fix semantic heading hierarchy in Latest Post card#79
NickJLange wants to merge 1 commit intomainfrom
palette-fix-semantic-heading-922177666261906777

Conversation

@NickJLange
Copy link
Copy Markdown
Contributor

@NickJLange NickJLange commented Mar 15, 2026

💡 What: Fixed semantic heading hierarchy in the Latest Update card on the homepage by changing the nested <h3> tag to an <h4> tag. Added a critical UX learning about semantic headings to .Jules/palette.md.
🎯 Why: Having an <h3> immediately inside another section already introduced with an <h3> ("Latest Update") disrupts the logical document outline, creating confusing navigation for screen reader users expecting correct semantic hierarchy. Changing it to <h4> restores parity.
📸 Before/After: See attached screenshot of the correct heading placement.
♿ Accessibility: Improved semantic HTML hierarchy by ensuring headings are properly incremented, avoiding accessibility violations for screen readers.


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


Summary by cubic

Fixes the semantic heading hierarchy in the homepage Latest Update card by changing the nested post title from <h3> to <h4>, aligning it under the existing <h3> and improving screen reader navigation. Adds an accessibility note to .Jules/palette.md to avoid hardcoded heading levels in reusable components.

Written for commit 97f922b. Summary will update on new commits.

- Changed hardcoded `<h3>` to `<h4>` inside `card__header` of `LatestPost` to properly follow the `<h3>Latest Update</h3>` parent container heading.
- Logged a critical accessibility learning in `.Jules/palette.md` regarding semantic heading structure and avoiding hardcoded, skipped heading levels in reusable UI components.

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