512 of our 516 pages carry a breadcrumb trail, and not one of them names the page you are on
Munchable's website is 516 URLs, and 512 of them ship a breadcrumb. Some of that breadcrumb is drawn on the page for a reader, and some of it is in a <script type="application/ld+json"> block for a crawler. I had always assumed those two were the same list rendered twice. They are not. They overlap in exactly one item. What a reader sees, and what a crawler reads Here is the whole visible trail…
Munchable's website consists of 516 URLs, with 512 of them featuring a breadcrumb trail. This breadcrumb trail is present both in the visible HTML for readers and in JSON format for search engines and crawlers. However, there is a discrepancy between the two - the visible trail focuses on the page the reader is currently on, while the structured trail starts from the site's root and ends one step before the page being viewed.
Despite both descriptions being valid, they do not align completely. This discrepancy affects the user experience for screen reader users, as no indication is provided as to which element represents the current page. The issue stems from the website having two separate sets of breadcrumb data, which are not coordinated. One solution would be to consolidate the trails into a single source of truth, thus eliminating the inconsistency and improving accessibility for all users.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
