- From: Charles McCathieNevile <charles@w3.org>
- Date: Thu, 6 Dec 2001 23:00:34 -0500 (EST)
- To: Jan Richards <jan.richards@utoronto.ca>
- cc: WAI AU Guidelines <w3c-wai-au@w3.org>
That seems like my proposal 2 below, since I don't believe that there is any way we can effectively force authors to provide meaningful text replacements. (Amaya requires an alt before it will insert an image, and I know that people who really care about accessibility from time to time use asdfasdf as the alt to get on with working). Leaving the accessibility error easily found is important, and I think it would be more likely to work if there was a missing alt (in XHTML, conforming browsers will stop processing and say "this page is broken" although they might then offer a recovery option) than trying to get some regular set of strings that can be detected by tools. (That isn't impossible, just takes more work for almost everyone). Hmmm. Seems like we have an issue here... cheers Charles On Thu, 6 Dec 2001, Jan Richards wrote: Let's try that again: 3.4 could be changed (in an errata) to specify that: the only allowable generated text is "place holder text generated by [authoring tool name]", which must be replaced by human authored text by the end of the document editing session. > > Charles McCathieNevile wrote: > > > > 2. We state in errata that 2.2 overrides 3.4 and that the checkpoint can be > > ignored in order to meet 2.2. I don't think this is what we intended either - > > it would lead to the addition of dummy text just to provide validity, and > > there is a real need not to do so. If we do go this way we should delete > > technique T0176 > > > > 3. We state in errata that 2.2 may be violated with respect to provision of > > textual alternatives, in order to meet the requirements of 3.4. We should > > point to that erratum in technique T0176 in that case. > >
Received on Thursday, 6 December 2001 23:00:35 UTC