Accelerated Checkout Button and <title> tag

Short description of issue

How or why is being used for the checkout buttons?

Link to Shopify Store

Reproduction steps

Go to site, inspect code, search for “”. Buy buttons have to my knowledge and w3c, you cannot have more than one in a html document.

Additional info

“Note: You can NOT have more than one element in an HTML document.”

Surely the html spec is correct ?

If so how did that even get past QC / testing?

Cheers

What type of topic is this

Bug report

Upload screenshot(s) of issue


In fact, there are more of them, and they are all in the payment icons.

Indeed I did notice that to after the fact. it will need correcting I think, as the basically breaks SEO and doc spec for all sites that use those buttons :shaking_face:

A title is a valid element to be inside of an SVG: <title> — the SVG accessible name element - SVG | MDN

Thank you, for clearing that up, this might be a preference on what documents to follow…

I see that the recommendation by MDN, is “Text in a <title> element is not rendered as part of the graphic, but browsers usually display it as a tooltip. If an element can be described by visible text, it is recommended to reference that text with an aria-labelledby attribute rather than using the <title> element.” Avoiding the issue with the W3C docs.

Given the fall back, granted would it still not be applicable to have just one “” tag in the whole document. As SEO testers and the like in the whole will see it and then say that document is needing to be fixed ?

While I agree that maybe these SVGs could be using a different approach this should have no effect on SEO. If the testers are flagging this tag then they aren’t robust enough to understand where a title tag is being rendered. If you’re relying on a particular tool it might be worth exploring another one.

On a personal note, I’ve avoided using W3Schools for anything for more than a decade now as there are much better resources available (like MDN!).

Sure, and thank you for the response. I do check both MDN and W3C, always took W3C as the authority on such matters, though now I will look more at MDN.

Is a good to know for sure, again thank you. @Gray-Shopify - it is a muddy world out there, just have to wear the right boots. :slight_smile:

One point of clarity: there’s a big difference between W3C (authority) and W3Schools (learning site). Referencing W3C is totally fine though I find the docs hard to read sometimes :slight_smile:

1 Like

To be fair, I find the google doc’s a massive pain to read. So I understand, I did read that W3C, where helping with the MDN, after looking further into to this. I think it said since 2018! So I totally missed that one :person_facepalming:

It’s all good, and indeed a switch in SEO test, did prove the robustness of the SEO check I did run.

All good from my point of view and it is an interesting subject for the most part, I am just glad there is a “standard”, otherwise it would be worse then the whole “USB” debacle we all suffered.

Like when there was “internet explorer” / “safari” / “chrome” / “Firefox” / “opra browser” all at the same time using different engines at one point I seem to remember.

My opinion is slightly biased, as I had the pleasure to have a pint with a chap that wrote W3C doc’s, way back in 2013. ( he must have bribed me with a beer lol ). Cool chap.

Good to get another view point via discussion here and learn more I have. @Gray-Shopify

1 Like