> The context of use and necessity of this SC is very different - and therefore this should be rethought with that user context in mind. Only if the requirement for the content is different, in this case the requirement is the same (programmatic association for particular inputs). > At the very least 'the meaning of' should be removed from the stem. But that is what is needed to fulfil the requirement when specifying it in as technology-agnostic way as possible. (Which is admittedly difficult in this example due to the reliance on the HTML5 spec.) > The text of the SC should reflect the intention of the requirement - that is, to assist users in populating commonly used form input data. In which case we need to overhaul the rest of WCAG! Where (in the SC text) does 1.3.1 talk about headings? Or 1.1.1 talk about being able to see images? Or 2.1.1 talk about switch access? That info goes in the understanding doc. Bottom line: If we were sitting down to start this SC from scratch, I think we’d get to the same place because that is the requirement for the content. Cheers, -Alastair
Received on Friday, 23 February 2018 17:32:20 UTC