Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 15 additions & 18 deletions docs/general-development/accessibility-in-sharepoint.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Accessibility in SharePoint
description: Learn about the features, products, and services that make SharePoint accessible for people with disabilities, and find developer resources that can help you design and build apps and websites that support key accessibility scenarios.
ms.date: 09/25/2017
ms.date: 04/14/2026
ms.assetid: c9106d47-c523-49c1-b9f1-cdd7420abd5e
ms.localizationpriority: medium
---
Expand All @@ -14,7 +14,7 @@ Accessible technology enables users to interact with computers and applications



Microsoft strives to build products that are accessible to everyone. For information about these efforts, see the [Microsoft Accessibility](https://www.microsoft.com/enable/default.aspx) site.
Microsoft strives to build products that are accessible to everyone. For information about these efforts, see the [Microsoft Accessibility](https://www.microsoft.com/accessibility) site.
## Accessibility features in SharePoint
<a name="bkmk_AccessibilitySP2013"> </a>

Expand All @@ -27,13 +27,13 @@ For more information about accessibility features in SharePoint, see the followi



- [Accessibility features in SharePoint products](https://office.microsoft.com/sharepoint-foundation-help/accessibility-features-in-sharepoint-products-HA102772892.aspx?CTT=1)
- [Accessibility features in SharePoint products](https://support.microsoft.com/sharepoint)


- [Keyboard shortcuts in SharePoint Online](https://support.office.com/article/keyboard-shortcuts-in-sharepoint-online-466e33ee-613b-4f47-96bb-1c20f20b1015)


Users who have site administrator responsibilities typically use the SharePoint Central Administration site to manage deployments. A mouse and keyboard are the typical devices that you use to interact with Central Administration. For more information about accessibility for administrators and other IT pros in SharePoint, see [Accessibility for SharePoint](https://technet.microsoft.com/library/jj219681.aspx).
Users who have site administrator responsibilities typically use the SharePoint Central Administration site to manage deployments. A mouse and keyboard are the typical devices that you use to interact with Central Administration. For more information about accessibility for administrators and other IT pros in SharePoint, see [Accessibility for SharePoint](https://learn.microsoft.com/SharePoint/accessibility-guidelines).



Expand All @@ -49,7 +49,7 @@ As you design and build apps and solutions for SharePoint, you should implement



For information about developing accessible applications and websites, see [Resources for Designing Accessible Applications](https://msdn.microsoft.com/library/426bf023-bb34-43c4-9edb-c307191c8170%28Office.15%29.aspx) in the Visual Studio documentation.
For information about developing accessible applications and websites, see [Resources for Designing Accessible Applications](https://learn.microsoft.com/previous-versions/visualstudio/visual-studio-2015/ide/reference/resources-for-designing-accessible-applications?view=vs-2015) in the Visual Studio documentation.



Expand All @@ -58,23 +58,23 @@ For information about Windows app development and providing accessibility in Win



- [Accessibility](https://msdn.microsoft.com/windows/bb735024.aspx)
- [Accessibility](https://learn.microsoft.com/windows/apps/develop/accessibility)


- [Design for Accessibility (Windows Store apps)](https://msdn.microsoft.com/library/windows/apps/hh700407.aspx)
- [Design for Accessibility (Windows Store apps)](https://learn.microsoft.com/windows/apps/design/accessibility/accessibility-overview)


- [Meeting basic accessibility requirements (Windows Store apps using JavaScript and HTML)](https://msdn.microsoft.com/library/windows/apps/hh700338.aspx)
- [Meeting basic accessibility requirements (Windows Store apps using JavaScript and HTML)](https://learn.microsoft.com/previous-versions/windows/apps/hh700338(v=win.10))


- [Accessibility in Windows Store apps using JavaScript](https://msdn.microsoft.com/library/windows/apps/hh452702.aspx)
- [Accessibility in Windows Store apps using JavaScript](https://learn.microsoft.com/previous-versions/windows/hh452702(v=win.10))



## Accessibility features in Visual Studio
<a name="bkmk_AccessVS"> </a>

If you build solutions and apps for SharePoint in Visual Studio, you will find that Visual Studio 2012 provides default shortcut key combinations to help you navigate and code within the IDE. For more information about accessibility features in Visual Studio, see [Accessibility Features of Visual Studio](https://msdn.microsoft.com/library/aa1ada29-4d93-4bf0-af8b-03633fcb0fba%28Office.15%29.aspx). For a list of Visual Studio keyboard shortcuts, see [Pre-defined Keyboard Shortcuts](https://msdn.microsoft.com/library/c2c64648-00f8-4e48-a8a0-96c67cfd968c%28Office.15%29.aspx).
If you build solutions and apps for SharePoint in Visual Studio, you will find that Visual Studio 2012 provides default shortcut key combinations to help you navigate and code within the IDE. For more information about accessibility features in Visual Studio, see [Accessibility Features of Visual Studio](https://learn.microsoft.com/previous-versions/visualstudio/visual-studio-2015/ide/reference/accessibility-features-of-visual-studio?view=vs-2015). For a list of Visual Studio keyboard shortcuts, see [Pre-defined Keyboard Shortcuts](https://learn.microsoft.com/previous-versions/visualstudio/visual-studio-2015/ide/default-keyboard-shortcuts-for-frequently-used-commands-in-visual-studio?view=vs-2015).



Expand All @@ -93,7 +93,7 @@ SharePoint administrators and users depend on the accessibility features that we
|**Browser**|**For more information**|
|:-----|:-----|
|Internet Explorer <br/> | [Accessibility in Internet Explorer 9](https://www.microsoft.com/enable/products/ie9/default.aspx) <br/> |
|Firefox <br/> | [Accessibility features in Firefox](https://go.microsoft.com/fwlink/p/?LinkId=275209) <br/> |
|Firefox <br/> | [Accessibility features in Firefox](https://support.mozilla.org/kb/accessibility-features-firefox?redirectslug=accessibility-features-firefox-make-firefox-and-we) <br/> |
|Safari <br/> | [Safari Accessibility](https://go.microsoft.com/fwlink/p/?LinkId=275210) <br/> |
|Chrome <br/> | [Chrome Accessibility Technical Documentation](https://go.microsoft.com/fwlink/p/?LinkId=275211) <br/> |

Expand All @@ -102,16 +102,16 @@ SharePoint administrators and users depend on the accessibility features that we
<a name="bk_addresources"> </a>


- [Accessibility](https://msdn.microsoft.com/windows/bb735024.aspx)
- [Accessibility](https://learn.microsoft.com/windows/apps/develop/accessibility)


- [Microsoft Accessibility Resource Centers](https://www.microsoft.com/enable/centers/)


- [Guidelines and checklist for accessibility](https://msdn.microsoft.com/library/windows/apps/hh700325.aspx)
- [Guidelines and checklist for accessibility](https://learn.microsoft.com/previous-versions/windows/apps/hh700325(v=win.10))


- [SharePoint Add-ins UX design guidelines](https://msdn.microsoft.com/library/a4a8f53c-27d7-43dc-b6db-aa7b1f1c7d45%28Office.15%29.aspx)
- [SharePoint Add-ins UX design guidelines](https://learn.microsoft.com/sharepoint/dev/sp-add-ins/sharepoint-add-ins-ux-design-guidelines)


- [Develop SharePoint Add-ins](../sp-add-ins/sharepoint-add-ins.md)
Expand All @@ -123,7 +123,4 @@ SharePoint administrators and users depend on the accessibility features that we
- [Accessibility in Microsoft Products](https://www.microsoft.com/enable/products/default.aspx)


- [Accessibility for SharePoint](https://technet.microsoft.com/library/jj219681.aspx)



- [Accessibility for SharePoint](https://learn.microsoft.com/SharePoint/accessibility-guidelines)
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Build mobile apps for other platforms using SharePoint
description: Learn how to use Representational State Transfer (REST) to create a SharePoint mobile app for any platform.
ms.date: 09/25/2017
ms.date: 04/14/2026
ms.assetid: 017df869-44fb-4ffe-82fb-4654e01329ad
ms.localizationpriority: high
---
Expand All @@ -10,13 +10,16 @@ ms.localizationpriority: high
# Build mobile apps for other platforms using SharePoint
Learn how to use Representational State Transfer (REST) to create a SharePoint mobile app for any platform.

> [!IMPORTANT]
> Building mobile apps using the Windows Phone SDK and the SharePoint Windows Phone SDK is a legacy approach. Windows Phone is discontinued. For new mobile solutions targeting SharePoint, consider using [SharePoint Framework (SPFx)](../spfx/sharepoint-framework-overview.md), [Microsoft Graph](https://learn.microsoft.com/graph/overview), or cross-platform frameworks (React Native, Flutter, etc.) with SharePoint REST or Microsoft Graph APIs.

Mobile devices have become more powerful and easy to use nowadays. Laptops, netbooks, tablet PCs, and mobile phones provide workers access to the information and applications that they need to do their jobs. And developing applications for mobile devices is now easier than ever. As a result, more and more business scenarios demand integrating client applications together with their business processes. This article describes how to integrate mobile client apps together with SharePoint. You can create a mobile app to browse SharePoint content from any location and connect with SharePoint lists and libraries to access data.




To develop a mobile app that interacts with SharePoint, you can use common services that can be accessed using open protocols. SharePoint Foundation 2010 introduced the client object models, which enabled developers to perform remote communication with SharePoint by using the web programming technology of their choice: .NET Framework, Microsoft Silverlight, or JavaScript. SharePoint introduces a Representational State Transfer (REST) service that is fully comparable to the client object models. In SharePoint, nearly every API in the client object models will have a corresponding REST endpoint. Now, developers can interact remotely with the SharePoint object model by using any technology that supports REST web requests. REST can be consumed by any programming language that you want to use for your mobile application development.
You can perform basic create, read, update, and delete (CRUD) operations by using the REST interface provided by SharePoint. REST exposes all of the SharePoint entities and operations that are available in the other SharePoint client APIs. One advantage of using REST is that you don't have to add references to any SharePoint libraries or client assemblies. Instead, you make HTTP requests to the appropriate endpoints to retrieve or update SharePoint entities, such as webs, lists, and list items. For a thorough introduction to the SharePoint REST interface and its architecture, see [Use OData query operations in SharePoint REST requests](https://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72%28Office.15%29.aspx).
To develop a mobile app that interacts with SharePoint, you can use common services that can be accessed using open protocols. SharePoint Foundation 2010 introduced the client object models, which enabled developers to perform remote communication with SharePoint by using the web programming technology of their choice: .NET Framework or JavaScript. SharePoint introduces a Representational State Transfer (REST) service that is fully comparable to the client object models. In SharePoint, nearly every API in the client object models will have a corresponding REST endpoint. Now, developers can interact remotely with the SharePoint object model by using any technology that supports REST web requests. REST can be consumed by any programming language that you want to use for your mobile application development.
You can perform basic create, read, update, and delete (CRUD) operations by using the REST interface provided by SharePoint. REST exposes all of the SharePoint entities and operations that are available in the other SharePoint client APIs. One advantage of using REST is that you don't have to add references to any SharePoint libraries or client assemblies. Instead, you make HTTP requests to the appropriate endpoints to retrieve or update SharePoint entities, such as webs, lists, and list items. For a thorough introduction to the SharePoint REST interface and its architecture, see [Use OData query operations in SharePoint REST requests](https://learn.microsoft.com/sharepoint/dev/sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests).



Expand Down Expand Up @@ -75,22 +78,22 @@ In choosing an HTTP request to use, you should also consider the following:
- Use **PUT**, **PATCH**, and **MERGE** operations to update existing SharePoint objects. Any service endpoint that represents an object property **set** operation supports both **PUT** requests and **MERGE** requests. For **MERGE** requests, setting properties is optional; any properties that you do not explicitly set retain their current property. But for **PUT** commands, any properties you do not explicitly set are set to their default properties. In addition, if you do not specify all settable properties in object updates when you use HTTP **PUT** commands, the REST service returns an exception.


- Use the HTTP **DELETE** command against the specific endpoint URL to delete the SharePoint object represented by that endpoint. For recyclable objects, such as lists, files, and list items, this results in a **Recycle** operation. For more information, see [Get to know the SharePoint REST service](https://msdn.microsoft.com/library/2de035a0-ac75-43bd-9665-5c5a59c4c590%28Office.15%29.aspx).
- Use the HTTP **DELETE** command against the specific endpoint URL to delete the SharePoint object represented by that endpoint. For recyclable objects, such as lists, files, and list items, this results in a **Recycle** operation. For more information, see [Get to know the SharePoint REST service](https://learn.microsoft.com/sharepoint/dev/sp-add-ins/get-to-know-the-sharepoint-rest-service?tabs=csom).



## Authenticate users to SharePoint
<a name="BuildMobileAppsInSharePoint2013ForNonWindowsPhone_AuthenticatingNonWindowsAppForSharePoint"> </a>

To authenticate your mobile app with SharePoint, you can use the MS-OFBA protocol. For more information, see [[MS-OFBA]: Office Forms Based Authentication Protocol Specification](https://msdn.microsoft.com/library/30c7bbe9-b284-421f-b866-4e7ed4866027%28Office.15%29.aspx). The protocol client is configured to store and transmit cookies. The protocol client relies on the remote protocol server to set the user's identity as one or more HTTP cookies. After the user's identity is established, the client then sends each cookie with each subsequent HHT request.
To authenticate your mobile app with SharePoint, you can use the MS-OFBA protocol. For more information, see [[MS-OFBA]: Office Forms Based Authentication Protocol Specification](https://learn.microsoft.com/openspecs/sharepoint_protocols/ms-ofba/30c7bbe9-b284-421f-b866-4e7ed4866027). The protocol client is configured to store and transmit cookies. The protocol client relies on the remote protocol server to set the user's identity as one or more HTTP cookies. After the user's identity is established, the client then sends each cookie with each subsequent HHT request.



When a user signs in to SharePoint, the user's token is validated and then used to sign in to SharePoint. The user's token is a security token that is issued by an identity provider. SharePoint supports several kinds of authentication. For more information, see [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md). To authenticate a user, you can use the REST interface. The authorization process verifies that an authenticated subject (an app or a user the app is acting on behalf of.md) has permission to perform certain operations or to access specific resources (for example, a list or a SharePoint document folder.md).



OData lets you access a data source, such as a database, by browsing to a specially constructed URL. This allows for a simplified approach for connecting to, and working with, data sources that are hosted within an organization. OData is a protocol that uses HTTP, Atom, and JavaScript Object Notation (JSON) to enable developers to write applications that communicate with an ever-growing number of data sources. Microsoft supports the creation of this standard as a way to enable the exchange of data between applications and data stores that can be accessed from the web. The new OData connector enables SharePoint to communicate with OData providers. For more information, see [Open Data Protocol](http://www.odata.org).
OData lets you access a data source, such as a database, by browsing to a specially constructed URL. This allows for a simplified approach for connecting to, and working with, data sources that are hosted within an organization. OData is a protocol that uses HTTP, Atom, and JavaScript Object Notation (JSON) to enable developers to write applications that communicate with an ever-growing number of data sources. Microsoft supports the creation of this standard as a way to enable the exchange of data between applications and data stores that can be accessed from the web. The new OData connector enables SharePoint to communicate with OData providers. For more information, see [Open Data Protocol](https://www.odata.org/).



Expand Down Expand Up @@ -286,7 +289,7 @@ headers:

```

For more information, see [Complete basic operations using SharePoint REST endpoints](https://msdn.microsoft.com/library/e3000415-50a0-426e-b304-b7de18f2f7d9%28Office.15%29.aspx).
For more information, see [Complete basic operations using SharePoint REST endpoints](https://learn.microsoft.com/sharepoint/dev/sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints).



Expand All @@ -299,7 +302,6 @@ For more information, see [Complete basic operations using SharePoint REST endp
- [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md)
- [Use OData query operations in SharePoint REST requests](https://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72%28Office.15%29.aspx)
- [Get to know the SharePoint REST service](https://msdn.microsoft.com/library/2de035a0-ac75-43bd-9665-5c5a59c4c590%28Office.15%29.aspx)
- [Open Data Protocol](http://www.odata.org/)
- [Open Data Protocol](https://www.odata.org/)
- [Authorization and authentication of SharePoint Add-ins](https://msdn.microsoft.com/library/bde5647a-fff1-4b51-b67b-2139de79ce4a%28Office.15%29.aspx)
- [Windows Phone SDK 8.0](https://www.microsoft.com/download/details.aspx?id=35471)
- [Microsoft SharePoint SDK for Windows Phone 8](https://www.microsoft.com/download/details.aspx?id=36818)
Original file line number Diff line number Diff line change
@@ -1,14 +1,18 @@
---
title: Changes in the BDC model schema for SharePoint
description: Learn what has changed in SharePoint for the BDC model schema.
ms.date: 09/25/2017
ms.date: 04/14/2026
ms.assetid: 882ea867-9acb-4313-99c9-865a523b72fd
ms.localizationpriority: medium
---


# Changes in the BDC model schema for SharePoint
Learn what has changed in SharePoint for the BDC model schema.

> [!IMPORTANT]
> Business Connectivity Services (BCS) and BDC model schema are considered legacy technologies in modern SharePoint development. For new solutions, we recommend using SharePoint Framework (SPFx), Microsoft Graph, and Power Platform integrations.

The number of changes in the schema (BDCMetadata.xsd) for creating BDC models in SharePoint is relatively small. But these changes have significant impact on the feature set offerings of Business Connectivity Services (BCS).


Expand Down
Loading