🎨 Palette: accessibility and UX improvements to README.md

[Moohan]

💡 What:

• Updated tooltips for social links (ORCID, Mastodon, Bluesky) to be more descriptive and correctly placed on the link element.
• Added "(deprecated)" text to the phssensitivitylabels link.
• Moved tooltip title for Skill Icons to the link element and updated it to "Visit skillicons.dev".
• Redirected GitHub stats cards to the user's profile instead of the tool's repository and fixed tooltip placement.

🎯 Why:

• Improve the intuitiveness and accuracy of interactions (tooltips describing destination, links going to expected profile).
• Ensure that screen reader users are aware of the deprecated status of a project.

📸 Before/After:

• Tooltips now appear on the link, describing the destination.
• Clicking GitHub stats now takes you to the user's profile.
• Explicit "(deprecated)" text added.

♿ Accessibility:

• Added explicit textual confirmation for deprecated status.
• Ensured tooltips describe link destinations, which is beneficial for both visual and screen reader users.

---

PR created automatically by Jules for task 6197350914072018308 started by @Moohan

Summary by Sourcery

Improve README and internal documentation for clearer, more accessible link tooltips and profile navigation.

Enhancements:

• Clarify that the phssensitivitylabels project is deprecated in the projects list.
• Update skillicons, GitHub stats, and social profile links so tooltips describe the destination and stats cards link to the user profile.
• Document best practices for placing Markdown link tooltips in the internal palette guide.

Summary by CodeRabbit

Documentation

• Improved tooltip handling for linked images in profiles
• Updated project deprecation information
• Profile and stats badges now link to GitHub profile
• Added guidance on markdown link tooltip placement

[google-labs-jules]

👋 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]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR refines Markdown link and tooltip usage in the README to improve accessibility and UX, ensuring tooltips describe link destinations, deprecated status is explicit, and image links point to the expected user profile, while documenting the learning in the palette notes.

File-Level Changes

Change	Details	Files
Adjust tooltip placement for linked images so titles describe the destination link rather than the image.	Move the skillicons tooltip title from the image element to the wrapping link and update the text to "Visit skillicons.dev" Remove title attributes from GitHub stats images and add descriptive titles to the surrounding profile links	README.md
Clarify link destinations and deprecated status in project and social links.	Append explicit "(deprecated)" text to the phssensitivitylabels project reference while keeping the strikethrough formatting Update ORCID, Mastodon, and Bluesky shield links so tooltips live on the link elements and describe visiting James Hayes's profiles	README.md
Capture new accessibility learning about Markdown link tooltip placement in the palette documentation.	Add a dated note explaining why title attributes should be placed on the link wrapper for image links Document an actionable guideline to always put descriptive tooltips on the outer link element when using linked images 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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Walkthrough

Updates documentation and README to standardise tooltip placement on anchor elements rather than image elements when displaying linked images, alongside updating badge links to point to GitHub profile pages and adding deprecation notices.

Changes

Cohort / File(s)	Summary
Tooltip Placement Guidance .Jules/palette.md	Adds new dated section documenting best practice for Markdown link tooltip placement: place title tooltips on outer link elements rather than on images themselves when using linked images.
Tooltip and Link Updates README.md	Relocates title attributes from image elements to their parent anchor elements across Skills, GitHub Stats, Contact sections; updates badge links to point to GitHub profile page; adds "(deprecated)" notation to phstemplates entry; removes title attributes from image elements whilst updating anchor titles to reflect profile view destinations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• 🎨 Palette: Add tooltips to social media badges #8: Modifies tooltip/title attributes for social and profile badges in README, addressing the same tooltip placement concern across badge elements.
• 🎨 Palette: Make skill icons a clickable link #35: Documents and implements the practice of placing title tooltips on outer anchor elements when using linked images, directly corresponding to the guidance added in the palette file.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title mentions accessibility and UX improvements to README.md, which aligns with the actual changes in the pull request; however, it does not accurately reflect that changes were also made to .Jules/palette.md.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch palette-readme-ux-improvements-6197350914072018308

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider moving the '(deprecated)' text outside the strikethrough (e.g., ~~phssensitivitylabels~~ (deprecated)) so that the deprecated status remains visually and semantically clear, especially for assistive technologies that may handle struck-through text differently.
• Some of the new link titles repeat visible link text almost verbatim; you might simplify or tailor them (e.g., adding brief context like 'Open skillicons.dev in a new tab') to provide additional value beyond what is already on screen.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider moving the '(deprecated)' text outside the strikethrough (e.g., `~~phssensitivitylabels~~ (deprecated)`) so that the deprecated status remains visually and semantically clear, especially for assistive technologies that may handle struck-through text differently.
- Some of the new link titles repeat visible link text almost verbatim; you might simplify or tailor them (e.g., adding brief context like 'Open skillicons.dev in a new tab') to provide additional value beyond what is already on screen.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}