Alexey Feldgendler wrote:
Interesting. But this lacks one important thing: a clear indication of
why some page doesn't qualify as accessible. Google seems reluctant to
disclose their criteria, and it's a pity.
Indeed, and, from the broad indications they do give, there's /nothing/
to suggest
Indeed, and, from the broad indications they do give, there's /nothing/
to suggest that they favour conformant markup over non-conformant
markup: Currently we take into account several factors, including a
given page's simplicity, how much visual imagery it carries and whether
or not its primary
On Fri, 15 Dec 2006 11:03:23 +0100, Rimantas Liubertas
[EMAIL PROTECTED] wrote:
Make sure that your TITLE and ALT tags ...
Tags... Right.
--
Anne van Kesteren
http://annevankesteren.nl/
http://www.opera.com/
Make sure that your TITLE and ALT tags ...
Tags... Right.
ha ha, good catch, how did I miss this one...
Regards,
Rimantas
--
http://rimantas.com/
On Fri, 15 Dec 2006 15:49:24 +0600, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
I think basic conformance is part and parcel of creating an accessible,
interoperable site; but it's worth noting that there are plenty of
captains of accessibility who reject that viewpoint, e.g.:
Alexey Feldgendler wrote:
They do mention validation:
http://www.anysurfer.be/fr/obtenir-label/procedures-de-labellisation/la-validation/
-- though I'm not sure they mean ensuring valid HTML.
I'm afraid they mean validating to /their/ accessibility standards, not
the (X)HTML
When creating DHTML widgets (e.g. a colour picker) developers have to
battle the CSS cascade. A widget might be made of various HTML elements
which inherit style from the page. Sometimes inherited styles can mess
with the layout of your widget. So we end up coding stuff like this:
#widget div
On Fri, 15 Dec 2006 18:08:35 +0100, Dean Edwards [EMAIL PROTECTED] wrote:
Thoughts?
My thought is that this is a CSS issue and not a markup issue.
--
Anne van Kesteren
http://annevankesteren.nl/
http://www.opera.com/
Anne van Kesteren wrote:
On Fri, 15 Dec 2006 18:08:35 +0100, Dean Edwards [EMAIL PROTECTED] wrote:
Thoughts?
My thought is that this is a CSS issue and not a markup issue.
It feels right to fix it with markup. Maybe reset does not give the
right semantic meaning? But I hate the word
On 12/15/06, Dean Edwards [EMAIL PROTECTED] wrote:
Thoughts?
In Mozilla's xbl the attribute inheritstyle=false is used for that.
Maybe an attribute would be more appropriate?
I like the idea, because I have this problem also, once in a while.
But how would you be able to style the elements in
Dean Edwards wrote:
Anne van Kesteren wrote:
On Fri, 15 Dec 2006 18:08:35 +0100, Dean Edwards [EMAIL PROTECTED]
wrote:
Thoughts?
My thought is that this is a CSS issue and not a markup issue.
It feels right to fix it with markup. Maybe reset does not give the
right semantic meaning? But
On 12/15/06, Dean Edwards [EMAIL PROTECTED] wrote:
Thoughts?
It seems like a very good use case for using namespace...
Xmlizer
James Graham wrote:
But this element would be purely for the purpose of interacting with CSS
so it does indeed seem to be a CSS issue.
Not entirely. It also has some semantic value in that the element acts
as a container for other elements that comprise a widget. Perhaps
reset is the wrong
On Fri, 15 Dec 2006 23:45:52 +0600, Dean Edwards [EMAIL PROTECTED] wrote:
But this element would be purely for the purpose of interacting with
CSS so it does indeed seem to be a CSS issue.
Not entirely. It also has some semantic value in that the element acts
as a container for other
Alexey Feldgendler wrote:
Elements comprising a widget should carry appropriate semantic value by
themselves. For example, a properly styled unordered list can be used as
a color picker. widget should not be used as an excuse for writing a
bunch of meaningless divs to make a custom control.
On Fri, 15 Dec 2006 23:56:42 +0600, Dean Edwards [EMAIL PROTECTED] wrote:
Elements comprising a widget should carry appropriate semantic value by
themselves. For example, a properly styled unordered list can be used
as a color picker. widget should not be used as an excuse for writing
a
Alexey Feldgendler wrote:
In this context, fieldset would express the meaning better.
I guess you're right.
I would still like a way to prevent CSS inheritance though. So far the
suggestions are:
1. reset element
2. inheritstyle=false attribute
3. cascade:off; CSS property
I don't really
On Fri, 15 Dec 2006 19:27:28 +0100, Dean Edwards [EMAIL PROTECTED] wrote:
I guess you're right.
I would still like a way to prevent CSS inheritance though. So far the
suggestions are:
1. reset element
2. inheritstyle=false attribute
3. cascade:off; CSS property
I don't really mind which one
Hi,
Not entirely. It also has some semantic value in that the
element acts as a container for other elements that comprise
a widget. Perhaps reset is the wrong name.
Perhaps div encapsulate=true/div or something along those lines? I
agree there's the conceptual need - I'm tired of using
Anne van Kesteren wrote:
Now I get your widget idea better. Perhaps it would be useful to
look into XBL?
Yes, XBL can already do this for me. But I get the feeling that I won't
be able to use it (cross-browser) until the year 2056. :-(
-dean
On Fri, 15 Dec 2006, Dean Edwards wrote:
Yes, XBL can already do this for me. But I get the feeling that I won't
be able to use it (cross-browser) until the year 2056. :-(
Without actually making any comment on the proposal, or whether XBL solves
the problem at all (I haven't examined the
On Fri, 15 Dec 2006 18:26:53 +0100, Dean Edwards [EMAIL PROTECTED] wrote:
Anne van Kesteren wrote:
Dean Edwards wrote:
Thoughts?
My thought is that this is a CSS issue and not a markup issue.
I agree with Anne; this is a CSS issue.
It feels right to fix it with markup.
I completely
On 2006-12-16 00:52, Asbjørn Ulsberg wrote:
A much better solution is a 'reset' property or property value in CSS
that can reset different inherited and cascaded property values. I can
picture something like this:
#box {
color : red;
text-align: center;
}
#box div {
reset : color; /*
Dean Edwards wrote:
So I'm suggesting a new element: reset
This element is in the document flow as normal except that it acts as a
blank canvas as far as CSS is concerned. Ideally, it should have no
style at all.
This is definitely a styling issue, not an HTML issue. Other than using
XBL,
24 matches
Mail list logo
