Thierry Koblentz wrote:
Because
like I said, following this logic why not using table markup to
give
users
of other UAs (old visual browsers like IE 5 Mac, NN6, etc) a better
experience too? Why just SR users?
because thats a different issue. It's an issue of the user not
On Behalf Of Steve Green
I have a big problem with the term 'best practice', especially when it
is
used to effectively terminate a discussion. It implies that not only is
there currently no better solution, but that there never will be.
I believe that the most appropriate solution
Steve Green wrote:
I have a big problem with the term 'best practice', especially when it is
used to effectively terminate a discussion. It implies that not only is
there currently no better solution, but that there never will be.
I believe that the most appropriate solution invariably depends
] semantic list with explanations
Thierry Koblentz wrote:
Because
like I said, following this logic why not using table markup to
give
users
of other UAs (old visual browsers like IE 5 Mac, NN6, etc) a
better experience too? Why just SR users?
because thats a different issue. It's
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] semantic list with explanations
On Behalf Of Steve Green
I have a big problem with the term 'best practice', especially when it
is used to effectively terminate a discussion. It implies that not
only is there currently no better solution
David Hucklesby wrote:
On Wed, 09 Jan 2008 18:13:13 +1100, Chris Knowles wrote:
because thats a different issue. Its an issue of the user not upgrading to
software
thats available and thats better. ...
Just one niggle here. The user might well be using a computer
at work, school, a
Thierry Koblentz wrote:
Because
like I said, following this logic why not using table markup to give
users
of other UAs (old visual browsers like IE 5 Mac, NN6, etc) a better
experience too? Why just SR users?
because thats a different issue. Its an issue of the user not upgrading
to
agents is absurd.
Steve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Thierry Koblentz
Sent: 09 January 2008 06:58
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] semantic list with explanations
Absolutely it is. I'm rather surprised at how badly
On Wed, 09 Jan 2008 18:13:13 +1100, Chris Knowles wrote:
because thats a different issue. Its an issue of the user not upgrading to
software
thats available and thats better. ...
Just one niggle here. The user might well be using a computer
at work, school, a library, or an Internet café.
The desire for semantic purity is only one of many factors when
deciding how
to mark up a page. Other factors include (but are not limited to) UA
support, the user experience, the time available to implement the
design and
the expected life of the website. I would expect a professional
Thierry Koblentz wrote:
No, what I'm saying is that we should write semantic markup and hope
that SR
manufacturers fix their product asap.
JAWS, to name one product, is a very expensive software.
Freedomscientific
should take care of its customers, it is not to the authors to lower
Definition List?
On Jan 9, 2008 2:48 PM, Tim MacKay [EMAIL PROTECTED] wrote:
Hello all,
Just looking for a little help. I'm creating a sort of 'point form' list
that goes a bit like this:
1. Pursuit of customer satisfaction
We promise to pursue customer satisfaction as our
Definition List for sure.
E. Michael Brandt
www.divahtml.com
www.divahtml.com/products/scripts_dreamweaver_extensions.php
Standards-compliant scripts and Dreamweaver Extensions
www.valleywebdesigns.com/vwd_Vdw.asp
JustSo PictureWindow
JustSo PhotoAlbum, et alia
--
Tim MacKay wrote:
Hello all,
My first guess would be an ordered list but the definitions underneath don’t
really allow for
it.
Why?
A definition list doesn’t seem very appropriate either because of
the wordiness of the explanations; to me a true definition list would
only be a few words.
I think that definition lists would be appropriate semantically but in the
real world I don't know of any user agent that does anything useful with a
definition list or any user group that derives any benefit from them.
Certainly they make no sense when read with a screen reader because you
cannot
Steve Green wrote:
I think that definition lists would be appropriate semantically but in
the real world I don't know of any user agent that does anything useful
with a definition list or any user group that derives any benefit from
them. Certainly they make no sense when read with a screen
Tim,
a definition list is called for. You can set it to be numbered in the
CSS.
You could also use headings and paragraphs (semantically it is the same
as we have a set of name-value pairs). You could also use a two column
table (name-value pairs).
cheers
Paul
Paul MInty Director
the incentive for
SR manufacturers to take care of the problem?
--
Regards,
Thierry | http://www.TJKDesign.com
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Steve Green
Sent: Tuesday, January 08, 2008 8:19 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] semantic list
Unless order is important, I'd vote for a Definition List too
--
Regards,
Thierry | http://www.TJKDesign.com
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tim MacKay
Sent: Tuesday, January 08, 2008 7:49 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] semantic
I don't think theres any rules about the length of definitions?
You are correct sir.
A definition list implies to me the expansion of a term through
definition. If anything that means the more text the better! I just
noticed that Tim's list includes numbering... This means there could
be some
Thierry Koblentz wrote:
Isn't the responsibility of screen reader manufacturers to treat DLs for
what they are?
Following this logic, we should be using basic table markup for layout
to give people using old visual browsers a better experience.
If we cheat with the markup to please user
January 2008 05:21
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] semantic list with explanations
Hi Steve,
Isn't the responsibility of screen reader manufacturers to treat DLs for
what they are?
Following this logic, we should be using basic table markup for layout to
give people using old
Thierry Koblentz wrote:
Isn't the responsibility of screen reader manufacturers to treat DLs
for
what they are?
Following this logic, we should be using basic table markup for
layout
to give people using old visual browsers a better experience.
If we cheat with the markup to
Absolutely it is. I'm rather surprised at how badly they handle DLs, but
almost zero percent of web developers use them even now (remember that
standards-compliant designers represent perhaps 1% of the industry). Go
back just a few years and no one at all was using them.
Is it not also the
Thierry Koblentz wrote:
No, what I'm saying is that we should write semantic markup and hope that SR
manufacturers fix their product asap.
JAWS, to name one product, is a very expensive software. Freedomscientific
should take care of its customers, it is not to the authors to lower the
Tim MacKay wrote:
Hello all,
Just looking for a little help. I'm creating a sort of 'point form'
list that goes a bit like this:
1. Pursuit of customer satisfaction
We promise to pursue customer satisfaction as our main point of
customer focus...blah blah blah
2.
26 matches
Mail list logo
