Topic for discussion from spec review

I'm going through my HTML 5 bugs from our end to end spec review.  We didn't create a bug for this issue.  Should we?  I don't think it's an issue for the HTML spec per se.  More UAAG, WCAG or maybe api mapping.

3.5.3 Document.write(...) has this big warning on it This method has very idiosyncratic behavior. In some cases, this method can affect the state of the HTML parser<http://www.w3.org/TR/2011/WD-html5-20110525/parsing.html#html-parser> while the parser is running, resulting in a DOM that does not correspond to the source of the document. In other cases, the call can clear the current page first, as if document.open()<http://www.w3.org/TR/2011/WD-html5-20110525/apis-in-html-documents.html#dom-document-open> had been called. In yet more cases, the method is simply ignored, or throws an exception. To make matters worse, the exact behavior of this method can in some cases be dependent on network latency, which can lead to failures that are very hard to debug. For all these reasons, use of this method is strongly discouraged.

I believe this is the behavior that people have sometimes though caused accessibility problems. I have never encountered problems with AT and document.write. Having a DOM that doesn't correspond to the source happens with lots of other script too, so I'm not sure why that is a problem. Does anyone have documented test cases of where document.write is a problem (with a specific page, browser and AT combination)?

If so, can we document that as part of the warning, and also discuss in WCAG 2.0 techniques?

discuss, Cynthia to discuss with Rich and Steve