<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>extra88</author><text>Marco Zehe is an Accessibility QA Engineer at Mozilla, he is blind, and he writes on his own site. Two years ago, he wrote a post, &amp;quot;The Firefox developer tools Inspector Panel is becoming accessible&amp;quot; [0]. I don&amp;#x27;t know how things have progressed since then and I wonder if there are problems particular to Firefox on Linux and Orca, as opposed to other combinations like Firefox for Windows with JAWS or NVDA.&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.marcozehe.de&amp;#x2F;2016&amp;#x2F;05&amp;#x2F;24&amp;#x2F;the-firefox-developer-tools-inspector-panel-is-becoming-accessible&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.marcozehe.de&amp;#x2F;2016&amp;#x2F;05&amp;#x2F;24&amp;#x2F;the-firefox-developer-to...&lt;/a&gt;</text><parent_chain><item><author>ndarilek</author><text>I hope this means the developer tools &lt;i&gt;themselves&lt;/i&gt; will actually become accessible. 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&amp;#x27;m considering switching to ChromeOS and running Linux in chroots&amp;#x2F;containers just to get a better set of web development tools. I&amp;#x27;m glad that they&amp;#x27;re empowering developers to create accessible websites, but if blind&amp;#x2F;disabled developers were empowered to &lt;i&gt;develop&lt;/i&gt; on equal footing, then that&amp;#x27;d be another way to achieve the same goal.&lt;p&gt;As one example, I can&amp;#x27;t navigate the network inspector via keyboard in any meaningful way. 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 &lt;i&gt;only&lt;/i&gt; mode.) And yes, I&amp;#x27;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.</text></item></parent_chain></comment><story><title>Firefox Developer Tools: Accessibility inspector</title><url>https://developer.mozilla.org/en-US/docs/Tools/Accessibility_inspector</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>kps</author><text>Documentation, too. Most of MDN, ironically including this article, violates Web Content Accessibility Guidelines.</text><parent_chain><item><author>ndarilek</author><text>I hope this means the developer tools &lt;i&gt;themselves&lt;/i&gt; will actually become accessible. 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&amp;#x27;m considering switching to ChromeOS and running Linux in chroots&amp;#x2F;containers just to get a better set of web development tools. I&amp;#x27;m glad that they&amp;#x27;re empowering developers to create accessible websites, but if blind&amp;#x2F;disabled developers were empowered to &lt;i&gt;develop&lt;/i&gt; on equal footing, then that&amp;#x27;d be another way to achieve the same goal.&lt;p&gt;As one example, I can&amp;#x27;t navigate the network inspector via keyboard in any meaningful way. 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 &lt;i&gt;only&lt;/i&gt; mode.) And yes, I&amp;#x27;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.</text></item></parent_chain></comment><story><title>Firefox Developer Tools: Accessibility inspector</title><url>https://developer.mozilla.org/en-US/docs/Tools/Accessibility_inspector</url></story>