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-2661 Next: LC-2670
---------- Forwarded message ---------- From: Neil Soiffer <NeilS@dessci.com> Date: Thu, Sep 6, 2012 at 4:19 PM Subject: WCAG2ICT To: public-comments-wcag20@w3.org I have a lot of trouble trying understand how this document helps anyone. On the one hand, the document refers to WCAG "programmatically determined" repeatedly, and this doesn't make sense in many closed systems such as ATMs or Kiosks. On the other hand, it lacks details to help me as a developer figure out what I need to do. E.g., my personal focus is math. A question that often comes up is "what is required for math accessibility?" A search for the term math comes up empty as does a similar search of WCAG 2.0 (not good). Having spent a good deal of time reading the WCAG guidelines, I know that math is covered under 1.1.1 (text alternatives) or 1.3.1 (information, structure, and relationships). So how to meet 1.1.1 in a non-web environment? WCAG2ICT says to provide a text alternative. Similarly, for 1.3.1, it says the structure should be "programmatically determined or are available in text". But these don't make sense in many situations away from a PC such as a kiosk in a museum. The focus should be on providing an alternative presentation such as speech or braille, not on the actual underlying content. The bottom line is that it seems that the document is just lazy: it doesn't do the work needed to understanding non-web context and simply parrots WCAG. It leaves it up to the reader to try and figure out if WCAG makes sense for the particular technology or not and how to adopt WCAG to the appropriate situations... but isn't the purpose of this document to inform the reader about how WCAG applies to their non-web situation? Sincerely, Neil Soiffer Senior Scientist Design Science, Inc. www.dessci.com ~ Makers of MathType, MathFlow, MathPlayer, MathDaisy, Equation Editor ~