SharePoint Accessibility Audit Checklist: Pages, Documents, Lists, and Forms
accessibilityWCAGSharePoint intranetcontent qualityemployee experience

SharePoint Accessibility Audit Checklist: Pages, Documents, Lists, and Forms

SSharePoint.news Editorial Team
2026-11-16
7 min read

Use this recurring SharePoint accessibility audit checklist to review pages, documents, forms, lists, media, and intranet navigation.

An accessible SharePoint intranet needs more than a readable page template. This audit checklist helps content owners, site designers, and Microsoft 365 administrators review modern pages, documents, lists, forms, images, links, navigation, and embedded media before publishing, during quarterly reviews, and after significant changes.

Overview

A SharePoint accessibility audit is a structured review of whether people can find, understand, navigate, and complete tasks using the intranet. The review should include both the content itself and the way the SharePoint experience behaves with a keyboard, browser accessibility settings, zoom, and assistive technology.

Use the Web Content Accessibility Guidelines (WCAG) as a reference framework, but treat a checklist as a risk-reduction tool rather than proof of universal compliance. SharePoint features, custom components, embedded services, Office files, and organizational requirements can introduce different issues. A page that passes an automated check may still have unclear instructions, poor heading structure, or a form that is difficult to complete.

Assign an owner to every finding and record the page, file, list, or form affected. A useful issue log includes:

  • Location: the site URL, page section, document, list, or form.
  • Issue: a plain-language description of what prevents or makes access more difficult.
  • Impact: who may be affected and what task is blocked or slowed.
  • Priority: critical, high, medium, or low, based on task importance and the availability of an alternative.
  • Owner and due date: the person responsible for remediation and the next review point.
  • Verification: how the team will confirm that the fix works.

Keep accessibility in the same review process as content quality, permissions, link health, and site ownership. A broader SharePoint site health review can provide the operational framework for this recurring work.

What to track

Pages, headings, and landmarks

  • Confirm that every page has a clear, descriptive title that matches the user's task.
  • Review headings in order. Use headings to describe sections, not simply to create larger or bolder text.
  • Check that the page has a logical reading order when viewed from top to bottom and with a screen reader.
  • Use SharePoint section layouts and web parts consistently. Avoid placing essential instructions only in decorative elements, background images, or visual positioning.
  • Check that navigation labels, page names, and breadcrumbs make sense without relying on color or surrounding context.

Link text should explain the destination or action. Replace vague labels such as “click here” or repeated “read more” links with descriptions such as “Read the travel expense policy.” If several links lead to the same destination, simplify the presentation where possible.

Test menus, accordions, buttons, search controls, dialogs, and other interactive elements using only the keyboard. Check that focus is visible, follows a sensible order, does not become trapped, and does not disappear behind a fixed header or panel. Confirm that the action can be completed without requiring a mouse gesture.

Images, icons, and color

  • Add alternative text that conveys the purpose of meaningful images. If an image is decorative, configure it accordingly rather than adding unnecessary description.
  • Do not place essential text only inside an image. Provide the information as selectable page text or an equivalent accessible format.
  • Check charts, diagrams, and infographics for a nearby text summary or data table when the visual carries important meaning.
  • Do not use color alone to communicate status, required fields, categories, or errors. Add text, symbols, or another clear indicator.
  • Review text and control contrast, including hover, focus, disabled, and error states. Automated tools can help identify possible contrast issues, but manual review is still useful.

Documents and document libraries

Audit Office files separately from the SharePoint page that links to them. In Word documents, review heading structure, lists, table headers, language settings, reading order, image descriptions, and link text. In Excel workbooks, inspect sheet names, table headers, formulas, merged cells, chart descriptions, and whether the workbook remains understandable when zoomed or navigated without a mouse. For PowerPoint, check slide titles, reading order, image descriptions, captions, and sufficient contrast.

Use the relevant Microsoft 365 Accessibility Checker where available, then manually test the completed file. The checker can identify common patterns, but it may not determine whether a heading is meaningful, whether a description is accurate, or whether the document's instructions are understandable.

Lists, forms, and embedded media

