This document:Public document·View comments·Disposition of Comments·
Nearby:Accessibility Guidelines Working Group Other specs in this tool Accessibility Guidelines Working Group's Issue tracker
Quick access to LC-2464 LC-2476 LC-2490 LC-2571 LC-2572 LC-2587 LC-2588 LC-2599 LC-2600 LC-2645 LC-2685 LC-2716 LC-2720 LC-2725 LC-2727 LC-2743 LC-2758 LC-2759 LC-2760 LC-2762 LC-2763 LC-2766 LC-2767 LC-2768 LC-2769 LC-2778 LC-2779 LC-2780 LC-2876 LC-2922 LC-2941 LC-2942 LC-2964 LC-2972
Previous: LC-2767 Next: LC-2780
Name: Makoto Ueki Email: makoto.ueki@gmail.com Affiliation: WAIC(Web Accessibility Infrastructure Committee in Japan) Document: W2 Item Number: Success Criterion 1.3.2 Part of Item: Comment Type: question Summary of Issue: Text field followed by instructions Comment (Including rationale for any proposed change): We'd like to make sure if the following example "affects its meaning" or not. ex1. Instructions <label for="account">Credit card account number</label> <input type="text" id="account"> <p>15 - 16 digits, no dashes or spaces</p> There is a text field which is followed by restrictions on the format of data that users must enter. Screen reader users might not be able to perceive that there is the instructions for this text field. Or they could perceive it after they input data to the text field. Does this text field meet SC 1.3.2? Proposed Change: WAIC would like to have the answer from WCAG working group in order to harmonize JIS(Japanese Industrial Standards) with WCAG.