> We have lists implemented like divs, navs like divs, lack of appropriate attributes, aria labels and few other things...Articles speaks about optimizing for performance but will still attempt to load 150kb of analytics library and doesn't handle fallback fonts and font rendering properly.
I'm not sure what you mean by 'lists implemented like divs'. My lists are good old <ul>/<ol>, as God intended.
The fallback fonts and font rendering are also implemented correctly AFAIK: we use a high-quality Adobe FLOSS font, we swap fonts for performance, and we have a full fontstack which falls back through all of it down through system to a last-resort.
The analytics is also super-useful for me. I use it all the time for finding broken links, discussions, making design choices about device screen size, etc. I do not regard it as wasted at all.
A lot of the WAVE stuff you refer to is things I neither can nor would fix, so gwern.net is never going to be the pinnacle of what you consider accessibility. While none of it is quite as stupid as when accessibility people were telling me to not use hyphens because screenreaders, 20+ years later, still are unable to delete soft hyphens (and this is somehow my fault and I should break hyphenation for 99% of readers), I raise my eyebrow at the claim that justified text is an accessibility problem; and when it flags PDFs, I can only shrug - yes, and I would like a pony too, but that ain't happening either.
I've switched the two navbar divs to <nav>s, and added a skip-to-content link. I also ran it through WAVE and fixed a few things. (I did a long time ago but there's been a lot of changes since then. I've added a cron job to check it again every few months.)
> The dialog popups also lack the same usability, they would benefit of clearer aria-labels on the links.
I'm not sure what you mean by 'lists implemented like divs'. My lists are good old <ul>/<ol>, as God intended. The fallback fonts and font rendering are also implemented correctly AFAIK: we use a high-quality Adobe FLOSS font, we swap fonts for performance, and we have a full fontstack which falls back through all of it down through system to a last-resort. The analytics is also super-useful for me. I use it all the time for finding broken links, discussions, making design choices about device screen size, etc. I do not regard it as wasted at all. A lot of the WAVE stuff you refer to is things I neither can nor would fix, so gwern.net is never going to be the pinnacle of what you consider accessibility. While none of it is quite as stupid as when accessibility people were telling me to not use hyphens because screenreaders, 20+ years later, still are unable to delete soft hyphens (and this is somehow my fault and I should break hyphenation for 99% of readers), I raise my eyebrow at the claim that justified text is an accessibility problem; and when it flags PDFs, I can only shrug - yes, and I would like a pony too, but that ain't happening either.
I've switched the two navbar divs to <nav>s, and added a skip-to-content link. I also ran it through WAVE and fixed a few things. (I did a long time ago but there's been a lot of changes since then. I've added a cron job to check it again every few months.)
> The dialog popups also lack the same usability, they would benefit of clearer aria-labels on the links.
Which aria-labels? There's a ton of them.