I have read another closed thread about the fact a user cannot reach the footer due to the infinite scroll feature. It wasn’t resolved. Concerns were raised about it being a UX issue - which it most certainly is. But it has been brought to my attention because it is an Accessibility issue.
Although the user is giving input i.e. scrolling they are not necessarily intending to activate the infinite scroll, instead the intention may be to reach the footer for additional information or support.
Any community using this setup will not pass level A of the WCAG 2.1.
Level A is considered to be the most basic and essential level of web accessibility.
I have been auditing a community and would class this issue a failure of success criteria:
2.2.2 Pause, Stop, Hide (Level A) Critical
For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
3.2.5 Change on Request (Level AAA) Serious
Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
- Add a ‘load more posts’ button to the feed to give back the users control.
- Allow users to choose how many posts to view at a time so that those seeking a more infinite experience can do so.
It’s not really acceptable to say “if you don’t like this setup choose another” - this one can easily be made more useable and should be. It is a moral and legal requirement for a lot of our clients.
Hopefully this helps make the case for the changes required.