WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: data table pagination - focus position?

for

From: Brandon Keith Biggs
Date: Nov 9, 2018 4:04AM


Hello,
AccDC has a perfect example of how to do a datatable for screen reader
users:
http://whatsock.com/tsg/Coding%20Arena/ARIA%20Data%20Grids/ARIA%20Data%20Grid%20(Dynamic)/demo.htm

Thanks,


Brandon Keith Biggs <http://brandonkeithbiggs.com/>;


On Thu, Nov 8, 2018 at 7:06 PM Jonathan Avila < <EMAIL REMOVED> >
wrote:

> I agree -- for sighted keyboard users leaving focus on the next button may
> make sense -- but screen readers will definitely need some information
> letting them know that the main context of the page indeed was updated and
> they may also want some context of what changed to make the decision to
> read it or move on the next or go back to the previous page.
>
> Jonathan
>
> Jonathan Avila, CPWA
> Chief Accessibility Officer
> Level Access
> <EMAIL REMOVED>
> 703.637.8957 office
>
> Visit us online:
> Website | Twitter | Facebook | LinkedIn | Blog
>
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution or copying of this communication is strictly prohibited.
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Isabel Holdsworth
> Sent: Thursday, November 8, 2018 9:56 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] data table pagination - focus position?
>
> Only thing is, if you leave the focus on the "Next page" button,
> screenreader users might not know that the page was updated and might keep
> pressing the button and thinking it doesn't work.
>
> I would either pop up an accessible toast telling users the new page
> number ("Page 3 of 7"), or provide a heading with the same information just
> above the table and move the focus to the heading. And as a screenreader
> user myself, I think I marginally prefer the second solution as it lines me
> up for reading the new records.
>
> Cheers, Isabel
>
> On 07/11/2018, glen walker < <EMAIL REMOVED> > wrote:
> > 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
> >>
> >> > >> > >> archives at http://webaim.org/discussion/archives
> >> > >>
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
> > > at http://webaim.org/discussion/archives
> > > > > >