Advisory technique for required inputs is linked to SC 1.3.6 instead of 1.3.5

[Seirdy]

The document Understanding Success Criterion 1.3.6: Identify Purpose lists the following advisory technique:

Using aria-invalid and aria-required

These two attributes typically relate to user input. This advisory technique should be moved to the document Understanding Success Criterion 1.3.5: Identify Input Purpose, since it's specifically for inputs.

[alastc]

1.3.6 includes "user interface components", and in general is a broader requirement than 1.3.5.

1.3.5 is quite narrow and requires input purposes, but invalid / required are not the "purpose" of the input as such.

[Seirdy]

On Thu, Jul 21, 2022 at 09:25:10AM -0700, Alastair Campbell wrote:

1.3.6 includes "user interface components", and in general is a broader requirement than 1.3.5.

1.3.5 is quite narrow and requires input purposes, but invalid / required are not the "purpose" of the input as such.

I understand. Perhaps it could be mentioned under both criteria, since it really is relevant to both.

-- Seirdy