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-2660 Next: LC-2698
[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"] The concepts/terms [non-web] "content" and [non-web] "document" are very fuzzy, if used without context, background, a proper definition etc. Among many other aspects the following would have to be addressed: - relationship between content, documents, data/data sets, and information - final form (and intentionally shared as thus with others) versus work in progress (a semi-finished letter, and possibly shared with someone for review) - formal (an email sent in some official matter, an order or invoice, a book) versus informal (a note, memo, private communication, diary, ...) - context: usage context, creator, sender, recipient, channel over which access happens, purpose - provide examples to illustrate what is to be considered content/document, and what not Unless at least substantial portions of the above are developed, I consider the document "Applying WCAG 2.0 to Non-Web Information and Communications Technologies" per its draft dated July 27, 2012, essentially meaningless, due to lack of a reasonable amount of specificity. In a nutshell: Clearly define the core terms [non-web] content/document, and establish semantic context. Olaf