Services · By platform
A SharePoint Audit, Because Your Intranet Counts Too
For the organization whose employees live in SharePoint, and which wants the leave-request workflow and the benefits PDF tested by somebody who uses a screen reader every day.
What We Keep Finding
Intranets get audited last and used most. An employee who cannot operate the leave-request workflow or read the benefits PDF is not inconvenienced. They are blocked from their own job, and there is nobody else on the internet they can go to instead.
Whether that is a legal question as well as a decent-employer question depends entirely on who you are, and it is worth being precise rather than waving at employment law. If you are a state or local government body, your intranet is government web content. The Justice Department's rule binds it to WCAG 2.1 Level AA, with dates of April 26, 2027 and April 26, 2028 depending on the population you serve. If you are a federal agency, Section 508 covers it at WCAG 2.0 Level A and AA. That comes with a safe harbor for legacy systems you leave untouched, and a rule that where conformance would be an undue burden you still have to get the information to the person another way. If you are a private employer, there is no technical standard pointed at your intranet, and what you have instead is a duty to accommodate an individual employee, which is a different mechanism with a different trigger.
SharePoint adds its own texture on top. Web parts with mixed semantics, document libraries full of untagged files, and years of team-site sprawl nobody owns. One thing to square before you read the report. Microsoft's own free checker targets WCAG 2.1 while our audit runs against 2.2. So a tenant that has already worked through Accessibility Insights will still see findings, and they will be the newer criteria rather than a contradiction.
What We Check
- Test the workflows employees must use, so requests, forms, approvals
- Audit key pages and web parts with a screen reader
- Sample the document library and rank the highest-use files
- Check search and navigation across sites by keyboard
- Cover the newer WCAG 2.2 criteria your own tooling is not looking for
- Deliver fixes per template and a document triage list
What You Get
Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.
The format is not a mystery either. Read the sample report before you spend anything.
The Honest Limit
One honest limit. Microsoft's own web part internals update on Microsoft's schedule, so we test what your tenant serves today, date it, and separate platform behavior from the fixes your team owns. Two practical notes as well. An intranet scope cannot be described in the order form, which asks for a website and a page list, so this one starts with an email. And the free scan cannot reach a tenant at all, since every page worth auditing is behind authentication and the scanner cannot sign in.
What It Costs
Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.
Worth Reading Next
Related on this site
Guides, checklists, tools, and terms that go with this service.