Accessibility
Microsoft Made Easy Accessibility Statement
This Microsoft Made Easy accessibility statement describes how we work to make our website usable for everyone, including people who use assistive technology. It explains what we do, where we fall short, and how to tell us about a problem.
Conformance goal
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 (opens in new tab) at Level AA. These guidelines are the recognized standard for making web content more usable for people with a wide range of disabilities, including visual, motor, auditory, and cognitive differences. We treat AA as an ongoing target rather than a one-time certification, and we review the site as we add pages.
Measures we take
Accessibility is part of how this site is built, not an afterthought. Concretely, we:
- Use semantic HTML with proper landmarks and a logical heading order, so screen readers can navigate the page structure predictably.
- Keep the site keyboard operable: interactive elements such as menus, the FAQ accordion, and the contact form can be reached and used without a mouse, with a visible focus indicator and a skip-to-content link.
- Maintain sufficient color contrast for text and meaningful interface elements against their backgrounds, aiming to meet the AA contrast thresholds.
- Provide descriptive alt text for meaningful images and mark decorative graphics so assistive technology can ignore them.
- Build labelled, accessible forms, where each field has an associated label, helpful error messages, and clear focus styling.
- Respect user preferences such as reduced motion and avoid relying on color alone to convey information.
Known limitations
We want to be honest rather than claim perfection. We are aware of areas that may not yet fully meet Level AA, and we are working to improve them:
- Some third-party embeds and analytics scripts are outside our direct control and may not meet the same standard as our own markup.
- Illustrative dashboard mockups on this site are rich, visual artifacts; while we describe them in surrounding text, the graphics themselves may not convey every detail to every assistive technology. When we deliver Microsoft 365 solutions for clients, we follow Microsoft's accessibility guidance for report authors (opens in new tab) to improve keyboard and screen-reader support.
- As we publish new pages, individual elements may temporarily fall short of our target until our next review catches them.
If you encounter a barrier that is not listed here, we would genuinely like to know so we can fix it.
How to report a problem
If any part of this website is difficult to use, or you need information in a different format, please tell us through our contact form.
Please include the page address and a short description of the problem, and the assistive technology or browser you were using if you know it. We aim to acknowledge accessibility reports within one business day and will work with you on a reasonable timeline to resolve the issue or provide the content another way.
This statement was last reviewed in 2026 and is updated as the site changes.
Book a free consultation
Get more from the Microsoft tools you already pay for
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
- Fixed-fee scope agreed before any work starts
- Senior, US-based Microsoft engineers — no handoffs
- Typical 2–4 week delivery
- 30 days of post-delivery hypercare included
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.