I think this script is an excellent candidate to keep around as a bookmarklet.

Just to try it out I used this:

javascript:(function(){document.body.appendChild(document.createElement('script')).src='https://github.com/accesslint/accesslint.js/releases/download/v1.1.2/accesslint.js';})();

Works great, I get output in console, but would be nice if there was a latest hosted either in a CDN or just on github where I could reference it.

Background

Hi, this is the maintainer of @staticmanlab, a public GitLab instance for Staticman. I've recently created PR pacollins/hugo-future-imperfect-slim#69 to introduced a new feature to the project (nested Staticman comments).

Problem

The setup of Staticman with reCAPTCHA for a static blog (theme) requires some hidden form fields.

<input hidden name="options[reCaptcha][siteKey]" value="{{ .sitekey }}">
<input hidden name="options[reCaptcha][secret]" value="{{ .encryptedkey }}">
<div class="g-recaptcha" data-sitekey="{{ .sitekey }}"></div>

Despite their invisibility in the rendered page, AccessLint has raised a false alarm for "missing label".

Expected behavior

No false alarm for hidden fields.

Remarks

Thanks for your great project. It spotted out a missing image alt in my image tags for Gravatar.

I was working on my organization's webpage and made a commit to one of my student's patch when I saw this:

Accesslint has left review comments

The strangest part was that it wanted me to edit my HTML:

- <h1>
+ <h3>

I knew that headings went from most important (h1) to least important (h6)

Does anybody know why this is happening?

Can we publish accesslint.js to npm? It would be preferable to be able to manage it via npm install than via copying/pasting a built file into a vendor directory.

Media Andromax

In index.js, that the mutation observer is set up at require time rather than after the window.load event has fired. It seems to me that you wouldn't want to report mutations that happen before the full document scan which happens on window load. I'm happy to file a PR for this as well

I'm trying to get accesslint running on a React page with a lot of DOM mutations happening. What I've noticed is that tons of mutations get registered, then a bunch of axe checks complete, and sometimes the nodes axe is reporting aren't even in the page any more by the time the violations are printed to the console. It also brings the UI to a grinding slow pace.

I am thinking it could be beneficial to have a throttled audit function which only runs on the full document no more than once per second, rather than on every individual mutation. Thoughts on that? I'm happy to prep a PR