update verbiage for a11y nav issue link

docs/blog/2020-02-05-accessible-client-side-routing-improvements/index.md

@@ -6,7 +6,7 @@ excerpt: "We recently released accessibility improvements to client side routing
 tags: ["accessibility, client-side-routing, diversity-and-inclusion"]
 ---
 
-We recently released accessibility improvements to client side routing, building on previous focus management improvements [released in version 2.13.2](https://github.com/gatsbyjs/gatsby/pull/13197). These improvements enable people relying on screen readers to successfully navigate sites built with Gatsby. If you'd like an in-depth look at how we made incremental changes to get to this release, have a look at the conversation in the ["a11y issues: page nav doesn't trigger assistive tech" issue](https://github.com/gatsbyjs/gatsby/issues/5581). It was opened way back in May 2018.
+We recently released accessibility improvements to client side routing, building on previous focus management improvements [released in version 2.13.2](https://github.com/gatsbyjs/gatsby/pull/13197). These improvements enable people relying on screen readers to successfully navigate sites built with Gatsby. If you'd like an in-depth look at how we made incremental changes to get to this release, have a look at the conversation in this [issue about assistive technology and navigation](https://github.com/gatsbyjs/gatsby/issues/5581). It was opened way back in May 2018.
 
 In July of 2019, Marcy Sutton teamed up with [Fable Tech Labs](https://www.makeitfable.com/) to conduct user testing to \ determine what the best user experience is for navigating JavaScript applications. Marcy wrote a thorough [blog post](/blog/2019-07-11-user-testing-accessible-client-routing/) about that research. This left us with some concrete recommendations to execute on: