Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Accessibility Setup #53

Open
aitala opened this issue Oct 20, 2015 · 1 comment
Open

Accessibility Setup #53

aitala opened this issue Oct 20, 2015 · 1 comment

Comments

@aitala
Copy link
Contributor

aitala commented Oct 20, 2015

On a clean install of NV, for the Accessibility setup -

Would you like the ability to create accessibility reports via access_lint? This can help with ensuring you maintain accessibility compliance to keep your website working well for users with disabilities. (y/n)

with a yes response -

sudo: npm: command not found

Things proceed from there with no more warnings/errors and the accessibility modules seem to be installed and working.
@mmilutinovic013
Copy link

This occurs for me too with the front-end development SASS part of the setup. Is npm not preinstalled? Or is this a bug where it does the install but reports sudo: npm: command not found?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aitala @mmilutinovic013