Suggestion: Accessibility Agent Persona

Open
#746 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Start by reading the repository’s existing agent list and skill definitions to see how agents are added. Compare those entry points with the linked accessibility-agents project and identify how an accessibility persona could check documentation and code for color vision and screen reader issues. Done means the proposal has a defined integration point and scope; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Description

I really like the list of agents we have here, and I was wondering if I could add my own agent to be used in the skills.
I wanted to use agents that would read the docs and code and check for accessibility issues, such as for colour blinding, screen reader, etc.

Ref: https://github.com/Community-Access/accessibility-agents

What are your thoughts on that?

Thank you in advance

Dominant language
TypeScript
Stars
25.6k
Forks
2.1k
Avg merge
3h 57m
Merged PRs (30d)
170

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 EveryInc/compound-engineering-plugin

All issues in EveryInc/compound-engineering-plugin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.