Atkinson Hyperlegible Font
brailleinstitute.org
brailleinstitute.org
Atkinson Hyperlegible Font - https://news.ycombinator.com/item?id=32799872 - Sept 2022 (234 comments)
Atkinson Hyperlegible – a font by the Braille Institute designed for legibility - https://news.ycombinator.com/item?id=28010540 - July 2021 (1 comment)
Atkinson Hyperlegible Font - https://news.ycombinator.com/item?id=26011945 - Feb 2021 (86 comments)
Atkinson Hyperlegible Font - https://news.ycombinator.com/item?id=25154417 - Nov 2020 (10 comments)
Atkinson Hyperlegible Font - https://news.ycombinator.com/item?id=24853550 - Oct 2020 (3 comments)
There have been other similar suggestions i.e. when filling the information for a new submission to have an automatic duplicate search and produce a warning, but I've come to understand that adding features to the simple/lean HN page is not desired. Same goes for native dark mode (with having to load scripts/plugins/whatever).
I can understand Feature Creep (https://en.wikipedia.org/wiki/Feature_creep) fears, but it seems that here we're doing the exact opposite :-)
Screenshot: https://www.imgpaste.net/image/SDoBg6
[0] https://chromewebstore.google.com/detail/refined-hacker-news...
[1] https://addons.mozilla.org/en-US/firefox/addon/refined-hacke...
P.S.: I choose to believe the neurons that instinctively throw up "but what if it's actually bad" represents a useful software design skill, rather than just a personality flaw. :p
https://fonts.google.com/specimen/Atkinson+Hyperlegible?prev...
https://fonts.google.com/specimen/Inconsolata?preview.text=0...
most importantly it's to differentiate it from ∅, mathematical null set.
"computer people" feel this understandable need to differentiate their zeroes, but "CS-is-math people" are like "but don't use null set!" <— ᵇᵘᵗ ʸᵒᵘ ʲᵘˢᵗ ᵘˢᵉᵈ ᶠᵃᶜᵗᵒʳᶦᵃˡ
lol no.
(also like the German commenter the null set is an empty set = {}, I only encountered ⌀ as diameter symbol, actually)
DejaVu Sans Mono does not look anywhere near as good as Lucida Sans which is LibreOffice Calc's default for me, comparing just the numerals. The digits in this variable pitch font are fixed pitch so it's suitable for spreadsheets.
(I mentioned the extra marking on zeros in the spirit of the thread, but personally I don't care about it, I'm not mixing up letters and digits much irl or especially in a spreadsheet.)
but in any case, the DejaVu Sans Mono glyphs rise up above the baseline, floating in the cells, and they are larger for a given pointsize. I don't know whose fault this is, but my complaint is that every time I try to look at different fonts, the futz-around-and-find-out factor is so great it's just a waste of time. It's a problem across systems (windows, linux, mac), across generations (Motif, 3.1) it's a problem across apps, it's just a problem that's completely unnecessary. I think font people spend too much time looking at their font on a tabula rasa wedding invite, and not enough time doing comparative font selection in ordinary apps.
If that's true then AH's choice seems counterintuitive to me.
https://fonts.google.com/specimen/Atkinson+Hyperlegible?prev...
I think it’s a fairly elegant solution at the slight cost of being a little unfamiliar (although the slashed zero itself is quite unfamiliar to most people).
You don't have long texts on slides, and everything is very distinct. I find it especially helpful, as many setups where one presents can be suboptimal (e.g., bad lighting, obstructed views, warped surface that is projected on, …). Which is where this font shines not only for people with impaired vision, but for everyone.
They are also all ever so slightly out of focus. Or dust on the lens. Or projecting on an orange peel wall instead of a screen.
I’m curious how things have improved in let’s say the last ten years. Still hot garbage?
More brightness/better contrast is probably the more important feature for university applications as it allows you to see stuff better even if we are not in a black-walled darkened cinema space.
Everything in 4k with decent colors and high brightness costs a fortune.
But a DCI conform 4k Laser projector is really a view to behold. If only it wasn't so damn expensive.
Either way most universities only feel compelled to spend money when something breaks. I wish that was different, as it makes my job very stressful at times, especially when multiple things break within a small time span.
Writing as I do from inside an organisation where the standard seems to be to communicate through meetings where someone reads out the text on a powerpoint slide, I can say that this is nothing if not optimistic.
Doesn't change my other points through ;)
At first glance for me it really seemed like its a font strait out of a elementary grade level textbook. Maybe its the website layout, maybe its that the font is huge and spaced the same, I'm not sure.
As far as easier to read, I am on the fence versus monospaced computer fonts if its any better or not. I wonder what their research behind this is but the website started to bug me so I didnt dig deeper personally
And I do find Atkinson hyperlegible more … legible. Not life changing since my vision is still ok and I’m still young.
And I find it interesting because with my mix of conditions, my issues aren’t seeing clearly (I see clearly with my glasses) but eye strain. I can have a day where I see clearly in the morning and blurry at night. Anything that reduces this strain changes my life. And, maybe it’s placebo, but I feel like this font helps.
If some font, color, or UI feature provides 1-5% improvement, it's huge because it accumulates over long term, but it's hard to notice immediately.
It doesn't really help you while reading that capital letter i looks different. You have to (1) know which font you're currently reading and (2) know that a straight bar isn't a capital i.
This is kind aggregated by the fact that I'd naturally assume if only one letter looked like that it would be capital letter i. An assumption that is backed by this very website: I, l
Unlike Comic Mono it is a paid font, but I find it a lot nicer to use/read.
EDIT: the font the website uses, not comic-code
Most attempts at making a font try to make all that stuff as regular as possible, even the one in the article we're discussing does this.
https://braileinstitute.app.box.com/s/rin3vzegmcy7sil28yfqsl...
If they want the OFL, then use the OFL. Don't make me try to understand yet another licence; I'm not a lawyer.
Was it really necessary to replace "Original or Modified Versions" with "The Original Version or Modified Version", or "Reserved Font Name(s)" with "Reserved Typeface Name"? So necessary that you're willing to sacrifice potential reuse?
Kinda too bad they don't just state which license they're aiming for.
You gotta be joking.
Maybe it really is a bug on Safari's part but creating custom zip archives is something which would be far saner to do on the server side in the first place.
Iosevka: https://typeof.net/Iosevka
"Hypersevka" build plans: https://github.com/jdknezek/Iosevka/blob/jdk/scripts/hyperse...
Screenshots: https://imgur.com/7BZS3Pp https://imgur.com/sudNqWM
I have my own builds -- not based on AH's glyph choices, but also chosen to minimize glyph ambiguity.
I'll mention another great legible monospace project: 0xProto
---
Build: https://github.com/AndydeCleyre/archbuilder_iosevka/releases...
Screenshot Mono: https://cdn.imgchest.com/files/k46acrxl297.png
Screenshot Mono with syntax highlighting: https://cdn.imgchest.com/files/l4nec9d8lm4.png
Screenshot Proportional: https://cdn.imgchest.com/files/6yxkce8p6a7.png
0xProto: https://github.com/0xType/0xProto
- semi-extended
- extended
- extra-extended
- ultra-extended
I think by default the extended variant is included in most builds anyway, if you want to try it.
FWIW here's a sample of my usual build's extended variant: https://cdn.imgchest.com/files/b49zcjd53oy.png
* Intel Commit.
* I am currently using Maple Mono.
- the zero must have a mark - the base of the lower case L must go to the right and not the left, for better distinction from the number one
I just tried to half-ass a similar test by editing the Google Font explorer UI to put them next to each other. Atkinson beats out Verdana for width, by about 4% (eyeballed and envelope math), however it's also 1 pixel taller per line at that size. So it's a more rectangular font. I'd have to think about how I'd want to use it, if I care more about lines per page or characters per column.
It backs what you say!
Do you have any handy links around this? I've a passing interest in information-dense UIs and font choice is a vital but often overlooked aspect of such interfaces. Would love to see how others evaluate such things.
It's only a "nice-to-have" font.
I have an OG mac.com email, and some woman used it to sign a donation to ASPCA, a number of years ago.
They then sold it to some liberal group, who then sold it to some ultra-liberal group.
I get dozens of extreme-left emails, every day. It's crazy.
I'm not extreme anything, and want to puke, just reading the subject lines (for the record, the extreme-right is an even more effective emetic).
I would be interested (but not really that interested) in finding out who these folks would sell my email to.
I suspect that would be true of Arial, even! This has been my goal for some time, but no browser has such an option. (You can change the default font, but almost no website leaves it set to default, so it does nothing.)
A few ligatures do have their own unicode code points, e.g. ffi, so the browser knows what is intended independent of the font. The ligatures used by icon fonts do not have their own code points.
Most icon fonts use private-use codepoints, not ligatures. These codepoints have no standard glyph, so disabling site-specific fonts will make those characters fail to render at all or display placeholder characters (e.g. �).
Thankfully, icon fonts are declining rapidly in usage - SVG icons are superior for most use cases.
> A few ligatures do have their own unicode code points, e.g. ffi, so the browser knows what is intended.
The precomposed ligature codepoints (e.g. U+FB00-FB06) only exist for compatibility with legacy encodings which included similar characters. They shouldn't be used in new documents. If you want text on a web page to use ligatures, use the CSS font-variant-ligatures property to control which ones are used. (And make sure to disable them on monospaced text!)
It does add a bit of performance gain not loading the fonts, and it may be a small security improvement, but if the goal was usability/readability that seems like a huge miss.
Add to that, this feature also needs to be understandable for non-technical people who might never have view a page source in their lives.
Much as a granular system would be more powerful and preferable for the HN community, having a dumb toggle makes a lot more sense from Firefox’s perspective.
This would be helpful for icon fonts, but also for user preferred fonts that don't cover all language character sets.
Apologies if I’ve completely misunderstood your comments
I wouldn’t be so sure about that. Resources like FontAwesome are still used heavily in VuePress and similar documentation generators.
edit: it may not be SVGs themselves. The icons on that site are repeated and I would reach for an SVG sprite that can be reused, I ran into issues with that working cross browser in XSLT - Firefox was actually the problem if I'm not mistaken.
Agreed.
It seems to improve legibility. I'm not so sure it improve readability.
Readability is largely influenced by the x-height (height of lowercase letter), because your brain is trying to discern the "shape" of a word - which allows you to read faster. Hence why ALL CAPS is difficult to read because the word shape is the same.
Atkinson appears to have a high x-height, which reduces readability.
OpenDyslexic [2] is another interesting font. I've heard that asymmetry helps dyslexic readers, and (given a cursory glance) they seem to have done a good job having asymmetry and style. I've also heard that SIL's font is helpful for dyslexics, but that was a while back and now they have multiple font styles, so I'm not sure if the one above is the one or not.
I didn't realize this until I worked on some software for dyslexic readers, but the normal computer font makes bdpq look pretty much identical except for rotation. It has a minimalist elegance, but for new/foreign readers, it's pretty subtle. I remember learning Chinese and had to spend quite some time with two characters, which differed only with one have a dot and one a short vertical line at top (a dot looks pretty similar to a vertical line at a cursory glance, as it is more inverted teardrop shape than a circle). After that the western alphabet looked a lot more uniform than I'd originally thought.
[1] https://software.sil.org/andika/andika-and-the-visually-impa...
Additionally "I" and "l" look way too similar.
So I think "Unambiguous Letterforms" in this case not necessarily true.
https://fonts.google.com/specimen/Atkinson+Hyperlegible/test...
Yikes, not a strong design IMO. I know very little about dyslexia, but reading individual words as a small child doesn’t seem like a comprehensive way to measure “how dyslexic people read.”
Presumably the primary envisioned use-case for a specialized typeface like this is paragraphs of text, read by people who have the language skills to ”think in paragraphs,” even if the visual processing is a challenge.
This is all armchair, I’d welcome correction or nuance.
When I was at the ages of the sample, my lexile scores were through the roof, compared to the sample here which has poor to middling reading ability (typical for dyslexia) — i do not have dyslexia but still feels like OpenDyslexic makes it easier to read.
The data in the study does not support your conclusion that it “actually is worse”, unless i missed something in my interpretation? It seems to be a wash.
This smaller N=3 study supports the efficacy of OpenDyslexic, using _actual reading tasks_ instead of the more artificial task in the study you provided: https://dergipark.org.tr/en/pub/tayjournal/issue/76493/11524...
There's no source
So-called "UI/UX" designer are making a lot of fancy work to make things illegible. Contrast between background (aka "paper") and foreground (aka "ink") is going down and down. So, no matter the font of choice, text is becoming less readable (and less relevant) also because of color choices. While video and audio contents is getting more and more attention.
For example when I first saw this new CV I thought, "that's really easy on the eyes".
You add a 1 pixel radius, zero offset 70% opacity white shadow to dark text, or the same shadow in black to inverse (light) text, and the letters pop without the shadow being noticeable except under zoom. The page takes a little bit longer to render, but at least you can read it despite the designer’s attempt to sabotage basic UX principles.
The translucency makes it work on other colors as well, if you have color coded labels for instance, like a dark blue bar with grey text.
[1]: https://github.com/jdknezek/Iosevka/blob/jdk/scripts/hyperse...
And here's an action shot: https://imgur.com/sudNqWM
Yours actually looks a bit more readable than mine, gonna check it out your build plan.
Thanks!
Gives credence that they do take it seriously.
I was thinking about how I'd fix it if it were an issue. A person who doesn't have enough visual acuity to see the distinctness of the glyphs might still want to understand the specific examples of normally-ambiguous glyphs. I came up with this, but it still isn't the best and probably breaks expectations:
<style type="text/css">
.sr-only {
border: 0 !important;
clip: rect(1px, 1px, 1px, 1px) !important;
-webkit-clip-path: inset(50%) !important;
clip-path: inset(50%) !important;
height: 1px !important;
overflow: hidden !important;
margin: -1px !important;
padding: 0 !important;
position: absolute !important;
width: 1px !important;
white-space: nowrap !important;
}
</style>
<figure>
<div>
<span class="sr-only">(distinct glyphs)</span>B8<span class="sr-only">(out of distinct glyphs)</span>
<span aria-hidden="true"> </span>
<span class="sr-only">(distinct glyphs)</span>O0<span class="sr-only">(out of distinct glyphs)</span>
</div>
<figcaption>
<strong>Unambiguous Letterforms<span class="sr-only">:</span></strong><br> Letters have received special care to ensure they’re legible and clear.
</figcaption>
</figure>
[0]: https://en.wikipedia.org/wiki/Mojibakehttps://github.com/polarsys/b612/issues/20#issuecomment-5448...
To answer the grandparent, unslashed 0s are used in numerical figures (speed, pressure) while slashed 0s are reserved for the alphanumeric figures (headings and other idenitifers)
So, "slashed in strings even if non-alpha, but non-slashed in numerics, and times are strings"? Seems viable enough, but I'd choose consistency instead. :)
I still think its a good step forward.
however: when I am in a spreadsheet, trying to choose a typeface & font for one column, my goal is NEVER to suddenly expand either the width, or the height, or the amount of hover over the baseline, or fabulous quantities of descender or ascender, or linespacing or i-don't-know,-you-tell-me-the-terminology, I don't want your typeface to shockingly change its alignment to all the other text I have
and that includes "oh, just select a different pointsize"; if things are the same pointsize, then they should be able to sit next to one another; I know it's not your fault, but you know whose fault it really really isn't? MINE
I really want to use your typefaces; don't make it so hard
Now of every font would do equal spacing (something that your spreadsheet software could just implement, btw.) what would the point be of having different fonts?
As you are running the system ypu could also just make a selection of particularily equal fonts and remove the rest, if that annoys you.