New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inaccessible Monkey Menu #2794

Closed
jsl303 opened this Issue Jan 7, 2018 · 8 comments

Comments

Projects
None yet
4 participants
@jsl303

jsl303 commented Jan 7, 2018

I'm a visually impaired user, and Monkey Menu seemed to become inaccessible since since 4.0 with screen reader.
Is there a way to bring back Monkey Menu under tools menu?
Or, is there way to present the UI objects in html view?
Thanks!

@Sxderp

This comment has been minimized.

Contributor

Sxderp commented Jan 7, 2018

Is there a way to bring back Monkey Menu under tools menu?

Unfortunately no.

Accessibility is being worked on (#2639) and feedback is appreciated. Being an individual who doesn't require these types of assistance can make it difficult to understand what will and will not work. As new updates are rolled out please continue to post your thoughts and feedback.

@arantius , If the Monkey Menu does not work then the decision to remove the full page menu may have to be reversed. Of course this is still early and the initial changes haven't been pushed yet.

@arantius

This comment has been minimized.

Collaborator

arantius commented Jan 8, 2018

Is there a way to bring back Monkey Menu under tools menu?

Maybe? Partially?

Monkey Menu seemed to become inaccessible since since 4.0

You're not the only person to report this, we've made the first bit of progress towards improving this recently ( 056f978 ). I'll keep this issue open to report the next beta build which will include that change, so you can let us know how much this improves things for you.

@arantius arantius added this to the 4.2 milestone Jan 8, 2018

@arantius

This comment has been minimized.

Collaborator

arantius commented Jan 9, 2018

The fix in PR #2660 is packaged in version 4.2beta2:
https://addons.mozilla.org/firefox/downloads/file/833159/greasemonkey-4.2beta2-an+fx.xpi?src=devhub

This is only a start, but better than we've done so far! Testing is always appreciated!

My experience so far is: click the toolbar button (I don't know how a non-sighted/non-mouse-using person does this???), press tab, then up/down/enter mostly work. The first "down" selects the second item, not the first.

@Eselce

This comment has been minimized.

Contributor

Eselce commented Jan 9, 2018

The first up after pressing tab selects first item, as I can see...

@Sxderp

This comment has been minimized.

Contributor

Sxderp commented Jan 9, 2018

I purposely made it so the first down selected the second item while the first up selects the first.

It felt 'normal' to me. I've seen that setup before but I don't recall where.

@jsl303

This comment has been minimized.

jsl303 commented Jan 10, 2018

@Sxderp

This comment has been minimized.

Contributor

Sxderp commented Jan 10, 2018

Could you attach a shortcut to bring that menu?

I did a quick search and I this is what I found in regard to APIs.
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/browserAction/openPopup

Activating a keyboard shortcut defined by the extension (note: this is not currently supported in Firefox).

I don't know if they're working on a fix.

Or, is there a way to set Greasemonkey to open an external editor

Not at the moment, but when the backend script installation / update flow is reworked and cleaned up to be faster and act more like 3.x, it should be easier to add an interface for external programs. Assuming it's added it won't be as simple as filesystem access (rip Addons) but a python wrapper or somesuch could potentially be used.

@arantius

This comment has been minimized.

Collaborator

arantius commented Jan 10, 2018

I'm glad you find this an improvement. We know we're not done, further things like the editor are being tracked at #2639.

@arantius arantius closed this Jan 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment