WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: data table pagination - focus position?

for

From: glen walker
Date: Nov 7, 2018 11:24AM

This is more of a usability question than an accessibility question, but
still a great question.

Since the "next page" button is just updating part of the page, I prefer to
keep the focus where it is. I might want to hit "next page" several
times. If the focus had moved back to the table, I'd have to navigate back
to the next button every time.

After I get to the page I want, I can easily hit Shift+T to navigate back
to the table.

This is just my personal opinion and not based on any user research or
guidelines other than experience in the field.

Glen


On Wed, Nov 7, 2018 at 11:19 AM Tomlins Diane <
<EMAIL REMOVED> > wrote:

> This may have come up before, but searching the archives didn't bring up
> anything directly, so please forgive me if it has.
>
> The setup: we have a health portal application and within this application
> a patient can go to their profile and see an Activity Log showing every
> login, and what they did within the application, such as viewing clinical
> information. It's presented in a sortable data table where you can select
> how many records per page to display, the maximum is 20/page. A couple of
> the columns are sortable and at the bottom is the pagination with page
> numbers and previous/next buttons.
>
> For SR testing, I use NVDA. I'm assuming the typical method for
> navigating such tables using the arrow and ctrl+arrow keys?
>
> So my question is around focus when changing 'pages' - should focus remain
> where it is, at the pagination controls and just have it announce 'page 3
> of 15'? Is it typical to then have to back up thru the data table to get to
> the top of the new page of records? Should focus shift to the top of the
> new set of displayed records?
>
> It's one thing for me to use a mouse, or keyboard, and see the data change
> when you change pages and then just scroll up and down the page to view
> it, but what's the expected interaction for those who can't do that?
>
> I just want to be sure we're using the right interaction and not
> complicating things for AT users.
>
> Thanks for your input,
>
> Diane R Tomlins
> HCA IT&S | UXCOE
> Accessibility SME
>
> > > > >