Mark Weiler said: Related to AT detection is how can a site or app know what web content technologies to serve up that are accessibly supported without knowing the user agents and AT the user is using? This is where standards and avoidance of fanciful “unicorn” widgets over combinations of standard HTML form elements comes into play. You are correct that there is no “one size fits all” solution. For instance, JAWS will deduce a possible accessible name for a form element even when a properly associated label is missing, whereas NVDA will not. The best approach is to adhere to standards, incorporate accessibility principles early (if that unicorn widget never makes it into the design, the developers won’t build it), and test. ________________________________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Received on Friday, 26 January 2018 14:02:28 UTC