Screenreader starts, but does not work with installer (ubiquity) in live session

Bug #1231091 reported by Paul Larson on 2013-09-25
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)

Bug Description

Image: 20130925

I started the image and let it boot to the gui selector for live session or install only. When the drum sound played, I pressed ctrl-s to start the screen reader and heard the familiar "screenreader on" sound, and it read the options to me. From there, I started the live session, and went into the installer, but orca would not read any of the screens. I also started a terminal window and noticed that it says "window" when I move the mouse over the unity launcher icon, and "unity dash" when I click on it, but nothing in the terminal is read to me either. So I don't think this is limited to just ubiquity.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-orca 3.9.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CasperVersion: 1.336ubuntu1
Date: Wed Sep 25 14:04:20 2013
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: gnome-orca
UpgradeStatus: No upgrade log present (probably fresh install)

Paul Larson (pwlars) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Paul Larson (pwlars) on 2013-09-25
description: updated

What happens when you launch the live image directly to the desktop, and enable accessibility from the F5 accessibility menu?

I was able to use the terminal as you described, although I had to do so after using alt tab to make sure it was switched to. I think Orca works better when nautilus properly loads, and there is a desktop frame for point of reference. THings behave correctly when I booted the live image directly to the desktop, and enabled accessibility from the boot menu.

Yes ubiquity is not accessible, when being run from the live session, but that is moreso an ubiquity problem, because Orca is able to work with applications if they are running as root, including their GUI.

Moving to ubiquity for now, and I'll try digging a bit further next week.

affects: gnome-orca (Ubuntu) → ubiquity (Ubuntu)

Still hitting this on the rc image for 20131016 - no sounds from ubiquity.
using the f5 menu, it works in ubiquity, but I still hit bug #1154345

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Para Siva (psivaa) wrote :

I hit this twice out of 3 attempts with 20131016.1 i386 image.

Changed in ubiquity (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-14.04
Mathew Hodson (mhodson) on 2015-11-12
Changed in ubiquity (Ubuntu):
milestone: ubuntu-14.04 → none
tags: added: a11y
Sai Vinoba (saivinoba) wrote :

Issue exists in 20.10 ISO as well. Currently testing 20201021.2 ISO. When installer started, it only reads installer started but there after no instruction to navigate. screen-reader installation testcase fails.

summary: - Screenreader starts, but quits working in live session on install
+ Screenreader starts, but does not work with installer (ubiquity)
summary: - Screenreader starts, but does not work with installer (ubiquity)
+ Screenreader starts, but does not work with installer (ubiquity) in live
+ session
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers