Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Accessibility options under settings #1286

Closed
vesta0 opened this issue Apr 1, 2019 · 12 comments
Closed

Accessibility options under settings #1286

vesta0 opened this issue Apr 1, 2019 · 12 comments
Assignees
Labels
access Accessibility: Talkback, HW keyboard/mouse, braile display etc. eng:qa:verified QA Verified eng:ready Ready for engineering P1 Current sprint Release Blocker Blocks a Release

Comments

@vesta0
Copy link
Collaborator

vesta0 commented Apr 1, 2019

User Story

As a user, I want to be able to change my browser accessibility settings so I can browse comfortably.

Dependencies

A-C Issue: Using system font for non-mobile pages (Landed in A-C) #577
UX designs: #1285

Updated settings screen: https://mozilla.invisionapp.com/share/X3R7SA84BFR
New accessibility screen: https://mozilla.invisionapp.com/share/87RPXG0QDUZ

Acceptance Criteria

I can adjust the size of website content font on desktop sites.

┆Issue is synchronized with this Jira Task

@vesta0 vesta0 added P1 Current sprint access Accessibility: Talkback, HW keyboard/mouse, braile display etc. labels Apr 1, 2019
@vesta0 vesta0 added this to the MVP Backlog milestone Apr 1, 2019
@vesta0 vesta0 added the 🙅 waiting Issues that are blocked or has dependencies that are not ready label Apr 1, 2019
@vesta0 vesta0 changed the title Accessibility options under settings [Meta] Accessibility options under settings Apr 3, 2019
@vesta0 vesta0 changed the title [Meta] Accessibility options under settings Accessibility options under settings Apr 9, 2019
@bifleming bifleming added this to Blocked by GV in Blocking Fenix Apr 17, 2019
@bifleming bifleming moved this from Blocked by GV to Blocked by Unknown in Blocking Fenix Apr 17, 2019
@bifleming bifleming moved this from Blocked by Unknown to Blocked by UX in Blocking Fenix Apr 17, 2019
@vesta0 vesta0 added the beta label Apr 17, 2019
@vesta0 vesta0 added this to Backlog of upcoming work in Fenix MVP UX via automation Apr 17, 2019
@vesta0 vesta0 added the UX label Apr 17, 2019
@vesta0 vesta0 removed this from Backlog of upcoming work in Fenix MVP UX Apr 17, 2019
@vesta0 vesta0 added 🙅 waiting Issues that are blocked or has dependencies that are not ready and removed beta 🙅 waiting Issues that are blocked or has dependencies that are not ready labels Apr 30, 2019
@project-bot project-bot bot added this to Blocked in Fenix Sprint Kanban Apr 30, 2019
@mheubusch mheubusch removed the 🙅 waiting Issues that are blocked or has dependencies that are not ready label May 1, 2019
@mheubusch mheubusch removed this from Blocked by UX in Blocking Fenix May 1, 2019
@vesta0 vesta0 moved this from Blocked to High priority backlog (not in the current sprint) in Fenix Sprint Kanban May 7, 2019
@bifleming bifleming added needs:product 🙅 waiting Issues that are blocked or has dependencies that are not ready labels May 8, 2019
@project-bot project-bot bot moved this from High priority backlog (not in the current sprint) to Blocked in Fenix Sprint Kanban May 8, 2019
@bifleming bifleming added 🙅 waiting Issues that are blocked or has dependencies that are not ready needs:UX-feedback Needs UX Feedback and removed needs:product 🙅 waiting Issues that are blocked or has dependencies that are not ready labels May 8, 2019
@vesta0 vesta0 added eng:ready Ready for engineering and removed UX labels May 16, 2019
@apbitner
Copy link

Good question. We're just going to follow what most other browsers do, which is a scale from 50% to 200%, in increments of 5%. I think the increments will make it easier to get back to 100% as well.

