I need feedback from sighted people about the website for my open-source project.
Here's the current version, using a third-party theme; I know the typography on the home page has problems: https://accesskit.dev/
And here's my proposed new version, using a minimalist template and CSS derived from an existing site (I stripped it down quite a bit): https://preview.accesskit.dev/
My main collaborator says the new appearance is from a past era. What do you think? Is it off-putting?
@matt
Aesthetically, the site is bland in a pleasing way. This is a page that’s here to convey information, and makes that information easy to read.
I really appreciate that it appears to respect my browser’s default font size.
The h2 and h3 headings are hard to visually distinguish. It looked at first glance as though “Rust” was a new section after (instead of under) “Getting Started.”
@inthehands Ugh. If the h2 and h3 styles are hard to distinguish, that's arguably the browser's fault. But if all the browsers have that problem, e.g. because they're all keeping slavish compatibility with something Netscape did in 1994, then maybe that's on me to fix.
@matt
It’s a tough call, and I’ve struggled with it too. I think ultimately it is on us to fix, though philosophically I don’t love that conclusion.
I suspect part of the problem on this page is that the h3 headings are very short, which makes the font size difference less apparent.
One solution that works well on this page to my eye is to indent the h3 and add a bullet:
h3:before {
content: '•';
color: gray;
margin-right: 1ex;
}
(Maybe bad for screen readers though?)
@inthehands All right, now I'm experimenting with putting the three subsections under "Getting started" into an actual HTML unordered list. That kind of nesting is completely valid IIUC, and screen readers can handle it just fine. And, I guess, it's actually better structured this way.
@inthehands Well, I got some negative feedback about putting those subsections in one big list, especially about the increased indentation and how that affects small screens. That was a somewhat weird structure anyway. So I backed that out and made the font size of h3 smaller. What do you think?
@matt I think that works just great! Much simpler than my idea.