WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: table paging

for

Number of posts in this thread: 17 (In chronological order)

From: adam solomon
Date: Sun, Jan 30 2011 3:21AM
Subject: table paging
No previous message | Next message →

What is the best way to implement a simple yet accessible paging. The two
standard ways I see all over the place are:
1. set of numbers, each one a link to that particular numbered page, with
arrow links to navigate to different sets of pages.
2. dropdownlist with all the pages, and a button next to it - choose the
page number and press go.

I personally prefer the second option - simple and to the point, and easier
to markp up correctly. Yet, I am worried about a situation where there are
many pages (500) and a keyboard user would have to navigate all the way down
with arrow keys. The truth is that this is a problem even in the numbering
paging - the user would have to suffer a number of postbacks before getting
to the correct set of pages.

Any thoughts?

--
adam solomon
linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
blogix <http://adam.blogix.co.il/>;

From: Priti
Date: Sun, Jan 30 2011 10:48PM
Subject: Re: table paging
← Previous message | Next message →

Hi Adam,

I will suggest go with the first option since users can click on the page
number and access the page whereas in case of the second option they need
to: 1. Select the relevant page number from the drop-down & 2. Hit the Go
button.

In case of large number of pages, a better alternative would be to provide
an edit box to allow users type in the page number. Of course one needs to
mention current as well as total number of pages (Page 1 of 500) to inform
users about the number of pages.

Hope this helps...

Thanks & Regards,
Priti Rohra
Head Accessibility Testing
Net Systems Informatics (India) Pvt. Ltd. & BarrierBreak Technologies
Web: www.n-syst.com | www.barrierbreak.com
Blog: www.barrierbreak.com/blog

Please don't print this email unless you really need to. This will preserve
trees on our planet.

From: Jeevan Reddy
Date: Sun, Jan 30 2011 11:30PM
Subject: Re: table paging
← Previous message | Next message →

Hi Adam,
I would Suggest you to go with First Method you Mentioned.
Irrespective of the number of pages you have, this method is popular now a
days, and accessible too.
And the numbered links can be accessible Via Link List for Screen Reader
users, and
You need to take Care of two things to implement this More Accessible.
1 Provide Enough clickable Area.
2 Provide Previous and Next Buttons(image buttons) so that Screen Reader
user can directly Access the Buttons and numbered list Between them as well.
Thanks and Regards,
Jeevan.

On Sun, Jan 30, 2011 at 3:49 PM, adam solomon
< = EMAIL ADDRESS REMOVED = >wrote:

> What is the best way to implement a simple yet accessible paging. The two
> standard ways I see all over the place are:
> 1. set of numbers, each one a link to that particular numbered page, with
> arrow links to navigate to different sets of pages.
> 2. dropdownlist with all the pages, and a button next to it - choose the
> page number and press go.
>
> I personally prefer the second option - simple and to the point, and easier
> to markp up correctly. Yet, I am worried about a situation where there are
> many pages (500) and a keyboard user would have to navigate all the way
> down
> with arrow keys. The truth is that this is a problem even in the numbering
> paging - the user would have to suffer a number of postbacks before getting
> to the correct set of pages.
>
> Any thoughts?
>
> --
> adam solomon
> linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
> blogix <http://adam.blogix.co.il/>;
>

From: William Lawrence
Date: Mon, Jan 31 2011 4:30AM
Subject: Re: table paging
← Previous message | Next message →

THere's a great paging information article out there that is not
available right now that talks about some different approaches to
paging.

THere's a copy here:
http://kurafire.net.sharedcopy.com/log/archive/2007/06/22/727aea9f881047adf6b42d874edd2bcd.html

The original was here:
http://kurafire.net/log/archive/2007/06/22/pagination-101

Best regards,
William
--
William Lawrence
Accessibility Engineer



