RuleID 6a7281 - map to 4.1.2 - ARIA state or property has valid value

[philljenkins]

ACT should not suppport rules that don't map to WCAG Success Criteria (e.g. none)
When tools report implementations, reporting against "none" too often will/has diluted the effectiveness of the rules, its reputation, and more importantly credibility and understanding of the accessibility requirements. Even recommendations by the tool should map to a success critera topic.

4.1.2 was designed to be used to report against custom ARIA widgets where attribute values are defined incorrectly. If ARIA is not defined correctly, then assistive technology can have determintal effects for users.
Success Criteria 4.1.2 about programmatically determined; states, properties, and values, which also includes that the states, properties, and values are correct/valid, not simply determinable alone by the AT.

Proposed
RuleID 6a7281
ARIA state or property has valid value
https://wai-wcag-act-rules.netlify.app/standards-guidelines/act/rules/6a7281/proposed/

• ACT should report 4.1.2 (vs none)
  

[WilcoFiers]

There is nothing about ACT rules that require they map to WCAG success criteria. Some rules, like those that require correct use of ARIA are useful for accessibility testing, even if they aren't strictly required for WCAG.

That said, there is a bit of an oddity around this particular scenario. Incorrect use of ARIA often does cause problems under 4.1.2. The ACT Rules Format currently has no way to report this, but the ACT Task Force is exploring how in version 1.1 we might be able to report such issues. If you're interested, you can see that work happening here: w3c/wcag-act#531