E-mail List Archives

Thread: How to report accessibility bugs to Mozilla / firefox Devs, or, am I going crazy?

for

Number of posts in this thread: 6 (In chronological order)

From: Bossley, Peter A.
Date: Fri, Mar 31 2017 8:07PM
Subject: How to report accessibility bugs to Mozilla / firefox Devs, or, am I going crazy?
No previous message | Next message →

Greetings,
From the I can't believe I never noticed this before department, it appears as though in Firefox 52.0.2 32-bit on windows 10 Enterprise 64-bit it is not possible for a screen reader or keyboard reliant user to reach the toolbar buttons on the upper right of Firefox e.g. Bookmarks, Downloads, as well as any extention-added buttons in that space.
I don't have any older versions around to test so not sure if this is a recent thing, but I'd like to report this if it isn't already a known issue.
I've tried all the ways I could think to get there e.g. F6 / Tab, etc. You can reach the address bar, search bar, and site info buttons, but that's it.
This seems like a pretty big oversight and I'm honestly surprised given that the FF folks have even started to make the developer tools accessible.
Anyone have any insight? I almost feel like I have to be missing something obvious.
Best,

From: Birkir R. Gunnarsson
Date: Sat, Apr 01 2017 3:39AM
Subject: Re: How to report accessibility bugs to Mozilla / firefox Devs, or, am I going crazy?
← Previous message | Next message →

I think you're right actually. This is why e.g. aXe is not keyobard
accessible (I can't fire it up with a screenreader/keyboard only),
WebAIM are ifxing that, of course, but the problem is that with
Mozilla, if it is in a visible toolbar in Firefox, you should be able
to reach it via the keyboard.
I can get to the toolbars menu through the view menu, but I don't
think it is the same )alt -> v and select "toolbars").


On 3/31/17, Bossley, Peter A. < = EMAIL ADDRESS REMOVED = > wrote:
> Greetings,
> From the I can't believe I never noticed this before department, it appears
> as though in Firefox 52.0.2 32-bit on windows 10 Enterprise 64-bit it is not
> possible for a screen reader or keyboard reliant user to reach the toolbar
> buttons on the upper right of Firefox e.g. Bookmarks, Downloads, as well as
> any extention-added buttons in that space.
> I don't have any older versions around to test so not sure if this is a
> recent thing, but I'd like to report this if it isn't already a known issue.
> I've tried all the ways I could think to get there e.g. F6 / Tab, etc. You
> can reach the address bar, search bar, and site info buttons, but that's it.
> This seems like a pretty big oversight and I'm honestly surprised given that
> the FF folks have even started to make the developer tools accessible.
> Anyone have any insight? I almost feel like I have to be missing something
> obvious.
> Best,
>
>
> > > > >


--
Work hard. Have fun. Make history.

From: Bossley, Peter A.
Date: Sat, Apr 01 2017 8:50AM
Subject: Re: How to report accessibility bugs to Mozilla / firefox Devs, or, am I going crazy?
← Previous message | Next message →

The items under the view menu simply toggle if the toolbars are shown or not.
I find it so incredibley strange that this hasn't been addressed. What I'm wondering is two things: is this perhaps something that was addressed previously and is simply a regression or has nobody ever thought to fix it?


-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: Saturday, April 1, 2017 5:40 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] How to report accessibility bugs to Mozilla / firefox Devs, or, am I going crazy?

I think you're right actually. This is why e.g. aXe is not keyobard
accessible (I can't fire it up with a screenreader/keyboard only),
WebAIM are ifxing that, of course, but the problem is that with
Mozilla, if it is in a visible toolbar in Firefox, you should be able
to reach it via the keyboard.
I can get to the toolbars menu through the view menu, but I don't
think it is the same )alt -> v and select "toolbars").


On 3/31/17, Bossley, Peter A. < = EMAIL ADDRESS REMOVED = > wrote:
> Greetings,
> From the I can't believe I never noticed this before department, it appears
> as though in Firefox 52.0.2 32-bit on windows 10 Enterprise 64-bit it is not
> possible for a screen reader or keyboard reliant user to reach the toolbar
> buttons on the upper right of Firefox e.g. Bookmarks, Downloads, as well as
> any extention-added buttons in that space.
> I don't have any older versions around to test so not sure if this is a
> recent thing, but I'd like to report this if it isn't already a known issue.
> I've tried all the ways I could think to get there e.g. F6 / Tab, etc. You
> can reach the address bar, search bar, and site info buttons, but that's it.
> This seems like a pretty big oversight and I'm honestly surprised given that
> the FF folks have even started to make the developer tools accessible.
> Anyone have any insight? I almost feel like I have to be missing something
> obvious.
> Best,
>
>
> > > > >


