From 943214d88c3113feec31a5c345dd48cd83b47041 Mon Sep 17 00:00:00 2001
From: "J. Degand" <70610011+jdegand@users.noreply.github.com>
Date: Thu, 8 Aug 2024 23:32:40 -0400
Subject: [PATCH] docs(angular): add routing content (#6452)

---
 .../angular/content/routing@8i_JD1P4gIhY1rdldwLC2.md   | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/src/data/roadmaps/angular/content/routing@8i_JD1P4gIhY1rdldwLC2.md b/src/data/roadmaps/angular/content/routing@8i_JD1P4gIhY1rdldwLC2.md
index 5904c1e21..e216775e1 100644
--- a/src/data/roadmaps/angular/content/routing@8i_JD1P4gIhY1rdldwLC2.md
+++ b/src/data/roadmaps/angular/content/routing@8i_JD1P4gIhY1rdldwLC2.md
@@ -1 +1,9 @@
-# Routing
\ No newline at end of file
+# Routing
+
+Tracking and controlling focus in a UI is an important consideration in designing for accessibility. When using Angular routing, you should decide where page focus goes upon navigation.
+
+Visit the following resources to learn more:
+
+- [@official@Angular Official Docs - a11y routing](https://angular.dev/best-practices/a11y#routing)
+- [@article@Accessibility - Focus](https://web.dev/learn/accessibility/focus/)
+- [@article@Router events in Angular](https://medium.com/@gurunadhpukkalla/router-events-in-angular-3112a3968660)
\ No newline at end of file