Answer first

Short answer

365 Security Assessment accessibility statement, WCAG 2.2 AA commitment, known limitations, and support path for accessibility feedback.

365 Security Assessment focuses on Microsoft 365 and Azure security posture, prioritized findings, executive reporting, and remediation-ready guidance for teams evaluating this topic.

  • Who it helpsMSPs, IT leaders, security teams, and Microsoft 365 administrators
  • What you getClear context for evaluating Microsoft 365 and Azure security risk
  • Next stepSee the sample report

Accessibility

Accessibility Statement

365 Security Assessment aims to make 365securityassessment.com accessible to the widest possible audience, including people using screen readers, keyboard navigation, voice control, magnification, and other assistive technologies.

Conformance goal

Our current accessibility target is Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We use automated scans, build-time checks, keyboard testing, and manual screen-reader review to identify and remediate accessibility barriers. Accessibility is an ongoing process, not a one-time overlay or widget.

Measures we take

  • Maintain semantic page structure, landmarks, headings, and a skip-to-main-content link.
  • Require accessible names for links, buttons, form fields, dialogs, and embedded frames.
  • Review text alternatives for meaningful images and hide decorative icons from assistive technology.
  • Test keyboard navigation for menus, forms, calls to action, and modal dialogs.
  • Check color contrast, visible focus indicators, reduced-motion preferences, and responsive behavior.
  • Run automated accessibility audits against the built website before public release.

Third-party content

Some pages may include embedded scheduling, forms, analytics, or media from third-party providers. We work to provide accessible labels, wrappers, and alternate contact paths for embedded content we do not fully control.

If an embedded form or scheduler is difficult to use with your assistive technology, use the contact page and tell us which page or task was blocked so we can route the request and remediate the issue.

Accessibility feedback

We welcome accessibility feedback. Please include the page URL, the assistive technology or browser you used, and what you were trying to do.

Report an accessibility issue

Status

This statement was last reviewed on June 8, 2026. We aim to respond to accessibility-related requests within two business days and prioritize fixes based on severity and user impact.