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-2672 Next: LC-2674
[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"] In the world of software development quite a bit of work has been carried out in order to make software more accessible than it used to be. The document "Applying WCAG 2.0 to Non-Web Information and Communications Technologies" per its draft dated July 27, 2012 does not take any of that into account though the concepts and principles behind those are extremely useful, both in terms of architecture as well as in terms of various specifics. I think it is essential to first learn from others about what has already been achieved, before coming up with something else out of the blue. In a nutshell: First learn from existing achievements, then - if really something new and useful can be added to it - come up with it. Don't (try to) reinvent the wheel - the world does not need yet another paradigm. Olaf