Firstly, thanks for this plugin - it looks great!

Apologies if this isn't the case, but I think that the graph is inaccessible to screen reader users and other users of assistive tech since, as far as I can tell, the graph is made up of a series of <div> elements. Would you consider reworking how the graphs are drawn, so that the information that the graphs are trying to convey are also accessible to users of assistive technologies?

This may or may not help, but Adrian Roselli wrote up a great piece on accessibility issues with GitHub's contributions graph. GitHub have since made some accessibility improvements. One of the changes they made was switching the graph from using an SVG to a <table>.

In the docs, it shows either using collections.posts to the shorttag, or custom data. But is there anything in particular in regards to collections.posts that folks should know about? I assume it has to have a date value?

Hi there,

first of all: thanks for this very cool plugin :)

I'm using it with data obtained from git log, the live version can be found here: https://ttntm.me/changelog/#timeline

Yesterday I noticed strange sizing ond extreme overflow in Chrome/Chromium on all devices I checked. After a little bit of investigation, I managed to figure out the cause - an extra <br> after the last div.epg__box in div.epg__squares:

I was rather late, so I checked again this morning and compared it to the version on your website.

Yours

Months

Squares

Mine

Months

Squares

Workaround

.epg__months > :not(div),
.epg__squares > :not(div) {
  display: none;
}

Additional Notes

• I'm using htmlmin for my site; tried turning it off, but the result was the same
• Firefox does not have any issues with the extra tags

Check out my post graph here:

https://www.raymondcamden.com/postgraph

Two issues I've noticed:

• 2018 and 2007 are 2x size wise. Any reason why?
• This is probably RTFM, but the dark spaces mean no content, green mean content... what do the empty spaces imply?

When the noLabels option is left to its default setting of false, it generates a line in the CSS of 'false' rather than being silent, resulting in a CSS validation error. When it is set to true, the option setting works correctly.

I tracked it down to this line in your plugin:

${options.noLabels && `
        .${prefix}__year, .${prefix}__months { display: none; }
    `}

It should probably be something like this:

${options.noLabels ? `.${prefix}__year, .${prefix}__months { display: none; }` : ''}

https://notacult.social/@carbontwelve/111613213713546355

I would like to ask it to sort descending and limit to displaying two years.

While working out some of my own issues to get the plugin working in my context. I noticed what appears to be an errant line with the word "false" on it between the CSS and HTML generated by the plugin. I'm attaching a screen grab of a portion.