1. Adding a setting to enable the gesture to turn on accessibility.
This is a new screen with a toggle switch similarly as screen
magnification which will contain explanation of how to perform
the gesture.
bug:6171929
Change-Id: I84dfa46a9b7b789d99923684e08e52cf7d236eb2
1. Screen magnification on the device has to he explicitly enabled
by the user before allowing a global gesture related interactions.
The feature toggle setting is in Settings->Accessibility and it
is a separate screen with instructions how to use the feature
and a toggle switch.
2. Added a setting in developer options for toggling the magnification
auto update feature. If this features is on the screen is zoomed
out or rotation or activity start. Also if the feature is enabled
the magnified viewport will scroll to show popped up windows.
bug:5587727
Change-Id: Ic45a21d3a3928e2f5aac034751801f090b261488
1. Now the the setting is names lock screen rotation
which is the opposite as it was before so this
patch reverses the checkbox state.
bug:6507335
Change-Id: Ic0aab21fa70871f64e37ac05f7917d69f9c0a0df
1. Now accessibility services request this mode and
we show a dialog so the user can give a consent.
Accessibility servces can toggle this mode at
runtime from their settings, for example.
bug:5932640
Change-Id: Id4d3e9c83c488f97b7e53d4baadf7de886958a4d
1. Adding text to speech (TTS) settings link under accessibility since
the TTS settings are buried under language and input, therefore it is
hard to find for a blind user. Note that TTS settings are some of the most
important for a visually impaired user.
bug:5713535
Change-Id: I60aed1aeec5d40aa633dbac6e6149ad12366e9e6
By default we do not speak passwords if the user has no headset. However,
many users find this too restrictive and would like a way to enable
password announcement. While we cannot speak the passwords all the time
,to avoid leaking them, we expose a preference so each user can choose
the option that best works for him/her.
bug:5712607
Change-Id: I1a6e95c392c18dc8d7406b1cef49705756b31254
1. Some string changes according to updated UX specs.
2. Explore by touch now shown only if accessibility is on.
3. The one time dialog for installing TalkBack if no services
are installed was not showing.
bug:5293099
bug:5286578
Change-Id: I633999f798b16e2910d95d541a7c33d1a4f296b9
1. Removed the global toggle switch - now each accessibility
feature has to be turned on or off separately.
2. Added a setting for the screen rotation (same as Dispaly)
since most of blind users want that behavior.
bug:5166161
bug:5127475
Change-Id: I659aef62a8499461075f43520a3008fa7b8ff911
1. Reimplemented accessibility settings accrding to UX design.
NOTE: The strings are not final, rather reasonable placeholders
to avoid blocking on them. Will submit another CL with string
updates and any necessary polishes.
bug:5065409
Change-Id: I3ba229a624298dbf238bc8562b42616b386f8c34
Also re-arrange the UI a bit to clearly put the button for
enabling/disabiling accessibility services along-side said
services.
Change-Id: Ica1ddecddf6e97800909ba6bea9ce4e124b59c01
Added a base class SettingsPreferenceFragment from which the settings activities should
be derived so that they can behave like fragments. It contains some commonly called
utility methods and dialog conversion to DialogFragment.
Some of the top-level activities can be launched directly without the left pane.
Settings.java acts as a proxy activity that contains just that settings fragment without
the left pane.
There are still a lot of second and third level activities that need to be fragmentized.
This is just the first pass to test the 2-pane layout.
This is part 3 of the fix for bug 2364220 "Accessibility improvements for
ending calls".
This change adds a checkbox under "Accessibility settings" to control the
new Settings.Secure.INCALL_POWER_BUTTON_BEHAVIOR value, which allows the
user to specify that the Power button should hang up while in-call
(instead of just turning off the screen.) The checkbox is only shown on
devices that actually have a POWER button.
Yeah, it's a little strange having this under Accessibility (since it's not
that obvious *why* this feature is accessibility-related), but there's no
obvious better place. See discussion in the bug for more info.
Bug: 2364220
Change-Id: I0fd7cf357972519b390575b9c06a4bbe46ff1c9b
