Re: Target browsers for web development

But that's exactly what educating the user is - empowering them. It's
not that we're educating the consumer about our "coding to standards"
as it is educating them that there are "standards" and what those
standards mean to them and can do for them. It's not that we should say
"coding to standards shortens our development cycle," but rather that
standards can ensure a more consistent experience across the board for
users; that standards means they can access the same content from their
Web browser, their PDA, or screen reader; that standards means their
pages will load faster, etc.

Pitch it from a "what this can do for you," not a "why this helps us."

On Tuesday, April 8, 2003, at 09:39  AM, Matthew Goddard wrote:

> I'm all for empowering the user through good design but should we
> really be "educating" the user about our coding standards. Standards
> are for us to worry about, they shouldn't be used as a way of bending
> the user to our design decisions.
>
>
> Matt

Cheers!

Todd R. Warfel

_//message first [method second]
-=========================-
User Experience Architect
Cornell University Lab of Ornithology
[P] (607) 254-2477
[F] (607) 254-2415
[E] [email protected]
-=========================-

In theory, theory and practice are the same,
but in practice, they're not.

The only thing necessary for evil to exist in the world is for good men
to do nothing.

    --------------------------------------------------------------
     POSTINGS (in plain text): [email protected]
           SUBSCRIPTION CHANGES:  http://lists.syntagm.co.uk
            (or send email to mailto:[email protected])
    --------------------------------------------------------------