- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Mon, 24 Oct 2022 09:10:56 -0400
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: John Foliot <john@foliot.ca>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>, Bryan Garaventa <bryan.garaventa@levelaccess.com>, Adam Cooper <cooperad@bigpond.com>
@Patrick H. Lauke: You wrote: "The question isn't though if developers should or shouldn't. It's whether or not the behaviour of browsers to use the fallback (documented in the accessible name computation algorithm) to expose an accessible name counts as passing 4.1.2 Name, Role, Value". I believe, as stated in my last email, that the fallback mechanism is for AT makers to support something they might be forced to do to aid their users. Is there a documented sufficient technique for use of placeholder like there is for label element or aria-labelledby / aria-label that developers can turn too? Granted the techniques doc says other methods may be used but I suppose only after robust testing that those work across target platforms and usage scenarios. Best wishes, -- Sailesh Panchang Customer Success Strategist and Principal Accessibility Consultant Deque Systems Inc 381 Elden Street, Suite 2000, Herndon, VA 20170 Mobile: 571-344-1765
Received on Monday, 24 October 2022 13:11:10 UTC