-
Notifications
You must be signed in to change notification settings - Fork 158
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
Settings should be named in the title bar Windows #2556
Comments
Hello, sorry but I didn't quite understand what you said, can you explain me what "settings" is for you? |
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
{page:WordSection1;}
-->Hi, The settings I refer to is the app settings. As a new user you would have to go there often to read the list of assigned shortcuts. This list is by the way also hard to read with a screen reader, and the list should be made more accessible and added to the documentation. In this way users can read it like other information and copy it to our own documents or even hardware like a braille notetaker. But as it is now you will often have to go into ssettings to check all the different shortcut keys.Here you can easily lose the overview of where you are. Either in the settings dialog or in the book you came from.This could be made more obvious if the title of the window with settings included the word setting. As it works now nothing changes when you open or close settings. This is not a problem for users that can see the entire screen, but it can be a problem for screen reader users that works with a much smaller part of the screen basically what is in focus at the time. Thorium - Thorium Reader Documentation EnglishReading with a screen reader Reading the text now If I open settings press ctrl+s I hear: Thorium - Thorium Reader Documentation English dialoggruppeCustomize text formatting check boks ikke markeret So I get the new focus. But let us say i get distracted by something comes back to the book Iand wwant to check where I am. Now reading the title foof the windo in Jaws jawsKey+t Now I hear: Thorium - Thorium Reader Documentation English So what I am told is the name of the book I was reading before I opened settings. This in my view is a bug since I am not in the book but in settings. This can be obvious because jaws sometiems will add extra information about the current heading, but the first infromation you get is in my view misleading. Regards Claus Sendt fra Mail til Windows Fra: Pierre LerouxSendt: 1. oktober 2024 14:57Til: edrlab/thorium-readerCc: thoeg; AuthorEmne: Re: [edrlab/thorium-reader] Settings should be named in the title bar Windows (Issue #2556) Hello, sorry but I didn't quite understand what you said, can you explain me what "settings" is for you?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am familiarizing myself with Thorium iu using JAWS. Learning the diffrent keyboard shortcuts.
They are hard to get but otherwise seem to work, however it would make the app more friendly and easier to understand if different windows hwere indicated in the title bar.
So settings when opened opens ok but the title bar is the same as the book or place in Thorium cyou came from.
If Settings was the title of the Window it would make navigation and orientation much easier for a screen reader user. This may also be the case in other places in the app I am not sure.
Win11 2023h2
jaws 2024.
The text was updated successfully, but these errors were encountered: