W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2008

FW: Your comments on WCAG 2.0 Last Call Working Draft of December, 2007

From: Richard Ishida <ishida@w3.org>
Date: Tue, 25 Mar 2008 19:58:28 -0000
To: <public-i18n-core@w3.org>
Message-ID: <00e801c88eb2$98446080$c8cd2180$@org>

I have had some offline exchanges of email with the WAI folks wrt these
comments.  I'm now satisfied that the sections 

http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-TECHS-20071218/H56.html

and 

http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-TECHS-20071218/H56.html

are OK.

If I don't hear to the contrary by tomorrow's call, I propose to reply on
behalf of the WG that we are happy.

Cheers,
RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)
 
http://www.w3.org/International/
http://rishida.net/blog/
http://rishida.net/

 

-----Original Message-----
From: Loretta Guarino Reid [mailto:lorettaguarino@google.com] 
Sent: 11 March 2008 00:21
To: Richard Ishida
Cc: public-comments-WCAG20@w3.org
Subject: Your comments on WCAG 2.0 Last Call Working Draft of December, 2007

Dear Richard Ishida,

Thank you for your comments on the 11 Dec 2007 Last Call Working Draft
of the Web Content Accessibility Guidelines 2.0 (WCAG 2.0
http://www.w3.org/TR/2007/WD-WCAG20-20071211). The WCAG Working Group
has reviewed all comments received on the December draft. Before we
proceed to implementation, we would like to know whether we have
understood your comments correctly and whether you are satisfied with
our resolutions.

Please review our resolutions for the following comments, and reply to
us by 31 March 2008 at public-comments-wcag20@w3.org to say whether
you accept them or to discuss additional concerns you have with our
response. Note that this list is publicly archived.

Please see below for the text of comments that you submitted and our
resolutions to your comments. Each comment includes a link to the
archived copy of your original comment on
http://lists.w3.org/Archives/Public/public-comments-wcag20/, and may
also include links to the relevant changes in the WCAG 2.0 Editor's
Draft of 10 March 2008 at
http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20080310/.

Note that if you still strongly disagree with our resolution on an issue,
you have the opportunity to file a formal objection (according to
3.3.2 of the W3C Process, at
http://www.w3.org/2005/10/Process-20051014/policies.html#WGArchiveMinorityVi
ews)
to public-comments-wcag20@w3.org. Formal objections will be reviewed
during the candidate recommendation transition meeting with the W3C
Director, unless we can come to agreement with you on a resolution in
advance of the meeting.

Thank you for your time reviewing and sending comments. Though we
cannot always do exactly what each commenter requests, all of the
comments are valuable to the development of WCAG 2.0.


Regards,

Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact

On behalf of the WCAG Working Group

----------------------------------------------------------
Comment 1: Problems with H34 and H56
Source:
http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Dec/0053.html
(Issue ID: 2375)
Status: VERIFIED / ACCEPTED
----------------------------
Original Comment:
----------------------------

There are still some significant issues with the text in H34 and H56. I will
list them and suggest fixes below.


============================================

H34

[a] In the first para of Example 1 there is what I suspect is an accidental
sentence "Inserting a Unicode right-to-left mark (via the HTML character
entity ) after the exclamation mark positions it correctly."  This
sentence is repeated (appropriately) later, but in this position creates
confusion about the example that immediately follows.  I recommend you just
delete that sentence. (It wasn't in my original suggested text at
http://www.w3.org/International/2007/11/wai-examples.html which you seem to
have used.)

[b] You have the text "(in this case via the HTML character entity
)".  This introduces more than one problem:

[b1]  is not a character entity (that would be ), it is a
numeric character reference (NCR)

[b2] looking at the source I don't see any evidence of an NCR or entity, so
others may also find this misleading (possibly caused during XSLT processing
of this document)

[b3]  is a decimal NCR; the Character Model recommends the use of
hex-based NCRs, ie. in this case  (see
http://www.w3.org/TR/charmod/#C045).  This would also make it easier for
readers to relate to the description further up the page that shows hex
rather than decimal notation.

In my proposed rewrite I simply omitted that parenthetical remark to avoid
problems. That would be my recommendation here.  It is described in the text
anyway.

[c] This is down to us.  We recently revisited ascii-only examples of bidi
text in the i18n WG, and we came up with a new proposal.  We now plan to use
an English translation for Arabic/Hebrew text, with characters running rtl,
and to upper case rtl text and lowercase ltr text. In short, I would suggest
that you replace

The title is "biula riiacm Hatfm!" in Arabic.

with

the title is "HCTIWS SDRADNATS BEW!" in arabic.

and do similar for the example with the exclamation mark to the left.


=============================================

H56

[d] The <span dir="ltr"> markup is not needed to correctly render the "W3C"
text and so should not be used. I doubt you need the language markup in this
case, either, since W3C is W3C in Hebrew. So I recommend you simply remove
the span around W3C. There is also a question about the appropriate ordering
of the text in the quote in the source - see the proposed text I mention in
[e] for what I think is a better approach.

[e] The example of the expected result actually comes out incorrectly,
because you didn't include the markup you show in the code example!  ;-)

To correct both of these issues, I propose you pick up the text I have added
to http://www.w3.org/International/2007/11/wai-examples.html for you as a
replacement for Example 1 of H56.

Note that you will need to pick up the source text for the examples
containing Hebrew text on that page, since two of them contain spans with
dir='rlt' to make the quote look as intended.

===================================================

Hope that helps.

RI


============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)

---------------------------------------------
Response from Working Group:
---------------------------------------------

Thank you. We have updated this technique as proposed.
Received on Tuesday, 25 March 2008 19:55:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:53 GMT