Removing 'and/or the optional fields are clearly labeled' from 3.3.2 seems to significantly change the meaning about wcag HOT 4 OPEN

that aspect is arguably something that is covered (or should be covered) by 2.4.6 Headings and Labels (as that SC is concerned with the quality of headings and labels), whereas 3.3.2 is concerned with the mere presence of labels/instructions (regardless of how good/comprehensive/accurate they are) - per the discussions that led to #1792 in the first place

because otherwise, conversely, if we said 3.3.2 is also concerned with the quality of labels or instructions, then we have an overlap for labels that both 2.4.6 and 3.3.2 mandate the same thing.

from wcag.

so a possibly better resolution for me would be to make sure that 2.4.6 also mentions/covers the "if something's required, or optional, it should be conveyed appropriately in the label" case

from wcag.

thanks, if that was the intention, should this also be removed from 3.3.2?

including identification of required fields

from wcag.

probably. might have some leftover bits of eggshell there while making the WCAG omelette

from wcag.