Firefox Hello accessibility review

RESOLVED INCOMPLETE

Status

Hello (Loop)
Client
P4
normal
Rank:
46
RESOLVED INCOMPLETE
3 years ago
a year ago

People

(Reporter: RT, Unassigned)

Tracking

({access})

unspecified
access
Points:
---
Dependency tree / graph
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [accessibility])

(Reporter)

Description

3 years ago
Firefox Hello will need an accessibility review at some point.
First step is to clarify if now is the good time and who can help us for that.
(Reporter)

Comment 1

3 years ago
Sevaan, we discussed this, can you please help there understand who can help us there?
Flags: needinfo?(sfranks)
Flags: needinfo?(sfranks)
David Bolter and Marco Zehe are able to help on the accessibility side. I have cc'd them here.

DavidB, MarcoZ: What can we provide to you to help move things forward?
I've used Hello a bunch already but for this testing should I be testing Nightly?

To get me started, how do I invoke Firefox Hello via the keyboard only (I'm currently trying on Mac)?
Well, that's a big problem already, haha.

Possible plan:

I think we should come up with a keyboard shortcut which opens the panel and moves focus to it. Then the user can keyboard down through the conversations. Hitting enter opens it and moves focus to the conversation window. If they keep keyboarding down they can hit the "Start a Conversation" button which opens a new room and moves focus there.

And we can implement a tab order as well maybe.
For opening the loop button via the keyboard, this is bug 1106932 which has already had some discussion about options - I suggest continuing that part of the discussion there.

I'm also adding a couple of other know issues as well.
Depends on: 1106932, 1066171, 1084287
Keywords: access

Comment 6

3 years ago
these will be taken around UX refresh time....add other related bugs under this.
Rank: 46
Flags: firefox-backlog+
Priority: -- → P4
Whiteboard: [Accessibility]

Comment 7

3 years ago
(In reply to :shell escalante from comment #6)
> these will be taken around UX refresh time....add other related bugs under
> this.

What does this mean? When is UX refresh time?
Flags: needinfo?(sescalante)
(In reply to :Gijs Kruitbosch from comment #7)
> (In reply to :shell escalante from comment #6)
> > these will be taken around UX refresh time....add other related bugs under
> > this.
> 
> What does this mean? When is UX refresh time?

We're currently planning a "refresh" of the UX, which will touch all parts of the UI. It will probably happen starting after the next release cycle (so prob end of June). It seems to make sense to complete this work at that time given our current workload, although obviously, if we can identify issues ahead of time, it'll mean we can be more aware and work them into the ongoing fixes that we're doing.
Flags: needinfo?(sescalante)
Depends on: 1211434
Whiteboard: [Accessibility] → [accessibility]
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.