Closed Bug 1018144 Opened 6 years ago Closed 4 years ago

[flatfish] Cannot navigate from 1st to 2nd home with screen reader when no icons

Categories

(Firefox OS Graveyard :: Gaia::Homescreen, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: steve, Unassigned)

References

Details

(Keywords: access)

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140527133511

Steps to reproduce:

Turn screen reader on. Go to home screen


Actual results:

It is not possibelto navigate to the settings to turn the screen reader off.

In the shipped build the volume up/down togle is not available


Expected results:

Icons should be there and so possibel to navigate to settings
Or, screen reader doesn't need an icon in main area to get focus before two finger scroll works (perhaps the bottom icons?)
[can't figure how to edit description]

The tablet as it ships has no group icons on the first home screen. 

This makes it impossible to navigate to the 2nd page of icons as an icon needs to have focus before 2 finger swipe works.

Thus once screen reader is turned on and home screen is reached it is impossible to turn the screen reader off via the UI.
See Also: → 1018142
Here's a work around

* Debugging ADB should be enabledb on the tablet (it is 'ADB only' by default)
* install and config ADB on host computer and connect to tablet via USB
* create a folder on host, ope na command shell and cd to the folder
* "adb pull data data" - this pulls files off the tablet into the folder
* edit data/prefs.js
* change line with screenReader in it from a value of 1 to 0
* "adb push data/b2g/profilename/prefs.js /data/" 
* "adb reboot"

Once screen reader is off you can install an app to creat and icon and you will then be able to 2 finger swipe to the 2nd home screen with the screen reader turned on 

(for simple instructions on using the screen reader see http://opendirective.net/blog/2014/05/help-i-bricked-my-firefox-os-1-3-device-by-enabling-the-accessibility-screen-reader/)
Blocks: gaiaa11y
Component: Gaia → Gaia::Homescreen
Keywords: access
this affects all devices if anything but the last home screen has, or is stripped of, all icons except the bottom row. We need a way to focus the container if there are no actual icons.
The way the scrolling with the screen reader works currently is to focus an icon in the main home screen area, then swipe left and right with two fingers to move to the next/previous home screen.
Observed the same error and with the help of raniere I used adb shell and then wipe data to remove the data folder and reboot. yes ADB comes enabled by default in the devices.
Thanks for the confirmation, we were getting some reports that adb was off.

Are you saying it is safe to delete the data folder as useful defaults are then set automatically? If so are they the same as the tablets ship with?
Yes, when you wipe the data folder, and reboot, it will come up with the first-run experience as if you had just unpacked it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
So the recovery instructions above don't work and I can't figure how to edit or delete them

To turn off the screen reader do a reset via a computer connected to the tablet as follows

1. run a command prompt
2. adb shell
3. cd data
4. rm -rf .
5. exit
6. adb reboot

That will wipe **all the data**, in essence resetting the device to its default state when it first was shipped. The first time user experience will run again.
(In reply to Steve Lee from comment #1)
> The tablet as it ships has no group icons on the first home screen. 
> 
> This makes it impossible to navigate to the 2nd page of icons as an icon
> needs to have focus before 2 finger swipe works.
> 
> Thus once screen reader is turned on and home screen is reached it is
> impossible to turn the screen reader off via the UI.

If all it needs is an app to be present on the first homescreen panel in order to swipe, then we can just have the user install an app from the marketplace via the web browser (which is in the doc).
That's a great idea. However browsing to marketplace, sign in and app search is quite difficult for no  screen reader user.

@Marco - can it be done fairly easily?

We could create a shortlink to go direct to the app page in the market place?
(In reply to Steve Lee from comment #9)
> That's a great idea. However browsing to marketplace, sign in and app search
> is quite difficult for no  screen reader user.
> 
> @Marco - can it be done fairly easily?

Is signing in necessary? I wasn't thinking it was. 
No need to search, just install one of the free, featured apps on the front page.
(Also, I expect things are easier once you're in an app (in screen reader mode).)

> We could create a shortlink to go direct to the app page in the market place?

Did you mean create an app that merely opens the Settings app?
I had that thought but half forgot it and half figured there would be a permissions issue, but if we could that could be a nice solution.
Summary: [flatfish] Cannot navigate from 1st to 2nd home with screen reader when no group icons → [flatfish] Cannot navigate from 1st to 2nd home with screen reader when no icons
Signin:(In reply to Caspy7 from comment #10)
> Is signing in necessary? I wasn't thinking it was. 

er, no. I'm obviously getting mixed up with other 'closed' marketplaces

> > We could create a shortlink to go direct to the app page in the market place?
> 
> Did you mean create an app that merely opens the Settings app?
> I had that thought but half forgot it and half figured there would be a
> permissions issue, but if we could that could be a nice solution.

Actually I meant a URL shortlink to the app install page in the market but that's a great idea.....
For info - it seems everything me was deliberately removed from the Flatfish build - https://bugzilla.mozilla.org/show_bug.cgi?id=1018142#c6
Blocks: flatfish
Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.
Blocks: 1231115
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.