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-2912 LC-2916 LC-2917 LC-2918 LC-2919 LC-2920 LC-2939 LC-2950 LC-2951 LC-2952 LC-2953 LC-2954 LC-2955 LC-2956 LC-2957 LC-2958 LC-2959 LC-2960 LC-2961 LC-2963
Previous: LC-2961 Next: LC-2955
https://github.com/w3c/wcag/pull/45 Currently uniqueness or necessity of F17 is unclear. F17 discusses uniqueness of id attribute correctness of referencing id or unique identifies (for, headers, usemap attributes) uniqueness of accesskey attribute However F77 and F62 discusses most of them. F77 discusses uniqueness of id F62 discusses correctness of referencing id or unique identifiers F68 discusses that in for attribute F90 discusses that in headers attribute Remaining issue is uniqueness of accesskey attribute. So we should remove other issuse from F17. F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determined F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID F90: Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes