[j42]

Really, though?

I always design with accessibility in mind, but I feel like there are more visceral complications than having to add a little extra context to a web search.

Almost everyone in development has encountered unfortunate name collisions that make what you're looking for hard to find... it's a pretty common inconvenience. Usually you just refine the query, like: "JAWS screenreader." The first result takes you where you probably intended to go, and it's at most 1-2 keystrokes away.

I think the real lesson here is to design inclusively. HTML has a lot of handy attributes to augment content; knowing & implementing the essentials means someone can follow the core flow of your site/application without relying on visual cues. And for the pragmatists... it has the added benefit of self-documenting and increasing semantic conformity in your markup.