Skip to content

Focus tab title instead of panel switching tabs in add-on store#15988

Merged
seanbudd merged 6 commits into
nvaccess:masterfrom
ABuffEr:fixAddonStorePageChange
Jan 4, 2024
Merged

Focus tab title instead of panel switching tabs in add-on store#15988
seanbudd merged 6 commits into
nvaccess:masterfrom
ABuffEr:fixAddonStorePageChange

Conversation

@ABuffEr

@ABuffEr ABuffEr commented Dec 30, 2023

Copy link
Copy Markdown
Contributor

Link to issue number:

See discussion in #14986

Summary of the issue:

Switching tabs in add-on store with ctrl+tab announces "tab control panel", and moves the focus in a strange position.

Description of user facing changes

Users will be positioned on tab list, over the new current tab, that will be read by NVDA.

Description of development approach

Simply SetFocus on addonListTabs (wx.Notebook) if it's not already here, at the end of page change event handler.

Testing strategy:

Manual, with steps in #14986.

Known issues with pull request:

It's a partial fix, as discussed in #14986, because it doesn't move focus to a panel element like the channel filter or the add-on list, that seems unreasonably complex to reach. But it's certainly better than nothing/current situation.

Being a small but very perceptible change, I suggest to integrate into 2024.1, and only later to work on another better solution.

Code Review Checklist:

  • Documentation:
    • Change log entry
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • API is compatible with existing add-ons.
  • Security precautions taken.

@ABuffEr ABuffEr requested a review from a team as a code owner December 30, 2023 20:41
@nvdaes

nvdaes commented Dec 30, 2023

Copy link
Copy Markdown
Collaborator

Being a small but very perceptible change, I suggest to integrate into 2024.1, and only later to work on another better solution.

I strongly agree with this proposal. I've reviewed changes and tested them, and I'd approve them if the changes.t2t file would reflect this, probably in the section corresponding to fixes, with credits to you @ABuffEr

@amirsol81

Copy link
Copy Markdown

@ABuffEr really nice touch! I was always baffled by NVDA's behavior upon pressing Control+Tab in the Add-on Manager.

@ABuffEr

ABuffEr commented Dec 30, 2023

Copy link
Copy Markdown
Contributor Author

I've reviewed changes and tested them, and I'd approve them if the changes.t2t file would reflect this, probably in the section corresponding to fixes, with credits to you @ABuffEr

Hi @nvdaes,
thanks, my last PR dates back a lot of time ago, I updated the first comment and filled the changelog part (that I remembered differently). Hope it's ok now.

@nvdaes

nvdaes commented Dec 30, 2023

Copy link
Copy Markdown
Collaborator

I updated the first comment and filled the changelog part (that I remembered differently).

You need to update 'changes.t2t`. See the Change log entry section in contributing.md

@XLTechie XLTechie left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ABuffEr this is great, a much improved user experience for tab changing in the store.

@seanbudd @michaelDCurran Please do consider including in beta!

@lukaszgo1 lukaszgo1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with this, as long as we agree that this is a work around, and ideally list of add-ons should be focused.

@nvdaes

nvdaes commented Dec 31, 2023

Copy link
Copy Markdown
Collaborator

Sincerely, I'm not totally convinced about the best element to be focused. Some people may prefer to focus the box to filter add-ons. But imo this pr is crutial and should be included in NVDA 2024.1.

@ABuffEr

ABuffEr commented Dec 31, 2023

Copy link
Copy Markdown
Contributor Author

Sincerely, I'm not totally convinced about the best element to be focused. Some people may prefer to focus the box to filter add-ons.

I agree at least until #15947 is solved/implemented; then, focusing on add-on list sounds more reasonable, and coherent with what happens e.g. in symbols dialog.

@nvdaes

nvdaes commented Dec 31, 2023

Copy link
Copy Markdown
Collaborator

with what happens e.g. in symbols dialog.

I think this should be discussed in a different thread, since the fact that we use lists at the end doesn't mean that we want to start focusing lists in NVDA dialogs, even if this has been done during long time.

@LeonarddeR

Copy link
Copy Markdown
Collaborator

Looking at this pr and associated issue, I wonder why the MultiCategorySettingsDialog approach wasn't chosen for the add-ons manager. That has custom logic for ctrl+tab I believe.

@CyrilleB79

Copy link
Copy Markdown
Contributor

