Add the flexibility to directly jump to the first element after last element while browsing in browse mode. #10695
Comments
|
Hi, this is duplicate of an issue discussed many years ago. Thanks.
|
|
So, what happened to that issue? |
|
So, what happened to that issue?
…On 1/17/20, Joseph Lee ***@***.***> wrote:
Hi, this is duplicate of an issue discussed many years ago. Thanks.
From: Akash Kakkar ***@***.***>
Sent: Friday, January 17, 2020 4:34 AM
To: nvaccess/nvda ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [nvaccess/nvda] Add the flexibility to directly jump to the first
element after last element while browsing in browse mode. (#10695)
Is your feature request related to a problem? Please describe.
Yes
Describe the solution you'd like
The flexibility and functionality should be added so that user can jump to
the first html element after pressing the quick key of the corresponding
html element while in browse mode.
For example, if we are on the last heading of the page and press 'h' then
NVDA announces: 'No next headings' instead of it, it should jump/wrap to the
first heading of the page with a sound just like JAWS.
It will help the users a lot and will reduce the efforts of manually going
to the first heading/button(every such element) manually.
Describe alternatives you've considered
N/A
Additional context
Tested with 2019.3 too and there too the same behaviour reproduces.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10695?email_source=notifications&email_token=AB4AXEF43ESLWO6GMLNWVLLQ6GQUBA5CNFSM4KIHUQT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IG5RTQA>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4AXECVNOJMCLVHNUSPMXTQ6GQUBANCNFSM4KIHUQTQ>
.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#10695 (comment)
|
|
Hi, if I recall correctly, it might still be open (or might have been closed). @jcsteh, do you remember the issue number for it where you outlined your concerns about first letter navigation commands and wrapping them to the first item after reaching the bottom of the document? Thanks.
|
|
Oh, ok.
I wanted to have that feature since so long but if previous issue was
closed then I feel that this is not going to be implemented sadly :(
…On 1/17/20, Joseph Lee ***@***.***> wrote:
Hi, if I recall correctly, it might still be open (or might have been
closed). @jcsteh, do you remember the issue number for it where you outlined
your concerns about first letter navigation commands and wrapping them to
the first item after reaching the bottom of the document? Thanks.
From: Akash Kakkar ***@***.***>
Sent: Friday, January 17, 2020 8:18 AM
To: nvaccess/nvda ***@***.***>
Cc: Joseph Lee ***@***.***>; Comment
***@***.***>
Subject: Re: [nvaccess/nvda] Add the flexibility to directly jump to the
first element after last element while browsing in browse mode. (#10695)
So, what happened to that issue?
On 1/17/20, Joseph Lee ***@***.***> wrote:
> Hi, this is duplicate of an issue discussed many years ago. Thanks.
>
>
>
> From: Akash Kakkar ***@***.***>
> Sent: Friday, January 17, 2020 4:34 AM
> To: nvaccess/nvda ***@***.***>
> Cc: Subscribed ***@***.***>
> Subject: [nvaccess/nvda] Add the flexibility to directly jump to the
> first
> element after last element while browsing in browse mode. (#10695)
>
>
>
>
> Is your feature request related to a problem? Please describe.
>
>
> Yes
>
>
> Describe the solution you'd like
>
>
> The flexibility and functionality should be added so that user can jump
> to
> the first html element after pressing the quick key of the corresponding
> html element while in browse mode.
> For example, if we are on the last heading of the page and press 'h'
> then
> NVDA announces: 'No next headings' instead of it, it should jump/wrap to
> the
> first heading of the page with a sound just like JAWS.
> It will help the users a lot and will reduce the efforts of manually
> going
> to the first heading/button(every such element) manually.
>
>
> Describe alternatives you've considered
>
>
> N/A
>
>
> Additional context
>
>
> Tested with 2019.3 too and there too the same behaviour reproduces.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#10695?email_source=notifications&email_token=AB4AXEF43ESLWO6GMLNWVLLQ6GQUBA5CNFSM4KIHUQT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IG5RTQA>
> , or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AB4AXECVNOJMCLVHNUSPMXTQ6GQUBANCNFSM4KIHUQTQ>
> .
>
>
>
> --
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> #10695 (comment)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#10695?email_source=notifications&email_token=AB4AXEHZ3FUE65Y22UKMR5DQ6HKZZA5CNFSM4KIHUQT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJIF63A#issuecomment-575692652>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4AXEFPPMODVXYLQDPSFQDQ6HKZZANCNFSM4KIHUQTQ>
.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#10695 (comment)
|
|
Hi, it might have been another duplicate of this issue being closed – the original one might still be open. Thanks.
|
|
Ok Joseph. Thanks for confirming
…On 1/17/20, Joseph Lee ***@***.***> wrote:
Hi, it might have been another duplicate of this issue being closed – the
original one might still be open. Thanks.
From: Akash Kakkar ***@***.***>
Sent: Friday, January 17, 2020 8:29 AM
To: nvaccess/nvda ***@***.***>
Cc: Joseph Lee ***@***.***>; Comment
***@***.***>
Subject: Re: [nvaccess/nvda] Add the flexibility to directly jump to the
first element after last element while browsing in browse mode. (#10695)
Oh, ok.
I wanted to have that feature since so long but if previous issue was
closed then I feel that this is not going to be implemented sadly :(
On 1/17/20, Joseph Lee ***@***.***> wrote:
> Hi, if I recall correctly, it might still be open (or might have been
> closed). @jcsteh, do you remember the issue number for it where you
> outlined
> your concerns about first letter navigation commands and wrapping them
> to
> the first item after reaching the bottom of the document? Thanks.
>
>
>
> From: Akash Kakkar ***@***.***>
> Sent: Friday, January 17, 2020 8:18 AM
> To: nvaccess/nvda ***@***.***>
> Cc: Joseph Lee ***@***.***>; Comment
> ***@***.***>
> Subject: Re: [nvaccess/nvda] Add the flexibility to directly jump to the
> first element after last element while browsing in browse mode. (#10695)
>
>
>
> So, what happened to that issue?
>
> On 1/17/20, Joseph Lee ***@***.***> wrote:
>> Hi, this is duplicate of an issue discussed many years ago. Thanks.
>
>>
>
>>
>
>>
>
>> From: Akash Kakkar ***@***.***>
>
>> Sent: Friday, January 17, 2020 4:34 AM
>
>> To: nvaccess/nvda ***@***.***>
>
>> Cc: Subscribed ***@***.***>
>
>> Subject: [nvaccess/nvda] Add the flexibility to directly jump to the
>> first
>> element after last element while browsing in browse mode. (#10695)
>
>>
>
>>
>
>>
>
>>
>
>> Is your feature request related to a problem? Please describe.
>
>>
>
>>
>
>> Yes
>
>>
>
>>
>
>> Describe the solution you'd like
>
>>
>
>>
>
>> The flexibility and functionality should be added so that user can jump
>> to
>> the first html element after pressing the quick key of the
>> corresponding
>> html element while in browse mode.
>
>> For example, if we are on the last heading of the page and press 'h'
>> then
>> NVDA announces: 'No next headings' instead of it, it should jump/wrap
>> to
>> the
>> first heading of the page with a sound just like JAWS.
>
>> It will help the users a lot and will reduce the efforts of manually
>> going
>> to the first heading/button(every such element) manually.
>
>>
>
>>
>
>> Describe alternatives you've considered
>
>>
>
>>
>
>> N/A
>
>>
>
>>
>
>> Additional context
>
>>
>
>>
>
>> Tested with 2019.3 too and there too the same behaviour reproduces.
>
>>
>
>> —
>
>> You are receiving this because you are subscribed to this thread.
>
>> Reply to this email directly, view it on GitHub
>> <#10695?email_source=notifications&email_token=AB4AXEF43ESLWO6GMLNWVLLQ6GQUBA5CNFSM4KIHUQT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IG5RTQA>
>> , or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/AB4AXECVNOJMCLVHNUSPMXTQ6GQUBANCNFSM4KIHUQTQ>
>> .
>
>>
>
>>
>
>>
>
>> --
>
>> You are receiving this because you authored the thread.
>
>> Reply to this email directly or view it on GitHub:
>
>> #10695 (comment)
>
>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#10695?email_source=notifications&email_token=AB4AXEHZ3FUE65Y22UKMR5DQ6HKZZA5CNFSM4KIHUQT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJIF63A#issuecomment-575692652>
> , or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AB4AXEFPPMODVXYLQDPSFQDQ6HKZZANCNFSM4KIHUQTQ>
> .
>
>
>
> --
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> #10695 (comment)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#10695?email_source=notifications&email_token=AB4AXEHWAGQOSPXUEDXRLGTQ6HMDPA5CNFSM4KIHUQT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJIHCHY#issuecomment-575697183>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4AXEFUY7M4TYIEKDZPGWDQ6HMDPANCNFSM4KIHUQTQ>
.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#10695 (comment)
|
|
Have we not had this discussion before? I am in favor, actually, but I can
see why you might not want this to be there.
|
|
I do feel it might be more relevant now though, considering that we are
increasingly seeing web sites where the tab order is not as expected. I had
hoped by now that web designers might have grasped the plot that the order
things are in matters from the accessibility standpoint. All to often the
visual site looks easy to use but the blind use means going to the bottom
then top then bottom etc or the focus jumps as you use it.
In this confusing environment page wrapping with a warning tone would seem
to be a good idea. Pages are increasingly cluttered in my view.
|
|
There are, at least, two add-ons making available this feature:
NVDAExtensionGlobalPlugin and screenRapping
|
|
See also: Issue #8193 |
|
NVDAExtensionGlobalPlugin looks promising as it is python 3 compatible and has many features. |
|
I'm going to close this issue for now. Given there are add-ons that support this behavior, and it is unlikely to be critical for users and the current behavior is likely preferred by most. |
|
@feerrenrut imo this issue should be reopened. the addons in questions are not official addons and at least Global Plugin extension has not passed the review due to its complexity and some conflicts with already existing NVDA features and key strokes. Thus, these addons are only used by a limited number of users worldwide. Back to the point, I think there are use cases where such a feature is useful and could be added to browse mode settings as an optional feature. |
|
I think I have seen another issue suggesting that wrapping be achieved with a double press. I think a new issue should be opened to describe this clearly. Reaching the final element should continue to say "no next element type. Press twice to go to go to first element." or "Press twice to wrap" or something similar. |
|
Completely agreed with @Adriani90 the issue should be reopened and I don't think that there's any problem in implementing the behaviour same as JAWS. there shouldn't be any need of logging the fresh issue. |
|
Moreover, I don't feel that there's any need of achieving the wrapping with double press/tap. The wrapping can be made togglable altogether and if required then it can be kept off by default. |
|
What exactly is the point against having this on double press? Is it because this should be like in jaws? Actually having this on a double press is more efficient and you don‘t need an additional setting. We should avoid an overload of settings like it is in jaws. They even seem to begin cleaning up the settings section because there are far too much settings which are not needed or which remain the default value in general.
I Will open a new issue as suggested by @feerrenrut and discussions can be continued there.
meinem iPhone gesendet
… Am 01.05.2020 um 17:44 schrieb Akash Kakkar ***@***.***>:
Moreover, I don't feel that there's any need of achieving the wrapping with double press/tap. The wrapping can be made togglable altogether and if required then it can be kept off by default.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Ok, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Yes
Describe the solution you'd like
The flexibility and functionality should be added so that user can jump to the first html element after pressing the quick key of the corresponding html element while in browse mode.
For example, if we are on the last heading of the page and press 'h' then NVDA announces: 'No next headings' instead of it, it should jump/wrap to the first heading of the page with a sound just like JAWS.
It will help the users a lot and will reduce the efforts of manually going to the first heading/button(every such element) manually.
Describe alternatives you've considered
N/A
Additional context
Tested with 2019.3 too and there too the same behaviour reproduces.
The text was updated successfully, but these errors were encountered: