Help - What to Do for 2.1.1 needs suggestive guidance, if applicable #3889

[aliunwala]

We saw in a user session Needs Review help for 2.1.1. It did not include suggestive guidance - e.g. Decide if the element should be in the tab chain - before telling them to fix it.

[aliunwala]

From Triage: We need better help text in the "What to do" section

[mbgower]

From the partial screen shot, it's difficult to judge what the issue is. The partial screenshot shows an anchor element, which does take a tabstop, so the message appears to contradict the element location. However, it is likely a result of a partial element (maybe it has an explicit tabstop?).

So task should be for a SME to examine the rule, determine if the rule is sound, and if so, adjust the documentation to address the issue. If investigation shows it is a problem with the underlying rule, escalate to dev.

[philljenkins]

Should be simple Help change to add guidance to the developer to:

• decide 1st if the element should be tabbable (in the tab chain)
• and then do this to add to the tab chain

[philljenkins]

RuleID: widget_tabbable_exists group message: Component must have at least one tabbable element Reason ID: fail_no_tabbable fail message: Component with "{0}" role does not have a tabbable element

[philljenkins]

Testing reference:

The following test cases will trigger rule help:

• widget-button-tabbable.html No fail examples.
• widget-link-tabbable.html 3 fail examples.
• widget-radio-tabbable.html No fail examples.

[philljenkins]

@shunguoy please send me a screenshot of the help so I can verify the formatting. RuleID: widget_tabbable_exists

[philljenkins]

The formatting is good, but "What to do" is too verbose and repeats what's in "About this requirement", so deleting the last line. ~~Refer to the ARIA practices - Developing a Keyboard Interface for more information on how to manage keyboard focus.~~

[ErickRenteria]

Good to go