form id=seek action=seek.php method=post
fieldset
label for=seektextSeek: /label
input name=seektext id=seektext type=text /
input type=submit value=sök /
/fieldset
/form
A few days ago i have the same problem, legend or not legend, sow i
think if fieldset are to allows
Marvin,
The WSG list isn't for discussing client or server side scripting. The list
guidelines discuss what is applicable for this list.
Cheers
James
Admin.
On 11/30/06, marvin hunkin [EMAIL PROTECTED] wrote:
Hi.
do you know of any php accessible and java script mailling lists.
if so let me
Gaspar wrote:
How can i group just one single input? i think there's no reason to do
that, sow i removed the fieldset and just use the label for the input.
am i right or not?
For my own tuppence, I'd say there's no reason for it. I'm almost
certain I've seen pages adorned with every kind of
Hmm, I've found this not to work in Firefox.. doesn't seem to allow legends
to be positioned off screen. display:none works but that defeats the purpose
entirely.
I've found legends very difficult to be styled cross browser - dumping the
legend and using a heading tag will allow much easier
Hello,
I just cant remember who call to definition list dl as description list.
I would use a dl dt dd to your Actors Name list, i know that you
can call as tabular data but in that case i think is better a dl
If u prefer table u can use
table summary=
caption/caption
thead
trth id=actorActor
I just ran a form with a xhtml strict doctype and no legend thru the W3C
validator and it didn't complain..?
XHTML strict won't but HTML strict will.
--
Tyssen Design
www.tyssendesign.com.au
Ph: (07) 3300 3303
Mb: 0405 678 590
On 2006/11/30 14:07 (GMT) ed radford apparently typed:
i am currently working on a simple site and thought it to be a good
opertunity to try and implement some image and text scaling using
ems. have got everything working fine on safari and such but the
design gets completely broken in
I had written:
fieldset {
border : 0;
}
legend {
position : absolute ;
top : -9000px;
left : -9000px;
}
James wrote:
[...] doesn't seem to allow legends
to be positioned off screen [...]
Whoops, I did not know this. Sorry.
I've found legends very difficult to be styled cross
[...] doesn't seem to allow legends
to be positioned off screen [...]
Whoops, I did not know this. Sorry.
That's the truth! I use them but I do allow for some cross-browser
variances. They aren't a mandatory element, but they *can* be helpful,
especially for complex forms. I think a
i'm not quite sure what you mean here. the revised original menu listed all
of the main links in a tree(?). what i want to do is hide the subnav parts
and have them exposed on hover. now what you are saying, i think, is that
this is not a user friendly way to do the vertical menu.
the menu in
Hi All,
Just my penneth worth.
I have always said anything that needs a plugin is automaticaly
un-accessable.
Trevor.
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
That's not taking things to an extreme - it's a totally different argument
altogether. A screen reader is a user agent, not a plug-in. A person uses a
screen reader because they want or have to, not because of the technologies
used to build the websites they view. That's totally different from
ah ha, onclick. i like that. so i guess i go borrow your code? is there
js involved? there doesn't seem to be any here, yes?
thanks, this is a terrific solution and i think it works better for me.
dwain
On 11/30/06, Thierry Koblentz [EMAIL PROTECTED] wrote:
Dwain Alford wrote:
i'm not
Dwain Alford wrote:
ah ha, onclick. i like that. so i guess i go borrow your code? is
there js involved? there doesn't seem to be any here, yes?
Yes, it is needed to reveal the sub-menus, and to create the skip links,
but it is unobtrusive and it degrades well (the menu expands if there is
You're talking to someone who deals with accessibility frustrations
every single day of her life.
I'd sure like to see that all spoken audio in electronic media (video
games, video clips of newscasts on the Internet, etc.) be
captioning/subtitling-enabled (can be turned on or off by the
I totally agree with your point about accessible content, which is why we have
contributed towards Joe Clark's micropatronage project to raise money for
research into the production of standards, training and certification schemes
for captioning, audio description, subtitling, and dubbing.
Yes, although I think a more to the point of his question is why such
sites render even when served as xhtml.
Tee, the problem is quite complicated and would take quite a few words
to explain fully, however what follows are the bare basics.
When viewing an xhtml page with an xhtml doctype
I have found companies and governments to be totally unresponsive to
standards.
In the USA esp. target, but also Walmart etc. The American government
couldn't care less.
Most sites fail S.508 testing even their best Ivy league Universities.
On Thu, 30 Nov 2006 17:34:58 -0800, Scott Tankard wrote:
[...]
When viewing an xhtml page with an xhtml doctype and served as
application/xhtml+xml mime type, the markup errors you described (in fact
pretty much all markup errors) would give and ugly yellow 'parsing error'
page in Firefox.
19 matches
Mail list logo
