Merge pull request #313 from MicrosoftDocs/master

4/4 PM Publish

Author: v-alje

powerapps-docs/maker/TOC.yml

@@ -115,6 +115,8 @@
         href: ./canvas-apps/add-scrolling-screen.md
       - name: Build a global app
         href: ./canvas-apps/global-apps.md
+      - name: Create Accessible Apps
+        href: ./canvas-apps/accessible-apps.md
     - name: Manage your app
       items:
       - name: Introduction to powerapps.com
@@ -222,12 +224,12 @@
     - name: Delete a custom entity
       href: ./common-data-service/data-platform-delete-entity.md
   - name: Tutorials
-    items: 
+    items:
     - name: Create a custom entity that has components
       href: ./common-data-service/create-custom-entity.md
   - name: Samples and resources
     href: ./common-data-service/samples-resources.md
   - name: For Developers
     href: ../developer/common-data-service/TOC.yml
 - name: Common Data Model
-  href: ../common-data-model/overview.md    
+  href: ../common-data-model/overview.md

powerapps-docs/maker/canvas-apps/accessible-apps.md

@@ -0,0 +1,67 @@
+---
+title: Create Accessible Apps | Microsoft Docs
+description: How to make apps accessible for people with disabilities
+services: ''
+suite: powerapps
+documentationcenter: na
+author: fikaradz
+manager: anneta
+editor: ''
+tags: ''
+
+ms.service: powerapps
+ms.devlang: na
+ms.topic: article
+ms.tgt_pltfrm: na
+ms.workload: na
+ms.date: 04/03/2018
+ms.author: fikaradz
+
+---
+# Create accessible apps
+An accessible app will allow users with vision, hearing and other impairments to successfully use the app.  In addition to being a requirement for many governments and organizations, following the below guidelines increases usability for all users, regardless of their abilities.
+
+## Layout and color
+Common sense and uncomplicated design helps apps be more accessible to all users.  When doing heavy customization of apps take note of the below suggestions.  PowerApps themes are by default accessible.
+- Ensure all elements are clearly visible and text is of sufficient size.  All content must be easily read and understood by the naked eye.
+- Avoid using the visibility property of items to bring an element into view.  If you need to show something conditionally, create the content in a new screen and navigate to it and back.
+- Ensure input elements are labeled on the screen. **[AccessibilityLabel](controls/properties-accessibility.md)** property defines what the screen reader will announce.
+- If customizing colors, ensure the contrast of text:background is 4.5:1 or greater.  Software tools that assist this process are readily available.
+- Ensure layout follows a logical flow when read top-bottom, left to right.
+
+
+## Keyboard support
+When testing your app's accessibility, ensure the app can be used with the keyboard only, the accessibility modes on iOS and Android, as well as navigated successfully with the screen reader enabled.
+
+For keyboard navigation (with or without the screen reader) ensure that a logical order is followed when using the TAB key to navigate to input fields by setting each control's **[TabIndex](controls/properties-accessibility.md)** property:
+- Label, Image, Icon, Shape contols - if they represent interactive elements (i.e.buttons) set TabIndex to 0; if they are decorative elements or text, set TabIndex to -1.
+- Avoid setting tab index higher than zero.
+
+## Screen reader support
+The following software combinations are the supported recommendations for consuming PowerApps with a screen reader:
+
+- **Windows**: Edge / Narrator
+- **macOS**: Safari / VoiceOver
+- **Android**: PowerApps app / Talkback
+- **iOS**: PowerApps app / VoiceOver
+
+To ensure a satisfying experience with the screen reader it is recommended to:
+
+- Ensure all input controls have the **[AccessibilityLabel](controls/properties-accessibility.md)** property set.
+- For images set **[AccessibilityLabel](controls/properties-accessibility.md)** to an appropriate description.
+  - If a picture is not used as a button or a link (i.e. icon is there just for the decoration) and should not be read by the screen reader, make sure the **[AccessibilityLabel](controls/properties-accessibility.md)** is empty or not set.
+  - If a picture or an icon is used as a button, then set **[TabIndex](controls/properties-accessibility.md)** to 0 and **[AccessibilityLabel](controls/properties-accessibility.md)** to the link description.
+
+
+## Multimedia
+Ensure all videos are captioned and a transcript of all audio recordings is available to the user.  **Video** control suppports closed captions  in WebVTT format via the **ClosedCaptionsUrl** property.
+
+Note that with the screen reader enabled, **Timer** does not announce button text, but how much time has passed.  Announcements can't be turned off, even if timer is hidden with low opacity.
+
+## Working with signatures
+If you have a signature field that uses the PenInput control you need to enable an alternative method of signature input.  The recommended way is to show a TextInput control where a user can type their name.  Ensure the signing instructions are placed in the **[AccessibilityLabel](controls/properties-accessibility.md)** property and the control is placed close to the Pen input - to the right or immediately below.
+
+
+
+Related:
+**[Accessibility properties](controls/properties-accessibility.md)**