I don't recommend that solution. We have tested this kind of form with a
highly proficient screen reader user, and he could not understand it at all.
In fact it was one of the few tasks he has ever failed to complete. This is
one of those cases where marking up content so it is semantically
Hi Nick,
The sample code on this page you link to does not look ideal. As has been
mentioned on this list a few times, title attributes are often ignored by
screen readers. And the use of a table element to lay out the form is a
little odd.
Unless I am missing something, I'd say it would be much
Steve Green wrote:
I recommend using label elements for each radio button and hiding them
off-screen.
Possibly even better for keyboard and screenreader users: swapping out
the radio buttons approach with a single SELECT. However, this of course
throws the expected visual design out the
Hi Patrick,
Actually I had already prepared one as an alternative version to
discuss with the client so glad you brought it up independently.
Nick
On 04/12/2007, at 5:10 AM, Patrick H. Lauke wrote:
Steve Green wrote:
I recommend using label elements for each radio button and
hiding them
Hi Steve,
I don't recommend that solution. We have tested this kind of form
with a
highly proficient screen reader user, and he could not understand
it at all.
In fact it was one of the few tasks he has ever failed to complete.
This is
one of those cases where marking up content so it is
On 04/12/2007, at 12:07 AM, russ - maxdesign wrote:
Hi Nick,
The sample code on this page you link to does not look ideal. As
has been
mentioned on this list a few times, title attributes are often
ignored by
screen readers. And the use of a table element to lay out the form
is a
The problem with the code below is that the content of the legend
will be
read before every label. That makes it very difficult for a
screen reader
user to read it fast. I would just have the question in a p or
possibly
even a header element.
Once the user has read through a few questions
Steve Green wrote:
The problem with the code below is that the content of the legend will be
read before every label. That makes it very difficult for a screen reader
user to read it fast. I would just have the question in a p or possibly
even a header element.
However, if the user is in JAWS'
@webstandardsgroup.org
Subject: Re: [WSG] Accessible likert scale (disagree/agree/strongly
agree/etc) forms
On 04/12/2007, at 12:07 AM, russ - maxdesign wrote:
Hi Nick,
The sample code on this page you link to does not look ideal. As has
been mentioned on this list a few times, title attributes are often
PROTECTED] On
Behalf Of Nick Lo
Sent: 03 December 2007 23:51
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessible likert scale (disagree/agree/strongly
agree/etc) forms
The problem with the code below is that the content of the legend
will be read before every label. That makes it very
to navigate quickly.
Steve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Patrick H. Lauke
Sent: 04 December 2007 00:00
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessible likert scale (disagree/agree/strongly
agree/etc) forms
Steve Green wrote
they will be able to navigate quickly.
Steve
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Patrick H. Lauke
Sent: 04 December 2007 00:00
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessible likert scale (disagree/agree/strongly
agree/etc) forms
12 matches
Mail list logo
