Internationalization Comments on Techniques for WCAG 2.0
Version reviewed:
http://www.w3.org/TR/2007/WD-WCAG20-TECHS-20070517/
Lead reviewer and date of initial review: Richard Ishida, June 2007
Subject lead: [WCAG2 TECHS]
These are comments on behalf of the Internationalization Core WG, unless otherwise stated. The "Owner" column indicates who has been assigned the responsibility of tracking discussions on a given comment.
We recommend that responses to the comments in this table use a separate email for each point. This makes it far easier to track threads. Click on the icons in the right-most column to see email discussions.
| ID | Location | Subject | Comment | Owner | Ed. / Subs. |
||
|---|---|---|---|---|---|---|---|
| 1 | H34 | H34 example source direction |
The example of source code is problematic, since it assumes a particular behaviour on the part of the authoring tool (see the discussion on this at http://www.w3.org/International/geo/html-tech/tech-bidi.html#d2e277 ). I would recommend just describing that the ‏ is placed immediately alongside the exclamation mark, and showing before and after examples of the displayed text, as in http://www.w3.org/International/geo/html-tech/tech-bidi.html#ri20030726.140315918 Note, also, that for people to appreciate the examples, their user agent needs to support bidi text display and Arabic fonts. This is why I am providing a pseudo-arabic version of the example in our best practices doc. |
RI | E | ||
| 2 | H34 | H34 use of entities |
You don't have to use a character entity, although that may be inferred from the current text in H34. In fact, there are more than one possible issue with that: - the editor may not display character entities as you'd expect, due to the bidi algorithm (on the other hand, the editor may make RLM characters visible, like Notepad does, in which case this becomes a better solution) - there is a case for using NCRs rather than character entities in XHTML, since it is XML-based and the entities are declared outside the document, and some parsers may not validate when such entities are involved. If you keep the example you should probably modify the text to say "Inserting a Unicode right-to-left mark (in this case via the HTML character entity) ..." or just indicate that characters, entities and ncrs are possible approaches. |
RI | E | ||
| 3 | H56 | H56 link to bidi primer |
In H34 you say "The concepts used in this technique are described in What you need to know about the bidi algorithm and inline markup." I think you should repeat that and add that document to the resources for H56 too. |
RI | E | ||
| 4 | H56 | H56 incorrect link target |
The link in "necessary because the Unicode bidirectional algorithm" should point to the same version of this document as in H34 (rather than the copy on my personal site). |
RI | E | ||
| 5 | H56 | H56 source text |
This example, unlike the two following, omits the <head> element. It seems at best inconsistent. (Note, btw, that these examples are invalid, since the title element is required.) |
RI | E |