This whitepaper is about enhanced usability of SharePoint with Discover Access. We observed several important accessibility improvements with Discover Access over standard SharePoint. For example, with Discover Access enabled: the heading order is consistent with WCAG 2.0 standards; the people picker is enhanced such that it is accessible; rich text and wiki editing controls are made to be 508 and WCAG 2.0 compliant; and there is highlighted focus for all links, buttons and form fields, which makes SharePoint keyboard navigable.
Microsoft SharePoint, widely used by the Department of Defense as a document repository and collaboration tool can be difficult to use in low-bandwidth environments because of latency in driving its graphical user interface (GUI). Discover Technologies solves this problem with Discover Access for SharePoint by stripping out all GUI and other bandwidthhungry features to create a solution that slashes navigational latency by 5 to 7 times.
The new IT environment often includes a combination of on-premise and off-premise applications. Another way of describing that environment is the private cloud plus the public cloud, which Gartner defines as a “hybrid cloud.”
One application that is likely to remain on-premise is enterprise content management. Large enterprises have invested significant money and manpower in their ECM systems and are simply not ready to abandon them and rely solely on cloud applications.
The approach some organizations are adopting is “hybrid ECM.” As defined by Gartner, hybrid ECM describes an environment in which some enterprise content is stored, managed, and shared in a traditional ECM application while other enterprise content is stored, managed, and shared in a public cloud application.
This white paper has been created for the stakeholders who are responsible for migrating from one ECM system to another, including management, source, and target system experts, and any third-party contractors. Specifically, this white paper will provide a detailed best practices guide to the first step in a four-step process of planning and executing an ECM migration. We consider these the four critical steps, or phases, of planning and executing a successful ECM migration: 1) Early pre-migration planning; 2) Evaluation of migration products and solutions; 3) Migration planning; and 4) Testing.
One of the most critical issues in web applications today is that there is a subset of users who find web sites difficult, if not impossible to navigate. This audience includes but is not limited to, people who are blind, have low vision, as well as people with dexterity impairments and cognitive disabilities. Many web applications take advantage of the latest technology to provide flashy, interactive user interfaces that are appealing to many users but put little or no emphasis on accessibility and usability.
In order to solve the problem, the interface for SharePoint must be redesigned to meet Section 508 and Web Content Accessibility Guidelines (WCAG) 2.0 AA compliance. Discover Access for SharePoint™ fills the gap between accessibility and usability and provides blind and low vision workers with a comparable SharePoint user experience to that of sighted users.
When the move to Office 365 is not a desirable option and companies want to retain certain levels of control over the data, configuration of the environment and have an ability to deploy third-party components, organizations can migrate to the cloud based virtual machines and virtual network services that allow them to install and operate an Internet-facing or intranet-only SharePoint Server farm with SQL Server Always-On Availability Groups in Azure. SharePoint provides an extensive set of features to support a wide range of collaborative activities for an organization. However, these features and capabilities can make planning and design a challenge due to the following:
SharePoint 2013 has evolved into a fully matured content, records and documents management system. One of the key pillars of the SharePoint platform is search. It is pervasive throughout the SharePoint platform and many key components in SharePoint 2013 are powered by search, with the inclusion of several of the out-of-the-box web parts that are fully dependent on the search to provide an enriched user experience.
Years ago, companies were faced with the problem of what to do with the ever growing accumulation of data that they could not discard; either because they had to store this data based on industry regulations or they just simply stored it following the powerful statement that “knowledge is power.” With the cost of storage not being an issue anymore, companies continued gathering and storing the data and content in all of its various forms – especially unstructured content such as emails, instant messages, electronic and paper documents, images, video, voice and web pages. All of which make up the majority of all data stored by IT departments and service providers and this is doubling every two years or sooner. In the information age, easy access to content or data and the ability to manage information throughout its lifecycle is mission-critical.
An upgrade to a newer version of SharePoint is a great undertaking for IT. However, besides the IT department involvement, training and end-user adoption must be addressed while business users struggle to continue to use the environment and stay productive. Training and end-user adoption can be expensive and during this period and SharePoint users may not be as productive as when they were working within the old, familiar version of the platform.
The introduction of Microsoft’s new Workflow Manager, and the separation of the workflow engine from SharePoint 2013, have downstream impacts on users of business process management software (BPMS) like Nintex Workflow and K2 blackpearl®.
For users of SharePoint 2010 looking to upgrade their Nintex Workflow solutions to use the new platform and its features, staying current with SharePoint can mean refactoring workflow processes or even shifting Nintex solutions altogether. Although it is possible for SharePoint 2010-based Nintex solutions to run “as-is” in SharePoint 2013, this capability may not extend beyond the 2013 edition.