Thank you for the quick response.
Okay, so currently combining an infinite feed and footer creates an inaccessible solution.
But that doesn’t have to be the answer. Controls could be placed on the feed to give the user choice between loading more posts or reaching the footer. Is there any scope for this?
A footer is a really common web pattern. Making consistent, recognisable web experiences is a core principle in creating usable and understandable experiences.
Footers support Success Criteria (SC): 2.4.5 Multiple Ways (AA)
- More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.
Not having footers turned off on specific pages supports SC 3.2.3 Consistent Navigation (AA)
- Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
Is it Discourse’s stance that if you choose that combination it’s your issue?
Do you know if any advice around this is provided in documentation somewhere that states this fact: “as adding a footer on a infinite scrolling website would render it inaccessible”?
I’m in a tricky position, I will have to suggest redesigns for some big communities we’re running. So just working out the full picture of this issue.