3 ms·
Curiosity is *never something to be excused. It's to be celebrated. Anyway, HN is actually not all that great in terms of accessibility. The tree styling of the
by ctoth 12y ago
Curiosity is *never something to be excused. It's to be celebrated.
Anyway, HN is actually not all that great in terms of accessibility. The tree styling of the comments, and the marking of downvotes are both indicated visually and not semantically. It means that I will often have to use context to determine where one thread ends and another begins, or when comments pass my personal taste threshold I just whack page down a few times.
- dang 12y agoWe're working on changing HN's markup, and the new markup should allow us to address the concerns you mention here. We don't know yet when we'll release it, but then will be a good time for us to fix any of these issues that remain. (The look and feel of the site won't change, but more will be indicated semantically.)
- mwcampbell 12y agoI think the best way to represent comment threads with semantic HTML would be using the <ul> element. So the top-level comment thread for a post goes in a <ul> element, and then there's a nested <ul> element for each subthread. Of course, you can use CSS to drop the bullets and adjust the amount of indentation. Then, a screen reader or browser extension can easily provide a way to skip over whole subthreads, without having to do something HN-specific.