- From: David Todd <dltodd@us.ibm.com>
- Date: Mon, 8 Jun 2009 14:10:26 -0400
- To: w3c-wai-gl@w3.org
- Message-ID: <OFEC1F0FD5.10D182F8-ON852575CF.0057302D-852575CF.0063BB4A@us.ibm.com>
Glad to see this being discussed as it's a topic of some confusion . To me, the intent of the guideline is to avoid non-DOM functions when adding content to a page. Hence, any use of document.write(), innerHTML, outerHTML, innerText or outerText is non-WCAG 2.0 compliant. The guideline is likely to cause many Web applications/pages to to be non-compliant as the use of document.write() and innerHTML are pervasive. David Todd IBM Human Ability & Accessibility Center From: Andi Snow-Weaver/Austin/IBM@IBMUS To: w3c-wai-gl@w3.org Date: 06/08/2009 08:07 AM Subject: SCR21 In SCR21, the test procedure says "Examine the source code and check that the new content is not created using document.write(), innerHTML, outerHTML, innerText or outerText." Some of the evaluation tools are flagging any use of these functions as non-compliant with WCAG 2.0. But I don't think this is a correct interpretation. It is only a failure if the intent was to use the technique "Using functions of the Document Object Model (DOM) to add content to a page". We don't have a failure technique around the use of document.write(), innterHTML, etc. Perhaps we need to add a technique that demonstrates the correct use of these functions. Andi
Received on Monday, 8 June 2009 18:11:07 UTC