Open Bug 1919599 Opened 5 months ago Updated 3 days ago

[meta] accessibility metabug for profiles

Categories

(Toolkit :: Startup and Profile System, task)

Product:
Toolkit
Component:
Startup and Profile System
Type:
task

Tracking

()

Project Flags:
a11y-review requested

People

(Reporter: jhirsch, Assigned: nstroud)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

Parent metabug for a11y feature requests and bugs

Description:
Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).
Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.

Hello, we have added support for multiple profiles to desktop firefox in 134 nightly. While we are still working on a number of additional features and bugs (captured under metabug 1927938), the core functionality is available (the profiles menu is displayed in the OS menubar and in the app menu once the pref is flipped).

How do we test this?
If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.

  • Enable the feature by setting the browser.profiles.enabled pref to true in 134 nightly. You can then create additional profiles and switch between them using the profiles menu in the OS menubar or the app menu.
  • Clicking a profile entry in either menu will either switch app focus to that profile, if it is running, or otherwise launch that profile in a new Firefox instance.
  • It is possible to configure the profile selector dialog to appear at startup, but some open bugs make this a bumpy experience right now.

When will this ship? initially, we will ship in a 0.5% rollout sometime soon after 134 (exact version TBD)

Tracking bug/issue: bug 1927938

Design documents (e.g. Product Requirements Document, UI spec):

Engineering lead: Jared Hirsch

Product manager: Kim Bryant

The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:
https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:

  • Our additions to existing menus should be accessible, as we have reused existing menu-related code.

  • Our new about pages (about:newprofile, about:editprofile, about:deleteprofile) have used semantic html and desktop reusable components to give us good accessibility by default, including keyboard navigation support. There is also an about:profilemanager page that is normally only displayed inside a manage profiles dialog window, but it can be visited by typing about:profilemanager into the urlbar.

Describe any areas of concern to which you want the accessibility team to give special attention:

  • We have added a new profiles manager dialog window, which can be opened by going to the Profiles menu then clicking 'Manage profiles'. We want to be sure this window is accessible.

  • Users can choose from a number of new desktop themes on the customization pages (either about:newprofile or about:editprofile). We want to be sure these provide sufficient contrast and are generally accessible.

  • Mac dock entries for different profiles are badged with the avatar and theme colors for each individual profile. (Work on multiple distinct taskbar entries for windows is ongoing.) We want to be sure that our badged icon approach is sufficiently accessible.

a11y-review: --- → requested
Depends on: 1934866
Depends on: 1934860

Just a note for a11y eng folks - we're now targeting 138 for the initial small rollout, and all the a11y work that was spec'd in Figma has landed in Nightly.

Ready for review any time

Assignee: nobody → nstroud
You need to log in before you can comment on or make changes to this bug.