<story><title>GitHub Releases Dark Mode</title><url>https://github.com/settings/appearance</url></story><parent_chain><item><author>userbinator</author><text>The fact that it used to work perfectly fine without JS is proof enough that it don&amp;#x27;t need it. But I guess the average web deviloper is more concerned with stuffing one&amp;#x27;s resume with the latest fads than &lt;i&gt;real&lt;/i&gt; accessibility and efficiency.</text></item><item><author>j-james</author><text>I would suppose the above user is referring, rather snidely, to GitHub not loading commit information without JavaScript. GitHub&amp;#x27;s JavaScript use is really quite minimal, and certainly nothing like GitLab.</text></item><item><author>viraptor</author><text>What are the actual issues? JS does not necessarily mean lack of accessibility on its own.</text></item><item><author>bluefox</author><text>GitHub have the gall talking about accessibility while flinging their octotentacles, dragging users screaming down to the firey pits of JavaScript hell.</text></item><item><author>da_big_ghey</author><text>I believe the CEO stated an intention to add more themes for, say, colorblind people, so there might be additional options coming.&lt;p&gt;Edit: Found the link.  &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;natfriedman&amp;#x2F;status&amp;#x2F;1330924323952091137&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;natfriedman&amp;#x2F;status&amp;#x2F;1330924323952091137&lt;/a&gt;</text></item><item><author>deadmik3</author><text>Nice to see but it&amp;#x27;s too contrast-y for me compared to the stylus theme I&amp;#x27;ve already been using which honestly looks better &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;StylishThemes&amp;#x2F;GitHub-Dark&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;StylishThemes&amp;#x2F;GitHub-Dark&lt;/a&gt;</text></item></parent_chain><comment><author>pkage</author><text>There&amp;#x27;s a lot of hostility on HN towards web developers. &amp;quot;Real accessibility&amp;quot; doesn&amp;#x27;t really have much to do with Javascript or not, it has everything to do with ensuring the site is screen reader accessible, ensuring the site is available for low-vision users, and ensuring that the site is available at slow bandwidths. Given that the site caters to those already (good kb navigation, stated future support for color-blindness, and the site is ~300kb&amp;#x2F;page) I think that they&amp;#x27;re in pretty good shape.&lt;p&gt;Ultimately, choosing not to run JS is your decision—but a vanishingly small percentage of users choose to do that, and as a company your focus is on providing features for the product, and not supporting every single user and their unique configurations. Should Github explicitly support terminal-based browsers like Lynx as well?&lt;p&gt;Plus, you can avoid 99% of the github website just by using git from the command line (or your favorite client) and using their CLI tool for repo creation&amp;#x2F;etc.</text></comment>
<story><title>GitHub Releases Dark Mode</title><url>https://github.com/settings/appearance</url></story><parent_chain><item><author>userbinator</author><text>The fact that it used to work perfectly fine without JS is proof enough that it don&amp;#x27;t need it. But I guess the average web deviloper is more concerned with stuffing one&amp;#x27;s resume with the latest fads than &lt;i&gt;real&lt;/i&gt; accessibility and efficiency.</text></item><item><author>j-james</author><text>I would suppose the above user is referring, rather snidely, to GitHub not loading commit information without JavaScript. GitHub&amp;#x27;s JavaScript use is really quite minimal, and certainly nothing like GitLab.</text></item><item><author>viraptor</author><text>What are the actual issues? JS does not necessarily mean lack of accessibility on its own.</text></item><item><author>bluefox</author><text>GitHub have the gall talking about accessibility while flinging their octotentacles, dragging users screaming down to the firey pits of JavaScript hell.</text></item><item><author>da_big_ghey</author><text>I believe the CEO stated an intention to add more themes for, say, colorblind people, so there might be additional options coming.&lt;p&gt;Edit: Found the link.  &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;natfriedman&amp;#x2F;status&amp;#x2F;1330924323952091137&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;natfriedman&amp;#x2F;status&amp;#x2F;1330924323952091137&lt;/a&gt;</text></item><item><author>deadmik3</author><text>Nice to see but it&amp;#x27;s too contrast-y for me compared to the stylus theme I&amp;#x27;ve already been using which honestly looks better &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;StylishThemes&amp;#x2F;GitHub-Dark&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;StylishThemes&amp;#x2F;GitHub-Dark&lt;/a&gt;</text></item></parent_chain><comment><author>viraptor</author><text>Please take a step back for a moment and imagine that you&amp;#x27;re one of the blind users of HN running into this comment. Reading that GitHub devs who took the time to actually support some assistive technology on their website (not sure how well, but see the existing aria attributes in the source) and track their support (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;government.github.com&amp;#x2F;accessibility&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;government.github.com&amp;#x2F;accessibility&amp;#x2F;&lt;/a&gt;) don&amp;#x27;t care about &amp;quot;real accessibility&amp;quot; by not catering to what technology choices you prefer.</text></comment>