Repository navigation
3.1.2 Language of Parts - How do we comply for user-submitted content for WCAG 2.2 AA? #4970
Replies: 1 comment 1 reply
|
I believe 3.1.2 Language of Parts was written at a time when user-generated content and therefore the issue you raise was not common. The pretty dated Authoring Tools Guidance https://www.w3.org/TR/ATAG20/ does not say anything about including the setting of the right language for user-submitted input. It is certainly feasible, e.g. via an editor menu for setting the language for text content selected in the editor, the same way as an editor might give you options for marking things as heading or providing an alternative text for images. Whether some user entering content then uses these options if they exist is largely outside the control of the author, so I would treat 3.1.2 Language of parts as exempt for user-submitted content, certainly where the interface does not offer an option for setting the language of input (but admittedly, the normative text does not include such exception, which shows its age). An alternative would be automatic language detection and consequent mark-up by the authoring tool (or authoring functionality on a page). This is certainly feasible and may exist already out there, but I do not think this translates into a normative requirement for user-submitted content that is outside the control of the author. |
|
Very useful summary, especially the point about the exception for user-submitted content and the suggestion of offering language selection directly in the editor. Worth adding this: User profile names will, in most cases, fall under the exception for proper names, which is part of the wording of this success criterion, so this case does not really need to be addressed at all. What remains is mainly free text (for example profile descriptions), where this exception does not apply. On the original question about the "Partially Supported" status, I'd add this: it is terminology from the Voluntary Product Accessibility Template (VPAT), or more precisely from the resulting Accessibility Conformance Report (ACR), not a status of the success criterion itself under the Web Content Accessibility Guidelines (WCAG). Under WCAG, a success criterion is either met or not met, at the level of the page or set of pages being evaluated. If conformance is declared with a normative standard, whether directly with WCAG at level AA or with EN 301 549, which normatively incorporates WCAG 2.1 AA, unmarked text outside the exceptions formally means success criterion 3.1.2 is not met for that page. In a VPAT/ACR statement, by contrast, the status "Partially Supports" with a stated description of the limitation is a common and accepted practice. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
For a english-only app, the users can submit content (e.g. names, profile descriptions) in other languages, which can be displayed to other users. Aiming to acheive WCAG 2.2 AA
Question:
What is the expected standard for handling
langattributes on user-generated content where the user could enter anything and that needs to be shown to other users? Found a library that can do it https://www.npmjs.com/package/franc, but this does not seem to support this 100% of the time.Are there more accepted ways for it or how do people handle this for WCAG 2.2, if we dont support this it i think we can label it has
Partially Supportedis that fine for full 2.2 compliance?All reactions