I have not tested this PR. But from the description, I fully support its inclusion in beta branch (cc @seanbudd, @michaelDCurran).
This is still much better than today's very bad user experience.

The discussion on the best place where the focus should land can still remain open after merging this PR.

Comment thread user_docs/en/changes.t2t Outdated
- When reinstalling an incompatible add-on it is no longer forcefully disabled. (#15584, @lukaszgo1)
- Disabled and incompatible add-ons can now be updated. (#15568, #15029)
- NVDA now recovers and displays an error in a case where an add-on fails to download correctly. (#15796)
- When pressing ctrl+tab, focus properly moves to the new current tab title. (#14986, @ABuffEr)

@seanbudd seanbudd Jan 1, 2024

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this PR is targeting master and should go into 2024.2. Please move the change log to 2024.2.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My mistake, looking now at branches available I suppose to have to do a PR targeting beta; if you'll accept it I close this and open another PR. I'll move changelog line otherwise, but 2024.1 would be preferable.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2024.1 is already deep into beta stage - it is too late for risky changes of behaviour - particularly this case where it is generally agreed that it might not be the final behaviour. I believe the behaviour included in this PR was part of the original add-on store PR (if not, it was something similar) which was reverted to the current behaviour based on feedback.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I strongly doubt that there was a feedback against this feature, I'm quite sure it's an accessibility issue of that wx control from a long time ago (I mean, at least since we changed settings structure years and years ago).
Anyway, ok, I disagree but will change release target in changelog with next commit. Move it as needed if discussion proceeds.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For reference, the prototype set focus to the add-on list view, this was later reverted due to feedback and the comment/issue was created to find a new solution.

@seanbudd seanbudd added the conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review. label Jan 1, 2024
@cary-rowen

Copy link
Copy Markdown
Contributor

Hi @seanbudd

This is a useful improvement, I receive this feedback frequently in the Chinese community, and I agree that it should be targeted for 2024.1.

@ABuffEr

Because it doesn't move focus to a panel element like the channel filter or the add-on list, that seems unreasonably complex to reach.
Also, I agree with @CyrilleB79's comment in #14986.

@seanbudd seanbudd added this to the 2024.2 milestone Jan 2, 2024
Comment thread source/gui/addonStoreGui/controls/storeDialog.py
Comment thread source/gui/addonStoreGui/controls/storeDialog.py
Comment thread user_docs/en/changes.t2t
@seanbudd seanbudd marked this pull request as draft January 3, 2024 22:43
ABuffEr and others added 3 commits January 4, 2024 00:13
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
@ABuffEr ABuffEr marked this pull request as ready for review January 3, 2024 23:24

@seanbudd seanbudd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ABuffEr

@seanbudd seanbudd merged commit 88ceef4 into nvaccess:master Jan 4, 2024
Nael-Sayegh pushed a commit to Nael-Sayegh/nvda that referenced this pull request Feb 15, 2024
…cess#15988)

See discussion in nvaccess#14986

Summary of the issue:
Switching tabs in add-on store with ctrl+tab announces "tab control panel", and moves the focus in a strange position.

Description of user facing changes
Users will be positioned on tab list, over the new current tab, that will be read by NVDA.

Description of development approach
Simply SetFocus on addonListTabs (wx.Notebook) if it's not already here, at the end of page change event handler.
SaschaCowley pushed a commit to SaschaCowley/nvda that referenced this pull request Feb 27, 2024
…cess#15988)

See discussion in nvaccess#14986

Summary of the issue:
Switching tabs in add-on store with ctrl+tab announces "tab control panel", and moves the focus in a strange position.

Description of user facing changes
Users will be positioned on tab list, over the new current tab, that will be read by NVDA.

Description of development approach
Simply SetFocus on addonListTabs (wx.Notebook) if it's not already here, at the end of page change event handler.
Adriani90 pushed a commit to Adriani90/nvda that referenced this pull request Mar 13, 2024
…cess#15988)

See discussion in nvaccess#14986

Summary of the issue:
Switching tabs in add-on store with ctrl+tab announces "tab control panel", and moves the focus in a strange position.

Description of user facing changes
Users will be positioned on tab list, over the new current tab, that will be read by NVDA.

Description of development approach
Simply SetFocus on addonListTabs (wx.Notebook) if it's not already here, at the end of page change event handler.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants