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-2582 LC-2583 LC-2584 LC-2595 LC-2596 LC-2601 LC-2605 LC-2610 LC-2611 LC-2612 LC-2613 LC-2619 LC-2620 LC-2622 LC-2625 LC-2626 LC-2627 LC-2628 LC-2631 LC-2632 LC-2646 LC-2647 LC-2648 LC-2683 LC-2684 LC-2703 LC-2704 LC-2718 LC-2719 LC-2723 LC-2724 LC-2726 LC-2728 LC-2729 LC-2730 LC-2745 LC-2770 LC-2771 LC-2773
Previous: LC-2718 Next: LC-2719
SCR18: Providing client-side validation and alert. Refer to http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/SCR18 Summary: I see a problem suggesting this technique as a sufficient technique for SC 3.3.1 when implemented on pages that have multiple mandatory form fields (Situation A), or follow Situation B. I have noticed when there are more than a certain number of form fields, client side validation is generally not helpful -- as a user must resubmit and then follow the pop up dialog route for every incorrectly filled field. Proposed Change: Make it an advisory technique that works under specific conditions, say when there are fewer than three (3) mandatory form fields on the page.