fix (a11y): add accessible name to social buttons and copy button

[virus-rpi]

Changes:

• add aria labels to all blog post social buttons
• add aria label to the copy button
• add translation for these labels

[netlify]

✅ Deploy Preview for satellytes ready!

Name	Link
🔨 Latest commit	dff39c5
🔍 Latest deploy log	https://app.netlify.com/sites/satellytes/deploys/66eaebbbcc33360008b3e725
😎 Deploy Preview	https://deploy-preview-814--satellytes.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 83 (🔴 down 1 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 93 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[hofmann-felix]

Awesome 🚀 I tested the changes with VoiceOver and it works great.

However, I don't feel like approving yet because I have a question about the translation keys: Since the blog is only in English, the keys are unnecessary and potentially misleading. I see there were already other translation keys for the blog before the changes. @satellytes/website-crew Does anyone know if there is a specific reason for this?

[georgiee]

I think it's historical. We aimed to provide a bilingual experience throughout the entire website but for the blog we did not bother to serve translated content and decided to keep it in a single language even though the content is mixed (we redirect people from German to English on this page: https://www.satellytes.com/de/blog/).

I think we can keep the PR as is as the keys are just not used right now - but ideally they are going to be used in a future iteration of the implementation (which is a separate topic). Thanks for pointing this out.

[hofmann-felix]

@georgiee Thanks for the clarification 🙏

Then this PR ist good to go from my side