Kilotest: Diagnoses of image not named violation by HTML element 301 on Probably Good page

Basics

About the Probably Good page

• URL: https://probablygood.org/
• Tested 3 days ago by job n2u on 2026-05-30 at 00:32

About HTML element 301

• Tag name: IMG
• Text: Career Guide … A practical guide to doing good with your career.
• Start tag: <img fetchpriority="high" decoding="async" width="500" height="508" class="gbp-topics-small_image" src="https://probablygood.org/wp-content/uploads/Home-Page_Career-Guide_Boat-Lighthouse.webp" title="Home-Page_Career-Guide_Boat-Lighthouse" alt="" srcset="https://probablygood.org/wp-content/uploads/Home-Page_Career-Guide_Boat-Lighthouse.webp 500w, https://probablygood.org/wp-content/uploads/Home-Page_Career-Guide_Boat-Lighthouse-295x300.webp 295w" sizes="(max-width: 500px) 100vw, 500px">
• XPath: /html/body/div[3]/div[1]/div[1]/main[1]/article[1]/div[1]/div[1]/div[2]/div[1]/div[2]/div[1]/img[1]
• Bounding box: x = 861, y = 901, width = 169, height = 173

Take me there

About the image not named issue

• Why it matters: User cannot get help to know what is in an image
• Priority: highest
• Related WCAG standard: 1.1.1

Diagnoses

Here is how tools diagnose the image not named issue for HTML element 301 of the Probably Good page.

1. The image 'alt' attribute is empty, but the 'title' attribute is not empty

   Tool: Accessibility Checker (IBM)

   Rule: img_alt_null