Merge branch 'master' of https://github.com/Lauragra/sp-dev-docs

Author: Lauragra

docs/apis/communication-site-creation-rest.md

@@ -2,9 +2,6 @@
 
 Learn how to create and get the status of a new modern SharePoint Communication site with the REST interface.
 
-> [!NOTE]
-> There is a known bug with this API which is blocking completely this behavior. Fix will be rolling gradually to SharePoint Online by end of October 2017.
-
 ## Prerequisites
 
 This topic assumes that you are already familiar with the topics Get to know the SharePoint REST service and Complete basic operations using SharePoint REST endpoints. It does not provide code snippets.

docs/declarative-customization/column-formatting.md

@@ -7,7 +7,7 @@ Before you get started, make sure that you're familiar with the following:
 - [Using the Client Object Model](https://msdn.microsoft.com/en-us/library/ff798388.aspx)
 - [Common Programming Tasks in the Managed Client Object Model](https://msdn.microsoft.com/en-us/library/ee537013.aspx)
 
-You will also need to install the [Microsoft.SharePointOnline.CSOM](https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/) NuGet package (version 16.1.6906.1200 or later).
+You will also need to reference the [Microsoft.SharePointOnline.CSOM](https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/) NuGet package (version 16.1.6906.1200 or later).
 
 ## CSOM code example
 
@@ -20,17 +20,19 @@ The following example shows how to create a __Microsoft.Online.SharePoint.Tenant
 
 ```C#
 using System.Security;
-using SPClient=Microsoft.SharePoint.Client;
+using Microsoft.SharePoint.Client;
 using Microsoft.Online.SharePoint.TenantAdministration;
 using Microsoft.Online.SharePoint.TenantManagement;
 
-SPClient.ClientContext ctx = new SPClient.ClientContext("https://mysite-admin.sharepoint.com/");
+...
+
+ClientContext ctx = new ClientContext("https://mysite-admin.sharepoint.com/");
 var pwd = "mypassword";
 var passWord = new SecureString();
 foreach (char c in pwd.ToCharArray()) passWord.AppendChar(c);
-ctx.Credentials = new SPClient.SharePointOnlineCredentials("[email protected]", passWord);
+ctx.Credentials = new SharePointOnlineCredentials("[email protected]", passWord);
 Tenant tenant = new Tenant(ctx);
-SPClient.ClientObjectList<ThemeProperties> themes = tenant.GetAllTenantThemes();
+ClientObjectList<ThemeProperties> themes = tenant.GetAllTenantThemes();
 ```
 
 ## Theme definition example
@@ -69,7 +71,7 @@ public class SPOTheme 
 
 ## Applying a theme
 
-The methods described in this section are used to manage the available themes in your tenant. To _apply_ a theme to a particular SharePoint website, use the [SPWeb.ApplyTheme](https://msdn.microsoft.com/en-us/library/office/jj251358.aspx) method of the [Microsoft.SharePoint.Client.Web](https://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.client.web.aspx) class.
+There's currently no supported API to programmatically apply a theme to specific site.
 
 ## Methods/properties of the Microsoft.Online.SharePoint.TenantAdministration.Tenant class
 
@@ -118,7 +120,7 @@ __Return type:__ ClientResult<bool>
 
 ## Methods of the Microsoft.Online.SharePoint.TenantManagement.Tenant class
 
-Use the following methods to manage themes in a multitenant environment.
+These are alternative APIs to manage your themes in tenant level.
 
 ### AddTenantTheme public method
 Add a theme to the tenant.

docs/declarative-customization/site-theming/sharepoint-site-theming-csom.md

@@ -124,20 +124,6 @@ C:\> Get-SPOTheme -Name "Custom Cyan" | ConvertTo-Json
 ```
 Note that this example uses the PowerShell _ConvertTo-Json_ filter to display the theme in JSON format.
 
-To see all the themes currently available in the tenant store, use **Get-SPOTheme** with no arguments.
-
-```powershell
-c:\> Get-SPOTheme
-Blue
-Orange
-Red
-Purple
-Green
-Gray
-Dark Yellow
-Dark Blue
-Custom Cyan
-```
 ## Remove-SPOTheme
 
 The **Remove-SPOTheme** cmdlet removes a theme from your tenant store. For example, this cmdlet removes the "Custom Cyan" theme that was used in the previous examples.

docs/declarative-customization/site-theming/sharepoint-site-theming-powershell.md

@@ -133,3 +133,4 @@ RestRequest("/_api/thememanager/GetTenantThemingOptions");
 * [SharePoint site theming: CSOM](sharepoint-site-theming-csom.md)
 * [Complete basic operations using SharePoint REST endpoints](https://dev.office.com/sharepoint/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md)
 * [Making REST calls with C# and JavaScript for SharePoint 2013](http://www.microsoft.com/resources/msdn/en-us/office/media/video/video.mdl?cid=sdc&from=mscomsdc&VideoID=4e4cc094-ff69-405b-852f-2ac7c41293c5)
+

docs/declarative-customization/site-theming/sharepoint-site-theming-rest-api.md

@@ -0,0 +1,137 @@
+---
+title: Accessibility in SharePoint web part design
+ms.date: 9/25/2017 
+---
+
+<!--Based on how rough this content is in it's current state, i'm going to pull it from this initial release so we can edit and better prepare. -->
+
+
+
+
+# Accessibility in SharePoint web part design
+
+Developing an equal experience that meets all users' unique visual, hearing, dexterity, cognitive, and speech needs is an important component of SharePoint web part design. Accessible design applies not only to people with disabilities, but also to potential situational impairments. Accessible design is good design.
+
+## Accessibility guidelines
+
+<!-- Make sure that this is an external resource that folks can access. Original link was to a OneNote file. -->
+All Microsoft products must meet the requirements listed in the [Microsoft Accessibility Standards](https://microsoft.sharepoint.com/teams/msenable/Pages/MASDetails.aspx
+"Link to Microsoft Accesssibility Standards").  
+
+<!-- Fabric components are not designed to be accessible already? And, shouldn't components that aren't based on Fabric also be accessible? -->
+
+If you're building a dialog box, file picker, or any other [Office UI Fabric](https://dev.office.com/fabric#/components) component, follow the guidance in this article to ensure that your content is accessible. 
+
+<!-- Not sure why we have that link? It currently goes to the OneNote file. Where is the Common UI Controls content? Is that related to accessibility? -->
+
+[Common UI Controls](https://microsoft.sharepoint.com/teams/STS/_layouts/OneNote.aspx?id=%2Fteams%2FSTS%2FShared%20Documents%2FSP%20Accessibility%2FAccessibility%20Guidance&wd=target%28Accessibility%20101.one%7C0005C142-938C-4411-B543-B9F4199E19B3%2FEverything%20you%20need%20to%20know%20about%20Accessibility%7CE099AFE3-8804-4E1F-BA50-99493AB8A3D0%2F%29 "Link to Common UI Controls")
+
+## Accessibility testing
+
+<!-- FYI, I added links. Can we assume that our target audience uses the Edge browser? -->
+
+Test your web part first with [Narrator](https://support.microsoft.com/en-us/help/22798/windows-10-narrator-get-started) and Microsoft Edge, and then verify the accessibility experience with [JAWS](http://www.freedomscientific.com/Products/Blindness/JAWS).
+
+Narrator and Microsoft Edge are standards compliant. When you test with that combination, you are more likely to find issues, and you can validate that your site meets accessibility standards. 
+
+JAWS is the market leader in screen readers. JAWS includes features that can improve the accessibility of some websites that aren't as accessible in other screen readers. Therefore testing in JAWS might not ensure that your site meets all accessibility requirements. 
+ 
+You might also want to test for whatever combination of browser and screen reader has the greatest market share for your website.
+
+<!-- Delete? This doesn't seem like text that should be in externally published docs? 
+When suppliers test with JAWS, we ask them to repro identified bugs with Narrator and Edge. In the case a bug does not repro with Narrator/Edge it is sent to Mary Smith who works with VFO for a Jaws specific fix. 
+-->
+
+## Keyboard navigation
+
+<!-- Is this section telling people how to navigate via a keyboard, or how to design to optimize for keyboard navigation? If the former, . -->
+
+For some users, navigating a site via keyboard is more accessible. Power users also often rely on keyboard navigation. Use keyboard shortcuts such as tabs to go controls on the page, and use arrow keys to navigate inside controls.
+
+### Navigation between controls
+
+Each control is a tab stop. Within a control, the following rules apply:
+
+- In general, the first tab stop is the top left area of the control. The last tab stop is the bottom right control.
+- For modal surfaces, the last tab stop should be the commit actions.
+- For lists, the first tab stop should be the first item in the list, the next should be the commands, and then the navigation, settings, and so on.
+
+<!-- We should make sure the content in the accessibility topic is accessibible. ;) Please describe the information that the image conveys; something like this (also consider making the image an actual screen shot, that might be more clear):
+
+In the following image:
+The first tab is the list item.
+The second tab is the command.
+The third tab is the navigation.
+-->
+![Image that shows the tab stops on a SharePoint page](https://i.imgur.com/Vn3VosN.png)
+
+### Navigation within a control
+
+You can use arrow keys to move to items in a control, such as choices in a menu, commands in a command bar, or items in a list.
+
+<!-- This image is not very clear. Do you need to have the "blank" list box on the left? -->
+
+![Using arrow keys to navigate within a control](https://i.imgur.com/vF0Nk73.png)
+
+### Selecting the current item
+
+Use the space bar to select or deselect the item currently in focus in a control.
+
+![Using the space bar to select an item in a list](https://i.imgur.com/j3fBKPl.png)
+
+### Run a control
+
+Press **Enter** or the return key to run a control.
+
+![Press enter to run a control](https://i.imgur.com/s0nMPdT.png)
+
+### Leave a control
+
+Press **Escape** to exit a control and return to the container.
+
+![Pressing Escape to leave a control and return to the container](https://i.imgur.com/uD99zIX.png)
+
+### Go to the first or last item
+
+Press **Home** or **End** to go directly to the first or last item in a list, menu, and so on.
+
+![Pressing Home or End to go to the first or last item in a list](https://i.imgur.com/gGKsh74.png)
+
+
+## Screen reader navigation
+
+Users who have vision impairments rely on screen readers to navigate the site UI. 
+
+<!-- Narrator isn't a third-party product. This image needs more text/explanation; please also clarify the alt text. Is this section important, or can it be removed, given the previous mention of testing with Narrator and JAWS? Again, the intent/target audience for this information isn't clear - is it for the user, or the designer? Can you explain why this information is important from the designer's POV? -->
+
+![Screen reader navigation of a SharePoint page](https://i.imgur.com/ar23o3X.png)
+
+## Alt text and transcripts
+
+Use alt text to provide descriptions of images that can be consumed by screen readers. This is useful for vision-impaired users who cannot consume information visually. Make sure that your alt text is descriptive, keeping in mind that some readers are relying on a screen reader to access the information conveyed in the image. 
+
+Don't rely only on color to convey meaning; rely on both color and shape.
+
+To be fully compliant with accessibility standards, include alt text and a complete transcript of audio and video content on your site.
+
+## Minimum readable contrast
+
+A minimum level of contrast is essential to help users with vision impairments consume the content on the page. It is also important to aid readability in low light and glare situations. 
+
+<!-- Convert this image into a table, for accessibility. ;) -->
+
+![Neutral, Theme, and Alert colors for minimum readable contrast](https://i.imgur.com/L7pSF1w.png)
+
+
+## High contrast
+
+Use high contrast colors as a guide for color choices for components and states on the web. Windows computers only have the ability to detect whether a PC is running high contrast, or high contrast white. For this reason, use the default high contrast black setting for any high contrast, non-white theme.
+
+<!-- In the left part of the image, I think the title should be "High Contrast Black". -->
+
+![High contrast black and high contrast white settings](https://i.imgur.com/qvTFzd4.png)
+
+
+
+
+