With the Breeze style the (old) focus indicator looks like this:

@werner Could these two patches could be backported to 2.2? These changes give same level of performance increase in 2.2 as seen in 2.3.

This is related to T5950: Allow viewing expired certificates more easily where a user was wondering why some key wasn't offered as encryption key. It turned out that the encryption subkey was expired.

Backported for for 2.2.37

When the protocol is already choosen then the wizard is still opened and not the dialog. E.g. if the key is created from the welcomewidget's "New Key Pair" button. Or if S/MIME Certificate creation is disabled completely.

This is about showing the corresponding about dialog text for the disable support option.

Now the buttons react to Enter/Return. But for now only the tool buttons in the welcome widget do. This needs to be extended to all other tool buttons used by Kleopatra. -> T6110: Kleopatra: All buttons shall be activatable with the Enter/Return key

Sorry, I did not mean to imply that this was a regression, I only noticed this as I was tabbing through the welcome dialog and then wanted to test openpgp certificate creation by keyboard and was also irritated that it did not work as expected on the button.

I very much doubt that the buttons ever reacted on Enter. Those buttons are and always were QToolButtons. QToolButton doesn't reimplement keyPressEvent and QAbstractButton::keyPressEvent explicitly ignores Enter and Return. I think you are confusing this with the old "Choose Protocol" page of the wizard which used QCommandLinkButtons which indeed to react on Enter.

I'm using QFocusFrame for the visual indication. Qt uses QFocusFrame only with the MacStyle and there it probably looks much better. Breeze also uses it (inspired by the MacStyle).

When the protocol is already choosen then the wizard is still opened and not the dialog. E.g. if the key is created from the welcomewidget's "New Key Pair" button. Or if S/MIME Certificate creation is disabled completely.

In T5824#160925, @ikloecker wrote:

Because it doesn't look good, but it is required for full accessibility, I have considered adding a configuration option to enable/disable extended accessibility.

Please add a subtask for the other problems in the welcome widget or add the information to the corresponding existing subtask (if there is one). This task here really only serves as Klammer-Ticket for the actual work items.

I know that the black frame looks bad. (It looks a bit better with Breeze.) The problem is that accessibility requires a visual indication of the keyboard input focus (see second recommendation for issue [3] in the report).

Fix will go into 2.2.37 and 2.3.8.

I tried to reproduce this as we had similar problems in the past, but for me this works with full unicode characters.

The welcomewidget has some problems:

The table is now (more) accessible. The second issue doesn't apply anymore because of T6108: Kleopatra: Information on storage location of OpenPGP key should be per subkey.

Hi Marcel!

I just confirmed that firmware 5.4.3 works fine with the changes (to be 2.2.37 and 2.3.8).

Sure... it's really more of a cosmetic issue. Even without verbose mode, it should become quickly clear to anyone.

New release of libassuan is expected to make sure it's cleared off.

What I found: When the page is served by the server, it omits "charset=utf-8" part. This is the issue.

I used to have the option of generating PGP Keys up to 4,096 key size. That function has completely disappeared.

Probably fixed meanwhile in 2.2.
Please re-open if experience this problem also with a decent gnupg 2.2 versions.

Probably an invalid specified keyserver

2. Tables need to work with TAB focus and then arrow button navigation

Issues:

• Fingerprint is inaccessible (finding [3] in the Prüfbericht Barrierefreiheit GnuPG Kleopatra 3.1.20.3)
• "Certify with" label not associated with combo box
• Collapsible "Advanced" section is not accessible (announced as "check box")
• UI elements in "Advanced" section can receive focus, even if section is collapsed (finding [12] in the Prüfbericht Barrierefreiheit GnuPG Kleopatra 3.1.20.3)
• "Tags" label not associated with input field
• Pressing Esc cancels dialog even if explanation tooltip is shown
• "Domain" input field has no label (finding [4] in the Prüfbericht Barrierefreiheit GnuPG Kleopatra 3.1.20.3)
• No accessible feedback when checking/unchecking user ID

Thanks for fixing.

That is not easy to change because we show all kind of error codes. If you run in --verbose mode you should see more info.

There won't be any semantic changes for obvious reasons.