koddsson / koddsson/accessibility-scanner

Implement descriptiveness ACT rules (5 rules)

Open
#385 0 comments 0 reactions 0 assignees View on GitHub
out-of-scope: heuristic
Dominant language
TypeScript
Stars
11
Forks
2
Avg merge
3d 6h
Merged PRs (30d)
11

Description

## ACT rules requiring semantic/subjective evaluation

| ACT Rule | Name |
|---|---|
| `b49b2e` | Heading is descriptive |
| `c4a8a4` | HTML page title is descriptive |
| `cc0f0a` | Form field label is descriptive |
| `5effbb` | Link in context is descriptive |
| `aizyf1` | Link is descriptive |

## Blocker
These rules require understanding whether text is *descriptive enough* — a subjective judgment that cannot be reliably automated with DOM inspection alone. An LLM-based approach could work but would add significant complexity and a non-deterministic dependency.

Related to #350.

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the five listed ACT rules and the discussion in related issue #350 first. The work is complete only when all five descriptiveness rules are implemented, but the issue does not define an objective evaluation approach for their subjective requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
accessibility, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.