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

Should urls be read? #35

Open
sakhdevel opened this issue Oct 4, 2022 · 1 comment
Open

Should urls be read? #35

sakhdevel opened this issue Oct 4, 2022 · 1 comment

Comments

@sakhdevel
Copy link

Please fill out the following to help us help you. Replace ... with your own values, where applicable.

It is not very useful and clear-to-listen when extension reads full urls.

...

Don't read them at all or say "link" or prounounce domain part of url or make reading them optional

...

Steps to reproduce behavior

...

Website

any web site

Text and language

  • Which part of the website did you want spoken: ...
  • If possible, include the full text: ...
  • Language the text was expected to be spoken in: ...

System information

  • Your browser: ...
  • Your browser version: ...
  • Your operating system: ...
  • Your operating system version: ...

Additional information

...

@joelpurra
Copy link
Owner

joelpurra commented Sep 13, 2023

@sakhdevel: yes, URL shortening sounds like a good idea. Perhaps "link to example.com" (and translated, at least to current user interface languages). Ideally it would be configurable, but would probably start with a simple enable/disable option. Unfortunately I cannot say if/when this would be implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants