From: Bradley Montgomery, Rachael L. [mailto:rbradley@mitre.org] Sent: Friday, June 24, 2016 5:37 PM The user selects the Yes radio button and a query is launched to get populate data for the fields following the radio button. The user then tabs past those fields while they are being built without realizing s/he missed something. [Jason] The author is supposed to set aria-busy on the element while the update is happening. If we maintain that aria-busy is not in fact set by the user (although it does occur in response to the user’s action, albeit indirectly, so the point is debatable), then this scenario wouldn’t fail to meet WCAG 2.0 SC 4.1.2. I think 4.1.2 is written more narrowly than it should be, since some states and properties are updated in response to events that occur in the application but which are not set by the user; yet assistive technologies should still be notified of the changes. https://www.w3.org/TR/wai-aria/states_and_properties#aria-busy ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Saturday, 25 June 2016 00:08:11 UTC