E-mail List Archives
Thread: Need Accessibility solution for Fliter Options in the website
Number of posts in this thread: 3 (In chronological order)
From: Mayur.Dawda@cognizant.com
Date: Fri, Jul 22 2011 6:27AM
Subject: Need Accessibility solution for Fliter Options in the website
No previous message | Next message →
Accessibility Issue:
Normally checkbox is clubbed with label "for" attribute.
How to inform user onclick of checkbox the page is refreshed.
This kind of feature normally we see in the filter's. For example in
amazon, ebay etc. Onclick of any filter options page is refreshed but
the disabled user is not informed in adavance regarding the same.
Example Code:
<fieldset>
<legend>Hobbies</legend>
<ul>
<li>
<input type="checkbox" onclick="http://......com"
title="On Select of cricket page will refresh" id="txt_cricket"/>
<label for="txt_cricket">Cricket</label>
</li>
</ul>
</fieldset>
Solution:
1) Normally one solution is to provide button, user will filter the
options and then click on search but here comes the usability issues for
normal peoples.
Please let me know the best Accessibility solution towards the same.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
From: YOUNGV5@nationwide.com
Date: Fri, Jul 22 2011 8:00AM
Subject: Re: Need Accessibility solution for Fliter Options in the website
← Previous message | Next message →
I'll just add one possible addition:
As long as the situation is appropriate, consider using ARIA to notify
screen reader users of the changes. You would need to take a look at the
user experience and decide what should and should not be notified.
http://codetalks.org/wiki/index.php/How_to_use_ARIA_Live_Regions_for_dynamic_content
Vincent Young
User Experience, Web Accessibility Specialist
Nationwide Corporate Marketing
Nationwide®
o | 614·677·5094
c | 614·607·3400
e | = EMAIL ADDRESS REMOVED =
From:
Jared Smith < = EMAIL ADDRESS REMOVED = >
To:
WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Date:
07/22/2011 09:47 AM
Subject:
Re: [WebAIM] Need Accessibility solution for Fliter Options in the website
Sent by:
= EMAIL ADDRESS REMOVED =
On Fri, Jul 22, 2011 at 6:23 AM, < = EMAIL ADDRESS REMOVED = > wrote:
> Onclick of any filter options page is refreshed but
> the disabled user is not informed in adavance regarding the same.
In your example, I don't think anyone would be aware of the page
refresh. I don't see any necessity to inform screen reader users (I'm
assuming this is what you mean by "disabled user") of a refresh that
sighted users will be equally unaware of.
> 1) Normally one solution is to provide button, user will filter the
> options and then click on search but here comes the usability issues for
> normal peoples.
Buttons are used all the time by those with and without disabilities.
Next to links, they are the most common way of requesting page
changes. I see no issue with presenting a button in this situation.
This would likely be the most accessible and intuitive approach.
To summarize, I would suggest:
1. Leaving as it is and cause the page refresh. This seems to be
equally inaccessible to all users, so isn't very optimal.
2. Rather than causing a page refresh, you could use scripting to
modify the page to present the appropriate content updates after the
checkbox is selected.
3. Use a standard button to submit the form information.
Jared
From: Jared Smith
Date: Fri, Jul 22 2011 8:18AM
Subject: Re: Need Accessibility solution for Fliter Options in the website
← Previous message | No next message
On Fri, Jul 22, 2011 at 6:23 AM, < = EMAIL ADDRESS REMOVED = > wrote:
> Onclick of any filter options page is refreshed but
> the disabled user is not informed in adavance regarding the same.
In your example, I don't think anyone would be aware of the page
refresh. I don't see any necessity to inform screen reader users (I'm
assuming this is what you mean by "disabled user") of a refresh that
sighted users will be equally unaware of.
> 1) Normally one solution is to provide button, user will filter the
> options and then click on search but here comes the usability issues for
> normal peoples.
Buttons are used all the time by those with and without disabilities.
Next to links, they are the most common way of requesting page
changes. I see no issue with presenting a button in this situation.
This would likely be the most accessible and intuitive approach.
To summarize, I would suggest:
1. Leaving as it is and cause the page refresh. This seems to be
equally inaccessible to all users, so isn't very optimal.
2. Rather than causing a page refresh, you could use scripting to
modify the page to present the appropriate content updates after the
checkbox is selected.
3. Use a standard button to submit the form information.
Jared