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-2663 Next: LC-2661
WCAG 2.0, even after translation, may not be suitable to environments outside of the desktop A fundamental assumption made in many success criteria of WCAG 2.0 is the presence of a browser, an operating system, and some form of assistive technologies. This was a fair assumption during the creation of WCAG 2.0. But it is not appropriate assumption in the context of non-web ICT. This is most obviously the case for ICT functionalities closed from assistive technologies such as most ATM machine functionalities. All success criteria containing the term "programmatically determined" were constructed to allow assistive technologies to better decipher the web content. But when assistive technologies are not present, these success criteria are effectively useless. Indeed, it is still necessary for the content to be presented in a way that users with disabilities can consume. But implementing such solutions in a programmatically determined nature is not necessary in such context. We recognize that WCAG2ICT TF has not considered ICT with closed functionalities from assistive technologies yet. But the TF should be aware of the unstated limitation of its work so far and make this clear to its audience as soon as possible.