mruby / mruby/mruby.github.io

Add AccessLint for automated web accessibility testing

Open
#98 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SCSS
Stars
26
Forks
32
PR merge metrics
No merged PRs in 30d

Description

Setup a free plan for open source.

AccessLint brings automated web accessibility testing into your development workflow. When a pull request is opened, AccessLint reviews the changes and comments with any new accessibility issues, giving you quick, timely, and targeted feedback, before code goes live.

AccessLint helps you keep on target with digital accessibility by giving specific, ongoing accessibility feedback to your team. It can catch simple errors that might break your website for your customers with disabilities.

Accessibility guidelines defined in WCAG 2.0 help us build applications that work better for more people. They also give us a rough measure of compliance with legal requirements outlined in the ADA and Section 508. AccessLint runs a growing list of WCAG 2.0 tests, e.g. missing alt attributes that make pages more opaque for screenreader users, positive tabindex values that can create confusion for keyboard users, invalid ARIA, and unlabelled fields.

https://github.com/marketplace/accesslint

Contributor guide

No contributing guide indexed for this repository

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 with the AccessLint Marketplace page linked in the issue and determine how its free open-source plan is enabled for this repository. Done means AccessLint is connected and reviews pull requests for the repository, reporting new accessibility issues.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
accessibility, ci-cd, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.