[a11y] 9.3.3.1 - Error detection

[tbsbdr]

• Context: The Web UI should be accessible according to the WCAG2.1 /BITV 2.0 guidelines. The number in the title relates to the test-steps: https://www.bitvtest.de/bitv_test/das_testverfahren_im_detail/pruefschritte.html
• "Status" relates to the evaluation scheme https://www.bitvtest.de/bitv_test/das_testverfahren_im_detail/verfahren.html#c1262
• "a11y" is short for accessibility

---

Status: partly fulfilled

• Page 1 (Alle Dateien)
  When creating a public link and in case the user leaves the fields empty, an error message appears above the form:
  a) The error message is in English language but should be in German - "error creating public share"
  b) The text of the error message is not informative because it doesn’t explain what went wrong (what data caused the error?)
  c) The error message is not handled by screenreaders. One solution could be the use of aria- live or role="alert“.

Status: fulfilled

• Page 2 (Mit anderen geteilten Dateien)

Status: not applicable

• Page 3 (Gelöschte Dateien)
• Page 4 (Konto)

[lookacat]

1. The workflow as described doesn't lead to an error.
   to a) in the filesharing sidebar all messages are translated using $gettext
   to b) as discribed in 1. the error doesn't exist, other possible errors in the component are meaningful
   to c) role=alert will be set

[kulmann]

Error message is coming untranslated from the server.

[kulmann]

OcAlert has role="alert" now since owncloud/owncloud-design-system@895c090

[kulmann]

We fixed the frontend side form validation for required password. Other fields don't have any requirements. Only thing left are unforeseen server side errors. For those we now show a generic error message as a notification (read by screenreaders, disappears after a few seconds). 14a12b8

[kulmann]

Also made sure that the same is fine for people shares and that focus management doesn't break.
49c9f03

[pascalwengerter]

Closing here since backend errors now get wrapped in a user-friendly and translated way