Florian<p>Always fun to read <a href="https://cupoftea.social/tags/hackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hackerNews</span></a> and their rather ... let's call it ... qualitatively exceedingly disappointing mentality towards <a href="https://cupoftea.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accessibility</span></a> (stroopwafel to the dutchies who see what i did there). But some points do make me think to what degree, say, <a href="https://cupoftea.social/tags/screenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>screenReaders</span></a> could be innovating more.<br>One thing that stuck by me was a comment on an article regarding the use of "click here" that basically suggested some kind of heuristic for, say, reading the entire line of text when that's encountered, rather than the link text. Another one could be including the previous sibling's accessible name on unlabeled form fields which I ...think? JAWS might already be doing?<br>Like obviously these should be toggleable to not screw up audits but I think after 30 years we can safely say people often can't be forked to learn <a href="https://cupoftea.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> basics and it might make some things smoother?</p>