-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tarsnap Website Screen Reader Compatibility #477
Comments
Thanks for the report. Do you work on accessibility or use a screen reader? I'm aware that firefox reports this an accessibility issue, but I haven't found a definitive reference to back them up. For anybody skimming these issues, the html in question is this:
or, expanded for readability:
The question of "how should we deal with a website logo?" is an old one. There's a fair amount of discussion here: There's a few options:
At the moment, I'm not convinced that options 2-4 are better than option 1. |
I'm going to be honest with you, I just saw the issue in Firefox, and I just wanted to make sure that you were aware of the issue. I'm a noob at web design, and don't really have much to add to this, except for this question, how bad for SEO would it be if you just didn't put the logo in a |
Fair enough. I don't think that we're too concerned about SEO; it's more a question of "what's the best for accessibility and good practice?". As for having the logo inside That's not to say that the website is perfect; one piece of advice I've seen multiple places is that you shouldn't skip any headings, and our pages currently skip over |
Hello,
On the Tarsnap website, the Tarsnap logo/graphic at the top is inside an
<h1>
tag. This can cause issues with how a screen reader reads a websites formating. The screen reader expects text to be inside a<h1>
tag, not graphics or logos. More information here: https://developer.mozilla.org/en-US/docs/Web/Accessibility/Understanding_WCAG/Text_labels_and_names#headings_should_have_visible_text_contentThe text was updated successfully, but these errors were encountered: