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-2651 LC-2652 LC-2653 LC-2654 LC-2655 LC-2656 LC-2657 LC-2658 LC-2659 LC-2660 LC-2661 LC-2662 LC-2663 LC-2664 LC-2665 LC-2666 LC-2667 LC-2668 LC-2669 LC-2670 LC-2671 LC-2672 LC-2673 LC-2674 LC-2675 LC-2676 LC-2677 LC-2678 LC-2679 LC-2680 LC-2681 LC-2682 LC-2686 LC-2687 LC-2688 LC-2689 LC-2690 LC-2691 LC-2692 LC-2693 LC-2694 LC-2695 LC-2698 LC-2700 LC-2701 LC-2702 LC-2817 LC-2818
Previous: LC-2658 Next: LC-2654
[This email has been submitted as a comment on the July 27, 2012 draft of "Applying WCAG 2.0 to Non-Web Information and Communications Technologies"] From my point of view trying to offer guidelines for something that is left undefined asks for disaster. The document "Applying WCAG 2.0 to Non-Web Information and Communications Technologies" per its draft dated July 27, 2012, claims to offer informative guidance about how WCAG 2 guidelines and success criteria might be applied to non-web documents/content and to non-web software. Nevertheless, nowhere in the document is there any explanation as to what is meant by these two. In essence this makes it impossible to have any serious discussion about whether the document as such or parts of thereof make any sense. In a nutshell: First define the main terms/concepts for the purpose of this document - most notably non-web content/documents and non-web software –, then start discussion of guidelines, success criteria etc. Olaf