Skip to content
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

[BUG] VoiceOver on Range fails to read out all values #3774

Open
1 of 9 tasks
chi-jyskebank-dk opened this issue Jan 28, 2025 · 0 comments
Open
1 of 9 tasks

[BUG] VoiceOver on Range fails to read out all values #3774

chi-jyskebank-dk opened this issue Jan 28, 2025 · 0 comments
Labels
accessibility bug 👶🏻 New For new issues before prioritisation and refinement NOT Prioritized Issue not yet prioritized and added to a Milestone NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild

Comments

@chi-jyskebank-dk
Copy link
Collaborator

Describe the bug

When operating the Range slider with VoiceOver enabled, not all values of the slider are read out loud

Describe how to reproduce the bug

  1. Go to this StackBlitz: https://stackblitz.com/edit/stackblitz-starters-wxb9gweu?file=src%2Fmain.ts
  2. Operate slider with VoiceOver enabled
  3. Notice, that values > 5000 and < 105000 are not read out loud

Which Kirby version was used?

10.2.1

What was the expected behavior?

All values the Range slider can have should be read out loud

Additional context

The Range where the error was detected has a minimum of 0, a maximum of 500000 and a step-value of 5000.

Add any screenshots

See attached screen recording

Please complete the following information:

  • OS: macOS 15.2 with VoiceOver
  • Browser: Google Chrome

Are there any additional context?


Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Verification

To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.

  • Make sure the NOT verified label has been removed by a member of team Kirby; do not proceed until this is done.

Implementation

The contributor who wants to implement this issue should:

Review

Once the issue has been implemented and is ready for review:

Kirby.Range.mov
@chi-jyskebank-dk chi-jyskebank-dk added accessibility bug NOT Prioritized Issue not yet prioritized and added to a Milestone NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild 👶🏻 New For new issues before prioritisation and refinement labels Jan 28, 2025
@github-project-automation github-project-automation bot moved this to 💌 Inbox in Kirby Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility bug 👶🏻 New For new issues before prioritisation and refinement NOT Prioritized Issue not yet prioritized and added to a Milestone NOT Verified Applied to bug reports that have not been verified by a member of @kirbydesign/kirby-guild
Projects
Status: 💌 Inbox
Development

No branches or pull requests

1 participant