E-mail List Archives
Re: Need Accessibility solution for Fliter Options in the website
From: YOUNGV5
Date: Jul 22, 2011 8:00AM
- Next message: Andrew Kirkpatrick: "Re: Is noscript really needed to comply with 508>"
- Previous message: Ney André de Mello Zunino : "Re: Concurrent use of aria-describedby and aria-activedescendant"
- Next message in Thread: Jared Smith: "Re: Need Accessibility solution for Fliter Options in the website"
- Previous message in Thread: Mayur.Dawda@cognizant.com: "Need Accessibility solution for Fliter Options in the website"
- View all messages in this Thread
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 REMOVED>
From:
Jared Smith < <EMAIL REMOVED> >
To:
WebAIM Discussion List < <EMAIL REMOVED> >
Date:
07/22/2011 09:47 AM
Subject:
Re: [WebAIM] Need Accessibility solution for Fliter Options in the website
Sent by:
<EMAIL REMOVED>
On Fri, Jul 22, 2011 at 6:23 AM, < <EMAIL 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
- Next message: Andrew Kirkpatrick: "Re: Is noscript really needed to comply with 508>"
- Previous message: Ney André de Mello Zunino : "Re: Concurrent use of aria-describedby and aria-activedescendant"
- Next message in Thread: Jared Smith: "Re: Need Accessibility solution for Fliter Options in the website"
- Previous message in Thread: Mayur.Dawda@cognizant.com: "Need Accessibility solution for Fliter Options in the website"
- View all messages in this Thread