W3C home > Mailing lists > Public > public-xhtml2@w3.org > August 2008

[XHTMLAccess] i18n comment 4: Rendering by user agent (PR#8044)

From: <ishida@w3.org>
Date: Wed, 6 Aug 2008 07:40:59 -0500
Message-Id: <200808061240.m76CexQZ009235@htmlwg.mn.aptest.com>
To: public-xhtml2@w3.org
CC: xhtml2-issues@mn.aptest.com


Comment from the i18n review of:
http://www.w3.org/MarkUp/2008/WD-xhtml-access-20080526/

Comment 4
At http://www.w3.org/International/reviews/0806-xhtml-access/Overview.html
Editorial/substantive: S
Tracked by: RI

Location in reviewed document:
3.1.2 [http://www.w3.org/MarkUp/2008/WD-xhtml-access-20080526/#sec_3.1.2.]

Comment: 
"The rendering of access keys depends on the user agent. We recommend that authors include the access key character in label text or wherever the access key is to apply. If the user agent can recognize that the currently mapped access key character appears in the label text of the element to which it is mapped, then the user agent may render the character in such a way as to emphasize its role as the access key and distinguish it from other characters (e.g., by underlining it)."

 
This is likely to be problematic for non-Western text. For example, in scripts that combine character into complex shapes (such as Hindi/Devanagari or Urdu/Nastaliq) it can be difficult to isolate a specific character. For such scripts it is likely to be better to give the control to the author when identifying the character to highlight.

 
In some cases the author may include the access key in parentheses after the label, in others they may prefer to highlight a letter in the label itself. 

 
Received on Wednesday, 6 August 2008 12:44:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 February 2010 18:12:49 GMT