Add Note to Clause 11.1.3.5 for Consistency and Technical Feasibility

REFERENCE: Clause 11.1.3.5, Notes

The EN 301 549 version of Clause 11.1.3.5 omits Note 1 from WCAG. This deviates from WCAG’s own normative allowance for content implemented in technologies that do not fully support all of the Input Purposes for User Interface Components as stated in the Note in that section.

This is problematic, as there may be software platforms that do not support providing additional attributes such as the HTML attributes listed in WCAG and software implemented for that platform should not be required to meet something that is impossible to meet on that platform.

Additionally, this note was added as-is to the non-web Document clause and, thus for the reasons above and consistency, should also be applied to the non-web software clause.

PROPOSED CHANGE

Please add Note 1 (below) and renumber existing Note 1 to NOTE 2.

NOTE 1: Software technologies that do not provide attributes that support identifying the expected meaning for the form input data are not in scope for this success criterion.

OR

Open an issue against WCAG2ICT to find more acceptable language that is similar to the Authoring tool note found in 5.10.1 Content Technology which states “to the extent that information required for accessibility is supported by the format used for the output of the authoring tool”. There could be a note with language similar to:

NOTE: Software would need to utilize technology attributes that support identifying the expected meaning for form input data listed in the WCAG 2 section Input Purposes for User Interface Components to the extent those attributes are supported by that technology.