SharePoint Accessibility: WCAG Compliance Guide

Why Accessibility Matters

Accessibility isn't just about compliance—it's about ensuring every employee can effectively use your SharePoint environment regardless of ability. With approximately 15% of the global population experiencing some form of disability, accessible design is essential for inclusive digital workplaces.

Understanding WCAG Standards

Web Content Accessibility Guidelines

WCAG provides the international standard for web accessibility:

WCAG 2.1 Levels

• Level A: Minimum accessibility (must-have)
• Level AA: Enhanced accessibility (standard target)
• Level AAA: Highest accessibility (aspirational)

Most organizations target WCAG 2.1 Level AA compliance.

Four Core Principles (POUR)

Perceivable

• Information must be presentable to users
• Provide text alternatives for images
• Captions for multimedia
• Sufficient color contrast

Operable

• Interface must be navigable
• Keyboard accessibility
• Sufficient time to interact
• No seizure-triggering content

Understandable

• Content must be readable
• Predictable functionality
• Input assistance
• Error prevention

Robust

• Content must work with assistive technologies
• Valid HTML markup
• Compatible with screen readers
• Future-proof design

SharePoint Accessibility Features

Built-In Accessibility

Modern SharePoint includes many accessible features:

Keyboard Navigation

• Tab through page elements
• Enter to activate links/buttons
• Arrow keys for menus
• Escape to close dialogs

Screen Reader Support

• ARIA landmarks for navigation
• Alt text support for images
• Heading hierarchy
• Form labels

Visual Accessibility

• High contrast modes
• Zoom support
• Focus indicators
• Responsive design

Accessibility Checker

SharePoint includes a built-in accessibility checker:

Using the Checker

• Edit your page
• Click the Accessibility icon in the toolbar
• Review identified issues
• Follow remediation guidance
• Re-check after fixes

Common Issues Detected

• Missing alt text
• Low contrast text
• Missing form labels
• Heading order violations
• Link text problems

Creating Accessible Content

Images and Media

Alt Text Best Practices

• Describe the image's purpose, not just appearance
• Keep alt text under 125 characters
• For decorative images, use empty alt (alt="")
• Don't start with "Image of..." or "Picture of..."

Good vs. Bad Alt Text

```

Bad: "Chart"

Good: "Bar chart showing Q4 sales increased 23% over Q3"

Bad: "Image of team"

Good: "Marketing team celebrating product launch milestone"

Bad: "logo.png"

Good: "Contoso company logo"

```

Video Accessibility

• Include captions (auto-generated or professional)
• Provide transcripts
• Add audio descriptions for visual content
• Ensure player is keyboard accessible

Text and Typography

Readable Text

• Minimum 16px font size for body text
• Line height at least 1.5x font size
• Maximum line length ~80 characters
• Left-align body text (avoid justified)

Color Contrast

• Normal text: 4.5:1 contrast ratio minimum
• Large text (18pt+): 3:1 contrast ratio minimum
• Use WebAIM Contrast Checker to verify
• Don't rely solely on color to convey meaning

Headings

• Use proper heading hierarchy (H1, H2, H3...)
• Don't skip heading levels
• One H1 per page
• Headings should describe content that follows

Links and Buttons

Descriptive Link Text

```

Bad: "Click here"

Good: "Download the SharePoint migration guide"

Bad: "Read more"

Good: "Read more about our consulting services"

Bad: "Link"

Good: "View project documentation"

```

Button Accessibility

• Clear, descriptive labels
• Sufficient size (44x44 pixels minimum)
• Visible focus states
• Distinguish from links visually

Forms and Input

Accessible Forms

• Label every form field
• Group related fields with fieldset/legend
• Provide clear error messages
• Don't rely only on placeholder text

Error Handling

• Identify errors clearly
• Explain how to fix
• Don't clear form on error
• Focus on first error field

Testing for Accessibility

Automated Testing Tools

Built-In Tools

• SharePoint Accessibility Checker
• Microsoft Accessibility Insights
• Edge DevTools Accessibility features

Third-Party Tools

• WAVE (WebAIM)
• axe DevTools
• Lighthouse (Chrome)
• ANDI (SSA)

Manual Testing

Keyboard Testing

• Unplug your mouse
• Tab through the entire page
• Verify all interactive elements are reachable
• Check focus is always visible
• Ensure logical tab order

Screen Reader Testing

• NVDA (free, Windows)
• JAWS (commercial, Windows)
• VoiceOver (built-in, Mac/iOS)
• Narrator (built-in, Windows)

Visual Testing

• Test with browser zoom at 200%
• Enable high contrast mode
• Check with color blindness simulators
• Verify on mobile devices

Testing Checklist

Quick Accessibility Audit

• [ ] All images have alt text
• [ ] Color contrast meets standards
• [ ] Headings follow proper hierarchy
• [ ] Links have descriptive text
• [ ] Forms have proper labels
• [ ] Page is keyboard navigable
• [ ] Focus indicators are visible
• [ ] Videos have captions

Remediation Strategies

Prioritizing Fixes

Priority 1 (Critical)

• Keyboard traps (users get stuck)
• Missing form labels
• Auto-playing audio/video
• Flashing content

Priority 2 (High)

• Missing alt text on informational images
• Insufficient color contrast
• Broken heading hierarchy
• Missing focus indicators

Priority 3 (Medium)

• Non-descriptive link text
• Missing skip links
• Complex data tables without headers
• Missing language declaration

Common Fixes

Missing Alt Text

• Edit the page
• Click on image
• Select "Edit" in image toolbar
• Add meaningful alt text
• Save and republish

Low Contrast

• Identify affected text
• Use theme colors with sufficient contrast
• Avoid light gray on white
• Test with contrast checker

Heading Issues

• Use built-in heading styles
• Don't use bold for pseudo-headings
• Maintain proper hierarchy
• Review with accessibility checker

Governance for Accessibility

Accessibility Policy

Policy Components

• Target conformance level (typically AA)
• Scope (all public-facing, all internal, etc.)
• Roles and responsibilities
• Testing requirements
• Remediation timelines

Training Program

Who Needs Training

• Content authors (everyone who creates pages)
• Site owners and administrators
• Developers (SPFx, Power Platform)
• Reviewers and approvers

Training Topics

• WCAG basics
• Using accessibility checker
• Creating accessible content
• Testing procedures
• Remediation techniques

Monitoring and Reporting

Regular Audits

• Monthly automated scans
• Quarterly manual audits
• Annual comprehensive review
• New content checks

Metrics to Track

• Pages scanned
• Issues found by severity
• Remediation rate
• Time to fix

Legal Considerations

Compliance Requirements

United States

• Section 508 (federal agencies)
• ADA (Americans with Disabilities Act)
• State-specific requirements

European Union

• European Accessibility Act
• EN 301 549 standard
• Country-specific implementation

Other Regions

• AODA (Ontario, Canada)
• DDA (UK)
• Various national standards

Risk Mitigation

Documentation

• Accessibility policy
• Testing records
• Remediation efforts
• Training completion

Proactive Approach

• Build accessibility into processes
• Regular testing and fixing
• User feedback channels
• Continuous improvement

Conclusion

Accessibility is an ongoing commitment, not a one-time project. By building accessibility into your SharePoint governance, training content creators, and regularly testing and remediating issues, organizations can create inclusive digital workplaces that serve all employees effectively.

Ready to improve your SharePoint accessibility? Contact our accessibility specialists for an audit and remediation roadmap.