Merge pull request #3232 from MicrosoftDocs/user/mikehoffms/skip-h3

Skip h3 in all files in repo, to show main structure of articles

microsoft-edge/accessibility/build/index.md

@@ -41,7 +41,9 @@ For more information on web accessibility, check out the [Introduction to Web Ac
 
 The [Accessible Rich Internet Applications (ARIA)](https://www.w3.org/TR/wai-aria) specification by the W3C's [Web Accessibility Initiative](https://www.w3.org/WAI) defines as a syntax for making dynamic web content and custom user interfaces accessible to all people.  ARIA extends HTML by using additional attributes (roles, properties, and states) that are designed to convey custom semantics.  These attributes are used by browsers to pass along the controls' state and role to the accessibility API.
 
-### Roles, properties, and states
+
+<!-- ------------------------------ -->
+#### Roles, properties, and states
 
 ARIA roles are set on elements using the [role](https://developer.mozilla.org/docs/Web/HTML/Reference) attribute to give assistive technologies and accessibility APIs information about the element.  For example, the below `<li>` element is assigned `role="menuitem"` to signify that it's an item in a menu.
 
@@ -82,17 +84,23 @@ Different browsers might map elements to the platform accessibility APIs differe
 
 WebAIM conducts surveys with [screen reader](https://webaim.org/projects/screenreadersurvey8) and [low vision](https://webaim.org/projects/lowvisionsurvey2) users that help you decide which assistive technologies and browsers to test.
 
-### Learning how to test
+
+<!-- ------------------------------ -->
+#### Learning how to test
 
 Assistive technologies are sophisticated tools.  Don't assume that you're able to immediately start testing with an assistive technology without first learning about how it works.  Learning to test with a screen reader has an especially steep learning curve.  A novice user of screen readers might think that a screen reader has a bug, while the issue might actually be an error in using the screen reader.
 
 [Testing with Screen Readers](https://webaim.org/articles/screenreader_testing) at WebAIM provides more information about learning to test with assistive technologies.
 
-### Testing locally
+
+<!-- ------------------------------ -->
+#### Testing locally
 
 Most devices include assistive technology that is built-in to the OS.  Microsoft Windows includes the [Windows Narrator](https://support.microsoft.com/help/22798) screen reader and [Windows Magnifier](https://support.microsoft.com/windows/414948ba-8b1c-d3bd-8615-0e5e32204198).  3rd party assistive technologies like [NVDA](https://www.nvaccess.org/about-nvda), [FreedomscientificSoftwareJaws](https://www.freedomscientific.com/products/software/jaws), and [ZoomText](https://www.freedomscientific.com/products/software/zoomtext) are available to download.  Apple macOS includes the [VoiceOver](https://www.apple.com/accessibility/mac/vision) screen reader.  And iOS, Android, and Linux all support a variety of assistive technologies.
 
-### Testing in virtual machines and emulators
+
+<!-- ------------------------------ -->
+#### Testing in virtual machines and emulators
 
 Under macOS, if you want to test with an assistive technology only available for Windows, like Windows Narrator or NVDA, create a Windows virtual machine.
 
@@ -101,7 +109,9 @@ Under macOS, if you want to test with an assistive technology only available for
 > [!NOTE]
 > The iOS Simulator doesn't currently include VoiceOver.
 
-### Cloud-based testing tools
+
+<!-- ------------------------------ -->
+#### Cloud-based testing tools
 
 If an assistive technology isn't available on your OS or you not possible to install one on a virtual machine or emulator, cloud-based assistive technology testing tools are the next best thing.
 
@@ -115,11 +125,15 @@ See also [Cloud-based emulators and simulators](../../devtools-guide-chromium/de
 
 These are projects and initiatives for accessibility.
 
-### The A11Y project
+
+<!-- ------------------------------ -->
+#### The A11Y project
 
 [The A11Y Project](http://a11yproject.com) is a community-driven effort to make web accessibility easier.  Check out [The A11Y Project](https://a11yproject.com) site to learn about basic accessibility principles, their accessible pattern and widget [library](https://a11yproject.com/patterns), and their [resources](http://a11yproject.com/resources.html) on accessibility software, blogs, books, and tools.
 
-### Web Accessibility Initiative (WAI)
+
+<!-- ------------------------------ -->
+#### Web Accessibility Initiative (WAI)
 
 The W3C [Web Accessibility Initiative (WAI)](https://w3.org/WAI) is an effort to help improve the accessibility of the web.  Their site provides a variety of resources for [Getting Started with Web Accessibility](https://www.w3.org/WAI/gettingstarted/Overview.html), [Designing for Inclusion](https://www.w3.org/WAI/users/Overview.html), [tutorials and presentations](https://www.w3.org/WAI/train.html), and more.
 
@@ -129,11 +143,15 @@ The W3C [Web Accessibility Initiative (WAI)](https://w3.org/WAI) is an effort to
 
 These are blogs about accessibility.
 
-### TPGi, LLC
+
+<!-- ------------------------------ -->
+#### TPGi, LLC
 
 [TPGi, LLC](https://www.tpgi.com/blog) provides consulting and technology solutions to organizations around the world to ensure that their clients reach all audiences effectively and efficiently, while meeting governmental and international standards.  Their blog covers topics like web accessibility best practices, accessibility tools, and accessibility trends.
 
-### Level Access
+
+<!-- ------------------------------ -->
+#### Level Access
 
 [Level Access](https://www.levelaccess.com/blog) is a digital accessibility firm supporting their clients in developing and deploying accessible products and services.  Their blog addresses topics like ARIA best practices, accessibility trends, webinars, and more.
 
@@ -143,15 +161,21 @@ These are blogs about accessibility.
 
 These are libraries and examples for accessibility.
 
-### ally.js - Tutorials
+
+<!-- ------------------------------ -->
+#### ally.js - Tutorials
 
 JavaScript library to help modern web applications with accessibility concerns by making accessibility simpler.  For more information, go to [ally.js - Tutorials](http://allyjs.io/tutorials).
 
-### OpenAjax examples
+
+<!-- ------------------------------ -->
+#### OpenAjax examples
 
 The [OpenAjax Alliance website](http://oaa-accessibility.org) is an excellent resource for verifying the rules for WAI-ARIA and provides a number of examples of WAI-ARIA implementations.
 
-### Patterns
+
+<!-- ------------------------------ -->
+#### Patterns
 
 [The A11Y Project](http://a11yproject.com) offers a library of accessible widgets and patterns like menus, buttons, tooltips, and more.  For more information, go to [Patterns](http://a11yproject.com/patterns.html).
 
@@ -161,70 +185,104 @@ The [OpenAjax Alliance website](http://oaa-accessibility.org) is an excellent re
 
 These are techniques and tools for improving accessibility.
 
-### Accessibility: Creating accessible extension icons for Microsoft Edge
+
+<!-- ------------------------------ -->
+#### Accessibility: Creating accessible extension icons for Microsoft Edge
 
 Get guidance on creating accessible extensions icons for Microsoft Edge.  For more information, go to [Accessibility: Creating accessible extension icons for Microsoft Edge](/archive/microsoft-edge/legacy/developer/extensions/guides/accessibility).
 
-### Accessible Name and Description: Computation and Mappings 1.1
+
+<!-- ------------------------------ -->
+#### Accessible Name and Description: Computation and Mappings 1.1
 
 This W3C mapping document explains how browsers determine name and descriptions of accessible objects from web content languages and expose them in accessibility APIs.  For more information, go to [Accessible Name and Description: Computation and Mappings 1.1](https://www.w3.org/TR/accname-1.1).
 
-### Accessibility Evaluation Resources
+
+<!-- ------------------------------ -->
+#### Accessibility Evaluation Resources
 
 Accessibility Evaluation Resources is a multi-page resource by the W3C that outlines different approaches for evaluating websites for accessibility.  For more information, go to [Accessibility Evaluation Resources](https://www.w3.org/WAI/eval/Overview.html).
 
-### Assistive technology compatibility tests
+
+<!-- ------------------------------ -->
+#### Assistive technology compatibility tests
 
 Test results showing how different content types and standards behave in assistive technologies (AT) like screen readers.  For more information, go to [Assistive technology compatibility tests](http://www.powermapper.com/tests).
 
-### Building accessible websites just got a lot easier
+
+<!-- ------------------------------ -->
+#### Building accessible websites just got a lot easier
 
 This .NET Web Development and Tools blog post describes the Visual Studio extension [Web Accessibility Checker](https://marketplace.visualstudio.com/items?itemName=MadsKristensen.WebAccessibilityChecker).  For more information, go to [Building accessible websites just got a lot easier](https://devblogs.microsoft.com/aspnet/building-accessible-websites-just-got-a-lot-easier).
 
-### Core Accessibility API Mappings 1.1
+
+<!-- ------------------------------ -->
+#### Core Accessibility API Mappings 1.1
 
 This W3C mapping document explains how the semantics of web content languages are exposed to accessibility APIs.  For more information, go to [Core Accessibility API Mappings 1.1](https://www.w3.org/TR/core-aam-1.1).
 
-### Easy Checks – A First Review of Web Accessibility
+
+<!-- ------------------------------ -->
+#### Easy Checks – A First Review of Web Accessibility
 
 A series of quick checks by the WAI that help you assess the accessibility of a web page.  For more information, go to [Easy Checks – A First Review of Web Accessibility](https://www.w3.org/WAI/eval/preliminary.html).
 
-### How to Meet WCAG 2.0
+
+<!-- ------------------------------ -->
+#### How to Meet WCAG 2.0
 
 A quick reference to Web Content Accessibility Guidelines (WCAG) 2.0 requirements (success criteria) and techniques.  For more information, go to [How to Meet WCAG 2.0](https://www.w3.org/WAI/WCAG20/quickref).
 
-### HTML Accessibility API Mappings 1.0
+
+<!-- ------------------------------ -->
+#### HTML Accessibility API Mappings 1.0
 
 This W3C mappings document explains how HTML5.1 element and attributes map to platform accessibility APIs.  For more information, go to [HTML Accessibility API Mappings 1.0](https://www.w3.org/TR/html-aam-1.0).
 
-### Quick Tips
+
+<!-- ------------------------------ -->
+#### Quick Tips
 
 A list of quick web development tips for accessibility by [The A11Y Project](http://a11yproject.com).  For more information, go to [Quick Tips](http://a11yproject.com#Quick-tips).
 
-### Site Scan
+
+<!-- ------------------------------ -->
+#### Site Scan
 
 The Site Scan tool on Microsoft Edge Dev Center checks for out-of-date libraries, layout issues, and accessibility issues.  For more information, go to [Site Scan](https://developer.microsoft.com/microsoft-edge/tools).
 
-### Techniques for WCAG 2.0
+
+<!-- ------------------------------ -->
+#### Techniques for WCAG 2.0
 
 Techniques from the W3C that provide guidance for web developers on meeting [Web Content Accessibility Guidelines (WCAG) 2.0](https://w3.org/TR/WCAG20) success criteria.  For more information, go to [Techniques for WCAG 2.0](https://www.w3.org/TR/WCAG20-TECHS/Overview.html).
 
-### Tips on Developing for Web Accessibility
+
+<!-- ------------------------------ -->
+#### Tips on Developing for Web Accessibility
 
 Tips from the W3C on developing web content that is more accessible to people with disabilities.  For more information, go to [Tips on Developing for Web Accessibility](https://w3.org/WAI/gettingstarted/tips/developing.html).
 
-### WAI-ARIA Authoring Practices 1.1
+
+<!-- ------------------------------ -->
+#### WAI-ARIA Authoring Practices 1.1
 
 A document by the W3C that provides readers with an understanding of how to use WAI-ARIA 1.1 and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties.  For more information, go to [WAI-ARIA Authoring Practices 1.1](http://w3c.github.io/aria-practices).
 
-### WAI Guidelines and Techniques
+
+<!-- ------------------------------ -->
+#### WAI Guidelines and Techniques
 
 A series of web accessibility guidelines and standards developed by the WAI.  For more information, go to [WAI Guidelines and Techniques](https://w3.org/WAI/guid-tech.html).
 
-### Web Accessibility Evaluation Tools List
+
+<!-- ------------------------------ -->
+#### Web Accessibility Evaluation Tools List
 
 A list of web accessibility evaluation tools to help determine if websites meet accessibility guidelines.  For more information, go to [Web Accessibility Evaluation Tools List](https://www.w3.org/WAI/ER/tools/index.html).
 
-### Web Accessibility Perspectives: Explore the Impact and Benefits for Everyone
+
+<!-- ------------------------------ -->
+#### Web Accessibility Perspectives: Explore the Impact and Benefits for Everyone
 
 A series of short situational videos by the W3C about the impact of accessibility and the benefits for everyone.  For more information, go to [Web Accessibility Perspectives: Explore the Impact and Benefits for Everyone](https://w3.org/WAI/perspectives).