fix(web): add discernible text to landing page links

[yanthomasdev]

This PR adds discernible text to the landing page links. Currently, assistive technologies don't have any textual cue of what the images mean, so an sr-only span was added with "home", for the home page link in the React Email logo, and the name of the service for the integration section links. This is a necessary change to comply with WCAG's Sucess Criterion 1.4.2 - Name, Role Value (Level A).

Fun fact, some assistive technologies (like NVDA) workaround this missing information using the link's href and the page's title metadata, so they actually read these links fine in my main screen reader, but it's always nice to go with the most compatible approach to ensure wider compatibility and reap the SEO and AI benefits as well.

I am making this PR against main based on the contributing guide's instructions, since my last PR was merged into canary I believe it did not trigger a new deploy for the app.

---

Summary by cubic

Add sr-only labels to the home logo link and each integration link so screen readers announce meaningful labels. Improves accessibility and aligns with WCAG’s Name, Role, Value.

^{Written for commit 9a152c3. Summary will update on new commits.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9a152c3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@yanthomasdev is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

[cubic-dev-ai]

No issues found across 2 files

[gabrielmfern]

We're actually going to change that workflow of merging to main directly, mainly because want to avoid bringing in changes from main to canary, so I'm going to merge this into canary and move it to main in a bit. Again, thank you!