3 ms·

This is cool. I wish this sort of analysis existed for many major websites! The reason I think this would be useful is the accessibility of the results - we'd b

This is cool. I wish this sort of analysis existed for many major websites! The reason I think this would be useful is the accessibility of the results - we'd be able to consider the various analytics within the context of something highly familiar (the mention of Slack still using "text/..." is one such example). Although... hmm, maybe I don't want all websites scored. Arc (ie, HN) would probably rank 0.5/10 in terms of technical design (I begrudgingly admit the Spartan UI could be worse). Upvoting is done by creating an empty image then loading it - but the "hide" link uses XHR, so that's a bit inconsistent; the layout is based on tables... and still uses the old 1x1px spacer image trick for padding!!1; there's absolutely no ARIA to be found anywhere, so I wonder what screen-readers think of it (a valid consideration, I've read comments by blind users here); and the Firebase API is read-only and doesn't permit posting/interaction, so if I want to make a 3rd-party app, I'd have to ask users for their passwords. That works for app storage but localStorage is neither encrypted or "reasonably resilient", so that won't work in a Web framework demo context. I have a lot of reluctance to give out my HN password in a world of OAuth2, all the more when I consider that HN is regarded more highly than other communities such as reddit, twitter, etc. I think this could explain why most 3rd-party HN demo apps don't allow posting, and it's sad. Incentive to make own, better website intensifies And I'll make a note of this person, and ask them what they think of it when it's live.

redmaniack 8y ago
Glad you found it interesting. I enjoy to dig into this kind of analysis stuff from time to time: A while ago I made an HTML study on around 8 million web pages: https://www.advancedwebranking.com/html/ https://www.advancedwebranking.com/html/ Also, I wrote about this journey on CSS-Tricks: 1. https://css-tricks.com/average-web-page-data-analyzing-8-million-websites/ https://css-tricks.com/average-web-page-data-analyzing-8-mil... 2. https://css-tricks.com/random-interesting-facts-htmlsvg-usage/ https://css-tricks.com/random-interesting-facts-htmlsvg-usag... On accessibility, I'd have loved to try out some screen readers but at the moment I write this article, I thought this accessibility analysis would deserve its own separate topic/article. A11Y is always hard. https://catalin.red/thoughts-on-accessibility/ https://catalin.red/thoughts-on-accessibility/ Sorry for all these plugs.
- exikyut 8y ago
  The plugs are cool, thanks! :) The 8 million webpage one was really interesting. I don't know why yet though. (I'm serious - I know this info will come in hand for figuring something out one day. Thanks.) TIL about [aria-hidden] from "HTML/SVG usage"/"Hiding DOM elements"! I wonder what the raw stats on display:none vs visibility:hidden are (especially considering that they have different effects). I wouldn't have expected 117000 webpages (is this a discrete page count or a website count?!) to use the highly specific ".visuallyhidden"... oh it's part of the HTML5Boilerplate framework, that explains it. The main issue with screen readers is that, AFAIK, JAWS doesn't offer a developer-access program! Or if it does, I've never heard of it. A LOT of people still use JAWS, AFAIK, in spite of the newer offerings out there. The main difficulty here is the differing-client-behavior problem, although NVDA and ChromeVox's free-ness are surely shifting the usage share (something I've wondered about for a while).

redmaniack 8y ago

Glad you found it interesting. I enjoy to dig into this kind of analysis stuff from time to time: A while ago I made an HTML study on around 8 million web pages: https://www.advancedwebranking.com/html/ https://www.advancedwebranking.com/html/ Also, I wrote about this journey on CSS-Tricks: 1. https://css-tricks.com/average-web-page-data-analyzing-8-million-websites/ https://css-tricks.com/average-web-page-data-analyzing-8-mil... 2. https://css-tricks.com/random-interesting-facts-htmlsvg-usage/ https://css-tricks.com/random-interesting-facts-htmlsvg-usag... On accessibility, I'd have loved to try out some screen readers but at the moment I write this article, I thought this accessibility analysis would deserve its own separate topic/article. A11Y is always hard. https://catalin.red/thoughts-on-accessibility/ https://catalin.red/thoughts-on-accessibility/ Sorry for all these plugs.

exikyut 8y ago
The plugs are cool, thanks! :) The 8 million webpage one was really interesting. I don't know why yet though. (I'm serious - I know this info will come in hand for figuring something out one day. Thanks.) TIL about [aria-hidden] from "HTML/SVG usage"/"Hiding DOM elements"! I wonder what the raw stats on display:none vs visibility:hidden are (especially considering that they have different effects). I wouldn't have expected 117000 webpages (is this a discrete page count or a website count?!) to use the highly specific ".visuallyhidden"... oh it's part of the HTML5Boilerplate framework, that explains it. The main issue with screen readers is that, AFAIK, JAWS doesn't offer a developer-access program! Or if it does, I've never heard of it. A LOT of people still use JAWS, AFAIK, in spite of the newer offerings out there. The main difficulty here is the differing-client-behavior problem, although NVDA and ChromeVox's free-ness are surely shifting the usage share (something I've wondered about for a while).