From 04235fa079340ea18729a7b7944fbdca613eff7e Mon Sep 17 00:00:00 2001 From: pavlenko Date: Sat, 20 Mar 2021 18:57:29 +0500 Subject: [PATCH] docs: replace Codelyzer recommendation with Angular-ESLint in accessibility guide (#41294) Replace Codelyzer recommendation with Angular-ESLint in accessibility guide since that tool is deprecated and was removed from the Angular CLI. Closes #41573 PR Close #41294 --- aio/content/guide/accessibility.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/aio/content/guide/accessibility.md b/aio/content/guide/accessibility.md index 4e62070a422..082c8c3a008 100644 --- a/aio/content/guide/accessibility.md +++ b/aio/content/guide/accessibility.md @@ -141,15 +141,10 @@ You should avoid situations where focus returns to the `body` element after a ro * [Rob Dodson A11ycasts](https://www.youtube.com/watch?v=HtTyRajRuyY) -* [Codelyzer](http://codelyzer.com/rules/) provides linting rules that can help you make sure your code meets accessibility standards. +* [Angular ESLint](https://github.com/angular-eslint/angular-eslint#functionality) provides linting rules that can help you make sure your code meets accessibility standards. Books * "A Web for Everyone: Designing Accessible User Experiences", Sarah Horton and Whitney Quesenbery * "Inclusive Design Patterns", Heydon Pickering - -## More on accessibility - -You may also be interested in the following: -* [Audit your Angular app's accessibility with codelyzer](https://web.dev/accessible-angular-with-codelyzer/).