Predictify-org / Predictify-org/predictify-frontend

[GrantFox][Medium] Make prediction cards accessible without color dependence

Open
#881 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

GrantFox OSS Maybe Rewarded priority:medium Third Campaign
Dominant language
TypeScript
Stars
4
Forks
194
Avg merge
15h 38m
Merged PRs (30d)
23

Description

Summary

Make prediction cards accessible without color dependence

Why this matters

Market status, probability, and outcome affordances must work for keyboard and screen-reader users.

Scope

Add semantic labels, focus order, text alternatives, and contrast-safe states.

Acceptance criteria

  • Every probability/status has a textual equivalent.
  • Keyboard users can inspect and activate actions.
  • Focus is visible and preserved.
  • Automated accessibility tests cover active, closed, and settled states.

Validation

Add regression coverage for existing behavior, failure modes, authorization boundaries, and compatibility. The implementation must pass the repository CI checks.

Non-goals

  • Typo-only, formatting-only, or documentation-only changes.
  • Unrelated refactors or dependency upgrades.
  • Weakening existing security, authorization, CI, or production safeguards.

Contributor application

Before implementation, comment with relevant experience, a 1–4 bullet approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding.

PR requirements

Use a feature branch, include Closes #<issue-number>, check every acceptance criterion, link criteria to code/tests, explain security and failure-mode considerations, and pass CI.

Reward-readiness

This is a substantive GrantFox campaign issue. Merge and CI success do not by themselves guarantee reward eligibility; final reward-readiness is determined by campaign review.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the prediction card components and the existing accessibility test setup. Trace active, closed, and settled states, then define coverage for textual equivalents, keyboard activation, visible focus, and contrast-safe states. Done means all acceptance criteria are covered by regression tests and the repository CI checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
accessibility, frontend, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.