adhit-r/fairmind

Frontend: Improve Accessibility & Keyboard Navigation

Open

#103 opened on Nov 5, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (12 forks)auto 404
enhancementfrontendgood first issuehelp wanted

Repository metrics

Stars
 (9 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

Improve accessibility and keyboard navigation across the FairMind frontend application to ensure WCAG 2.1 AA compliance and better user experience for all users.

Why This Is a Good First Issue

  • High impact on user experience
  • Clear guidelines (WCAG 2.1)
  • Good learning opportunity for accessibility
  • Can be done incrementally
  • Well-documented standards

Current State

  • Basic accessibility exists
  • Some keyboard navigation gaps
  • Focus management needs improvement
  • ARIA labels may be missing in some areas

Goals

  1. Keyboard Navigation

    • All interactive elements accessible via keyboard
    • Logical tab order
    • Skip links for main content
    • Keyboard shortcuts where appropriate

  2. Screen Reader Support

    • Proper ARIA labels
    • Semantic HTML
    • Alt text for images
    • Form labels and error messages

  3. Focus Management

    • Visible focus indicators
    • Focus trapping in modals
    • Focus restoration after modal close

  4. WCAG 2.1 AA Compliance

    • Color contrast ratios
    • Text alternatives
    • Keyboard accessible
    • Predictable navigation

Getting Started

  1. Prerequisites

    • Understanding of HTML semantics
    • Basic knowledge of ARIA attributes
    • Familiarity with React/Next.js
    • Accessibility testing tools (axe DevTools, WAVE)

  2. Files to Review

    • apps/frontend-new/src/components/ - Component files
    • apps/frontend-new/src/app/ - Page files
    • Focus on interactive components

  3. Implementation Steps

    • Audit current accessibility (use axe DevTools)
    • Identify keyboard navigation gaps
    • Add ARIA labels where needed
    • Improve focus management
    • Test with screen readers
    • Verify WCAG compliance

  4. Testing

    • Use keyboard only navigation
    • Test with screen readers (NVDA, JAWS, VoiceOver)
    • Run accessibility audits
    • Check color contrast

Acceptance Criteria

  • All interactive elements keyboard accessible
  • Logical tab order throughout application
  • ARIA labels on all interactive elements
  • Focus indicators visible and clear
  • WCAG 2.1 AA compliance verified
  • Screen reader testing completed
  • Documentation updated

Resources

Related

Related to parent issue #133 (Platform Enhancements & User Experience)

Labels

enhancement, help wanted, good first issue, frontend, accessibility

Contributor guide

Research direction
Audit current accessibility using axe DevTools, identify gaps, and implement improvements for keyboard navigation, ARIA labels, focus management, and WCAG 2.1 AA compliance.
Tech stack
javascripttypescriptreactnextjs
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
HTMLCSSARIAReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80