[BITV] Lazy loading is not accessible

[PVince81]

"Lazy loading not accessible as you can not move very far to the past quickly. Pagination would be much better here"

To discuss how this applies to:

• file lists
• comments list in sidebar
• versions list in sidebar

[PVince81]

as soon as we know how to do it (ex: pagination) we can at least do it for comments and versions

for file list it is going to be tricky due to legacy jquery code

[PVince81]

maybe we can check how other solutions are doing it that deal with file lists

[skjnldsv]

So, to add more on this, a proper lazy loading should be accessible if tabbing or keyboard arrow-down focuses the next row.
Screen readers can have hidden cue that the list is incomplete if they want. But really, it should just start announcing how many items are in the list (we know the total amount), and then announce each row as the focus move forward.

Best of both worlds +1

[skjnldsv]

But what kind of accessibility are we talking here?
Screen readers I assume, right? Because if this is only about keyboard navigation, then this is easily covered.

Screen readers should just state:

• Files list below, one hundered and thirty three entries
• <tab>
• Entry one. Image1.jpg. 145KiB. Last modified: 3 days ago.
• <tab>
• Entry two. Image2.jpg. 211KiB. Last modified: 2 hours ago.
• <pagedown>
• Entry twenty-five. Quarter results 2021.ods. 211KiB. Last modified: 19 January 2022.

[PVince81]

as far as I remember it goes further than that: on table elements you can set aria attributes that have the screen reader announce how many entries there are in the table (or it might be automatic)

with lazy loading it would only say that there are 20 rows but actually there's more

and with pagination implemented, there are also ways IIRC where you can have the screen reader tell you that there's pagination and that you're on page X of Y, and possibly some allow you to jump directly to specific pages or to the pagination controls

[skjnldsv]

with lazy loading it would only say that there are 20 rows but actually there's more

But we can trick the screen reader into that. Screen readers can also read whatever we want them to :)

[PVince81]

let's split the topics:
files list I think is most important because the likeliness of pagination there is much higher

for versions and comments we currently don't paginate nor lazy load but also it's seldom that there's more than one page of entries there

[PVince81]

note: we need to keep the "table" element for the file list, otherwise a lot of code and apps will break

so we need to research how to make the table/listing/pagination accessible with the current structure

[skjnldsv]

We can use role=table.
Table elements have too much downsides with css.

[PVince81]

to clarify:

for the files 2 vue project, we can switch to whatever we need.

for stable25 accessibility we need to keep the table with minimal changes to make it pass certification in regards to pagination