Re: Text in buttons - a solution and proposal. (Everybody happy?)

gregg, in regards to your comment, "Having so many legacy browsers makes it
almost impossible to design a page which will look right these days."  i
agree and at some point, there will need to be a minimum browser version
required just to utilize the security and functionality.

the driver here will not be functionality for everyone but information
security.

my thoughts are that ecommerce requires a certain browser version just to
work with the newer versions of the SSL key that provides more security.  so
i think there is a precedent that will be made as more information and
personal submittal is driven to be under SSL.  that is to protect user
information.  therefore SSL may be a driver in the web browser world that
will force everyone to upgrade.  the alternative to SSL is to provide a 1
800 phone number for customer service so users can interact.  this is even
being used by people who have the correct browser version but fear sending
giving their information online.

my philosphy that i pushed when i was in government service was, you cannot
compromise security so you provide an alternative methodology for those who
will not or cannot access your site due to earlier browser versions.
therefore provide a button for accessibilty and provide a means for a
telephone call or email the question.

/rob



----- Original Message -----
From: "Gregg Vanderheiden" <GV@trace.wisc.edu>
To: <seeman@netvision.net.il>; "'WAI (E-mail)'" <w3c-wai-gl@w3.org>
Sent: Sunday, October 29, 2000 3:42 PM
Subject: RE: Text in buttons - a solution and proposal. (Everybody happy?)


> This looks good to me. Also makes the sentence easier to read and
> understand.   But let's drop the capital letters.  I just put those in to
> show where words had been added.
> Lisa suggestion then looks like
>
> 3.1 When an appropriate markup language exists and will work, use markup
> rather than images to convey information to allow text scalability.
> [Priority 2]   For example, use SVG for line art, MathML to mark up
> mathematical equations, and CSS for text-oriented special effects. You may
> use text in images, when the text has a primarily graphical function, if
the
> effect cannot be achieved with markup, (as in the case of some for logos
and
> limited accent elements) provided that you provide a textual equivalent to
> the content contained in the image.
>
>
> Adding condition clauses like "when something is true then etc.",  always
> makes automatic testers harder..... but if we don't put them in,  then the
> checkpoints are not practical.
>
> Sometimes I wonder if we shouldn't try to work harder on tools to make the
> pages accessible no matter what they look like........
>
> Having so many legacy browsers makes it almost impossible to design a page
> which will look right these days.
>
> Gregg
>
> -- ------------------------------
> Gregg C Vanderheiden Ph.D.
> Professor - Human Factors
> Dept of Ind. Engr. - U of Wis.
> Director - Trace R & D Center
> Gv@trace.wisc.edu, http://trace.wisc.edu/
> FAX 608/262-8848
> For a list of our listserves send "lists" to listproc@trace.wisc.edu
>
>  -----Original Message-----
> From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org]  On
> Behalf Of Lisa Seeman
> Sent: Sunday, October 29, 2000 1:12 AM
> To: WAI (E-mail)
> Subject: Text in buttons - a solution and proposal. (Everybody happy?)
>
> OK, I would like to propose a compromise position.
>
> Lets change Greg's draft to :
>
> "You may use text in images, when the text  has a primarily graphical
> function, if ..."
>
> instead of :
>
> "You may use text in images when the text does not convey its literal
> meaning, but has a more graphical function, if".
>
>
> This will address the concern that a designer making a show case site will
> be restricted.
>
> Further if a designer places redundant textual links, then the main
function
> of the graphical link becomes its look. I.E. the primary function is now
> graphical.
>
> However I _can_ not_ make a bitmap of all my BILI text and use that in
place
> text - which was my main concern.
>
> Are there any problems with this?
>
>
> The revised proposal is now:
>
> 3.1 When an appropriate markup language exists AND WILL WORK, use markup
> rather than images to convey information TO ALLOW TEXT SCALABILITY.
> [Priority 2]   For example, use SVG for line art, MathML to mark up
> mathematical equations, and CSS for text-oriented special effects. You may
> use text in images, when the text has a primarily graphical function, if
the
> effect cannot be achieved with markup,
> (as in the case of some for logos and limited accent elements) provided
that
> you provide a textual equivalent to the content contained in the image.
>
>

Received on Sunday, 29 October 2000 22:23:58 UTC