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

HTML5 markup for breadcrumbs #256

Closed
Willem-Siebe opened this Issue Sep 20, 2013 · 7 comments

Comments

Projects
None yet
2 participants
@Willem-Siebe

See https://www.w3.org/Bugs/Public/show_bug.cgi?id=22739.
And: http://www.w3.org/html/wg/drafts/html/master/common-idioms.html#rel-up

But, when I choose for a text like 'You are here', then in my opinion it must become (no aria-label):

[nav]
[h1]You are here[/h1]
etc. etc.
[li]Second hand[/li]
[/ol]
[/nav]

  • the last li element is now without 'a', there I would use an 'a' without a 'href', see also the buglink where that is explained.
@jdevalk

This comment has been minimized.

Show comment
Hide comment
@jdevalk

jdevalk Aug 8, 2014

Member

Sorry, as long as Google is so bad at recognizing other types of markup, we're not going to change our defaults...

Member

jdevalk commented Aug 8, 2014

Sorry, as long as Google is so bad at recognizing other types of markup, we're not going to change our defaults...

@jdevalk jdevalk closed this Aug 8, 2014

@Willem-Siebe

This comment has been minimized.

Show comment
Hide comment
@Willem-Siebe

Willem-Siebe Aug 9, 2014

Hi, isn't it recognized by the micordate you are using? I remeber other topic where you have been asked to use schema.org for it, and there I also commented that schema.org is not picked up by Google like you already knew. But correct HTML5 together with the old microdata, does that really give problems?

Hi, isn't it recognized by the micordate you are using? I remeber other topic where you have been asked to use schema.org for it, and there I also commented that schema.org is not picked up by Google like you already knew. But correct HTML5 together with the old microdata, does that really give problems?

@Willem-Siebe

This comment has been minimized.

Show comment
Hide comment
@Willem-Siebe

Willem-Siebe Mar 31, 2015

Hi Joost, although the topic is closed and I haven't got a resons the last time: this issue is not about using schema.org > it's only about using other HTML, don't you agree using the method of W3C I linked to?

Hi Joost, although the topic is closed and I haven't got a resons the last time: this issue is not about using schema.org > it's only about using other HTML, don't you agree using the method of W3C I linked to?

@jdevalk

This comment has been minimized.

Show comment
Hide comment
@jdevalk

jdevalk Apr 1, 2015

Member

Hey @Willem-Siebe so... You're able to do this. You can filter it any way you like. But I'm not going to change it to a list in our default output, sorry :)

Member

jdevalk commented Apr 1, 2015

Hey @Willem-Siebe so... You're able to do this. You can filter it any way you like. But I'm not going to change it to a list in our default output, sorry :)

@Willem-Siebe

This comment has been minimized.

Show comment
Hide comment
@Willem-Siebe

Willem-Siebe Apr 1, 2015

Hi @jdevalk , thanks for letting me know. Instead of making a pull request for other HTML output I will now start using the filters to accomplish this for myself, luckily the plugin is this flexible, thanks for that as well.

Hi @jdevalk , thanks for letting me know. Instead of making a pull request for other HTML output I will now start using the filters to accomplish this for myself, luckily the plugin is this flexible, thanks for that as well.

@jdevalk

This comment has been minimized.

Show comment
Hide comment
@jdevalk

jdevalk Apr 1, 2015

Member

I keep hearing that at some point we will actually be able to switch to schema.org output, as soon as that happens we might look at this again.

Member

jdevalk commented Apr 1, 2015

I keep hearing that at some point we will actually be able to switch to schema.org output, as soon as that happens we might look at this again.

@Willem-Siebe

This comment has been minimized.

Show comment
Hide comment

Ok!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment