Skip to content

IJPL-175712 Accessibility UI guidelines #1505

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

dmitrii-drobotov
Copy link
Member

No description provided.

@MariannaKononenko MariannaKononenko self-requested a review July 11, 2025 14:57
Copy link
Collaborator

@MariannaKononenko MariannaKononenko left a comment

Choose a reason for hiding this comment

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

Great job, thank you! Left a few comments.


The basic way to interact with the UI by using the keyboard is to switch focus between components with <shortcut>Tab</shortcut> and <shortcut>Shift+Tab</shortcut>.
For some components, arrow keys can also be used to navigate between items.
Once a component is focused, it can be activated by pressing <shortcut>Space</shortcut>.
Copy link
Collaborator

Choose a reason for hiding this comment

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

also add info on how focused components should look like (e.g. get highlighted with the blue stroke)

Copy link
Member Author

Choose a reason for hiding this comment

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

I can now add some basic info (1-2 sentences) that focused components need to have a focus indicator. And then later you can expand it with an illustration and add more info if needed. I wrote about this part here: UX-3531. Does that sound good?

<!-- Copyright 2000-2025 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->

# Accessibility

Copy link
Collaborator

Choose a reason for hiding this comment

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

Since the article is mainly focused on iplementation details, maybe it makes sense to move it for example to the Base Platform section?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good idea. I think I can extract the Assistive technology support section into an article here: https://plugins.jetbrains.com/docs/intellij/user-interface-components.html. And we can keep things about keyboard accessibility in UI guidelines and also later add the information about colors here. Both articles will have links to each other. What do you think?

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

Successfully merging this pull request may close these issues.

2 participants