On Mon, Jan 31, 2011 at 1:30 AM, Jeevan Reddy
< = EMAIL ADDRESS REMOVED = > wrote:
> Hi Adam,
>    I would Suggest you to go with First Method you Mentioned.
> Irrespective of the number of pages you have, this method is popular now a
> days, and accessible too.
> And the numbered links can be accessible Via Link List for Screen Reader
> users, and
> You need to take Care of two things to implement this More Accessible.
> 1 Provide Enough clickable Area.
> 2 Provide Previous and Next Buttons(image buttons) so that Screen Reader
> user can directly Access the Buttons and numbered list Between them as well.
> Thanks and Regards,
> Jeevan.
>
> On Sun, Jan 30, 2011 at 3:49 PM, adam solomon
> < = EMAIL ADDRESS REMOVED = >wrote:
>
>> What is the best way to implement a simple yet accessible paging. The two
>> standard ways I see all over the place are:
>> 1. set of numbers, each one a link to that particular numbered page, with
>> arrow links to navigate to different sets of pages.
>> 2. dropdownlist with all the pages, and a button next to it - choose the
>> page number and press go.
>>
>> I personally prefer the second option - simple and to the point, and easier
>> to markp up correctly. Yet, I am worried about a situation where there are
>> many pages (500) and a keyboard user would have to navigate all the way
>> down
>> with arrow keys. The truth is that this is a problem even in the numbering
>> paging - the user would have to suffer a number of postbacks before getting
>> to the correct set of pages.
>>
>> Any thoughts?
>>
>> --
>> adam solomon
>> linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
>> blogix <http://adam.blogix.co.il/>;
>>

From: Birkir Rúnar Gunnarsson
Date: Mon, Jan 31 2011 6:33AM
Subject: Re: table paging
← Previous message | Next message →

Would it be possible to provide both of these options (how much work
would that be)?
A third navigation possibility may be to navigate by chapters, have a
list box of chapters along with their page numbers (chapter 1, page4 -
chapter 2, page 23 - etc).
As a user I am most likely just reading the book through, page by
page, or I have to jump to a specific chapter, or I have to find a
specific page (assuming this is a book in html format).
The problem with next and prev buttons is that I may need to go to
page 116, this might be a text book for class, and I sure do not want
to click "next" 115 times, it would render the next nearly useless to
me.
By both having a next and prev buttons and a drop list you solve this problem.
Most often I will be reading a book straight through, but sometimes I
need to start reading at a certain point in the book.
The chaper idea is bonus, and might not be worth the implemntation effort.
Cheers
-B

On 1/31/11, William Lawrence < = EMAIL ADDRESS REMOVED = > wrote:
> THere's a great paging information article out there that is not
> available right now that talks about some different approaches to
> paging.
>
> THere's a copy here:
> http://kurafire.net.sharedcopy.com/log/archive/2007/06/22/727aea9f881047adf6b42d874edd2bcd.html
>
> The original was here:
> http://kurafire.net/log/archive/2007/06/22/pagination-101
>
> Best regards,
> William
> --
> William Lawrence
> Accessibility Engineer
>
>
>
> On Mon, Jan 31, 2011 at 1:30 AM, Jeevan Reddy
> < = EMAIL ADDRESS REMOVED = > wrote:
>> Hi Adam,
>>    I would Suggest you to go with First Method you Mentioned.
>> Irrespective of the number of pages you have, this method is popular now a
>> days, and accessible too.
>> And the numbered links can be accessible Via Link List for Screen Reader
>> users, and
>> You need to take Care of two things to implement this More Accessible.
>> 1 Provide Enough clickable Area.
>> 2 Provide Previous and Next Buttons(image buttons) so that Screen Reader
>> user can directly Access the Buttons and numbered list Between them as
>> well.
>> Thanks and Regards,
>> Jeevan.
>>
>> On Sun, Jan 30, 2011 at 3:49 PM, adam solomon
>> < = EMAIL ADDRESS REMOVED = >wrote:
>>
>>> What is the best way to implement a simple yet accessible paging. The two
>>> standard ways I see all over the place are:
>>> 1. set of numbers, each one a link to that particular numbered page, with
>>> arrow links to navigate to different sets of pages.
>>> 2. dropdownlist with all the pages, and a button next to it - choose the
>>> page number and press go.
>>>
>>> I personally prefer the second option - simple and to the point, and
>>> easier
>>> to markp up correctly. Yet, I am worried about a situation where there
>>> are
>>> many pages (500) and a keyboard user would have to navigate all the way
>>> down
>>> with arrow keys. The truth is that this is a problem even in the
>>> numbering
>>> paging - the user would have to suffer a number of postbacks before
>>> getting
>>> to the correct set of pages.
>>>
>>> Any thoughts?
>>>
>>> --
>>> adam solomon
>>> linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
>>> blogix <http://adam.blogix.co.il/>;
>>>

From: Accessibility India
Date: Mon, Jan 31 2011 9:36AM
Subject: Re: table paging
← Previous message | Next message →

I believe the list showed with google search results will be a better
choice which is almost near to your first option.

Thanks & regards
Rakesh
On 1/30/11, adam solomon < = EMAIL ADDRESS REMOVED = > wrote:
> What is the best way to implement a simple yet accessible paging. The two
> standard ways I see all over the place are:
> 1. set of numbers, each one a link to that particular numbered page, with
> arrow links to navigate to different sets of pages.
> 2. dropdownlist with all the pages, and a button next to it - choose the
> page number and press go.
>
> I personally prefer the second option - simple and to the point, and easier
> to markp up correctly. Yet, I am worried about a situation where there are
> many pages (500) and a keyboard user would have to navigate all the way down
> with arrow keys. The truth is that this is a problem even in the numbering
> paging - the user would have to suffer a number of postbacks before getting
> to the correct set of pages.
>
> Any thoughts?
>
> --
> adam solomon
> linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
> blogix <http://adam.blogix.co.il/>;
>

From: Langum, Michael J
Date: Mon, Jan 31 2011 10:00AM
Subject: Re: table paging
← Previous message | Next message →

It seems to me that the important issue here is what is the most appropriate form of navigation for large multi-page documents.

We need to ask, how will users navigate the content. In my experience, navigation by links to content blocks (e.g. chapter and section titles) is usually most appropriate. I think it is rare when users need to navigate by page number.

But I can imagine cases (e.g. you can find the answer to your question on page 132), where page navigation is desirable. But in these cases, PDF is usually preferable. And PDF readers have built-in page navigation.

If a large document must be provided in HTML, and must be navigable by page reference, then the implication is that the user (when beginning his session) already knows what page he/she wants. In that case an edit field seems more useful that a large drop-down list.

-- Mike




From: Birkir Rúnar Gunnarsson
Date: Mon, Jan 31 2011 10:12AM
Subject: Re: table paging
← Previous message | Next message →

Mike raises an important point here.
I believe edit fields for page numbers might be a very good solution,
when added to "next" "prev" and possibly chapter and section links.
The important bit is though that any html page navigation must be
consistent with page layout and content in other formats (such as
printed text).
The use case is that user may get a reference to a particular paragrph
or bit of information on a certain page, and he or she must be able to
consistently find that page in his version of the document, be it
Word, html, Daisy, text file or pdf.
I believe pdf will be a better medium than html for large books,
especially when the pdf-ua standard is out for more consistent
accessibility encoding.
Also pdf readers have security/DRM management capabilities, page
navigation built in etc.


On 1/31/11, Langum, Michael J < = EMAIL ADDRESS REMOVED = > wrote:
> It seems to me that the important issue here is what is the most appropriate
> form of navigation for large multi-page documents.
>
> We need to ask, how will users navigate the content. In my experience,
> navigation by links to content blocks (e.g. chapter and section titles) is
> usually most appropriate. I think it is rare when users need to navigate by
> page number.
>
> But I can imagine cases (e.g. you can find the answer to your question on
> page 132), where page navigation is desirable. But in these cases, PDF is
> usually preferable. And PDF readers have built-in page navigation.
>
> If a large document must be provided in HTML, and must be navigable by page
> reference, then the implication is that the user (when beginning his
> session) already knows what page he/she wants. In that case an edit field
> seems more useful that a large drop-down list.
>
> -- Mike
>
>
>
>
>

From: E.J. Zufelt
Date: Mon, Jan 31 2011 10:18AM
Subject: Re: table paging
← Previous message | Next message →

The edit field for page number is a good idea, when talking about documents.

If talking about other tabular data it may be less useful.

As an example, in the Drupal bug tracker you can access a listing of open issues, which is formatted into a table.

Searching the tracker for "accessibility" will give you several pages of results (50 results per page).

The data is tabular as it may contain table headings such as: Project, Issue, Status, Assigned to, etc.

In drupal the pager consists of links for: First, Previous, 1, 2, 3, 4, Next and Last.

I am not sure how many pages are required before the list of numbers is truncated.

HTH,
Everett Zufelt
http://zufelt.ca

Follow me on Twitter
http://twitter.com/ezufelt

View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt



On 2011-01-31, at 12:00 PM, Langum, Michael J wrote:

> It seems to me that the important issue here is what is the most appropriate form of navigation for large multi-page documents.
>
> We need to ask, how will users navigate the content. In my experience, navigation by links to content blocks (e.g. chapter and section titles) is usually most appropriate. I think it is rare when users need to navigate by page number.
>
> But I can imagine cases (e.g. you can find the answer to your question on page 132), where page navigation is desirable. But in these cases, PDF is usually preferable. And PDF readers have built-in page navigation.
>
> If a large document must be provided in HTML, and must be navigable by page reference, then the implication is that the user (when beginning his session) already knows what page he/she wants. In that case an edit field seems more useful that a large drop-down list.
>
> -- Mike
>
>
>
>
>

From: adam solomon
Date: Mon, Jan 31 2011 11:27AM
Subject: Re: table paging
← Previous message | Next message →

Just to clarify: I didn't make it clear before that I am talking about
tabular data, not pages of a book. For instance, a list of schools, which
might reach 1000. The number of the pages is not important except insomuch
as finding a particular school is concerned.

On Mon, Jan 31, 2011 at 7:15 PM, E.J. Zufelt < = EMAIL ADDRESS REMOVED = > wrote:

> The edit field for page number is a good idea, when talking about
> documents.
>
> If talking about other tabular data it may be less useful.
>
> As an example, in the Drupal bug tracker you can access a listing of open
> issues, which is formatted into a table.
>
> Searching the tracker for "accessibility" will give you several pages of
> results (50 results per page).
>
> The data is tabular as it may contain table headings such as: Project,
> Issue, Status, Assigned to, etc.
>
> In drupal the pager consists of links for: First, Previous, 1, 2, 3, 4,
> Next and Last.
>
> I am not sure how many pages are required before the list of numbers is
> truncated.
>
> HTH,
> Everett Zufelt
> http://zufelt.ca
>
> Follow me on Twitter
> http://twitter.com/ezufelt
>
> View my LinkedIn Profile
> http://www.linkedin.com/in/ezufelt
>
>
>
> On 2011-01-31, at 12:00 PM, Langum, Michael J wrote:
>
> > It seems to me that the important issue here is what is the most
> appropriate form of navigation for large multi-page documents.
> >
> > We need to ask, how will users navigate the content. In my experience,
> navigation by links to content blocks (e.g. chapter and section titles) is
> usually most appropriate. I think it is rare when users need to navigate by
> page number.
> >
> > But I can imagine cases (e.g. you can find the answer to your question on
> page 132), where page navigation is desirable. But in these cases, PDF is
> usually preferable. And PDF readers have built-in page navigation.
> >
> > If a large document must be provided in HTML, and must be navigable by
> page reference, then the implication is that the user (when beginning his
> session) already knows what page he/she wants. In that case an edit field
> seems more useful that a large drop-down list.
> >
> > -- Mike
> >
> >
> >
> >
> >

From: Jordan, Courtney
Date: Mon, Jan 31 2011 1:48PM
Subject: Re: table paging
← Previous message | Next message →

That's certainly a lot of pages! Is there any way that you can break it
up into categories? Even as a sighted user, I would be frustrated
looking through 500 options in a drop-down list. That is assuming that I
even knew what the particular title of the page was. We can't expect
people to remember the title of every page. People can generally hold
about 5-7 or fewer items in memory. From my experience using JAWS 9, I
couldn't get the screen reader to "read" any items under the first one.
It would automatically trigger the first one and I would never get to
the others. Including a button avoided that issue as it didn't trigger a
JavaScript event from the drop-down selection itself, but from the
clicking of the button.

Good luck!
Courtney Jordan

From: adam solomon
Date: Tue, Feb 01 2011 1:15AM
Subject: Re: table paging
← Previous message | Next message →

