sinedied / a11y-ai

Experimental tool to automatically detect accessibility issues in web pages and provide suggestions for fixing them

$ npx @sinedied/card.

┌────────────────────────────────────────────────────────────┐
│                                                            │
│   Yohan Lasorsa / @sinedied                        【ツ】   │
│                                                            │
│       Work: Senior Cloud Developer Advocate @ Microsoft    │
│     GitHub: https://github.com/sinedied                    │
│    Twitter: https://twitter.com/sinedied                   │
│     Dev.to: https://dev.to/sinedied                        │
│   LinkedIn: https://linkedin.com/in/yohanlasorsa/          │
│                                                            │
│       Card: $ npx @sinedied/card                           │
│                                                            │
└────────────────────────────────────────────────────────────┘

a11y-ai's Issues

commands error out after fresh install of tool

Attempted to install this on my mac, running latest version of npm.

navigating to a folder and performing the command "a11y scan index.html" in terminal, I receive the following error:

file:///usr/local/lib/node_modules/a11y-ai/lib/cli.js:9
dns.setDefaultResultOrder('ipv4first');
    ^

TypeError: dns.setDefaultResultOrder is not a function
    at file:///usr/local/lib/node_modules/a11y-ai/lib/cli.js:9:5
    at ModuleJob.run (internal/modules/esm/module_job.js:152:23)
    at async Loader.import (internal/modules/esm/loader.js:177:24)
    at async Object.loadESM (internal/process/esm_loader.js:68:5)

Similar errors occur regardless of the command used. I'm at a loss for what to do here, since the installation / usage instructions are rather straight forward in their brevity, which is good. but there's not much in the way to help when encountering errors like these.

internal

"Fix" should not remove scripts

Discussed in #11

^{Originally posted by scottaohara May 23, 2023}
If the intent of this tool is to help create meaningful fixes that could be accepted / merged into code repositories, then the fix command should not be removing scripts it encounters. While many developers would likely notice this and revert these specific changes when they were reviewing the diff of the changes the fix command made, it's an extra step that has the potential to break pages, rather than fix them, if a removal goes unnoticed.

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://x-access-token:[secure]@github.com/sinedied/a11y-ai.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Error while running axe scan

There seems to be a error with axe finding playwright in this integhration. I have not been able to solve the issue no matter how many times I update the directories. I have attached logs

2023-12-30T21_11_53_999Z-debug-0.log
2023-12-30T21_11_55_366Z-debug-0.log
2023-12-30T21_12_28_811Z-debug-0.log
2023-12-30T21_12_29_571Z-debug-0.log
2023-12-30T21_12_56_374Z-debug-0.log
2023-12-30T21_12_56_396Z-debug-0.log
2023-12-30T21_12_57_248Z-debug-0.log
2023-12-30T21_12_57_272Z-debug-0.log
2023-12-30T21_13_57_571Z-debug-0.log
2023-12-30T21_13_58_307Z-debug-0.log