Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking Issue - Accessibility Review: Bounties Landing Page #1040

Open
3 of 9 tasks
jason-me opened this issue Feb 7, 2025 · 1 comment
Open
3 of 9 tasks

Tracking Issue - Accessibility Review: Bounties Landing Page #1040

jason-me opened this issue Feb 7, 2025 · 1 comment

Comments

@jason-me
Copy link
Contributor

jason-me commented Feb 7, 2025

Accessibility Review: Bounties Landing Page - WIP

URL: https://community.sphinx.chat
Objective: Identify and track accessibility issues on the Bounties Landing Page.

Applicable Guidelines: WCAG 2.2 & WAI-ARIA 1.2 as baseline; APCA & ISO 9241-171 supplemental

📌 Identified Issues:

  • Lack of visible keyboard focus on controls (Issue #1042)
  • Hamburger nav "menu" button missing required properties and states (e.g.aria-expanded) (Issue #1044)
  • Missing Landmark Regions (Banner, Main, Nav in footer, etc.) (Issue #1045)
  • Low contrast on CTA buttons (Fails both WCAG2 & APCA) (Issue #1046)
  • "Sign in" button name, role, value and focus order issues (Issue #1047)
  • Incorrect alt text for card images (Issue #1048)
  • List markup missing from nav content (header, footer, expanded mobile) (Issue #1049)
  • Lack of audio description or transcript for video (Issue #1050)
  • Auto-playing audio/video (Best Practice) (Issue #1051)

🔄 Next Steps:

  1. Create individual issues for each item above and link them here.
  2. Implement fixes based on acceptance criteria.
  3. Review and validate changes.
@jason-me
Copy link
Contributor Author

jason-me commented Feb 9, 2025

@humansinstitute - I am clear to start most of these with the exception of the contrast issue which will likely require a design decision and the audio description, which may involve professionally recording audio.

I have already written up code changes for the visible focus issues and sign-in button from a PR that was super-ceded that I can re-purpose.

  • Lack of visible keyboard focus on controls (Issue #1042)
  • "Sign in" button name, role, value and focus order issues (Issue #1047)

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

No branches or pull requests

1 participant