Skip to content
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

SEO Score not affected by img without alt attribute #8393

Closed
andreabisello opened this issue Apr 18, 2019 · 2 comments · Fixed by #8407
Closed

SEO Score not affected by img without alt attribute #8393

andreabisello opened this issue Apr 18, 2019 · 2 comments · Fixed by #8407
Assignees

Comments

@andreabisello
Copy link

andreabisello commented Apr 18, 2019

Provide the steps to reproduce

  1. Run LH on https://www.w3schools.com/code/tryit.asp?filename=G37S02M71XEE . This page contains this code
<!DOCTYPE html>
<html>
<body>

<p>
An image that is a link:
<a href="https://www.w3schools.com">
<img src="smiley.gif" width="42" height="42" border="0">
</a>
</p>

</body>
</html>
  1. Search for SEO score
  2. No warning about the missing alt attribute

What is the current behavior?

LH say nothing about img without alt tag

What is the expected behavior?

LH should warn about img without alt tag . Google in this document https://support.google.com/webmasters/answer/114016?hl=en says to use descriptive alt text

Environment Information

  • Affected Channels: DevTools
  • Lighthouse version: 4.0.0
  • Node.js version: 6.4.1
  • Operating System: updated windows 10
@patrickhulce
Copy link
Collaborator

Thanks @andreabisello good catch! We flag this in accessibility but not SEO.

cc @rviscomi / @AVGP for their blessing

@AVGP
Copy link
Collaborator

AVGP commented Apr 18, 2019

Yes, very good catch! From an SEO standpoint, your images should have an alt attribute. Thanks for flagging this, @andreabisello

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants