#FIREFOX DEVELOPER EDITION REVIEW UPDATE#
#FIREFOX DEVELOPER EDITION REVIEW PRO#
#FIREFOX DEVELOPER EDITION REVIEW CODE#

This is thanks to Jamie from the NVDA team who provided patches a while ago to make the web console and auto-completes read better. Yes, the web console is already accessible. I, of course, know Firebug myself, but having his way of working described to me in this depth helped me to understand better what the changes with the most short-term impact will be.

He described to me in detail how he, as a screen reader user, uses Firebug to give his clients feedback about their web sites and the problems he finds. What helped us greatly was a recent e-mail I received from Birkir, who is working as a web accessibility consultant at Deque Systems. For example, there are some tools which will help a lot of people at once, whereas others may never make much sense to somebody who cannot see the screen. So to make them accessible and at the same time achieve the highest amount of impact in the shortest amount of time possible, it was important to prioritize the different modules by importance.

#FIREFOX DEVELOPER EDITION REVIEW CODE#

There are web page inspection tools, debuggers for various components, a code editor, a style editor, a responsive design view and some far more visual components to examine performance, animations, and more. The developer tools have already become a big collection of tools for various purposes. So in order to secure the jobs of blind web accessibility consultants, it is our responsibility to make sure they continue to have an environment to work in when using Firefox. Firefox is accessible except for some small areas like the Customize Toolbar feature, so the developer tools should be, too.īut another reason is also that the built-in developer tools are becoming more and more integrated than the Firebug extension is, which has been used in the past if accessible web inspection and other tools were needed. The main reason of course is: It’s the right thing to do. This blog post marks the beginning of that journey. The majority of the tools are currently a very mouse-driven environment, and our goal is to make them equally accessible for keyboard users and those using assistive technologies such as screen readers. Also please note: I have been using FDF since 2015 and it’s only recently I started experiencing this behavior with Theme Co products.In the first quarter of 2016, Yura, who is part of the accessibility team at Mozilla, and I are starting on a journey to make the firefox developer tools accessible. Is this something your team can investigate and potentially fix? This is a great browser and I’m sure I’m not the only one (sorry, once more) that would love to have restored functionality in this browser. **I fully understand that these issues happen only in Firefox Developer Edition. All of the above I’ve attempted on cleared cache, refreshed browser (no extensions/add-ons).I do NOT experience any of these issues in Chrome.

#FIREFOX DEVELOPER EDITION REVIEW UPDATE#

You must refresh your browser in order for any items to update in the editor.The editor does not reflect any changes to ANY element when updated.I published a post previously with issues I had where:

#FIREFOX DEVELOPER EDITION REVIEW PRO#

I don’t think I’m the only person experiencing problems with the Cornerstone Standalone, Cornerstone in X, or Pro Theme editor while using Firefox Developer Edition.

Firefox developer edition review