Now used Aiatana design blocks Evince accessibility usage if the current session is not Unity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evince (Ubuntu) |
Fix Released
|
High
|
Lars Karlitski |
Bug Description
Dear Developers,
Since Evince 3.10.3-0ubuntu3 version used changes blocks Evince keyboard usage with accessibility related.
To testing some testcases, please install gnome-shell and gnome-shell-
Two simple testcases if the used session is not Ubuntu (Unity interface), for example gnome, gnome-classic or gnome-flashback:
1. Launch Evince if you using for example gnome or gnome-classic session.
2. Press F10 key. Expected result with original upstream version:
After F10 key press presenting a context menu with have possibility to use importanter functions (open, close, etc).
Actual result: nothing happening after F10 key press.
A testcase with Evince accelerators related:
1. Launch Evince.
2. Try opening a file with CTRL+O keystroke.
Expected result with upstream 3.10.3 version: the file open dialog is presenting the screen after CTRL+O keystroke.
Actual result: nothing happening.
My conclusion is following with GNOME Shell environment and downstream patched evince 3.10.3-0ubuntu3 and 3.10.3-0ubuntu4 package version related:
The evince 3.10.3-0ubuntu3 and higher versions killed the original upstream version available accessibility support. Visually impaired users using only with keyboard and screen reader support if entire not see the screen.
To demonstrate this bad change, try following testcase:
1. Launch Orca screen reader with orca command.
2. Launch evince and opening a text containing pdf document (only images containing pdf file is not good now).
3. Try enabling the F7 keystroke the caret navigation support.
Expected result with upstream version: a popup message dialog will be presenting the screen after F7 keystroke, and the user have possibility to click enable button.
When caret navigation support is enabled, visually impaired users have possibility to read text-only pdf documents with Evince the Orca screen reader, full accessible way.
Actual result with Ubuntu Trusty packaged version: when F7 keystroke is pressed, nothing happening. Impossible to enabling this function, so impossible reading a pdf document with arrow keys the Evince application and Orca screen reader, impossible to selecting only a part of a pdf file, etc.
Now, I need reverting following patches and using own compiled evince package to I get full the awailable a11y support this application:
0001-Port-
0002-Remove-
If I understanding right the purpose of the second patch, this patch reverting keyboard accelerators with Evince awailable actions.
If I using temporary my modified evince package, all wrote testcases passed right if I using gnome-classic session.
Attila
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evince 3.10.3-0ubuntu4
ProcVersionSign
Uname: Linux 3.13.0-7-generic i686
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CurrentDesktop: GNOME
Date: Fri Feb 7 07:29:29 2014
InstallationDate: Installed on 2013-12-13 (55 days ago)
InstallationMedia: BeLin 3.02 i386
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Ubuntu Desktop: Pending requested
-
Diff: 422 lines (+207/-46)2 files modifieddebian/patches/0001-Port-to-GMenuModel-and-add-menu-bar.patch (+36/-35)
debian/patches/0002-Remove-gtk_application_set_accels_for_actions.patch (+171/-11)
- Sebastien Bacher: Approve
-
Diff: 662 lines (+222/-276)4 files modifieddebian/patches/0001-Port-to-GMenuModel-and-add-menu-bar.patch (+35/-36)
debian/patches/0002-Don-t-use-gtk_application_set_accels_for_action.patch (+186/-0)
debian/patches/0002-Remove-gtk_application_set_accels_for_actions.patch (+0/-239)
debian/patches/series (+1/-1)
Changed in evince (Ubuntu): | |
assignee: | nobody → Lars Uebernickel (larsu) |
status: | New → In Progress |
Changed in evince (Ubuntu): | |
status: | New → Fix Committed |
importance: | Undecided → High |
This patch restoring missing a11y support for Evince, but not an optimal way.
Unfortunately if this patch applied a new version, will be kill Unity related doed menubar related modification.
Need founding a more optimal solution to al desktop environments have possibility to use you wanted menubar possibility, but keep already upstream level awailable a11y support.
I not see clear the concept. If an user using Unity and launching Evince, will be presenting a gtk.menubar style main menu, or an absolute different visually lookup main menu?
I not have possibility to using Unity, because GNOME Shell environment is more accessible now with orca.
Attila