You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Picking up on this comment from @JAWS-test, considering the reluctance to concede any notion of accuracy or correctness in 3.3.2, what does that imply for instructions? As confirmed in #3984, 3.3.2 only requires the presence of labels and instructions, with concerns about quality deferred to 2.4.6. However, 2.4.6 does not address instructions in either its normative or informative text.
For example, a form may include terse instructions like "Enter your details,""Choose an option," or "Complete all required fields." While the presence of these instructions meets the requirements of 3.3.2, their lack of clarity or detail would not be addressed under 2.4.6.
Should we assume that 2.4.6 applies to instructions as well? If so, it might be worth updating the Understanding document to clarify this. If not, and I don’t believe the normative language of 2.4.6 really supports that, where should issues related to inaccurate or imprecise instructions be addressed?
The text was updated successfully, but these errors were encountered:
This issue was flagged on the 10/4 TF call as being similar in nature to #3984. The conversation in the related PR #4056 is helpful (regardless that it was closed) because of having something explicit for response.
Picking up on this comment from @JAWS-test, considering the reluctance to concede any notion of accuracy or correctness in 3.3.2, what does that imply for instructions? As confirmed in #3984, 3.3.2 only requires the presence of labels and instructions, with concerns about quality deferred to 2.4.6. However, 2.4.6 does not address instructions in either its normative or informative text.
For example, a form may include terse instructions like "Enter your details," "Choose an option," or "Complete all required fields." While the presence of these instructions meets the requirements of 3.3.2, their lack of clarity or detail would not be addressed under 2.4.6.
Should we assume that 2.4.6 applies to instructions as well? If so, it might be worth updating the Understanding document to clarify this. If not, and I don’t believe the normative language of 2.4.6 really supports that, where should issues related to inaccurate or imprecise instructions be addressed?
The text was updated successfully, but these errors were encountered: