When testing apps for accessibility, we often find that important issues are overlooked during the development process, omitting a large portion of users from being able to use an app effectively. Most of these problems are simple to fix and can mean the difference between a friendly or frustrating user experience.
SharePoint is Microsoft’s answer to a Content Management System (CMS), used by organisations to collaborate and share documents on a browser-based platform. In recent years, Microsoft has made efforts to improve the accessibility capability of their CMS by adding a number of new accessibility features in SharePoint 2013 and much more recently in the beta version of SharePoint 2016. While these improvements are excellent steps forward, organisations still need to be wary that their SharePoint intranet may not be configured to have the best accessibility available. Here are 5 features that you can use in SharePoint 2016 that will improve the accessibility of your CMS.
A common approach for web development teams is to work in an agile environment where applications and sites are built, checked, and modified in an iterative way as the work progresses. This is opposed to a more formal waterfall approach with distinctive stages and formalised review sessions. For effective creation of an accessible website or application, it means that your “scrum” team needs to have good working accessibility knowledge and skills that they can apply and include as the definition of “done”.