Review SharePoint list and library forms for clear field names, useful descriptions, required-field instructions, understandable error messages, and a logical tab order. Test choice fields, date pickers, people fields, attachments, filtering, sorting, and validation messages. If a form is customized with Power Apps, include the customized experience in the audit rather than assuming the default SharePoint form behavior applies.

For videos and audio, check captions, transcripts, keyboard controls, visible focus, and an accessible alternative for essential information. Test embedded content in the actual page because an external player or service may behave differently inside a SharePoint web part.

Screen-reader and responsive checks

Use a supported browser and at least one screen-reader workflow appropriate to your organization. Start at the page title, navigate by headings and landmarks, open key links, complete a representative form, and locate an important document. Also test browser zoom and a narrow viewport. The goal is not to certify every possible device combination; it is to expose failures in the tasks employees actually need to complete.

Cadence and checkpoints

Run a lightweight check before every new intranet launch or major page publication. For high-use pages, forms, policies, and employee self-service journeys, include accessibility in the content approval step rather than treating it as a final technical gate.

A quarterly review is a practical baseline for established intranets. Prioritize pages with high usage, legal or operational importance, frequent updates, or known accessibility findings. Review the following after each major change:

  1. New web parts or layouts: retest keyboard navigation, headings, focus, and reading order.
  2. Brand or theme changes: recheck contrast, links, buttons, alerts, and navigation states.
  3. New forms or workflows: complete the full task, including validation, errors, submission, and confirmation.
  4. Document replacements: run the Office Accessibility Checker and manually review the new file.
  5. Embedded services or media: verify captions, controls, transcripts, and keyboard operation in context.
  6. Platform changes: review relevant SharePoint Online updates and test critical journeys in a controlled site before broad rollout.

When a SharePoint feature or page experience changes, record the date, affected sites, test owner, and outcome. A repeatable review process is easier to manage alongside a SharePoint Online roadmap review workflow.

How to interpret changes

Not every finding has the same operational consequence. A missing decorative label may be low priority, while an inaccessible approval form, inaccessible emergency instruction, or document with no usable structure may block a core employee task. Rank findings by task impact, audience size, urgency, and whether a practical alternative exists.

Look for patterns rather than treating every page as an isolated defect. Repeated problems with link text may indicate an editorial training issue. Contrast failures across a theme may require design-system changes. Similar form problems may point to a shared Power Apps component or template. A large number of outdated files may require ownership and lifecycle controls, not only individual document edits.

Separate platform limitations from authoring mistakes and custom-code issues. A content owner may be able to fix a heading or alternative text immediately. A custom SPFx component, embedded player, or form may require a developer. Capture that distinction in the issue log so remediation is directed to the right team.

After a fix, retest the complete user journey, not only the reported element. Changing a button label, layout, or form field can affect instructions, focus order, screen-reader output, and downstream automation. Keep evidence such as screenshots, test notes, or checker results according to your organization's governance process.

When to revisit

Revisit this SharePoint accessibility audit checklist at least quarterly for active intranets and whenever a major page, form, theme, embedded service, or document collection changes. Review it sooner after an accessibility complaint, a failed task test, a redesign, a migration, or a change to organizational accessibility requirements.

At the end of each review cycle, select a small set of representative journeys: finding a policy, submitting a request, reading an announcement, opening a document, and watching required media. Record what worked, what failed, and which fixes remain open. Then schedule the next review rather than closing the process with a one-time sign-off.

For a practical closeout, use this sequence:

  1. Choose the pages, files, forms, and journeys with the greatest employee impact.
  2. Run automated checks where available, followed by keyboard, zoom, and screen-reader testing.
  3. Log each issue with a location, impact, owner, priority, and verification method.
  4. Fix content issues immediately where possible and route custom or platform issues to the responsible team.
  5. Retest the full task and record the result.
  6. Set the next monthly or quarterly checkpoint and update the checklist when SharePoint experiences change.

Accessibility is most effective when it becomes part of ordinary SharePoint publishing and intranet governance. Pair this review with your site's lifecycle, navigation, and content-expiry processes so accessible content remains accessible after the initial launch.

Related Topics

#accessibility#WCAG#SharePoint intranet#content quality#employee experience
S

SharePoint.news Editorial Team

Editorial team

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.