Chaals, Thank you for your quick reply. I appreciate your insight. Alan Smith From: Chaals Nevile Sent: Friday, July 27, 2018 5:57 PM To: Jonathan Avila; Wilco Fiers; ALAN SMITH Cc: WAI Interest Group; wayneedick@gmail.com Subject: Re: How do we test for meeting the new WCAG 2.1 1.3.5 Identify InputPurpose Level AA The most common technology that supports this is HTML. If you use the autocomplete attribute for form fields, you pass. The list of Input Purposes was copied from the values for autocomplete that are listed in the HTML 5.2 specification. If you don't, because a form field asks for information not in that list, the requirement is not applicable, and you pass. If you don't use autocomplete, there are various other ways to say the same thing, e.g. with microdata or RDFa, but they are more complicated so I would suggest recommending autocomplete. When my hands are not so cold, I might describe more about alternative approaches that pass... cheers On Sat, 28 Jul 2018 02:42:01 +1000, ALAN SMITH <alands289@gmail.com> wrote: All, This new guideline has some limits from the second bullet: Success Criterion 1.3.5 Identify Input Purpose (Level AA): The purpose of each input field collecting information about the user can be programmatically determined when: • The input field serves a purpose identified in the Input Purposes for User Interface Components section; and • The content is implemented using technologies with support for identifying the expected meaning for form input data. I don’t think that most existing websites and current coding for form fields have been “implemented using technologies with support for identifying the expected meaning for form input data.” How do we test for this new guideline? Alan Smith -- Chaals: Charles (McCathie) Nevile find more at https://yandex.com Using Opera's long-abandoned mail client: http://www.opera.com/mail/ Is there really still nothing better?
Received on Sunday, 29 July 2018 17:33:33 UTC