The background is Violet 05 (#E7DFFF), 100% opacity. Text color is #232749.

@vesta0 vesta0 moved this from Ready for Dev to In Progress in Fenix Sprint Kanban May 17, 2019
@bifleming bifleming added the Release Blocker Blocks a Release label May 17, 2019
@ekager ekager added the eng:qa:needed QA Needed label May 17, 2019
@project-bot project-bot bot moved this from In Progress to Ready for QA in Fenix Sprint Kanban May 17, 2019
@lobontiumira
Copy link

lobontiumira commented May 20, 2019

The scale doesn't apply on menus, or websites with/without Desktop site on.
Tested on the latest build 1.0.1920 (#11391807), with Samsung Galaxy S8 (Android 8), and Sony Xperia Z5 Premium (Android 7.1.1).

@ekager I am not sure if the changes on the scale are applicable only after closing and reopening Fenix, or immediately, without closing the app?
Thanks!

@sv-ohorvath sv-ohorvath removed the eng:qa:needed QA Needed label May 20, 2019
ekager added a commit to ekager/fenix that referenced this issue May 22, 2019
@ekager
Copy link
Contributor

ekager commented May 22, 2019

@softvision-miralobontiu sorry for the delay! I should have left a comment here, but I was waiting on an AC issue that was merged yesterday to be able to dynamically change these engine settings. #2747 will reload the current session so you will be able to see the changes immediately when updating the setting.

@lobontiumira
Copy link

Verified that the font size on the websites is changed according to the scale modified in Settings - Accessibility.
Tested on the latest build 1.0.1921 (#11430614), with OnePlus 5T (Android 9), Huawei P9 Lite (Android 6), Sony Xperia Z2 tablet (Android 6.0.1).

@lobontiumira lobontiumira added the eng:qa:verified QA Verified label May 23, 2019
@lobontiumira lobontiumira moved this from Ready for QA to Done in Fenix Sprint Kanban May 23, 2019
@buttercookie42
Copy link

buttercookie42 commented May 23, 2019

2a. How does setAutomaticFontSizeAdjustment() work in with these new settings?

The currently implemented behaviour isn't ideal in any case, because if 100 % actually means "automatic font size adjustment enabled", then 100 % isn't necessarily 100 %, but instead whatever the OS-level font size setting is. So if the OS-level setting is e.g. at 125 %, then moving the FennecFenix slider from 100 % to 110 % actually decreases the font size, because in practice you're going from 125 % to 110 %.
Plus behind the scenes you need to manually need to turn on font inflation to keep it enabled (which apparently so far you didn't), because otherwise the effective font size on non-mobile-friendly pages decreases even more.

Basically I think that if you want some amount of manual control over the amount of font size scaling, you should decide between one of the following:

  • complete manual control and never follow the OS-level setting
  • a toggle switch for automatic font size setting, which when toggled off would show/enable the manual control
  • what Chrome does: the manual control is applied as an additional multiplier on top of the OS-level font size setting, in which case that would require some additional work on the GeckoView-side.

@ekager
Copy link
Contributor

ekager commented May 23, 2019

Thanks @buttercookie42 for the explanation! I think the last option is the most ideal going forward to follow Chrome's implementation of applying an additional multiplier. For now I will add a toggle using the system's text sizing.

ekager added a commit to ekager/fenix that referenced this issue May 23, 2019
@buttercookie42
Copy link

buttercookie42 commented May 24, 2019

CC me (:JanH) when you file a corresponding GeckoView bug, and I'm happy to look at it.

ekager added a commit to ekager/fenix that referenced this issue May 24, 2019
@data-sync-user data-sync-user changed the title Accessibility options under settings FNX2-16961 ⁃ Accessibility options under settings Aug 3, 2020
@data-sync-user data-sync-user changed the title FNX2-16961 ⁃ Accessibility options under settings FNX3-15450 ⁃ Accessibility options under settings Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX3-15450 ⁃ Accessibility options under settings FNX-4928 ⁃ Accessibility options under settings Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX-4928 ⁃ Accessibility options under settings FNX2-16961 ⁃ Accessibility options under settings Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX2-16961 ⁃ Accessibility options under settings Accessibility options under settings May 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
access Accessibility: Talkback, HW keyboard/mouse, braile display etc. eng:qa:verified QA Verified eng:ready Ready for engineering P1 Current sprint Release Blocker Blocks a Release
Projects
None yet
Development

No branches or pull requests

10 participants