Purpose of Purpose of Controls

[r12a]

Success Criterion 1.3.4 Purpose of Controls§
https://www.w3.org/TR/WCAG21/#purpose-of-controls

In content implemented using markup languages, the conventional name of conventional form fields, conventional buttons or controls, or conventional links can be programmatically determined.

It's not clear to me what are the implications of this SC, nor how one actually follows this advice. Following the links leads to lists such as https://www.w3.org/TR/WCAG21/#dfn-conventional-links. Are those terms in bold meant to be literal strings in the UI/markup? (If so, there's a big i18n issue.) How are they supposed to be detected/used? An example would help.

[jake-abma]

@r12a There is an ARIA module WD to support this with some examples and also A sample user experience.

Is this the example you’re looking for?

[jake-abma]

Hi @r12a

We are also not saying content authors should use literal strings which create the i18n issues but that its role as a control should be programmatically determinable. It is just for programmatic identification (so AT can identify them or autofill can work and other support) — but we are not requiring that they be the terms used for users to see.

Does this sufficiently answer your concern? If not please let us know and we'll be happy to respond!

[awkawk]

Thank you for your comment. The terms in the list are not meant to be string literals. We have made this more clear in the current draft.