> find / -type f
SITEMAP
Every page here, and where the site stands on accessibility.
Pages
- Index the archive, most recent first
- Whoami who is writing and why
- Tags every tag, with counts
- Cal every post by the day it went up
- Credits third-party work and its licences
- Privacy what this site collects, which is nothing
- Sitemap this page
Machine-readable
- Feed RSS, full text, every post
- sitemap.xml the same archive for crawlers
- llms.txt what this site is, for a reader without a browser
- robots.txt nothing is disallowed
- humans.txt who made it and what with
- security.txtwhere to send a security report
Posts
- What the model can't see25 August 2026
- First transmission14 August 2026
- A one-pixel image was a layout engine11 August 2026
- Nothing on the web is ever removed8 August 2026
- Cascade layers settled an argument from 19984 August 2026
- It was never the bundle29 July 2026
- Every framework is a bet about what stays the same22 July 2026
- Word of mouth is doing all the work15 June 2026
- Nobody can tell you what the tech debt costs13 April 2026
- Most code only needs to work16 February 2026
- The complexity is not new, it is just visible12 January 2026
- A sale is worth more than a thousand upvotes20 December 2025
- Public wealth is the kind that makes you happy13 December 2025
- You will write a framework whether you meant to or not21 September 2025
- Your degree stops mattering after about ten years19 October 2024
- Going to a website for the content is nostalgia13 July 2024
- No app needs a good UI until it has a rival6 April 2024
- The first memo already had applications in it8 November 2023
- Tailwind does not save you from CSS23 August 2023
- High quality code comes much later10 May 2023
- Defaulting to the office is giving up3 May 2023
- That behaviour is on you15 March 2023
- You cannot cargo cult the layoffs24 November 2022
- You are not in their thoughts at all12 October 2022
- React is not the code that gets bundled10 August 2022
- Most apps are doing nothing most of the time3 August 2022
- Employers do not care what you did at the weekend12 May 2022
- Your salary is somebody's lost profit11 March 2022
- Comfort takes away the need14 December 2021
- Most of the data you collect is a web counter7 December 2021
- Leeching off the system is not a skill30 November 2021
- Incompetence is not an explanation7 September 2021
- The design decisions get made either way20 April 2021
- Nothing makes you write the next one19 January 2021
- Market rate is the median of bad negotiators29 September 2020
- Your app is not slow because of the framework21 April 2020
- Your old workflow was fine because nothing broke14 April 2020
- Nothing in the stack is as new as it looks7 April 2020
- A NodeList is not an HTMLCollection25 February 2020
- You do not need to know how big the screen is14 January 2020
- Most people choose to work anyway21 December 2019
- Most of it was never private2 July 2019
- A proxy test measures the proxy18 June 2019
- A web page was never a document11 June 2019
- There is a ceiling on subscriptions5 March 2019
- Harmful is not the same as offensive11 February 2019
- Sell it before it is ready11 September 2018
- Almost none of it runs on your machine21 May 2018
- The reason you published it shows in the code27 March 2018
- Some problems are not nails5 February 2018
- Nobody is reading your GitHub29 January 2018
- A library is its documentation30 December 2017
- A hackathon is the worst parts of the job, unpaid30 July 2017
- Most people cannot afford the good idea4 June 2017
- The default is the lever23 April 2017
- No because is easier than yes if19 February 2017
Tags
Accessibility
The page you land on is the accessible one. It aims to meetWCAG 2.2 Level AA with no known failures, and it also meets four Level AAA criteria: contrast at 7:1, targets at 44 by 44 pixels, a choice of light or dark ground with larger type, and no content that changes without being asked to. Contrast, reflow, text spacing, keyboard operation, focus visibility and page structure have all been measured rather than assumed.
2.2 rather than 2.1 because that is the versionEN 301 549and the European Accessibility Act now point at. The six criteria 2.2 added were checked one at a time rather than assumed to carry over:
- 2.4.11 Focus Not Obscured — this one failed. The header is sticky, and the browser scrolls a newly focused element to the top of the window, which put it underneath. Anything reached by tabbing backwards, or by following a link to a #fragment, arrived hidden. Fixed with scroll padding measured from the header itself.
- 2.5.8 Target Size — controls are 44 square in this presentation. In the enhanced one the tag badges are 19 tall, which is under the 24 the criterion asks for, and they meet it through the spacing exception instead: no two are close enough for their 24-pixel circles to touch. Measured at both wide and phone widths.
- 2.5.7 Dragging Movements — nothing here is dragged.
- 3.2.6 Consistent Help, 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication — no help mechanism, no multi-step process and no accounts, so there is nothing for these to apply to. They are satisfied by absence, which is worth saying plainly rather than counting as a pass.
That is the default rather than an alternate you have to find, which is the whole argument: the version that works for the most people is the one nobody has to ask for.
The Progressive switch in the header turns on the enhanced presentation — the shader, the glow, the scanlines and the motion. It carries the same content and the same functionality, and it aims at Level AA rather than the four AAA criteria above, since neon on black does not reach 7:1 and the animation is content that moves without being asked. An Effects switch appears alongside it for turning the motion down without giving up the look.
Known exceptions at Level AAA
Two criteria are not met in either presentation, and both are about the writing rather than the display, so no switch can satisfy them:
- 3.1.3 Unusual Words — the posts use technical vocabulary without a glossary to define it.
- 3.1.5 Reading Level — the posts assume reading ability beyond lower secondary education and carry no plain-language summary.
Both are fixable by writing rather than by code, and neither is claimed.
If something here does not work
A conformance claim is a claim, and the useful thing to do with one is contradict it. If any part of this site is hard to use — with a screen reader, a keyboard, magnification, a stylesheet of your own, or none of those — it is worth reporting, and there is somewhere to report it:
- github.com/onion2k/hackooers/issues — the issue tracker for this site, which is read.
Say what you were using and what happened. There is no form to fill in and no reference number.
Statement last reviewed against the site on 28 August 2026, by testing rather than by re-reading it.