6/25/2023 0 Comments Firefox open network inspector![]() ![]() ![]() Try setting a breakpoint in a half-decent webapp - the whole browser(!) hangs for atleast 10 minutes, sometimes forever. Yes, there are some very useful features added in Firefox's Devtools but the performance is very poor. Even to this date, the Firefox Devtools are nowhere near Chrome's. The team was very receptive of the comments, but sadly not much was implemented until I stopped using FF as my main browser. I had expressed my concerns to them after trying the beta for a long time. They then decided to merge the two projects and stopped developing Firebug. When the Firebug team started making firebug.next, there were huge problems with the inbuilt dev-tools. We assume 'we know best' and that we know what a screen-reader user would want rather than reach out to anyone who is practically blind and ask them what they think. ![]() ordering the product and returning it, with all emails checked along the way, complete with physical packaging. I also have yet to see anyone offering accessibility audit services where a genuine, registered partially sighted person does the auditing and testing. The pitch should not be that hard given that the baby boomer generation have all the money and need spectacles to read anything closer than arms-length away. Nobody is talking about making the web better for everyone (which includes the customers with no accessibility problems) and that being the central plank of better sales.Ī further problem is that web 'design' agencies do not have the sales staff to sell accessibility. I find people still concerned with 'keyword frequency' and whether they have their H1 tags in the right place when it comes to 'SEO'. There is opportunity in this as SEO (a 'service' that can be sold) really depends on accessibility. It is deeply misunderstood across the 'industry'. So, IOW, I can't even file actionable bug reports for web apps without putting forth lots of effort to even identify the element that is at fault. Often, clicking Inspect Element from the context menu doesn't open the inspector with keyboard focus on the element I'm inspecting, either, which is a massive pain when I'm trying to tell a developer what is needed to make a site accessible. I've taken to using the context menu to copy an element's inner HTML into a text editor, then inspecting it that way. I can pull up a tree of elements, but sometimes I can expand tree levels from the keyboard and sometimes I can't. The entire developer tools interface is littered with these sorts of inconsistencies. I press Space on a button labeled "Start performance analysis" which immediately plunks focus into a text field from which I can't seem to escape. "Status", "Transferred", etc.) but I never reach a list of actual requests through which I can arrow. If I tab around on the display, I get a bunch of buttons that are likely column headers (I.e. Right, but opening from the keyboard is only a tiny fraction of what is needed. Firebug used to have this nailed, to the point where you could even enable an accessibility mode (though arguably accessibility mode should have just been the only mode.) And yes, I'd happily file issues for this and half a dozen other things, but at some point I actually have to do my job, and in this case that might mean jumping ship to a browser that seems more accessible. I'm glad that they're empowering developers to create accessible websites, but if blind/disabled developers were empowered to develop on equal footing, then that'd be another way to achieve the same goal.Īs one example, I can't navigate the network inspector via keyboard in any meaningful way. As a blind web developer running Linux and Orca, bunches of things have been broken for a very long time, to the point where I'm considering switching to ChromeOS and running Linux in chroots/containers just to get a better set of web development tools. I hope this means the developer tools themselves will actually become accessible.
0 Comments
Leave a Reply. |