Common barriers and accessibility needs

Completed

When creating your SharePoint site, usability is critical. Think of it this way: if you can't easily move around your site to get what you want or accomplish what you need to do, how can others?

In this unit, we'll explore some of the common barriers to access and the type of accessibility needs that people with disabilities may have. This helps to have a clearer understanding of customizations you may need to make to ensure your SharePoint site is inclusive to all users.

We'll now explore examples of accessibility needs for some disabilities, including:

  • Vision
  • Hearing
  • Mobility
  • Learning
  • Mental Health
  • Neurodiversity

Vision

Some considerations for browsing a SharePoint site for people with vision disabilities such as blindness and low vision are:

  • Keyboard interaction to easily navigate a page with the keyboard alone, such as pressing the tab key to move between all interactive elements.
  • Name and role of elements that provide information on how to interact with the control, such as a link or button.
  • Larger typefaces that make text easier to read; black or high-contrast text.
  • A predictable tab order and landmarks on a web page (including dialog boxes) that enable users to build a mental model of the page, so they stay oriented and not lose track of where they are.
  • Alternatives to visuals (images, icons, etc.), and descriptive alternative text (alt text) for all images.
  • Audio descriptions for videos. And settings for video players, such as the ability to turn off autoplay, so a video's audio and the audible feedback from a screen reader don't overlap.
  • Inclusive language that doesn't always refer to "seeing" an element. For example, instead of saying, "See XYZ," you could say, "XYZ is included." Instead of saying, "Watch the video," you could provide a clear and inclusive alternative: "Watch the video or listen to the audio transcript for the video."
  • Alternatives to color to convey important information: Ensure that color is not the only means of conveying information on your site. For example, ensure that a hyperlink that is highlighted by color is also underlined, so a person who is color-blind knows it is a link, even if they can't see the color. When colors are used to convey or differentiate information—like in a pie chart or bar graph, this information should also be provided in another way, such as text or captions. Try textures instead of colors. Contrasting patterns help users with certain types of color blindness see things more clearly.

Hearing

Some considerations for browsing a SharePoint site for people who are Deaf or Hard of Hearing are:

  • Captions and text transcripts for videos. Adding closed captions makes video content accessible to a larger audience, including people with hearing disabilities and those who speak languages other than the one in your video, or those playing your video in a noisy environment. Transcription and Closed Captions are automatically generated for video files uploaded to SharePoint.
  • Text transcripts for audio. By using the transcribed feature in Microsoft Office, you convert speech to a text transcript with each speaker individually separated.
  • Text or visual alternatives to sounds. Users can get visual cues instead of sound alerts in Windows by changing their settings.
  • Language that provides alternatives to "hearing" or "listening to" an element. For example, rather than writing, "Listen to the audio," use clear and inclusive language that instead says, "Listen to the audio, or read the text transcript for it."

Mobility

Here are some considerations for people with mobility disabilities when browsing a SharePoint site:

  • Keyboard access. Not everyone can use a mouse, so build your site so content is accessible via the keyboard.
  • Opportunities to cancel major actions, such as providing a Cancel button when deleting a channel on a video portal. This ensures users recover from any mistakes made with an input device.
  • Ways to skip long lists. When scrolling is difficult, consider providing, for example, anchor links that enable a person to navigate to the top, to the end, or to the next section on a list or page in a site.

Learning

Here are some considerations for people with learning disabilities when browsing a SharePoint site:

  • Clear and consistent headings, labels, and navigation menus that help people find the information they need and avoid distractions.
  • Alternative formats for text-heavy content, such as images, audio, video, or infographics, that convey the same message in different ways.
  • Clear and concise information or instructions and include definitions or explanations in plain language.

Mental health

Some considerations for browsing a SharePoint site for people with mental health conditions are:

  • Options for adjusting the contrast, font size, and color scheme of the site, as some people may have preferences or sensitivities that affect their comfort and focus.
  • Avoid using flashing, blinking, or moving elements that may trigger anxiety, stress, or seizures. If such elements are necessary, provide a warning and an option to turn them off.
  • Clear and consistent navigation and layout, and provide breadcrumbs, search functions, and feedback mechanisms to help users find what they need and avoid frustration or confusion.

Neurodiversity

Some considerations for browsing a SharePoint site for people who are neurodiverse are:

  • Simple and clear language, avoid jargon and idioms, and provide definitions or explanations for uncommon terms or acronyms.
  • Avoid flashing or flickering images, animations, or videos that may trigger seizures or sensory overload.
  • Alternative text or captions for images, audio, or video content to help users who prefer or need textual information.
  • Consistent and meaningful color schemes, fonts, and icons to convey information, and provide options for users to adjust the contrast, size, or appearance of the site elements.
  • Organize the content logically and hierarchically, and use headings, subheadings, lists, and tables to structure the information and make it easier to scan and understand.