--
Work hard. Have fun. Make history.

From: Jared Smith
Date: Sat, Apr 01 2017 9:41AM
Subject: Re: How to report accessibility bugs to Mozilla / firefox Devs, or, am I going crazy?
← Previous message | Next message →

Birkir R. Gunnarsson wrote:
> This is why e.g. aXe is not keyobard
> accessible (I can't fire it up with a screenreader/keyboard only),
> WebAIM are ifxing that

I can't speak to aXe (that's a Deque product), but if you're referring
to the WAVE extension, both Chrome and Firefox versions now support
keyboard activation via a shortcut key (Ctrl/Command + Shift + U) and
context (right click) menu, in addition to the browser toolbar.

Jared

From: Birkir R. Gunnarsson
Date: Sat, Apr 01 2017 10:02AM
Subject: Re: How to report accessibility bugs to Mozilla / firefox Devs, or, am I going crazy?
← Previous message | Next message →

Jeez, I am losing it (the effects of a 65+ hour workweek and moving), sorry all.
I was referring to the Wave plug-in, and thumbs up to WebAIM for
having fixed it (subject to my verification, I wil download and play
with the plug-in this afternoon).
aXe for Firefox is keyboard accessible (via tools, dev tools,
Accessibility Audit).
I should know, I wrote the screen reader/keyboard accessibility guide
for axe while I was at Deque (I (I left Deque last summer for a job
with BB&T bank, they keep me busy).

Cheers all, sorry for the brain fart



On 4/1/17, Jared Smith < = EMAIL ADDRESS REMOVED = > wrote:
> Birkir R. Gunnarsson wrote:
>> This is why e.g. aXe is not keyobard
>> accessible (I can't fire it up with a screenreader/keyboard only),
>> WebAIM are ifxing that
>
> I can't speak to aXe (that's a Deque product), but if you're referring
> to the WAVE extension, both Chrome and Firefox versions now support
> keyboard activation via a shortcut key (Ctrl/Command + Shift + U) and
> context (right click) menu, in addition to the browser toolbar.
>
> Jared
> > > > >


--
Work hard. Have fun. Make history.

From: Birkir R. Gunnarsson
Date: Sat, Apr 01 2017 10:18AM
Subject: Re: How to report accessibility bugs to Mozilla / firefox Devs, or, am I going crazy?
← Previous message | No next message

And, yes, the Firefox Wave plugin now works with keyboard ... finally,
I've missed using it!

Thanks Jared and co.


On 4/1/17, Birkir R. Gunnarsson < = EMAIL ADDRESS REMOVED = > wrote:
> Jeez, I am losing it (the effects of a 65+ hour workweek and moving), sorry
> all.
> I was referring to the Wave plug-in, and thumbs up to WebAIM for
> having fixed it (subject to my verification, I wil download and play
> with the plug-in this afternoon).
> aXe for Firefox is keyboard accessible (via tools, dev tools,
> Accessibility Audit).
> I should know, I wrote the screen reader/keyboard accessibility guide
> for axe while I was at Deque (I (I left Deque last summer for a job
> with BB&T bank, they keep me busy).
>
> Cheers all, sorry for the brain fart
>
>
>
> On 4/1/17, Jared Smith < = EMAIL ADDRESS REMOVED = > wrote:
>> Birkir R. Gunnarsson wrote:
>>> This is why e.g. aXe is not keyobard
>>> accessible (I can't fire it up with a screenreader/keyboard only),
>>> WebAIM are ifxing that
>>
>> I can't speak to aXe (that's a Deque product), but if you're referring
>> to the WAVE extension, both Chrome and Firefox versions now support
>> keyboard activation via a shortcut key (Ctrl/Command + Shift + U) and
>> context (right click) menu, in addition to the browser toolbar.
>>
>> Jared
>> >> >> >> >>
>
>
> --
> Work hard. Have fun. Make history.
>


--
Work hard. Have fun. Make history.