A11Y Lint

B 81 completed
Cli Tool
web_app / json · tiny
44
Files
11,091
LOC
2
Frameworks
8
Languages

Pipeline State

completed
Run ID
#359352
Phase
done
Progress
1%
Started
Finished
2026-04-13 01:31:02
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
60.80
Framework unique
Isolation
Last stage change
2026-05-10 03:35:24
Deduplication group #54458
Member of a group with 6 similar repo(s) — canonical #83492 view group →
Top concepts (2)
Project DescriptionWeb Frontend
Source: Repobility analyzer · https://repobility.com

AI Prompt

Create an accessibility linter tool, similar to a11y-lint, that checks CLI output to ensure error messages follow accessible patterns. I need it to validate things like line length, avoiding ALL-CAPS, and ensuring error messages include "why" and "fix" context. The tool should support checking against WCAG rules and general policy rules. Since it's a CLI tool, I'd like to see examples of how to gate CI pipelines based on specific rule failures, rather than just letter grades. Please structure the project using Python and ideally include documentation in multiple languages like Japanese, Chinese, and Spanish.
python cli accessibility linter web-app testing json markdown
Generated by gemma4:latest

Catalog Information

a11y-lint is an accessibility linter that checks if error messages in CLI output follow accessible patterns.

Description

a11y-lint is a tool designed to validate the accessibility of Command Line Interface (CLI) output. It ensures that error messages conform to established accessible patterns, making it easier for users with disabilities to navigate and understand the output. This tool is particularly useful in environments where CLI output is critical, such as in development workflows or automated testing scenarios.

الوصف

هذا الأداة مصممة لتحقق من إصلاحات الوصول في خروجات واجهة السطر الأوامر. يضمن أن رسائل الخطأ تتوافق مع الأنماط الموصى بها، مما يجعلها سهلة للناس ذوي الإعاقة للتنقل والفهم. هذه الأداة مفيدة بشكل خاص في البيئات التي تعتمد على خروجات واجهة السطر الأوامر، مثل تدفقات التطوير أو اختبارات تلقائية.

Novelty

5/10

Tags

accessibility error-messages cli-output validation linting

Technologies

click rich

Claude Models

claude-opus-4.6 claude-opus-4.5

Quality Score

B
80.8/100
Structure
86
Code Quality
75
Documentation
68
Testing
85
Practices
80
Security
100
Dependencies
60

Strengths

  • CI/CD pipeline configured (github_actions)
  • Good test coverage (80% test-to-source ratio)
  • Code linting configured (ruff (possible))
  • Consistent naming conventions (snake_case)
  • Good security practices \u2014 no major issues detected
  • Properly licensed project

Weaknesses

  • 232 duplicate lines detected \u2014 consider DRY refactoring

Recommendations

  • Address 34 TODO/FIXME items \u2014 consider tracking them as issues

Security & Health

12.6h
Tech Debt (C)
A
OWASP (100%)
PASS
Quality Gate
A
Risk (3)
Repobility · MCP-ready · https://repobility.com
MIT
License
4.1%
Duplication
Full Security Report AI Fix Prompts SARIF SBOM

Languages

json
56.8%
python
25.7%
markdown
14.4%
yaml
1.6%
typescript
0.7%
toml
0.7%
javascript
0.1%
css
0.0%

Frameworks

Astro pytest

Concepts (2)

Generated by the Repobility scanner · https://repobility.com
CategoryNameDescriptionConfidence
Repobility (the analyzer behind this table) · https://repobility.com
auto_descriptionProject DescriptionLow-vision-first accessibility linting for CLI output. Validates that error messages follow accessible patterns with the [OK]/[WARN]/[ERROR] + What/Why/Fix structure.80%
auto_categoryWeb Frontendweb-frontend70%

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/83496.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV