You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
(Feature Request) - Accessibility Testing support #6572
Is there anything that stops you from adding them to a project right now? We try not to add extra tooling dependencies if possible, but if there's something that breaks usage of those tools maybe we can fix it.
No there is nothing stopping me from adding it currently. I just think that accessibility testing should be taken seriously and having it baked in into the CLI would reduce the friction to getting started, but I also understand that it might not be a priority at the moment.
@filipesilva that would be definitely welcome. Not to mix issues but maybe adding something like Lighthouse that supports customization would be useful as well. Then accessibility would be added as part of it. Just a thought, but not sure if the added functionality is needed.
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.
Activity
filipesilva commentedon Jun 6, 2017
Is there anything that stops you from adding them to a project right now? We try not to add extra tooling dependencies if possible, but if there's something that breaks usage of those tools maybe we can fix it.
sfabriece commentedon Jun 6, 2017
No there is nothing stopping me from adding it currently. I just think that accessibility testing should be taken seriously and having it baked in into the CLI would reduce the friction to getting started, but I also understand that it might not be a priority at the moment.
filipesilva commentedon Jun 12, 2017
Maybe we could add something as a flag e.g
ng e2e --accessibility.Luciaisacomputer commentedon Jun 13, 2017
I agree with @sfabriece , this is also something I would like to see as well.
sfabriece commentedon Jun 14, 2017
@filipesilva that would be definitely welcome. Not to mix issues but maybe adding something like Lighthouse that supports customization would be useful as well. Then accessibility would be added as part of it. Just a thought, but not sure if the added functionality is needed.
angular-robot commentedon Feb 1, 2022
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation.
angular-robot commentedon Feb 21, 2022
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.