- From: Marc Haunschild (Accessibility Consulting) <marc.haunschild@accessibility.consulting>
- Date: Wed, 31 Aug 2022 08:24:39 +0200
- Cc: WAI Interest Group discussion list <w3c-wai-ig@w3.org>
Hi guy, > Am 30.08.2022 um 23:26 schrieb Guy Hickling <guy.hickling@gmail.com>: > > consider what AT does with the information from the required attribute - all it does is announce "required" to the user when they land on the field. It also translates the text. 😉 In my opinion it’s easy to understand and ignore the error message of some browsers - it says, that there is an empty required field, what is completely okay with me while exploring a form. Also in my opinion it’s not a failure, because it’s completely correct that there is an empty required input.as a user I just ignore it, because it’s what I want (staying empty while I’m exploring). In the other hand programmatically determinable meta information may be very useful for future AT, parsers, automated validation… - so I think - although not the only way to pass this SC - using the required attribute is best practice. So I personally hide the visual label from AT and use the required attribute for more coding flexibility.
Received on Wednesday, 31 August 2022 06:24:53 UTC