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-2508 LC-2509 LC-2510 LC-2511 LC-2512 LC-2533 LC-2534 LC-2535 LC-2536 LC-2537 LC-2538 LC-2539 LC-2540 LC-2549 LC-2550 LC-2551 LC-2553 LC-2554 LC-2555 LC-2562 LC-2563 LC-2564 LC-2565 LC-2566 LC-2567 LC-2568 LC-2569 LC-2570
Previous: LC-2536 Next: LC-2562
Loretta, Thank you for your response. Thank you for submitting this technique. The working group has reviewed it and has the following feedback: 1. We do not feel this is a sufficient technique for SC 2.4.2. In the absence of the <title> element, this would not satisfy the success criterion. So at most it would be an advisory technique for SC 2.4.2. It might also be considered an advisory technique for SC 2.4.10. I am not sure what you mean here. My technique requires the use of title and H1 element. Could you clarify why you think the technique I submitted does not require the title element? See reference on the rules for implementation: http://html.cita.illinois.edu/nav/title/title-rules.php 1. This technique itself contains no content, only references to other resources on the web. The details of the technique need to be included inline, so that the technique stands on its own. Links to other resources can supplement the technique but cannot define it. Is this a better example? http://html.cita.illinois.edu/nav/title/title-example.php 1. We feel that many of the recommendations in the referenced sources are over-restrictive. Whether we would include them in a WCAG advisory technique would depend on exactly how the requirements of the technique were defined. My understanding is that the techniques document is informative. This is a technique we have been using for over 8 years and has wide adoption and a technique that many developers and people with disabilities have found very useful. Maybe this techniques does not work for everyone in all situations, but shouldn't there be more than one way to meet a success criteria, especially if it provides richer information that the current technique? Shouldn't the techniques document provide people with useful alternatives, let developers choose the ones that work for them and their customers? Jon