I am working on a web form that has Optgroup in it, and the first
time I realized browsers render this attribute differently.
I have something like this:
optgroup label=United States
option label=CA value=CaliforniaCalifornia/option
/optgroup
In Firefox, it display: California
On Oct 24, 2007, at 3:27 PM, Tee G. Peng wrote:
I am working on a web form that has Optgroup in it, and the first
time I realized browsers render this attribute differently.
IE Mac displays 'CA' in your 1st example
IE 7 Win displays 'CA' in your 1st example
Opera 9.5 alpha: idem ditto.
I
Hi all,
I'm looking for up to date info on title attribute behaviour screen
readers, especially where used on site global navigation.
As an example, http://www.e.govt.nz uses fairly long title attributes
for the main navigation links, and this repeats throughout the site
(i.e., not just on the
Hi Rebecca,
announcing of title attribute values on links is not a default screen
reader behaviour and for JAWS the announcing of the title attribute is
an OR choice (read title or link content) so effectively the title
attribute conentt for links is unavailable to most screen reader
users.
On
Hi Steve,
If I may follow on to Rebecca's query and based your reply, is it then
considered good practice (in general) _not_ to add title attributes and
values to hyperlinks?
Kind regards,
Frank
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Steven
Frank Palinkas wrote:
If I may follow on to Rebecca's query and based your reply, is it then
considered good practice (in general) _not_ to add title attributes and
values to hyperlinks?
You can add them, but you must be aware that it's likely that screen
reader users won't hear them by
Thanks Steven. Combined with Patrick's reply, and based on your experience
and deep involvement with accessibility, this is indeed excellent, practical
advice.
Kind regards,
Frank
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Steven Faulkner
Sent:
Hi Frank,
I would suggest that if you want the information available to screen
reader users or keyboard only users (as title attribute content is not
available to keyboard users), then don't place it in the title
attribute on links.
On 24/10/2007, Frank Palinkas [EMAIL PROTECTED] wrote:
Hi
Patrick H. Lauke wrote:
Also, sighted keyboard users will never see them either.
If they use IE.
Kind Regards
--
Chris Price
Choctaw
[EMAIL PROTECTED]
http://www.choctaw.co.uk
Tel. 01524 825 245
Mob. 0777 451 4488
Beauty is in the Eye of the Beholder
while Excellence is in the Hand of the
Also, sighted keyboard users will never see them either.
If they use IE.
although users of firefox can access the title attribute via the
keyboard, there is no way for them to know that there is a title there
to be queried, unlike mouse users who are presented with the title as
a tooltp when
Chris Price wrote:
Patrick H. Lauke wrote:
Also, sighted keyboard users will never see them either.
If they use IE.
Or Firefox, or Safari, or Opera, ...
Try tabbing to a link with a title via keyboard, and tell me if it
brings up a tooltip or similar to let a sighted user read the title...
On Oct 24, 2007, at 4:27 AM, Patrick H. Lauke wrote:
Try tabbing to a link with a title via keyboard, and tell me if it
brings up a tooltip or similar to let a sighted user read the title...
So it's concluded that title attribute is as useless as tabindex and
accesskey and therefor
So it's concluded that title attribute is as useless as tabindex
and accesskey and therefor shouldn't be used at all?
Need acknowledge by your accessible mastero :)
Need acknowledge from your accessible mastero :-)
tee
Patrick H. Lauke wrote:
Chris Price wrote:
Patrick H. Lauke wrote:
Also, sighted keyboard users will never see them either.
If they use IE.
Or Firefox, or Safari, or Opera, ...
Try tabbing to a link with a title via keyboard, and tell me if it
brings up a tooltip or similar to let a
Chris Price wrote:
I stand corrected.
You can sit as well, it's fine :)
P
--
Patrick H. Lauke
__
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk |
On Oct 24, 2007, at 12:14 AM, Philippe Wittenbergh wrote:
On Oct 24, 2007, at 3:27 PM, Tee G. Peng wrote:
I am working on a web form that has Optgroup in it, and the first
time I realized browsers render this attribute differently.
IE Mac displays 'CA' in your 1st example
IE 7 Win
On Oct 24, 2007, at 10:37 PM, Tee G. Peng wrote:
Under 17.6.1 it says (specifically for label in option):
http://www.w3.org/TR/html401/interact/forms.html#adef-label-OPTION
label = text [CS]
This attribute allows authors to specify a shorter label for
an option than the content of the
On 24 Oct 2007, at 14:37, Tee G. Peng wrote:
We must use 'label' right?
option label=3.7 value=pm2_3.7PortMaster 2 with ComOS 3.7/
option
The label attribute is only required on optgroup; it is optional on
option. If browsers are behaving differently when it's used on
option, just
I agree with what everyone is saying, altough it is not always
feasible to make the link text descriptive and sometimes makes it look
clunky when you've added the read more link straight after the
title, having to write read more about... and repeat the title
again.
All that aside, it is a
Hi all,
I've managed to avoid doing this for while, but I'm doing a CMS job
and the content in a floated group of LI's is going to be differeing
heights. They need to wrap onto a new line when they hit the right
edge of the container, causing layout problems.
I've found this article, but it
Personally, I often still use the keyboard because I'm fast with it.
And I really like good tabindexes. Why do you think they are useless?
Regards,
Rogier.
On 24/10/2007, Tee G. Peng [EMAIL PROTECTED] wrote:
So it's concluded that title attribute is as useless as tabindex
and accesskey
Can someone explain why I am generating a horizontal scroll bar at
1024 width?
http://www3.andersrice.com/
Thanks,
Dean
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
I use keyboard controls a lot too, and generally regard the use of tabindex
as a sign that a site was not designed properly in the first place. It
causes a number of problems such as being unable to predict where the focus
is going to go next. How can the designer predict what the user will want
Hi Dean,
Not sure what these two styles are actually doing but it looks like
they're the cause within your menu.css
#p7TBMsub03 { padding: 0 0 0 150px; }
#p7TBMsub04 { padding: 0 0 0 210px; }
Removing them seems to fix the problem with no adverse effect.
Cheers
Dave
- - - - - - - - - -
Dave
Actually, further investigation, I've spotted what's happening.
You're hiding the submenu's using this
.p7TBMsub {
position: absolute;
visibility:hidden;
left: 0;
top: 0;
width: 100%;
}
But then you're forgetting that the 100% width is being combined with
visibility: hidden does hide the content from screen readers the same as
display:none does.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Woods
Sent: 24 October 2007 22:04
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Minimum width help
visibility: hidden does hide the content from screen readers the same as
display:none does.
And it may get your site banned from search engines if overused:
http://www.google.com/support/webmasters/bin/answer.py?answer=66353
What I've done for accesskey code is use this:
position: absolute;
On Oct 24, 2007, at 5:04 PM, Dave Woods wrote:
You could take my original suggestion and remove the padding but the
better suggestion would be just to remove the width: 100%;
Thanks for the assist Dave.
***
List Guidelines:
Not in Safari Dean!
Tom
On 24 Oct 2007, at 21:05, Dean Matthews wrote:
Can someone explain why I am generating a horizontal scroll bar at
1024 width?
http://www3.andersrice.com/
Thanks,
Dean
***
List Guidelines:
Posted an article on this topic yesterday. Would be interested to hear
what you lot have to say about it: :)
http://www.datalink.com.au/company/emagination/webdev/improving_website_image_and_map_accessibility_
Regards,
Karl Lurman
I've been looking around the Opera site, but can't find answers to the
following:
Does Opera on the Wii support handlheld and/or projection stylesheets?
SVG?
Also, is SVG supported on the Nintendo DS browser?
Thanks,
Geoff.
Seeing as it looks like your developing for the browser without actually
having a Wii. I believe the PAL resolution is 480p (720x480). Obviously
also just take care not to have anything too fancy as it may be
difficult to interact with.
Geoff Pack wrote:
I've been looking around the Opera
I've managed to avoid doing this for while, but I'm doing a CMS job
and the content in a floated group of LI's is going to be differeing
heights. They need to wrap onto a new line when they hit the right
edge of the container, causing layout problems.
Would need to see what you have at the
33 matches
Mail list logo
