Fezzant Scanner ASDR Rule Proposal

Propose a new
ASDR rule

Use this form to submit a candidate rule for the Accessibility-Security Detection Ruleset. Your proposal will be reviewed before inclusion. Fields marked ✦ are required.

Rule identity

Basic metadata used to identify and catalogue the rule.

A short, plain-language name. Write it as a statement of what the rule checks, e.g. "Password field does not suppress autocomplete".

Atomic rules check one specific thing. Composite rules combine multiple atomic rules.

How severe is the barrier created by this issue?

The security or accessibility domain this rule belongs to.

Select any WCAG success criteria this rule maps to. If none apply, the rule will be tagged as ASG (Accessible Security Guidelines).

Describing the issue

Explain the problem clearly. The LLM will use this to understand what it is looking for and why it matters.

Start with "This rule checks…". Keep it to one sentence.

Describe what the problematic pattern looks like in a webpage. Be specific about the element, attribute, or behaviour involved.

Explain the impact from an accessibility-security angle. Who is harmed, and how? Connect the security issue to the accessibility barrier.

Select all user groups who face a barrier from this issue.

Detection guidance

Help the LLM know what to look for, what to ignore, and how confident to be.

Describe specific HTML attributes, element types, text patterns, or ARIA roles that indicate this issue. The more specific, the better.

Describe patterns that look like this issue but are actually acceptable.

How reliably can this issue be detected from a page snapshot?

Any extra caveats the LLM should keep in mind when assessing confidence.

Examples

Provide at least one flagged example and one passing example. HTML snippets are ideal, but plain descriptions work too.

Use real or representative HTML snippets wherever possible. The LLM uses these as positive and negative training signals for this rule.
Flagged example 1
Passing example 1

Remediation

Explain how a developer should fix the issue. Keep it actionable and plain-language.

Write for a developer who has just been told their page has this issue. Be direct and specific.

References

Link to any supporting standards, guidelines, or documentation.

About you

Optional — used for acknowledgments in the final ruleset.

Ready to submit?

Your proposal will be saved for team review, and a copy of the generated JSON will appear below.

GENERATED RULE — ASDR PROPOSAL