From 6075dd4f355efb2302c296765497c10a8dfa7dfd Mon Sep 17 00:00:00 2001 From: ajitsinghkaler Date: Fri, 10 Apr 2020 21:23:48 +0530 Subject: [PATCH] docs: place download section in accessibility to the top link is very deep down on acessibility page this commit is part of a larger effort to standardise ownload sections on angular.io This commit partially addresses #35459 --- aio/content/guide/accessibility.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/aio/content/guide/accessibility.md b/aio/content/guide/accessibility.md index 5cc3c52252da9..65a0809c075b7 100644 --- a/aio/content/guide/accessibility.md +++ b/aio/content/guide/accessibility.md @@ -10,6 +10,12 @@ For an in-depth introduction to issues and techniques for designing accessible a This page discusses best practices for designing Angular applications that work well for all users, including those who rely on assistive technologies. +
+ + For the sample app that this page describes, see the . + +
+ ## Accessibility attributes Building accessible web experience often involves setting [ARIA attributes](https://developers.google.com/web/fundamentals/accessibility/semantics-aria) @@ -92,8 +98,6 @@ The following example shows how to make a simple progress bar accessible by usin -To see the progress bar in a working example app, refer to the . - ## Routing and focus management Tracking and controlling [focus](https://developers.google.com/web/fundamentals/accessibility/focus/) in a UI is an important consideration in designing for accessibility.