Where the Disabled Button Got Its Rule
Comments on “Where the Disabled Button Got Its Rule”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
hipuku traces the disabled button's rule to Apple's 1980 Lisa interface standard, which let a dimmed menu item still be invoked. By the 1983 LisaDraw manual and the Mac's Inside Macintosh, dimmed meant unchoosable, and HTML 4 carried that into buttons. Across eight design systems, disabled labels measure 1.36:1 to 3.35:1 contrast, and Primer, Atlassian and GOV.UK advise avoiding the state. Material and Primer now offer reachable variants so users can be told why. Most historical and contrast claims could not be independently checked.
Why it ranked
No. 16 of 62 with a score of 0.62. The panel rated it highest on new information (0.89) and substantiated (0.84), lowest on significance (0.46). Placed No. 16, No. 26 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Well-researched history of disabled buttons tracing to Apple Lisa menu rules, with direct design-system comparisons and practical accessibility guidance; niche for builders, not a landmark, and not in the recent stories list.}
- AI judgeJudge 3gpt-5.6-luna
- A well-supported historical and comparative analysis of disabled-button behavior, accessibility, HTML, ARIA, and major design systems. It offers actionable design guidance, though its impact is mainly concentrated among frontend and product-design practitioners.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.62total under rubric v2.3
- Significance0.46
- Reader interest0.67
- Audience breadth0.64
- Practical relevance0.70
- Substantiated0.84
- Technical depth0.73
- New information0.89
- Counts against: Promotional0.04
- Counts against: Overclaim0.19
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.47 | 0.30 | 0.62 | 0.46 | 0.32 | +0.24 | +0.111 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.56 | 0.60 | 0.86 | 0.67 | 0.30 | +0.26 | +0.175 |
| Audience breadthHow many people who build technology does it concern? | 0.71 | 0.50 | 0.70 | 0.64 | 0.21 | +0.13 | +0.083 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.72 | 0.60 | 0.78 | 0.70 | 0.18 | +0.22 | +0.154 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.94 | 0.70 | 0.88 | 0.84 | 0.24 | +0.05 | +0.042 |
| Technical depthHow technically substantive is it? | 0.92 | 0.60 | 0.68 | 0.73 | 0.32 | +0.05 | +0.037 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.92 | 0.80 | 0.96 | 0.89 | 0.16 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.05 | 0.05 | 0.01 | 0.04 | 0.04 | −0.19 | −0.007 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.24 | 0.20 | 0.12 | 0.19 | 0.12 | −0.11 | −0.021 |
| Sum of contributions | +0.619 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.619 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-15/16/"><img src="https://rubric.hrih.si/badge/2026-11-15/16.svg" alt="Ranked #16 on Rubric, 15 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 3 no source given · 4 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkDate
The Lisa User Interface Standards, an internal document signed by Bill Atkinson, was written in September 1980.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The Lisa team wrote down its interface rules in September 1980, more than two years before the computer was announced”
The source says No passage could be compared.
Source cited by the article: guidebookgallery.org/articles/lisauserinterfacestandards
Couldn’t checkQuote
Section 26 of the Lisa standard allowed dimming a command that would have no effect, and said such an item could still be invoked anyway if the user wished.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Such an item can be invoked anyway, if the user wishes”
The source says No passage could be compared.
Source cited by the article: guidebookgallery.org/articles/lisauserinterfacestandards
No source givenQuote
The LisaDraw manual (1983), page A9, states that a dim menu item cannot be chosen.
The article gives no link or citation for it.
The article says “Note: When a menu item is dim, you can't choose it”
The source says No source to compare with.
Couldn’t checkQuote
Inside Macintosh (1985) says a disabled menu item cannot be chosen and appears dimmed without highlighting on hover.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “A disabled item cannot be chosen; it appears dimmed in the menu and is not highlighted when the cursor moves over it”
The source says No passage could be compared.
Source cited by the article: spinsidemacintosh.neocities.org/im202
Matches sourceQuote
The HTML 4 specification, published in 1997, says disabled controls do not receive focus and are skipped in tabbing navigation.
The cited source says the same thing.
The article says “Disabled controls do not receive focus.” “Disabled controls are skipped in tabbing navigation”
The source says “Disabled controls do not receive focus . - Disabled controls are skipped in tabbing navigation . - Disabled controls cannot be successful”
Source cited by the article: w3.org/TR/html401/interact/forms.html
Couldn’t checkDate
Shopify's Polaris adopted the aria-disabled plus tabindex=-1 pattern for disabled buttons in 2022.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Shopify adopted this pattern in 2022”
The source says No passage could be compared.
Source cited by the article: github.com/Shopify/polaris-react/pull/7760
No source givenNumber
Across the eight design systems, the disabled button label has contrast between 1.36:1 and 3.35:1 against its button.
The article gives no link or citation for it.
The article says “A disabled label in these systems sits between 1.36:1 and 3.35:1 against its button”
The source says No source to compare with.
No source givenGeneralization
Primer, Atlassian and GOV.UK have written guidance recommending that teams avoid disabled buttons.
The article gives no link or citation for it.
The article says “Primer, Atlassian and GOV.UK also have written guidance recommending that teams avoid it”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:46 UTC. It played no part in the ranking.