For simplicity (and because I think entering tab characters isn't really essential for the notepad) I decided to go with the first solution.

I guess, that's ok then, moving this to done.

In T7594#202471, @timegrid wrote:

Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).

Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).

Thanks for the Windows 11 screen shots.

Thanks for the feedback. The issues are the same as on win10:

Regarding the "unsure" findings:

• invalid state in cert list tooltip (red on black)

1. Issues found

Most issues with icons in high contrast modes (of Windows 10) should have been fixed. Needs to be verified especially with the high contrast modes of Windows 11.

Setting to Testing.

on gpg4win-5.0.0-beta190@win10 (high contrast):

I found more issues with the success, warning, and error icons we show in various places.

For reference the related MRs for upstream:
https://invent.kde.org/plasma/breeze/-/merge_requests/540 (pending)

Fixed. If high-contrast is active then tool tips now use the same colors as buttons (e.g. white text on black for Kontrast No. 1).

With the above patch for breeze the toolbar and the configuration dialog title now also look correct in high-contrast mode.

The wrong/inconsistent coloring of the icons has been fixed.

After T7587: Kleopatra: High contrast mode isn't respected anymore was fixed this is what the buttons look like in Gpg4win 5:

works as described.

VSD 3.3.0:

Fixed (for Gpg4win 4.4 / VSD 3.3) by patching Qt's Windows Vista style.

High priority since it affects accessibility and was mentioned as problem in the accessibility reports.

gpg4win-beta-50: There are no duplicate announcements of the entries in the result table of a keysearch with NVDA

Backported for VSD 3.3

Should be merged for VSD 3.3 to fix the finding made when testing T6936: Kleopatra: Auto-select in case of only one keysearch result (see T6936#187185).

Should be tested with NVDA on Windows to verify that this works as expected and that we don't get duplicate announcements by the screen reader.

ok, checked with Beta-41

Backported for VSD 3.3

Yes, please.

@werner Shall this be backported to VSD 3.3? The changes look more dramatic than they are. I mostly reordered existing code.

Fixed.

Yes, we can probably wait for Qt 6. It may anyway need to be fixed directly in Qt.

@ikloecker I would like your opinion if this should not wait for Qt6 if it is an issue with Qt. I guess "prio low" would anyway mean. "Let us leave this for a while" :)

The site is on purpose w/o Javascript which might be the cause for things you reported. But I agree that the tab order is not as one would expect.

I think the priority is low because the optional columns are not really that useful for most users and were mostly added as a "nice to have" feature. The details are in doubt available e.g. through the certificatedetails widget.