The app includes a search form which gives you the ability to filter
results, and generally, it is expected someone would filter the results to
only a few pages. But, if one does not filter, then he can get access to the
whole list. No one is going to actually know what schools are on each page
(each page contains about 15 results), but someone who didn't filter and
wanted to navigate to the a school starting with the letter m (middle of the
alphabet) would have to navigate a whole lot either way.

On Mon, Jan 31, 2011 at 10:46 PM, Jordan, Courtney < = EMAIL ADDRESS REMOVED = >wrote:

> That's certainly a lot of pages! Is there any way that you can break it
> up into categories? Even as a sighted user, I would be frustrated
> looking through 500 options in a drop-down list. That is assuming that I
> even knew what the particular title of the page was. We can't expect
> people to remember the title of every page. People can generally hold
> about 5-7 or fewer items in memory. From my experience using JAWS 9, I
> couldn't get the screen reader to "read" any items under the first one.
> It would automatically trigger the first one and I would never get to
> the others. Including a button avoided that issue as it didn't trigger a
> JavaScript event from the drop-down selection itself, but from the
> clicking of the button.
>
> Good luck!
> Courtney Jordan
>
>

From: Jim Allan
Date: Tue, Feb 01 2011 6:51AM
Subject: Re: table paging
← Previous message | Next message →

what about an option to display all results on one page, then the user
could use the in page search to quickly (relatively) jump.

Jim

On Tue, Feb 1, 2011 at 2:05 AM, adam solomon
< = EMAIL ADDRESS REMOVED = > wrote:
> The app includes a search form which gives you the ability to filter
> results, and generally, it is expected someone would filter the results to
> only a few pages. But, if one does not filter, then he can get access to the
> whole list. No one is going to actually know what schools are on each page
> (each page contains about 15 results), but someone who didn't filter and
> wanted to navigate to the a school starting with the letter m (middle of the
> alphabet) would have to navigate a whole lot either way.
>
> On Mon, Jan 31, 2011 at 10:46 PM, Jordan, Courtney < = EMAIL ADDRESS REMOVED = >wrote:
>
>> That's certainly a lot of pages! Is there any way that you can break it
>> up into categories? Even as a sighted user, I would be frustrated
>> looking through 500 options in a drop-down list. That is assuming that I
>> even knew what the particular title of the page was. We can't expect
>> people to remember the title of every page. People can generally hold
>> about 5-7 or fewer items in memory. From my experience using JAWS 9, I
>> couldn't get the screen reader to "read" any items under the first one.
>> It would automatically trigger the first one and I would never get to
>> the others. Including a button avoided that issue as it didn't trigger a
>> JavaScript event from the drop-down selection itself, but from the
>> clicking of the button.
>>
>> Good luck!
>> Courtney Jordan
>>
>>

From: ckrugman
Date: Fri, Feb 04 2011 3:48PM
Subject: Re: table paging
← Previous message | Next message →

usually with screen reader users in a dropdown menu they can type the
appropriatae page number once they are on the menu and it will take them to
the appropriate page so as to not have to use the arrow keys.
Chuck
----- Original Message -----
From: "adam solomon" < = EMAIL ADDRESS REMOVED = >
To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
Sent: Sunday, January 30, 2011 2:19 AM
Subject: [WebAIM] table paging


> What is the best way to implement a simple yet accessible paging. The two
> standard ways I see all over the place are:
> 1. set of numbers, each one a link to that particular numbered page, with
> arrow links to navigate to different sets of pages.
> 2. dropdownlist with all the pages, and a button next to it - choose the
> page number and press go.
>
> I personally prefer the second option - simple and to the point, and
> easier
> to markp up correctly. Yet, I am worried about a situation where there are
> many pages (500) and a keyboard user would have to navigate all the way
> down
> with arrow keys. The truth is that this is a problem even in the numbering
> paging - the user would have to suffer a number of postbacks before
> getting
> to the correct set of pages.
>
> Any thoughts?
>
> --
> adam solomon
> linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
> blogix <http://adam.blogix.co.il/>;
>

From: adam solomon
Date: Sat, Feb 05 2011 11:39AM
Subject: Re: table paging
← Previous message | Next message →

