ginal Message-
From: Marcos Caceres [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2008 10:50 PM
To: Arthur Barstow
Cc: Cynthia Shelly; public-webapps
Subject: Re: Accessibility requirement
On Tue, Jul 29, 2008 at 4:15 AM, Arthur Barstow <[EMAIL PROTECTED]> wrote:
> Marcos, Cynthi
On Tue, Jul 29, 2008 at 4:15 AM, Arthur Barstow <[EMAIL PROTECTED]> wrote:
> Marcos, Cynthia,
>
> Perhaps requirement #37 as currently written [1] is overly prescriptive.
>
> For example, rather than trying to enumerate the sub-requirements for the
> other language (i.e. the non-HTML language), th
Caceres [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2008 3:50 AM
To: Cynthia Shelly
Cc: public-webapps@w3.org
Subject: Re: Accessibility requirement
On Tue, Jul 15, 2008 at 12:10 AM, Cynthia Shelly
<[EMAIL PROTECTED]> wrote:
Interesting...
My experience has been that HTML 4.01 can be made
es [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2008 3:50 AM
To: Cynthia Shelly
Cc: public-webapps@w3.org
Subject: Re: Accessibility requirement
On Tue, Jul 15, 2008 at 12:10 AM, Cynthia Shelly
<[EMAIL PROTECTED]> wrote:
> Interesting...
> My experience has been that HTML 4.01 can
On Tue, Jul 15, 2008 at 12:10 AM, Cynthia Shelly
<[EMAIL PROTECTED]> wrote:
> Interesting...
> My experience has been that HTML 4.01 can be made accessible if it is
> carefully coded. WCAG 2.0 has many >techniques for this, including for
> scripted and styled content. While it is true than many
Marcos said
"the reason we have "should" and "may" is to accommodate HTML, which is
not as accessible as it could be. To have "must" would mean that
HTML4.01 could not meet the requirement."
Interesting...
My experience has been that HTML 4.01 can be made accessible if it is carefully
coded. WC
spec, and came across this accessibility requirement. Wondering why only
> should and may here, and not must?
>
the reason we have "should" and "may" is to accommodate HTML, which is
not as accessible as it could be. To have "must" would mean that
HTML4.01 could not meet th
Hi,
I'm a member of wai-pf and wcag, and met some of you at the web apps face to
face in redmond recently. I was reading through the widgets 1.0 requirements
spec, and came across this accessibility requirement. Wondering why only
should and may here, and not must?
R37. Lan