Greg Albers

Here's a temporary workaround to this issue: **1. In the `node_modules/@11ty/eleventy-plugin-vite/EleventyVite.js` file in your project, add `await fsp.rm(tmp, { recursive: true, force: true });` between lines 51 and 52:** **2....

There are now two open PRs for this in the `eleventy-plugin-vite` repo, but no response from the maintainer yet. See https://github.com/11ty/eleventy-plugin-vite/pull/34 and https://github.com/11ty/eleventy-plugin-vite/pull/35.

Thanks for posting @bjhewitt. I agree, those images should definitely include their alt test. Until this is fixed in core Quire, there's a fix you can try on your own....

One enhancement to this feature that would go beyond previous implementations, but might prove to be very useful, would be to make the filter results linkable. This would allow readers...

Approved for development: https://jira.getty.edu/browse/DEV-6508

Cool tool @naeluh. Reminds me that I should also add here our accessibility principles (some of which are duplicated in the list above) that also includes some links to other...

We're experiencing the same issue on [our project](https://github.com/thegetty/quire/). ``` "@11ty/eleventy": "^2.0.1", "@11ty/eleventy-plugin-vite": "^4.0.0", ``` Would be great to get a PR in to fix the issue. In the meantime, @anantakrishna,...

Thank you @anantakrishna! That fix worked for me, though I also had to change `path.sep` to `/` as you did.