We still have to take into consideration keyboard (not blind) users

On Sat, Feb 5, 2011 at 12:43 AM, < = EMAIL ADDRESS REMOVED = > wrote:

> usually with screen reader users in a dropdown menu they can type the
> appropriatae page number once they are on the menu and it will take them to
> the appropriate page so as to not have to use the arrow keys.
> Chuck
> ----- Original Message -----
> From: "adam solomon" < = EMAIL ADDRESS REMOVED = >
> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> Sent: Sunday, January 30, 2011 2:19 AM
> Subject: [WebAIM] table paging
>
>
> > What is the best way to implement a simple yet accessible paging. The two
> > standard ways I see all over the place are:
> > 1. set of numbers, each one a link to that particular numbered page, with
> > arrow links to navigate to different sets of pages.
> > 2. dropdownlist with all the pages, and a button next to it - choose the
> > page number and press go.
> >
> > I personally prefer the second option - simple and to the point, and
> > easier
> > to markp up correctly. Yet, I am worried about a situation where there
> are
> > many pages (500) and a keyboard user would have to navigate all the way
> > down
> > with arrow keys. The truth is that this is a problem even in the
> numbering
> > paging - the user would have to suffer a number of postbacks before
> > getting
> > to the correct set of pages.
> >
> > Any thoughts?
> >
> > --
> > adam solomon
> > linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
> > blogix <http://adam.blogix.co.il/>;
> >

From: ckrugman
Date: Sun, Feb 06 2011 5:45AM
Subject: Re: table paging
← Previous message | Next message →

JAWS versions will read items in a dropdown menu using a particular command
"alt down arrow" in most cases.
Chuck
----- Original Message -----
From: "Jordan, Courtney" < = EMAIL ADDRESS REMOVED = >
To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
Sent: Monday, January 31, 2011 12:46 PM
Subject: Re: [WebAIM] table paging


> That's certainly a lot of pages! Is there any way that you can break it
> up into categories? Even as a sighted user, I would be frustrated
> looking through 500 options in a drop-down list. That is assuming that I
> even knew what the particular title of the page was. We can't expect
> people to remember the title of every page. People can generally hold
> about 5-7 or fewer items in memory. From my experience using JAWS 9, I
> couldn't get the screen reader to "read" any items under the first one.
> It would automatically trigger the first one and I would never get to
> the others. Including a button avoided that issue as it didn't trigger a
> JavaScript event from the drop-down selection itself, but from the
> clicking of the button.
>
> Good luck!
> Courtney Jordan
>
>

From: adam solomon
Date: Tue, Mar 01 2011 11:48PM
Subject: Re: table paging
← Previous message | No next message

Going with the list of links option where there are numbered links and arrow
links to get to a different set of pages: the arrow links are just text -
i.e. one or two arrow characters. Even if we add a title specifying the
function of this link (namely to navigate to the next set of pages) is this
wcag conformed? Title attribute is not well supported in a link where there
is text - and understanding the link's function from the text (arrows) might
be a bit shaky? What say all of you?

On Sun, Feb 6, 2011 at 2:44 PM, < = EMAIL ADDRESS REMOVED = > wrote:

> JAWS versions will read items in a dropdown menu using a particular command
> "alt down arrow" in most cases.
> Chuck
> ----- Original Message -----
> From: "Jordan, Courtney" < = EMAIL ADDRESS REMOVED = >
> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> Sent: Monday, January 31, 2011 12:46 PM
> Subject: Re: [WebAIM] table paging
>
>
> > That's certainly a lot of pages! Is there any way that you can break it
> > up into categories? Even as a sighted user, I would be frustrated
> > looking through 500 options in a drop-down list. That is assuming that I
> > even knew what the particular title of the page was. We can't expect
> > people to remember the title of every page. People can generally hold
> > about 5-7 or fewer items in memory. From my experience using JAWS 9, I
> > couldn't get the screen reader to "read" any items under the first one.
> > It would automatically trigger the first one and I would never get to
> > the others. Including a button avoided that issue as it didn't trigger a
> > JavaScript event from the drop-down selection itself, but from the
> > clicking of the button.
> >
> > Good luck!
> > Courtney Jordan
> >
> >