- Add rationale-for-post and subsections to intro
- Expand on inclusivity-by-default in intro
- Mention that Can I Use is operated by a single person
- Describe parallels between Tor Browser security levels, iOS Lockdown,
and Edge's "enhanced" security mode.
- CSS containment was cutting off nested list-item markers; increase
their padding to compensate
- Remove nested <details> use, it was causing problems and was probably
unnecessary
- Add detailed information on targeting old browsers
- Move section on the Tor Browser after the aforementioned older-browser
section.
- Add cryptcheck, check-your-website
- Add document-policy to image-compression section to describe how to
enforce image compression.
- Link to ticket for opena11y eval library
- Minor clarification regarding Firefox a11y inspector: scrollable
elements in any direction will be interactive
- Update note on seirdy.one cache-control directives
- Add missing "Future users" section to gemtext version
- Updated outdated info on full-text feed sizes
- Spelling/typos
Make the SVG icon conform to the usvg spec, which is even more
restricted than the SVG Tiny Portable/Secure spec. It now works well in
NetSurf's "libsvgtiny" without weird glitches.
- Mention Ancienne TLS implementation for vintage computers
- Elaborate on contain-intrinsic-size being safer on long pages, and
explicitly mention scrollbar-jumping
- Grammar fixes
- Convert a long blurb of hard-to-follow text into bullet points
- Update dated info on this site having no breadcrumbs: it has
breadcrumbs now. Explain why.
- Allow long CC durations in webhint
- WH warns when load time is within a whole second of the target
load-time, so bump it up a little.
- Add a comment to the build manifest
The Tor hidden service does not use TLS, so it doesn't use HTTP/2 or
HTTP/3. Therefore, it can't use Brotli; statically-compressing Brotli
content is just wasted CPU cycles.
- Make xhtml and html alternates the same (we're polygot), cutting
static-compression time in half
- Make axe-ff run on local files, reducing some overhead.
- Run webhint in parallel with other site checks, right after the
deployment finishes
- Fix webhint perf budget (it warns when within 0.5 sec so give it a
0.5 sec buffer)
- Throttle LH a bit more
