Open tbostic32 opened 1 year ago
While we could hold the conversation here, there are so many discussion points that I think it would be best if we could put them in the discussion here (https://github.com/act-rules/act-rules.github.io/discussions/2046) where it will be more organized.
The task force is currently drafting up changes that may be made in the next version of the ACT format. The rule below shows some examples of new features we have discussed including in the new format as a way to begin discussions. For this rule, the main discussion points are given below:
<elements that will become the test targets>
, where<element condition is met>
after<action taken by tester>
.acttfNextAction
that should be called on thedocument
element until it returns false. Some sample code for a 2 step example is included below (I unrolled the loop, in actuality you would loop until it returns false).See https://github.com/act-rules/act-rules.github.io/issues/1953 for the discussion leading up to this example rule.
id: name: Status Messages are Announced to User rule_type: atomic description: | This rule checks that status messages use a live region role or aria-live to notify users. accessibility_requirements: # Remove whatever is not applicable wcag20:4.1.3: # (A | AA | AAA)
forConformance: true
failed: not satisfied
passed: further testing needed
inapplicable: further testing needed
aria12:live_region_roles: #
title: 5.3.5 Live Region Roles
forConformance: false
failed: not satisfied
passed: further testing needed
inapplicable: further testing needed
input_aspects:
Wilco Fiers
Applicability
For each [HTML element] containing [visible text], where this text appeared after the [activation] of an [HTML element] with one of the following roles:
Exceptions (NEW SECTION! SEE COMMENTS ABOVE)
Expectation
Each test target must meet one of the following criteria:
alert
,status
,log
, ortimer
.aria-live
attribute where the value is eitherpolite
orassertive
Assumptions
There are no assumptions.
Accessibility Support
There are no accessibility support issues known.
Background
The list of applicable semantic roles is derived by taking all the ARIA 1.1 roles that:
The Exceptions in the applicability are derived from the WCAG 2.1. definition of status messages
Test Cases
Passed
Passed Example 1
A success status message becomes visible after successfully completing the form. The status message is available to AT through the use of
role=status
.Passed Example 2
Status messages about the progress of the NASA launch progress are displayed and available to AT through the use of
role="log"
.Failed
Failed Example 1
A success status message becomes visible after successfully completing the form, but the status message is not available to AT since no live region role or
aria-live
attribute is used.Failed Example 2
Status messages about the progress of the NASA launch progress are displayed as [visible text], but are not available to AT since no live region role or
aria-live
attribute is used.Inapplicable
Inapplicable Example 1
The example shows updates to stock, which falls under the Not a Status Message exception.
Inapplicable Example 2
Focus is placed on the status message when the form is submitted, which falls under the Text Receives Focus exception to the applicability.