Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add skill - Accessibility checks infrastructure setup

Closed
#35 0 comments 1 reaction 1 assignee View on GitHub

@lukasmatta is already working on this.

Since Aug 31, 2026.

  • #38 by @lukasmatta — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cypress, javascript, playwright, python
Domain
testing-qa

Research direction

No specific files or tests are named in the issue. Start by locating the existing skill definitions and registration entry points in this repository, then inspect how existing test-setup skills are implemented and documented. Add the accessibility infrastructure skill in the same pattern using Playwright/Axe, and include setup/run/reporting guidance in the docs. Completion looks like a wired skill path plus user-facing documentation and a documented check sample.

Written by the indexing model from the issue text.

Description

Summary

In some of our projects, we've set up accessibility check infrastructure to validate the UI's compliance with the WCAG 2.2 AA standard.

It would be beneficial to introduce an agentic skill that makes it easy to set up such infrastructure within a new UI project.

Proposed Scope (high-level, to be refined)

  • The skill should check the existing testing infrastructure (Playwright, Cypress, etc.)
  • Based on the findings, it should introduce Playwright + Axe Core
  • It should add a sample accessibility check and validate that it passes
  • It should document the setup (e.g., how to run the checks, where results/reports are generated) so users can pick it up easily

Out of Scope

Accessibility test creation - this should be handled as a separate skill, distinct from infrastructure setup

Dominant language
Python
Stars
1
Forks
0
Avg merge
20d 22h
Merged PRs (30d)
1

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.

More from AbsaOSS/agentic-toolkit

All issues in AbsaOSS/agentic-toolkit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.