Skip to content

🎨 Palette: Update heading level for Latest Update card#82

Open
NickJLange wants to merge 1 commit intomainfrom
palette-semantic-headings-17558020667341023800
Open

🎨 Palette: Update heading level for Latest Update card#82
NickJLange wants to merge 1 commit intomainfrom
palette-semantic-headings-17558020667341023800

Conversation

@NickJLange
Copy link
Copy Markdown
Contributor

@NickJLange NickJLange commented Mar 22, 2026

💡 What:

Updated the <h3> tag in the LatestPost card's header to an <h4>. Also added an entry to .Jules/palette.md noting the importance of semantic heading hierarchies in reusable components.

🎯 Why:

The "Latest Update" section already uses an <h3> heading. Having the nested card's title also be an <h3> breaks the logical document outline and semantic navigation structure for screen reader users, who rely on heading levels to understand context.

📸 Before/After:

The visual presentation has not changed because the class-based styling handles the appearance. However, the raw HTML now correctly nests the post title <h4> under the section title <h3>.

♿ Accessibility:

Improved semantic HTML hierarchy for screen reader navigation by ensuring headings increment logically.


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


Summary by cubic

Updated the nested post title in the homepage "Latest Update" card from <h3> to <h4> to keep a correct heading hierarchy under the section’s <h3>. Improves screen reader navigation with no visual changes, and adds a note on semantic headings to .Jules/palette.md.

Written for commit ad3c200. Summary will update on new commits.

Updated the `<h3>` heading level to an `<h4>` in the nested card for the "Latest Update" section on the homepage. This fixes a semantic HTML issue where the nested title didn't increment correctly, improving the logical document outline for screen reader accessibility. Also appended the UX learning to `.Jules/palette.md`.

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