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
NVDA announces "Article" before every article while browsing the articles via quick keys #11103
Comments
As the implementer of article, I think I did this on purpose, as this is also the behavior for ARIA landmarks. If you navigate a page with d, for example, you will also hear the landmark announced first. I however agree that for article, at least those without a label (and I think hardly any have one), this should be changed. |
This requires a change in speech.getControlFieldSpeech, the speakContentFirst variable. Marking as good for new dev. |
This comment has been minimized.
This comment has been minimized.
You're right bro, but if we turn off the article reporting, then let's say we are navigating via arrow keys, then too we won't be able to know whether we landed on an article. :(
|
Wow, what's this label? name looks interesting though. |
Yes, people don't define the name/labels for the nearely all the articles. so for the unnamed articles, it can be changed.
|
@LeonarddeR wrote:
I agree. If ever an article has a label, your first implemented behavior is preferable, notably as it helps discriminate the label from the content. |
This comment has been minimized.
This comment has been minimized.
@Adriani90 Hmm, you are right, but, that way if we'll browse via arrow keys, then we won't be able to know that this page contains the articles at all.
|
This comment has been minimized.
This comment has been minimized.
@Adriani90 No this is not right. I already know that article navigation quick keys work regardless of the article reporting on/off in document format settings.
|
This comment has been minimized.
This comment has been minimized.
Ok. your wish.
…On 5/5/20, Adriani90 ***@***.***> wrote:
@akash07k I respectfully disagree. The user can easily find out if there are
articles by pressing the quick navigatoin key, there is no need for pressing
arrow keys to find out if there are articles. Given the workaround by
turning off reporting and using quick navigation key, this is consistent
with all other elements that you can choose from in the document formatting
settings. Why should articles treated differently than i.e. block quotes or
groupings or other elements? Inconsistencies would rather confuse users
rather than bringing positive impact.
If we think to change this behavior, than this should be done for every
element. But I wouldn't advise to do it.
However, since @LeonarddeR implemented this, I will let the decision to him
wether this issue should be closed or not.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#11103 (comment)
|
I don't agree with it however.. but.....
…On 5/5/20, Akash Kakkar ***@***.***> wrote:
Ok. your wish.
On 5/5/20, Adriani90 ***@***.***> wrote:
> @akash07k I respectfully disagree. The user can easily find out if there
> are
> articles by pressing the quick navigatoin key, there is no need for
> pressing
> arrow keys to find out if there are articles. Given the workaround by
> turning off reporting and using quick navigation key, this is consistent
> with all other elements that you can choose from in the document
> formatting
> settings. Why should articles treated differently than i.e. block quotes
> or
> groupings or other elements? Inconsistencies would rather confuse users
> rather than bringing positive impact.
> If we think to change this behavior, than this should be done for every
> element. But I wouldn't advise to do it.
> However, since @LeonarddeR implemented this, I will let the decision to
> him
> wether this issue should be closed or not.
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> #11103 (comment)
|
@Adriani90 wrote:
I disagree. It depends on how the page you're browsing is structured and how much junk there is in between. Sure, quick nav by article is a solution once you know what you're looking for, but it is no replacement for the announce made during the "exploration phase". The options in the document formatting settings not only serve the needs of different people, but also the varying needs of a single user. @LeonarddeR expressed his agreement on the need for a change in #11103 (comment) I expressed mine in #11103 (comment) I'd add that I often receive feedback from users complaining about the high verbosity level of the announces made by NVDA. Many wish to customize/reduce/tailor these announces to their needs. Thank you very, very much for so often trying to route users and change requesters towards existing solutions, increasing their knowledge of how NVDA can be used efficiently and reducing the work load of code contributors. |
@JulienCochuyt Thanks. You explained it very well and I absolutely agree with your point.
|
Yes @JulienCochuyt +1 on this.
|
Hi. I think consistency is taking a back seat in some cases where NVDA is concerned, which can be problematic. I think, broadly, until such verbosity can be customised:
|
@fisher729 what you describe is already the current behavior in NVDA. I am sorry, I totally missunderstood this issue... Now after testing, it seems only articles has the behavior of being reported before the text. All other elements are reported after the text. I will hide my comments to make the discussion more focused. Sorry for the inconvenience. |
I'm working on this issue at the moment, but struggling to understand how to access current active settings. Can anybody guide me where to look to check whether QuickNav is enabled? |
Quick nav is enabled by default in browse mode, i.e. when using NVDA in browsers. |
Ah thanks, that explains a lot actually! |
Steps to reproduce:
Actual behavior:
if we turn on the article announcement from the "document format settings", NVDA announces the "article" before every article even though browsing it via heading navigating quick key: "H" or specifically asigned article reading quick key..
It is very problematic and time consuming to here "article" with every element such as: headings while browsing.
Expected behavior:
When we use the quick keys to navigate to the articles on a web page, the article text/label should be announced first and then "article" should be announced after it,
System configuration
NVDA installed/portable/running from source:
Tried with both
NVDA version:
Tried with all the versions till latest alpha.
Windows version:
Windows 10 19041.208
Name and version of other software in use when reproducing the issue:
Any of the web browser/electron app
Other information about your system:
Tried on latest fast insider builds too
Other questions
Does the issue still occur after restarting your computer?
Yes always
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes all. Same behaviour/issue
If addons are disabled, is your problem still occuring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
Yes
The text was updated successfully, but these errors were encountered: