A screen reader should automatically report the result of the events triggered by a button-click.
Description
Description
Revisions and Commits
Revisions and Commits
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRAdd8cbab5314e Add missing UI marker to new message | |||
| rKLEOPATRA18441d47a36a Use better tooltip for Close button of result message | |||
| rKLEOPATRA2e409789f7b4 Notepad: Focus progress label while processing notepad | |||
| rKLEOPATRAb7a8a8d0f658 Notepad: Focus result widget after the crypto operation | |||
| rKLEOPATRA2a8bfef93cee Notepad: Give focus back to widget that had focus on start of processing | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T5824 Kleopatra: Full accessibility support | ||
| Testing | • ikloecker | T7770 Kleopatra: Ensure that result of notepad operation is accessible |
Event Timeline
Comment Actions
Solved by focusing the result message after the notepad operation is complete. I think that's an acceptable compromise for ensuring that users of assistive tools are informed about the result even if the focus is moved to a different UI element (which, in general, should be avoided because users can get lost).
Additionally, the progress message is focus while the notepad is processed. Most likely the progress message is never fully read to the user because either some other window pops up (e.g. pinentry or import progress dialog) or the operation is quickly completed.