Bring new files list component to oc-web

[exalate-issue-sync]

Stories

As a governmental decision maker looking into buying oCIS I want the product to be accessible for all my users (e.g. 1 out of 7 employees in german governmental institutions has some kind of disability) so that productive usage is possible for anyone. -> needs accessible files list component.

As a user I want to be able to make a bookmark of my current view of the files list to make it easy to come back to it later.

Requirements

• FileList component

Acceptance criteria

• use ODS component in files app
• acceptance tests still succeed - we have a lot of them already (if possible, replace some of them with unit tests)
• (ultimately: WCAG 2.0 compliance certification)

Status quo

Our current implementation of the files list causes some issues:

• It is not WCAG 2.0 compliant as it is. Could be solved be by converting it to an actual html table. See Audit #1 – General Overview when logged in – List of files and folders is no data table, should be web#4330
• It lacks pagination and filtering. Those + sorting should ideally be reflected in the route, so that a page reload (e.g. from a bookmark) brings the user back to the same view.

Requirements for a new files list component

• Right now the files list component lives in phoenix. We want to move it to ODS so that it can easily be used in other views/extensions.
• it should be based on html table markup instead of divs
• it needs proper focus management and good keyboard-only navigation
• we want to support filtering + reflect filtering in the route
• we want to support sorting + reflect sorting in the route
• we want to support pagination + reflect pagination in the route
• we want sorting/filtering/pagination to work server side
• we need support for locating and highlighting a resource with our existing scrollTo parameter
• already think about different view types (e.g. list, grid, ...). Different view type implementations are not in scope of this task, but should not require rewriting this component again.

[exalate-issue-sync]

Benedikt Kulmann commented: Story is too big. Needs to be split into smaller stories.