joelanman,
@joelanman@hachyderm.io avatar

Any thoughts on infinite scroll vs button to load more vs next page buttons? In the context of a feed
#ux #accessibility

bernat,
@bernat@social.ei8fdb.org avatar

@joelanman I do remember reading some #a11y best practices suggesting load more/next button providing users more control.

This control was particularly needed when the infinite scroll breaks leaving the user marooned:

  1. they have to either refresh the page (and presumably loose their position in the "infinite") or

  2. scroll back up/down/up/down to try and "replicate" the scroll to try and force the page to load the next.

For me it depends on how long you're expecting someone to scroll. HTH

joelanman,
@joelanman@hachyderm.io avatar

@bernat thanks I agree, gone with a button for now that goes to the next page. I can always enhance that in future if need be

Chris,
@Chris@mastodon.social avatar

@joelanman Overall I'm mixed on infinite scrolling.

If I'm looking for something specific on the page, such as within search results, they can be a problem because I'm often trying to Command+F to find something that should be there, but just isn't yet.

For something like a feed, however, where it's just a whole lot of everything, then it's a bit better.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • UX
  • ngwrru68w68
  • rosin
  • GTA5RPClips
  • osvaldo12
  • love
  • Youngstown
  • slotface
  • khanakhh
  • everett
  • kavyap
  • mdbf
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • megavids
  • InstantRegret
  • normalnudes
  • tacticalgear
  • cubers
  • ethstaker
  • modclub
  • cisconetworking
  • Durango
  • anitta
  • Leos
  • tester
  • provamag3
  • JUstTest
  • All magazines