Skip to content

Accessibility issues聽#2858

Closed
Bug
2 of 2 issues completed
Closed
Accessibility issues#2858
Bug
2 of 2 issues completed
Assignees
pringelmann
Labels
2. developingWork in progressa11yrelated to accessibilitybugSomething isn't working
Milestone
5.3

Description

@Thatoo
Thatoo
opened on Aug 9, 2025

Please use the 馃憤 reaction to show that you are affected by the same issue. Please don't comment if you have no relevant information to add!

Nextcloud Form test with screen reader :

  • checkboxes: a bug on the Nextcloud side for checking a box, SPACE SELECTED the voice says it's checked, which isn't the case, a second press on space actually checks the box when the voice only says SPACE.

In the checkboxes, everything needs to be reworked: the voices say completely contradictory things.

  • Radio buttons work correctly

  • Drop-down menu, at first it leaves the form, then reads the options without recalling the context or the question. Does not read the title of the form drop-down menu, but does read the choices. Reads list items, but doesn't mention which one is selected.

  • Can't set a date

  • Send form: Dynamic content change, but no notification!

Conclusion: Can't NextcloudForm be used for accessibility? No! Not recommended.

Expected behavior
It should be possible to fill a Nextcloud Form using a screen reader independently.

Nextcloud (please complete the following information):

  • Nextcloud-Version: 31.0.7
  • Forms-Version: 5.1.2

Activity

  1. Thatoo
    added
    bugSomething isn't working
    0. Needs triagePending approval or rejection. This issue is pending approval.
    on Aug 9, 2025
  2. Thatoo
    added the
    Bug
    issue type on Aug 9, 2025
  3. Chartman123
    added
    1. to developAccepted and waiting to be taken care of
    highHigh priority
    a11yrelated to accessibility
    and removed
    0. Needs triagePending approval or rejection. This issue is pending approval.
    on Aug 10, 2025
  4. Chartman123
    added this to the 5.2 milestone on Sep 1, 2025

  5. Chartman123 commented on Sep 6, 2025

    @Chartman123
    Chartman123
    on Sep 6, 2025
    Collaborator

    @susnux could this be caused by a bug in the vue lib? I did some debugging and when I used the keyboard to select a checkbox, our onChange method always receives the previous value of the selected checkbox upon the first keypress. Only the second keypress of the space bar has the correct values. with the mouse everythings works as expected and the updated values are used in the first call of onChange

  6. susnux commented on Sep 10, 2025

    @susnux
    susnux
    on Sep 10, 2025
    Collaborator

    checkboxes: a bug on the Nextcloud side for checking a box, SPACE SELECTED the voice says it's checked, which isn't the case, a second press on space actually checks the box when the voice only says SPACE.

    This sounds like its caused by forms itself

    Drop-down menu

    This seems like a problem with NcSelect in general

    Can set a date

    I do not understand this issue?

    Send form: Dynamic content change, but no notification!

    Which content changes here? I guess something needs a aria live region.

  7. Chartman123
    modified the milestones: 5.2, 5.3 on Sep 25, 2025
  8. Chartman123
    marked [Accessibility] Checkbox requires two keypresses to toggle with screen reader #3212 as a duplicate of this issue on Mar 9, 2026
  9. Chartman123
    added a parent issue on Mar 9, 2026
  10. github-project-automation
    added this to A11Y initiative 2026on Mar 9, 2026
  11. github-project-automation
    moved this to Todo in A11Y initiative 2026on Mar 9, 2026
  12. pringelmann
    self-assigned this
    on Mar 19, 2026
  13. pringelmann
    added
    2. developingWork in progress
    and removed
    1. to developAccepted and waiting to be taken care of
    on Mar 19, 2026

  14. pringelmann commented on Mar 19, 2026

    @pringelmann
    pringelmann
    on Mar 19, 2026
    Collaborator

    The date can indeed not be set using keyboard navigation. Attempting to enter the date picker using Tab immediately closes it. This will be fixed by #2972

  15. github-project-automation
    moved this from Todo to In Progress in A11Y initiative 2026on Mar 23, 2026
  16. Chartman123
    removed
    highHigh priority
    on May 13, 2026
  17. Chartman123
    added sub-issues on May 22, 2026

  18. Chartman123 commented on Jun 5, 2026

    @Chartman123
    Chartman123
    on Jun 5, 2026
    Collaborator

    All sub-issues resolved

  19. Chartman123
    closed this as completedon Jun 5, 2026
  20. github-project-automation
    moved this from In Progress to Done in A11Y initiative 2026on Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

2. developingWork in progressa11yrelated to accessibilitybugSomething isn't working

Type

Bug

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions