Render callouts correctly by inserting a newline between sections

Author: tahoon-ms

powerapps-docs/maker/canvas-apps/controls/control-barcodescanner.md

@@ -86,5 +86,6 @@ If you add this control, the user can update a data source with one or more phot
 
 ### Screen reader support
 * **[AccessibleLabel](properties-accessibility.md)** must be present.
+
 > [!NOTE]
 > Screen readers will annnouce when a new barcode has been found. The value will not be announced. As long as the barcode is in view, screen readers will remind every 5 seconds that the same barcode is still being identified.

powerapps-docs/maker/canvas-apps/controls/control-column-line-chart.md

@@ -133,6 +133,7 @@ There must be adequate color contrast between:
 ### Screen reader support
 * There must be a **[Label](control-text-box.md)** immediately before the chart graphic to serve as the title.
 * Consider adding a summary of the chart graphic. For example, "The line chart shows a steady increase in sales between March and August this year."
+
 > [!NOTE]
 > Chart graphics and **Legend** are hidden from screen reader users. As an alternative, a tabular form of the data is presented to them. They can also cycle through buttons that select data in the chart.
 
@@ -143,5 +144,6 @@ There must be adequate color contrast between:
 
 ### Keyboard support
 * **[TabIndex](properties-accessibility.md)** must be zero or greater so that keyboard users can navigate to it.
+
 > [!NOTE]
 > When keyboard users navigate to the chart, they can cycle through buttons that select data in the chart.

powerapps-docs/maker/canvas-apps/controls/control-combo-box.md

@@ -102,11 +102,13 @@ This is in addition to the [standard color contrast requirements](../accessible-
 
 ### Screen reader support
 * **[AccessibleLabel](properties-accessibility.md)** must be present.
+
 > [!NOTE]
 > On touch screens, screen reader users can navigate the contents of the combo box sequentially. The combo box acts as a button that shows or hides its contents when selected.
 
 ### Keyboard support
 * **[TabIndex](properties-accessibility.md)** must be zero or greater so that keyboard users can navigate to it.
 * Focus indicators must be clearly visible. Use **[FocusedBorderColor](properties-color-border.md)** and **[FocusedBorderThickness](properties-color-border.md)** to achieve this.
+
 > [!NOTE]
 > The tab key navigates to or away from the combo box. Arrow keys navigate the contents of the combo box. The escape key closes the drop down when opened.

powerapps-docs/maker/canvas-apps/controls/control-gallery.md

@@ -101,11 +101,13 @@ If clicking anywhere in a gallery item is meant to select it, there must be adeq
 
 ### Screen reader support
 * **[AccessibleLabel](properties-accessibility.md)** must be present.
+
 > [!NOTE]
 > Screen readers will annnouce when items in the gallery change. The **AccessibleLabel** is also mentioned. This gives context to the announcement and is even more important when there are multiple galleries on the same screen.
 
 ### Keyboard support
 * Consider setting **ShowScrollbar** to **true**. On most touch screen devices, the scrollbar will not show until scrolling begins.
 * If clicking anywhere in a gallery item is meant to select it, there must also be way for keyboard users to select the gallery item. For example, adding a **[Button](control-button.md)** that has its **OnSelect** property set to **Select(Parent)**.
+
 > [!NOTE]
 > Controls outside the gallery are not considered in the keyboard navigation order within the gallery. **[TabIndex](properties-accessibility.md)** of controls inside a gallery are scoped. See [accessibility properties](properties-accessibility.md) to learn more.

powerapps-docs/maker/canvas-apps/controls/control-image.md

@@ -142,11 +142,13 @@ If you add one or more **Image** controls to your app, you can show individual i
 * **[AccessibleLabel](properties-accessibility.md)** must be empty or the empty string **""**, if the graphic is purely for decoration. This causes screen readers to ignore the graphic.
 * **[AccessibleLabel](properties-accessibility.md)** can be empty or the empty string **""**, if the graphic provides redundant information.
     * For example, an **Image** of gears with its **[AccessibleLabel](properties-accessibility.md)** set to **Settings**. This image is not used as a button. It is next to a **[Label](control-text-box.md)** that also says **Settings**. Screen readers will read the image as **Settings**, and the label as **Settings** again. This is unnecessarily verbose. In this case, the **Image** does not need an **[AccessibleLabel](properties-accessibility.md)**.
+
 > [!IMPORTANT]
 > Screen readers will always read **Image**s that have **[TabIndex](properties-accessibility.md)** of zero or greater, even if **[AccessibleLabel](properties-accessibility.md)** is empty. This is because they are rendered as buttons. If no **[AccessibleLabel](properties-accessibility.md)** is provided, screen readers will simply read the graphic as **button**.
 
 ### Keyboard support
 * **[TabIndex](properties-accessibility.md)** must be zero or greater, if the graphic is used as a button. This allows keyboard users to navigate to it.
 * Focus indicators must be clearly visible, if the graphic is used as a button. Use **[FocusedBorderColor](properties-color-border.md)** and **[FocusedBorderThickness](properties-color-border.md)** to achieve this.
+
 > [!NOTE]
 > When **[TabIndex](properties-accessibility.md)** is zero or greater, the **Image** is rendered as a button. There is no change to the visual appearance, but screen readers will correctly identify the image as a button. When **[TabIndex](properties-accessibility.md)** is less than zero, the **Image** is identified as an image.

powerapps-docs/maker/canvas-apps/controls/control-list-box.md

@@ -164,5 +164,6 @@ This is in addition to the [standard color contrast requirements](../accessible-
 ### Keyboard support
 * **[TabIndex](properties-accessibility.md)** must be zero or greater so that keyboard users can navigate to it.
 * Focus indicators must be clearly visible. Use **[FocusedBorderColor](properties-color-border.md)** and **[FocusedBorderThickness](properties-color-border.md)** to achieve this.
+
 > [!NOTE]
 > The tab key navigates to or away from the **List box**. Arrow keys navigate the contents of the **List box**.

powerapps-docs/maker/canvas-apps/controls/control-pen-input.md

@@ -95,9 +95,11 @@ There must be adequate color contrast between:
 
 ### Screen reader support
 * **[AccessibleLabel](properties-accessibility.md)** should be present.
+
 > [!IMPORTANT]
 > **Pen input** is not accessible to screen reader users. Always provide an alternative form of input. For example, if a sketch is required, consider adding an **[Add picture](control-add-picture.md)** control for users to upload an image. Both methods can be offered and the user can choose the one they are more comfortable with.
 
 ### Keyboard support
+
 > [!IMPORTANT]
 > **Pen input** is not accessible to keyboard users. Always provide an alternative form of input. For example, if a signature is required, consider adding a **[Text input](control-text-input.md)** for users to enter their name. Both methods can be offered and the user can choose the one they are more comfortable with.

powerapps-docs/maker/canvas-apps/controls/control-pie-chart.md

@@ -98,6 +98,7 @@ There must be adequate color contrast between:
 
 ### Screen reader support
 * There must be a **[Label](control-text-box.md)** immediately before the chart graphic to serve as the title.
+
 > [!NOTE]
 > Chart graphics and **Legend** are hidden from screen reader users. As an alternative, a tabular form of the data is presented to them. They can also cycle through buttons that select data in the chart.
 
@@ -108,5 +109,6 @@ There must be adequate color contrast between:
 
 ### Keyboard support
 * **[TabIndex](properties-accessibility.md)** must be zero or greater so that keyboard users can navigate to it.
+
 > [!NOTE]
 > When keyboard users navigate to the chart, they can cycle through buttons that select data in the chart.

powerapps-docs/maker/canvas-apps/controls/control-rating.md

@@ -99,12 +99,14 @@ This is in addition to the [standard color contrast requirements](../accessible-
 
 ### Screen reader support
 * **[AccessibleLabel](properties-accessibility.md)** must be present.
+
 > [!NOTE]
 > Screen readers treat the **Rating** control as radio buttons.
 
 ### Keyboard support
 * **[TabIndex](properties-accessibility.md)** must be zero or greater so that keyboard users can navigate to it.
 * Focus indicators must be clearly visible. Use **[FocusedBorderColor](properties-color-border.md)** and **[FocusedBorderThickness](properties-color-border.md)** to achieve this.
 * Consider using a different control if there are too many stars. It can be tedious to navigate with a keyboard and difficult to select accurately with a touch screen.
+
 > [!NOTE]
 > The same keyboard interactions for radio buttons can be used on **Rating**.

powerapps-docs/maker/canvas-apps/controls/control-screen.md

@@ -77,5 +77,6 @@ In addition to text, consider checking color contrast with essential graphical o
 
 ### Screen reader support
 * There must be a meaningful name for each **Screen**. The screen name can be viewed and edited in the same way as other controls: in the tree view of the controls pane or in the header of the properties pane.
+
 > [!NOTE]
 > When a new **Screen** is loaded, screen readers will announce its name.