From 7d45ef702f13a35e83e4e2e7be26d36141dfa07d Mon Sep 17 00:00:00 2001 From: Yann Provoost Date: Sun, 28 Aug 2022 11:35:16 +0200 Subject: [PATCH] docs: fix doc linter warning and error in `accessibility.md` (#47282) PR Close #47282 --- aio/content/guide/accessibility.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/aio/content/guide/accessibility.md b/aio/content/guide/accessibility.md index a88abd4f19a..135fe97becd 100644 --- a/aio/content/guide/accessibility.md +++ b/aio/content/guide/accessibility.md @@ -121,7 +121,7 @@ router.events.pipe(filter(e => e instanceof NavigationEnd)).subscribe(() => -In a real application, the element that receives focus will depend on your specific application structure and layout. +In a real application, the element that receives focus depends on your specific application structure and layout. The focused element should put users in a position to immediately move into the main content that has just been routed into view. You should avoid situations where focus returns to the `body` element after a route change. @@ -167,9 +167,13 @@ The following example shows how to apply the `active-page` class to active links Books + + * "A Web for Everyone: Designing Accessible User Experiences", Sarah Horton and Whitney Quesenbery * "Inclusive Design Patterns", Heydon Pickering + +