In evaluating this library I ran a couple of tests and one in particular keeps coming up as a failure and I don't understand what the AMA related guidance is for enforcing this rule.
The following allowed roles are in pressable-role-required:
In our use case, we have a TS component that contains a Pressable that accepts children, and both role and state are defined, yet this test fails and the output is confusing as it seems to complain on the one hand the role is not valid, but the other failing assertion picks up on the checkbox role:
Why is this specific set of roles allow-listed, while others like checkbox are not?
Looks like this is somewhat related to #256 but I am still curious about the rule. I noticed some other implementation details, however, in our component that could be causing this to fail as well.
In evaluating this library I ran a couple of tests and one in particular keeps coming up as a failure and I don't understand what the AMA related guidance is for enforcing this rule.
The following allowed roles are in pressable-role-required:
In our use case, we have a TS component that contains a Pressable that accepts children, and both role and state are defined, yet this test fails and the output is confusing as it seems to complain on the one hand the role is not valid, but the other failing assertion picks up on the checkbox role:
Why is this specific set of roles allow-listed, while others like checkbox are not?