MarkusJohansen/ChimeraCSS

馃И Automated accesibility testing

Open

#100 opened on Jan 15, 2024

View on GitHubContributor guide
聽(3 comments)聽(0 reactions)聽(1 assignee)SCSS聽(3 forks)auto 404
Automation & PipelineTestinghelp wanted

Repository metrics

Stars
聽(25 stars)
PR merge metrics
聽(PR metrics pending)

Description

Is your feature request related to a problem? Please describe. We should have some sort of automated accesibility testing through axe, or google lighthouse

Contributor guide

Research direction
Investigate the project's CI configuration and add an automated accessibility testing step using tools like axe core or Lighthouse.
Tech stack
css
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-3 hours
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
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65