Fix Accessibility Violation for Slack Community Link

[huangkevin-apr]

Summary

This PR resolves 2 accessibility violations detected by the IBM Equal Access Accessibility Checker. Both violations stem from a single Slack community link element that lacks an accessible name for screen reader users.

Problem

The IBM A11Y Checker identified the following issues:
Hyperlink Without Accessible Name

• Issue: The Slack community link (/community/join-slack) lacks an accessible name
• Rule Violated: Hyperlinks must have an accessible name for their purpose
• Impact: Screen reader users cannot identify the link's purpose or destination
• WCAG Reference: WCAG Success Criterion 2.4.4 (Link Purpose in Context)

Solution

Added an aria-label attribute to provide an accessible name for the link

This change ensures compliance with WCAG 2.1 Level A standards and improves the experience for:

• Screen reader users: Can now identify the link as leading to Slack community
• Keyboard navigation users: Receive proper announcement when focusing the link
• Voice control users: Can reference the link by its accessible name ("Slack")
• All assistive technology users: Understand the link's purpose without visual context

Testing

✅ Both violations resolved in IBM A11Y Checker (2 violations → 0 violations)
✅ Accessible name properly announced by screen readers
✅ No visual or functional changes to the UI
✅ Consistent with accessibility best practices for icon-only links

Fix Before

Fix After

Additional Info

The patch submitted in this PR was generated by A11YRepair, an automated Web Accessibility repair tool that I developed to address common accessibility violations in web applications. The generated fixes were manually reviewed and validated before submission.