tee...you are quite right to point that out..every medium has its
booby traps and difficulties..I've spend my share of time wrangling
with recalcitrant files myself.
cs
On Oct 20, 2010, at 4:11 PM, tee wrote:
Fixing PostScript error is like knowing browser quirks
> This rule works
> a[href^="http"]
>
> Problem is almost every CMS system uses absolute url for internal link,
> this makes it impossible to target just the external link without the
> content editor having to add a class to it.
If you deal with absolute paths, you should be able to match intern
This rule works
a[href^="http"]
Problem is almost every CMS system uses absolute url for internal link, this
makes it impossible to target just the external link without the content editor
having to add a class to it.
tee
***
Li
On Oct 20, 2010, at 9:11 AM, cat soul wrote
>
> Please don't groan, but my background is in Print. Luckily, I never had to
> write PostScript. Illustrator, PS, Quark, and later InDesign all do a fine
> job of it.
>
>
> but just imagine if I DID have to write the post script, and to know
> v
Leslie,
This is such valuable feedback.
Thanks very much!
Does anyone have suggestions on how to obtain website usability feedback
from various members of the disabled community?
Thanks in advance,
Nick
--
Nick Stone, MBA
SEO, Web Accessibility, Web Development
http://nick-stone.com/
G
> stop sending me emails
We've stopped sending this person emails. no need to comment on this. :)
Continue with this great thread!
Thanks
Russ
BTW, every WSG email that goes out has an unsubscribe link at the bottom.
Better to click that that tell 7,000 people you don't want any emails :)
Heh! That is pretty funny!
However, clients may have the need to ensure a universal experience.
One example of this is in their brand values, which may call for a
certain look and feel. If a person experiences one thing on their
iPad and another experiences something different on their HP
stop sending me emails
On Wed, Oct 20, 2010 at 3:25 PM, Hassan Schroeder wrote:
> On 10/20/10 11:42 AM, cat soul wrote:
>>
>> I agree thoroughly, Hassan. Yet as this is a best-practices discussion and
>> group, and since
>> we've been hearing that these things A) don't always work and B) aren't
>
On 10/20/10 11:42 AM, cat soul wrote:
I agree thoroughly, Hassan. Yet as this is a best-practices discussion and
group, and since
we've been hearing that these things A) don't always work and B) aren't always
well-received by
end users, we're left with a need.
And that need is to know: out of
On Wed, Oct 20, 2010 at 1:42 PM, cat soul wrote:
> I agree thoroughly, Hassan. Yet as this is a best-practices discussion and
> group, and since we've been hearing that these things A) don't always work
> and B) aren't always well-received by end users, we're left with a need.
>
> And that need is
I agree thoroughly, Hassan. Yet as this is a best-practices
discussion and group, and since we've been hearing that these things
A) don't always work and B) aren't always well-received by end users,
we're left with a need.
And that need is to know: out of the universe of what we can do, wha
On 10/20/10 10:19 AM, cat soul wrote:
The picture I am developing now is this: HTML and CSS should be used strictly
for content,
structure and formatting.
*Behaviors* are best left to things like Javascript.
But it's not that cut and dried -- CSS has always had behaviors,
e.g. :hover, :focus
Well, I am down with that..I never did care for the jumpy, spinny,
whizzy things... As a print designer, I'm all about good design, good
typography, quality imagery and clear communication.
however, you sometimes get the idea that if you don't pay obeisance
to that fashion (jumpy, spinny, w
Help me if I mis-interpret the writer's fine article, but this
pertains to Javascript rollovers, too.
The end user doesn't know and doesn't care whether that thing popping
up was a CSS Hover, or a Javascript rollover. S/he only knows that,
by innocently mousing around, something popped up
Cat,
That's the holy trinity of web design: content, presentation and
behavior. ;)
Joseph R. B. Taylor
/Web Designer / Developer/
--
Sites by Joe, LLC
/"Clean, Simple and Elegant Web Design"/
Phone: (609) 335-3076
Web: http://sitesbyjoe.com
Email: j...@sites
I thank you for that link, David.
The picture I am developing now is this: HTML and CSS should be used
strictly for content, structure and formatting.
*Behaviors* are best left to things like Javascript.
Are these two statements ones that most here can buy into? Are they
fair statements,
From: "Patrick H. Lauke"
On 20/10/2010 10:44, cat soul wrote:
Yes, and while we're on the topic of things that won't work on phones
and iPadsis there anything else we need to know about that also
won't play nice with those two handheld platforms?
A gentle reminder that iDevices are not th
On 20 Oct 2010, at 16:59, cat soul wrote:
> will there be/can there be a new command/property which can be read by each
> device the way it needs to be?
>
> could there be soon a "touch" command so that you could write the code like:
>
> "hover, do this. If no hover, then touch, do this. If
Things are definitely better now than they once were in the world of
browsers.
Sure, we have a number of IE's of varying inability to deal with plus a
bunch of others.
Sure, we're constantly in a state of "it doesn't work on everything yet".
Sure, not one tool we use can be relied on 100% of
Well, you certainly busted wide open a huge can of worms, Joseph, and
I salute you for it.
the one comfy thing in that, to me, is the "no IE" part.
Starting with clean HTML is easy enough, but everything else is
squarely in the "don't count on it" category..revealing the lick and
a promise
will there be/can there be a new command/property which can be read
by each device the way it needs to be?
could there be soon a "touch" command so that you could write the
code like:
"hover, do this. If no hover, then touch, do this. If no touch, then
__ and do this"
?
On Oct
On 20/10/2010 10:44, cat soul wrote:
Yes, and while we're on the topic of things that won't work on phones
and iPadsis there anything else we need to know about that also
won't play nice with those two handheld platforms?
A gentle reminder that iDevices are not the only platform that has to
Good questions. I have yet to see definitive answers for most of these
questions.
I've been thinking on this constantly as I try to alter my work flow to
a format that will please all the devices.
Some things haven't changed:
Start with clean HTML that'll work on ANYTHING including JAWS etc.
Yes, and while we're on the topic of things that won't work on phones
and iPadsis there anything else we need to know about that also
won't play nice with those two handheld platforms?
Is a different design perspective in order now? Do we now design for
the iPad and for phones, and have
Good idea, but please remember that for someone with problems of
co-ordination or fine muscle control, hovering can be extremely
difficult. I've encountered javascript image galleries which work like
this, and on a bad day I find them completely unusable.
Lesley
On 19/10/10 21:13, cat soul w
An excellent and very up to date point about accessibility.
From: tee
Sent: Wednesday, October 20, 2010 1:57 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] CSS "rollovers" for images?
Caution with the use of hover for such purpose if you also want touchscreen
device user able to use it
26 matches
Mail list logo
