W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > June 2007

Grounds for \"200%\"

From: WCAG 2.0 Comment Form <nobody@w3.org>
Date: Fri, 29 Jun 2007 07:36:58 +0000 (GMT)
To: public-comments-wcag20@w3.org
Message-Id: <20070629073658.D3BC93320A@kearny.w3.org>

Name: Yukie Motomiya
Email: yukie.motomiya.zm@hitachi.com
Affiliation: Hitachi, Ltd.
Document: UW
Item Number: Understanding Success Criterion 1.4.4
Part of Item: Intent
Comment Type: question
Summary of Issue: Grounds for \"200%\"
Comment (Including rationale for any proposed change):
We have two questions on 1.4.4 and 1.4.7:

 Q1. Why \"200%\" and \"50%\"?

 Q2. Why do the authors have to be responsible for \"200%\"?

We couldn\'t understand the reason why the authors should ensure that the \"visually rendered text can be resized without assistive technology up to 200 percent and down to 50 percent\". In the section of \"Intent of this Success Criterion\", it reads \"The working group feels that 200% is a reasonable accommodation that can support a wide range of designs and layouts, ...\". However there should be more concrete reason why the working group feels \"200%\" and \"50%\" are reasonable. Also we\'d like to know this percentage can be applied to the characters in any other languages such as CJK languages.

Additionally, all the authors have to do is to use relative measurements in order to make text resizable. Do these SC mean that the authors should provide the mechanism with users to resize text up to 200 percent and down to 50 percent? If so, it should be done by the user agents.

Proposed Change:
- Add the concrete reason why \"200%\"/\"50%\" and the sufficient grounds for any other languages than English. Or change these SCs to simply saying \"Visually rendered text can be resized by the user agents without assistive technology.\"

- Add the concrete reason why \"authors\" should be responsible for \"200%\" and \"50%\".
Received on Friday, 29 June 2007 07:37:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:44 UTC