Bug 580964 - Accessibility issues regarding EGit (for screen reader users)
Summary: Accessibility issues regarding EGit (for screen reader users)
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-31 04:53 EDT by hamidreza abroshan CLA
Modified: 2022-10-31 09:09 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hamidreza abroshan CLA 2022-10-31 04:53:26 EDT
I am blind and use computers with the help of screan-reader NVDA. I
have some accessibility issues while using EGit.
1. when having merge conflicts, and resolving, in the merge tool, when
navigating on the list of files it is not distinguishable if each of
them is resolved or not yet.
They should be marked by a prefix like a * till screen-readers can report.
2. To study and comparing codes is difficult for a blind user that is
not able to study left and right editors in merge tools
simultaneously; so I prefer to study the code in a single normal
eclipse code editor that determines conflicts by <<< >>>.
when I need to open a file code to resolving a conflict it is better
to be a menu item like "open in code editor" in the context menu. I
know, the selected file will be opened in code editor if I select
""open from the context menu then select "project Explorer" option and
next I open code editor from there but this routine is too long. It
can have a shortcut or another shorter way.)
Thanks.
Comment 1 Thomas Wolf CLA 2022-10-31 09:09:03 EDT
Point (1): it's unclear to me which file list this is about. Do you mean in the staging view? A merge conflict is "resolved" only once the file has been staged.
If you mean some other file list, please state which one.

Point (2): which context menu do you mean? Again, in the staging view? There should be an entry for "Open Working Tree Version", which should do exactly what you want.