cloudfour / pwastats

A directory of Progressive Web App case studies.
https://www.pwastats.com
MIT License
102 stars 9 forks source link

Are the block links accessible? #205

Closed emersonthis closed 1 year ago

emersonthis commented 4 years ago

It's my understanding that large "block links" (components wrapped in an <a> tag) can be problematic for accessibility (and usability) reasons.

This article talks about this concern. Inclusive components echos some of those concerns, and offers mitigation strategies.

tylersticka commented 4 years ago

The block links are accessible, but they could be more accessible.

As is, the content of block links is likely to be read aloud as a run-on sentence consisting of the visually hidden heading and the paragraph that follows. Thankfully, the secondary links and meta information are separate elements and will not be read aloud in the same manner.

The main issue is that those headings are not navigable on their own. Since they are visually hidden, a very quick and easy fix would be to move those headings out of the anchor (but still nested within the <article> element).

(In the future, this pattern will be revised entirely. See: https://github.com/cloudfour/cloudfour.com-patterns/issues/493)

tylersticka commented 1 year ago

Closing this since the original question has been answered and there's an eventual plan for moving forward.