I was not using the term "standards" in the sense of a standards to be met
then everything is OK, but as a collective of best practices.

Web standards in the sense that I meant it, means designing with usability
and accessibility in mind.

Valid code is a pre-requisite to this.

Usability is the next step - e.g. don't use something that is consistently
in the top ten list of things that users hate; do use something that
usability studies have found to be helpful features.

Accessibility is an extension of usability to include non-standard ways of
browsing the web.

Complying with WCAG is step towards accessibility. Careful consideration
has to be given how one applies WCAG meaningfully.

Research has shown that Websites meeting WCAG were still found difficult
to use by disabled users - mainly because of a lack of consideration to
basic standards of usability.

Designing using these approaches is what I meant by designing to standards.


On Tue, December 2, 2008 8:07 pm, Joe Ortenzi wrote:
> standards compliance should not be confused with WCAG conformance.
>
> HTML is a standard WCAG is a guidance that people use as if it were a
> "standard", which could easily be a standard but is effectively not
> one. However, complying with WCAG confers added benefits which
> standards compliance creators strive for.
>
> On 29/11/2008, at 09:22 , Stuart Foulstone wrote:
>
>> It may validate, but valid code is just a pre-requisite to achieving
>> standards compliance.
>>
>>
>> On Fri, November 28, 2008 8:43 pm, Dave Hall wrote:
>>> On Fri, 2008-11-28 at 13:07 +0000, Stuart Foulstone wrote:
>>>> Blinking text is against standards in itself, so how can you do it
>>>> in a
>>>> standards compliant way?
>>>
>>> Using the sample I posted - see below.  That validates.
>>>
>>> Cheers
>>>
>>> Dave
>>>
>>>>
>>>> On Fri, November 28, 2008 10:45 am, Dave Hall wrote:
>>>>>>        <!-- ... -->
>>>>>>        <head>
>>>>>>        <style type="text/css">
>>>>>>               /* ... */
>>>>>>               .blink{
>>>>>>                       text-decoration: blink;
>>>>>>               }
>>>>>>               /* ... */
>>>>>>        </style>
>>>>>>        <!-- ... -->
>>>>>>        </head>
>>>>>>        <body>
>>>>>>        <!-- ... -->
>>>>>>        <span class="blink">my blinking test</span>
>>>>>>        <!-- ... -->
>>>>>>        </body>
>>>>>>
>>>>>>        instead of
>>>>>>        <!-- ... -->
>>>>>>        <blink>my blinking test</blink>
>>>>>>        <!-- ... -->
>>>
>>>
>>>
>>> *******************************************************************
>>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
>>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
>>> Help: [EMAIL PROTECTED]
>>> *******************************************************************
>>>
>>>
>>
>>
>>
>>
>> *******************************************************************
>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
>> Help: [EMAIL PROTECTED]
>> *******************************************************************
>>
>
> ================================
> Joseph Ortenzi
> [EMAIL PROTECTED]
> +61 (0)434 047 804
> http://www.typingthevoid.com
> http://twitter.com/wheelyweb
> http://www.linkedin.com/in/jortenzi
> Skype:wheelyweb
>
>
>
> *******************************************************************
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: [EMAIL PROTECTED]
> *******************************************************************
>
>




*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to