♿ AVT 2/3 ♿ Pagination usability use cases

[elizabethsjudd]

Pagination has made many improvements but there are still some open questions about usability.

Detailed description

Describe in detail the issue you're having.

Questions around the Carbon pagination come down to mainly checkpoints 3.2.1/3.2.2, we typically avoid changing content on blur since I’ve heard that is generally considered a bad practice aligning to these 2 checkpoints. However with current set up the only way to change the items per page and to directly jump to a page via the text input would be to perform those actions on an on change (items per page) and blur (if value changed for the navigating to a specific page). Because the demo on the site isn’t a working demo have those items been considered?

I’d also be curious about your usage guides for:
• when a user changes the items per page but is not on the first page. Where do they end up?
• how is the user informed that the new page is loaded if focus management isn’t handled? Are they notified that it’s loading, if so how?

I’ve also been told that pagination should actually use links instead of buttons as we are navigating the user to a new page/content and typically pagination would be something that would have unique URLs in web applications.

Is this issue related to a specific component?

Pagination

What did you expect to happen? What happened instead? What would you like to see changed?

We have clear usability guidelines about interacting with components as various user types and the Carbon pagination component follows these guidelines

What version of the Carbon Design System are you using?

Carbon X alpha

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

We have a user that is looking to have pagination in their next release and we’d like to have it come directly from Carbon if possible as we are trying to converge a lot of the work between Carbon and Watson Health specifically around the vanilla/handlebars setup.

Additional information

Working with @dakahn to figure out answers/solutions to these questions.

[stale]

We've marked this issue as stale because there hasn't been any activity for a couple of weeks. If there's no further activity on this issue in the next three days then we'll close it. Thanks for your contributions.

[dakahn]

keeping this open since I think these are great questions worth asking. moving this to our spec repo tho 🤖

[mattrosno]

@dakahn I'd move this out of the spec repo. I don't expect the spec repo to be long lived; from here on out we'll be working out of primary repo(s).