-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BITV] Accessibility issues #898
Comments
Since activity is not reverting a server rule there, would it make sense to do this on a global level? Otherwise we also need to track this for all the links in settings descriptions, notifications, ... |
You can't anyway as the responses are rather slow and only get 30 entries per grab (could increase that now that the server load was improved with #871 I split the issue list into "bug fixes" which we should do now and "follow up features" which can be done later. Let me know if you agree. |
yeah, lazy loading / moving to pagination is going to be a bigger challenge in multiple fronts anyway... |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
That should be applied to all Nextcloud? Or what makes it valid here, but e.g. not in notifications etc? |
|
Please check if some of the issues might be fixed by #1043. |
@michaelnissenbaum is this approach ok to you? |
@JuliaKirschenheuter If by 'open in place' you mean that the image/file will be opened on the same page in a viewer/editor, then that's acceptable to me. It's important that the editor/viewer is fully accessible. Additionally, please ensure that once a file or image is opened, the keyboard focus is properly placed and clearly visible. |
Bug fixes
<ul>
unordered list with<li>
elements #1020Following suggestions were moved to main "Lazy loading" nextcloud/server#33844 issue:
The text was updated successfully, but these errors were encountered: