HalfAccessible delivers manual accessibility audit services for websites, web applications, mobile apps, SaaS platforms, PDFs, and enterprise software. IAAP-certified auditors (CPACC, WAS, CPWA) and a DHS Section 508 Trusted Tester combine automated scanning with hands-on keyboard and screen reader testing, so you get findings a scanner alone cannot produce. Every audit is benchmarked against WCAG 2.2 AA, ADA Title II/III expectations, Section 508, the European Accessibility Act (EAA), and EN 301 549. Start with a $500 Quick Audit, or choose the $2,000 Complete Audit for a full manual review with a developer-ready report.
An accessibility audit is a structured evaluation of a website, application, or digital document to identify barriers that prevent people with disabilities from accessing digital content. A complete accessibility audit combines automated tools, manual keyboard testing, screen reader testing, mobile accessibility testing, and expert review against WCAG 2.2 success criteria to produce prioritized remediation guidance. In the 2026 WebAIM Million report, an annual review of the top one million home pages, 95.9% had detectable WCAG 2 failures, and automated tools can only detect part of the problem — which is why automated scans alone are never treated as a complete audit. HalfAccessible's WCAG audit services start with a $500 Quick Audit of up to 5 page templates, and the $2,000 Complete Audit is a full manual WCAG 2.2 audit of up to 25 templates or key user flows.
Think of an accessibility audit like a building safety inspection for your website or product. Instead of checking exits and alarms, it checks whether people using keyboards, screen readers, zoom, voice control, or other assistive technologies can understand content, navigate interfaces, complete forms, and finish important tasks.
An audit shows how real users experience your digital product, not just what automated tools can detect.
Accessibility barriers can stop customers from buying products, patients from accessing care, students from completing courses, and employees from using internal systems. An audit identifies those barriers before they become user complaints, procurement blockers, or legal risks.
The same improvements that help disabled users often improve the experience for everyone. Better form labels, clearer focus states, stronger contrast, consistent headings, readable error messages, and predictable navigation all make digital products easier to use.
Organizations use audits to understand gaps against WCAG 2.2, ADA expectations, Section 508, EN 301 549, PDF/UA, and other accessibility obligations. The audit gives teams a documented baseline and a prioritized plan.
Enterprise and government buyers increasingly ask for accessibility evidence before purchase. Audit findings, remediation plans, VPAT support, and retest results help product teams answer procurement questions with confidence.
Finding accessibility issues early is usually cheaper than fixing them after launch. Audits help teams prioritize root causes, update reusable components, and avoid repeating the same issues across pages and releases.
A good audit does more than list defects. It shows patterns your design, development, QA, and content teams can use to prevent similar accessibility issues in future work.
Our WCAG audit services cover public websites, authenticated web apps, SaaS platforms, mobile apps, documents, video and design systems, tested by people, not just scanners.
Corporate websites, marketing sites, government websites, university websites, healthcare websites, ecommerce journeys, landing pages, blogs, resource libraries, and multilingual content experiences.
Customer portals, admin dashboards, CRMs, internal software, enterprise workflows, complex forms, authenticated user journeys, data tables, reports, notifications, and role-based interfaces.
B2B platforms, cloud software, analytics dashboards, AI applications, product onboarding flows, account settings, billing workflows, and feature-rich application screens.
Native iOS, native Android, hybrid applications, progressive web apps, orientation changes, touch targets, gestures, screen reader flows, zoom behavior, and mobile form interactions.
PDFs, Word documents, PowerPoint files, forms, reports, policy documents, financial statements, healthcare documents, education resources, and procurement documentation.
Reusable components, UI libraries, pattern libraries, design tokens, Figma components, interaction patterns, and documentation that affects many pages or product screens.
Marketing, ecommerce, healthcare, government, education, nonprofit, and service organizations use accessibility audits to make essential public content available to more people.
Product teams use audits to validate complex workflows, reduce accessibility debt, improve component libraries, and prepare for enterprise accessibility reviews.
Legal, compliance, procurement, and sales teams use audit evidence to answer buyer questions, support VPAT work, and document remediation commitments.
Evaluate public websites against WCAG 2.2 AA using manual testing, automated scanning, keyboard-only navigation, and assistive technologies.
Review authenticated user journeys, dashboards, complex forms, data tables, notifications, custom widgets, and enterprise workflows.
Test native and hybrid applications using VoiceOver, TalkBack, keyboard alternatives, zoom, orientation changes, touch target review, and gesture accessibility checks.
Document accessibility audit services for PDFs, Word, PowerPoint and Excel files. We assess PDF/UA support, semantic tagging, reading order, alternative text, bookmarks, form fields, headings, tables and screen reader compatibility, and check every PDF with NVDA.
Identify accessibility issues in Figma files, design systems, and component specs before development begins, reducing rework and improving handoff quality.
Evaluate products and prepare accessibility documentation that supports enterprise and government procurement conversations.
Our WCAG audit services test your site or app against WCAG 2.2 Level A and AA. The $2,000 Complete Audit is a full manual audit of up to 25 templates or key flows, with each failure mapped to its success criterion, the affected page or component and a recommended fix. W3C states that content conforming to WCAG 2.2 also conforms to WCAG 2.0 and 2.1, so one audit covers the WCAG requirements behind the ADA, Section 508 and EN 301 549.
Section 508 testing for federal agencies and the vendors who sell to them, led by a DHS Section 508 Trusted Tester. The Revised 508 Standards require electronic content to conform to WCAG 2.0 Level A and AA, and our results can go straight into the Section 508 edition of a VPAT.
Accessibility testing services for ecommerce websites cover search, filters, product pages, cart, checkout, payment and account flows, plus third-party apps such as reviews, chat and pop-ups. Shopify stores can choose the $2,000 Shopify Accessibility Audit, and any other platform can start with the $500 Quick Audit.
Product accessibility audits for SaaS platforms, customer portals, internal tools and enterprise software, tested role by role with your test accounts. For non-web software and documents we apply WCAG 2.2 using the W3C WCAG2ICT guidance, updated in December 2025, and the findings can feed an Accessibility Conformance Report.
We check prerecorded video for accurate captions, audio description or a media alternative, transcripts for audio-only content, live captions, and media players that work with a keyboard and screen reader (WCAG 1.2.1 to 1.2.5). For large libraries we sample by channel, template and player, so the findings scale across every video.
Each issue is mapped to user impact, WCAG criteria, severity, affected users, and practical remediation guidance.
Missing or inaccurate alternative text prevents screen reader users from understanding meaningful images, icons, charts, infographics, product photos, and linked graphics. In an audit, we identify images that need concise alternatives, images that should be marked decorative, and complex visuals that need longer explanations. We map findings to the relevant WCAG criteria and recommend practical fixes, such as better alt text, adjacent explanations, captions, or revised content patterns.
Many users navigate with a keyboard, switch device, voice control, or assistive technology that relies on keyboard behavior. We test focus order, skip links, menus, modals, tabs, accordions, custom widgets, carousels, date pickers, and form flows without a mouse. We identify keyboard traps, missing focus indicators, unexpected focus movement, unreachable controls, and interactions that require pointer-only input.
Low contrast can make text, buttons, icons, form controls, charts, and graphical objects difficult or impossible to perceive. We evaluate contrast for normal text, large text, UI components, focus indicators, disabled states, links, error messages, and data visualizations. Findings include exact locations, severity, recommended color adjustments, and notes where design tokens or component styles should be updated.
Forms often block users when labels, instructions, required indicators, validation messages, autocomplete attributes, grouping, and error handling are not accessible. We test forms with keyboard navigation and screen readers to confirm that users can understand each field, complete inputs, recover from errors, and submit successfully. We also review password fields, payment flows, search forms, filters, file uploads, and multi-step workflows.
Headings, lists, landmarks, tables, and reading order help assistive technology users understand a page quickly. We identify skipped heading levels, visual headings that are not semantic headings, incorrect lists, missing landmarks, confusing page regions, table header problems, and reading-order mismatches. These findings improve navigation for screen reader users and make content easier for search engines and AI systems to summarize.
Accessible media requires more than basic alt text. We review decorative image handling, informative image alternatives, captions, transcripts, audio descriptions, video player controls, autoplay behavior, and media keyboard support. For complex images such as charts or diagrams, we recommend alternatives that communicate the same information without overwhelming users.
Dialogs, tabs, accordions, menus, carousels, date pickers, comboboxes, tooltips, drawers, and custom controls need correct semantics and predictable keyboard behavior. We test names, roles, states, focus management, escape behavior, announcements, and screen reader output. Findings include examples that help developers fix components at the source instead of patching each page one by one.
Data tables need programmatic relationships between headers and cells so users can understand rows, columns, totals, and comparisons. We review simple tables, complex tables, responsive tables, sortable tables, data grids, and financial or analytical reports. Recommendations may include header associations, captions, summaries, simpler table structures, or alternate layouts for small screens.
Modern applications often update content without refreshing the page. We test status messages, ARIA live regions, notifications, loading indicators, validation updates, filters, search results, and single-page app transitions. The audit identifies when important changes are not announced, when updates are too noisy, and when users lose context after interactions.
Login, MFA, password reset, account creation, security prompts, and session timeout flows must be accessible because they control access to the entire product. We test labels, instructions, error recovery, one-time codes, password rules, captcha alternatives, focus order, timeout warnings, and accessible authentication patterns so users can sign in without unnecessary barriers.
WCAG 2.2 added success criteria that older audits never checked. At Levels A and AA they are Focus Not Obscured (Minimum) 2.4.11, where sticky headers, cookie banners or chat widgets hide the focused element; Dragging Movements 2.5.7, which needs a single-pointer alternative to drag and drop; Target Size (Minimum) 2.5.8, which asks for targets of at least 24 by 24 CSS pixels or enough spacing around them; Consistent Help 3.2.6; Redundant Entry 3.3.7; and Accessible Authentication (Minimum) 3.3.8, which means a login must not depend on a memory or puzzle test unless there is an alternative, such as letting users paste a password or use a password manager. 4.1.1 Parsing was removed. Every WCAG audit we run covers all of them.
Mobile apps fail in ways a website scan never shows: unlabeled icon buttons, multi-finger or path-based gestures with no single-pointer alternative (WCAG 2.5.1), screens locked to one orientation (1.3.4), small touch targets (2.5.8) and focus that jumps when content updates. We test on real devices with VoiceOver, TalkBack, Switch Control and Voice Control, and use Apple’s Accessibility Inspector and Google’s Accessibility Scanner as a first pass. Google itself says the scanner is not a replacement for manual testing, which is why a person checks every flow. See our mobile accessibility testing guide.
| Feature | Automated Testing | Manual Testing |
|---|---|---|
| Speed | Fast (minutes) | Slower (days) |
| Cost | Low | Higher, but more accurate |
| Manual WCAG Review | No | Yes |
| Keyboard Navigation | Limited | Complete |
| Screen Reader Compatibility | No | Yes |
| Logical Reading Order | No | Yes |
| Meaningful Alternative Text | No | Yes |
| Form Usability | Partial | Yes |
| Overall User Experience | No | Yes |
A structured process gives your team clear findings, clear priorities, and a practical path to remediation.
We review your platform, page count, workflows and target standard (WCAG 2.2 AA, ADA, Section 508, EAA), then agree the scope and timeline. Our sampling lines up with the W3C WCAG-EM 2.0 methodology: define the scope, explore the product and select a representative sample of pages, templates and journeys.
We run automated tools across the defined scope to catch code-level issues quickly, giving us a baseline before manual review begins.
Certified specialists manually test keyboard navigation, focus order, forms, headings, and interactive components against WCAG 2.2 success criteria.
We test with screen readers (NVDA, JAWS, VoiceOver, TalkBack), voice control, and switch access to confirm real-world usability, not just code compliance.
Findings are documented with severity, WCAG references, screenshots, and reproduction steps, then organized into a prioritized remediation roadmap.
After your team implements fixes, we retest affected pages or flows to confirm issues are resolved and no new barriers were introduced.
A clear summary of audit scope, key risks, priority themes, and recommended next steps for stakeholders.
A practical status snapshot that helps teams understand current accessibility maturity and remediation priorities.
Issue-by-issue findings with screenshots, affected URLs or screens, severity ratings, WCAG references, and reproduction steps.
Practical remediation guidance, code-level notes, component recommendations, and examples your developers can act on.
A prioritized path that separates urgent blockers, high-impact component fixes, content improvements, and longer-term governance work.
Validation evidence after remediation, showing which issues were fixed and what remains open.
Audits are led by founder Mohammad Shadab Saifi, who holds all three IAAP credentials (CPACC, WAS and CPWA) and is a DHS Section 508 Trusted Tester, with a team of IAAP-certified specialists handling manual testing, remediation support and documentation.
Reports are written for action. Developers receive clear reproduction steps, expected behavior, affected users, WCAG mapping, and remediation guidance.
We support teams preparing for procurement, compliance reviews, product launches, design system improvements, and accessibility governance.
Fixed packages, no hourly billing: the $500 Quick Audit covers up to 5 page templates and the $2,000 Complete Audit covers up to 25 templates or key user flows. Send your URL through the free needs assessment and we reply within 2 business days with a recommended scope.
Whether you're launching a new website, responding to a demand letter, preparing for enterprise procurement, or improving an existing platform, our certified specialists will find the real accessibility barriers in your scope — not just what automated scanners catch — and hand your team a prioritized, developer-ready roadmap. Start a $500 Quick Audit today, or tell us about your project through the free needs assessment and we will reply within 2 business days with a recommended scope.
Start a $500 Quick Auditget in touch
Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.
Free 30-minute consultation (opens in new tab)
Free 30-minute call: talk through where you stand, scope a project or get a quote.
Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.
Indicates a required field.
Your information is kept private and never shared with third parties.
Answers to common questions about accessibility audits, manual testing, screen readers, WCAG, remediation, procurement support, and retesting.
An accessibility audit is a structured review of a website, application, mobile app, or document to identify barriers for people with disabilities. It combines automated scanning, manual WCAG review, keyboard testing, screen reader testing, and expert analysis.
Timeline depends on scope. A small marketing website may take a few days, while an enterprise SaaS product, authenticated application, or large document set may take several weeks. We confirm scope and timeline before starting.
Our audit pricing is fixed and published. A Quick Accessibility Audit costs $500 and covers up to 5 page templates with automated and manual spot checks, a top-10 issues report, WCAG 2.2 mapping and a 30-minute review call. The Complete Accessibility Audit costs $2,000 and covers up to 25 page templates or key user flows with a full manual audit (JAWS, NVDA, VoiceOver and keyboard), a severity-ranked report, a re-test of fixed issues, an accessibility statement draft and 90 days of support. The Shopify Accessibility Audit is also $2,000, and a 1-hour technical accessibility consultation (audit walkthrough, developer Q&A or live issue review) is $100. First conversations are a free 30-minute call. Multi-product and enterprise programs are quoted after scoping. Compare every tier on our pricing page, or read our accessibility audit cost guide to see what drives the price.
We manually test representative pages, templates, components, and critical user journeys based on the approved scope. For large sites, this usually includes key templates and high-risk workflows rather than every URL.
Yes. We test with screen readers such as NVDA, JAWS, VoiceOver, and TalkBack when relevant to the platform and scope.
No. Automated tools are useful for detecting many code-level issues, but they cannot reliably determine logical reading order, meaningful alternative text, keyboard usability, screen reader compatibility, or overall user experience.
We typically test against WCAG 2.2 AA unless your organization needs a different target such as WCAG 2.1, Section 508, EN 301 549, or PDF/UA.
Yes. HalfAccessible can provide remediation guidance, developer support, and direct code fixes depending on your technology stack and project needs.
Yes. Retesting verifies that accessibility fixes resolve the original barriers and do not introduce new issues in affected flows.
Yes. We support audit evidence, remediation roadmaps, VPAT and ACR preparation, accessibility documentation, and buyer-facing accessibility conversations.
Yes. We audit iOS, Android, hybrid, and progressive web applications using mobile screen readers, zoom, orientation checks, touch target review, and mobile interaction testing.
Yes. We can audit authenticated applications, portals, dashboards, CRMs, admin systems, and SaaS products when test credentials and representative workflows are provided. For product teams, our SaaS accessibility audit page explains how we scope logged-in workflows, design systems and VPAT evidence.
Yes. We audit PDFs for tagging, reading order, headings, tables, links, forms, alternative text, bookmarks, metadata, and screen reader compatibility.
Browser coverage depends on scope, but commonly includes Chrome, Safari, Firefox, and relevant mobile browsers.
Depending on scope, we use NVDA, JAWS, VoiceOver, TalkBack, keyboard-only navigation, browser zoom, voice control, and platform accessibility features.
Reports include issue descriptions, affected locations, expected and actual results, user impact, severity, WCAG references, screenshots, reproduction steps, and remediation recommendations.
Where useful, we include code examples or implementation notes so developers understand how to fix the issue in context.
Yes. We audit modern JavaScript applications, including React, Next.js, Angular, Vue, and other component-driven frameworks.
Yes. We audit WordPress, Shopify, Drupal, WooCommerce, Magento, and other CMS or ecommerce platforms.
Yes. Auditing design systems and reusable components is one of the best ways to reduce repeated accessibility issues across products.
Yes. Accessibility design reviews can identify issues before development, including contrast, focus behavior, form patterns, component states, headings, and interaction design.
An audit identifies barriers and provides a remediation roadmap. Compliance improves when the identified issues are fixed, validated, and supported by ongoing governance.
Yes. Findings are prioritized by severity, user impact, compliance risk, frequency, and remediation complexity so teams know where to start.
Yes. We can join walkthrough calls, answer developer questions, review fixes, and help teams address accessibility issues at the component level.
Yes. Audit findings can support VPAT or ACR preparation, especially for SaaS products and organizations selling to enterprise or government buyers.
Yes. Documents often require a dedicated audit because PDF/UA, tagging, reading order, and document structure are different from web page testing. Our PDF and document remediation service audits and fixes PDFs, Word files and forms, and we check every PDF with the NVDA screen reader. Our document accessibility testing checklist explains how we test PDFs, Word and PowerPoint files against PDF/UA, WCAG and Section 508.
The fastest way is to start a $500 Quick Audit: share your URL and up to 5 pages or templates and we take it from there. For a larger site, app or document set, tell us the URL, application type, representative workflows, target standard and any deadlines through our free accessibility needs assessment. We reply within 2 business days with a recommended audit scope and next steps.
An accessibility scan is an automated tool checking code for detectable errors, usually in seconds. An accessibility audit includes that scan plus manual keyboard testing, screen reader testing, and expert human review — because issues like logical reading order, meaningful alternative text, and real usability can’t be reliably detected by software alone.
Most organizations audit annually at minimum, and after any major redesign, feature launch, or CMS/platform migration. Regulated industries (healthcare, government, banking) or teams with frequent releases often pair a full annual audit with ongoing monitoring in between. Banks and fintechs can see how we scope login, payment and statement journeys on our banking accessibility audit page.
Yes, indirectly. Fixes like semantic headings, descriptive link text, proper landmark structure, and logical reading order are the same signals that help AI search tools and language models parse and summarize your content accurately. Sites that pass accessibility checks are often easier for AI crawlers to extract correctly.
Unresolved barriers keep blocking real users, increase legal and procurement risk, and compound as more pages and features get built on the same inaccessible patterns. We provide a prioritized roadmap specifically so teams can tackle urgent blockers first without needing to fix everything at once.
By people. Automated tools are only our first pass. The Complete Audit is a full manual audit: a human auditor tests your pages and user flows with a keyboard, NVDA, JAWS, VoiceOver and TalkBack. Audits are led by our founder, who holds the IAAP CPACC, WAS and CPWA credentials and is a DHS Section 508 Trusted Tester (see his profile). That matters because software cannot judge whether alt text is meaningful, whether focus order makes sense or whether a checkout works with a screen reader. Our ADA and Section 508 accessibility audit page explains how results map to ADA expectations.
Yes. The Revised Section 508 Standards require electronic content to conform to WCAG 2.0 Level A and AA, which the standards incorporate by reference, and federal agencies, government contractors and many public-sector buyers ask for that evidence. Our audits are led by a DHS Section 508 Trusted Tester, test against WCAG 2.2 AA (content that conforms to WCAG 2.2 also conforms to WCAG 2.0), and can feed a VPAT or Accessibility Conformance Report. See how our Section 508 testing and ADA audit service works, or use the government accessibility audit request form if you are a public agency. The official requirements are published in the U.S. Access Board’s Section 508 Standards.
The $500 Quick Accessibility Audit is a fast health check: up to 5 page templates, automated and manual spot checks, a top-10 issues report and a 30-minute review call. The $2,000 Complete Accessibility Audit is a full manual audit of up to 25 page templates or key user flows with JAWS, NVDA, VoiceOver and keyboard testing, a severity-ranked report, a re-test of fixed issues, an accessibility statement draft and 90 days of support. If you are unsure, start with the Quick Audit: it shows where your biggest risks are before you commit to full coverage.
Yes. Request our sample audit report and we will send the same WCAG 2.2 report format we deliver on Quick and Complete audits, with an executive summary, issue-by-issue findings mapped to WCAG criteria, severity ratings, screenshots and developer-ready fix guidance.
Yes. Start with a $500 Quick Audit to see the biggest barriers on up to 5 page templates, or choose the $2,000 Complete Audit when you need full manual coverage, a re-test of fixed issues and an accessibility statement draft to share with your attorney. Demand letters and lawsuits are common: Seyfarth Shaw counted 3,117 website accessibility lawsuits in U.S. federal court in 2025, up 27% from 2024. Our ADA lawsuit remediation page explains the audit, fix and re-test plan we follow. We are accessibility specialists, not lawyers, so keep your attorney involved in any legal response.
No. Overlays and toolbar widgets do not fix the underlying code, so screen reader, keyboard and form barriers usually remain. In April 2025 the U.S. Federal Trade Commission approved a final order requiring accessiBe to pay $1 million and barring it from claiming that its automated product can make any website WCAG-compliant without evidence. A manual audit followed by code-level accessibility remediation is what actually removes barriers. Read whether accessibility overlays stop ADA lawsuits for the data.
Yes. The DOJ’s ADA Title II rule requires state and local government web content and mobile apps to meet WCAG 2.1 AA. An interim final rule published on April 20, 2026 set the compliance dates at April 26, 2027 for public entities with a total population of 50,000 or more and April 26, 2028 for smaller entities and special district governments (Federal Register). Our WCAG 2.2 AA audits cover every WCAG 2.1 AA success criterion, plus PDFs and other documents. Use the government accessibility audit request form, or see our government and public sector accessibility services.
Yes. We test product pages, filters, carts, checkout, account and payment flows with a keyboard and screen readers, because those are the journeys where shoppers get blocked. The Shopify Accessibility Audit is $2,000 and covers your storefront, product pages, cart, checkout and apps; WooCommerce stores can use our WordPress accessibility audit; and any other platform can start with the $500 Quick Audit. See our ecommerce and retail accessibility services for industry-specific detail.
A WCAG audit tests a representative sample of your pages, templates and user journeys against WCAG 2.2 Level A and AA. Our process lines up with the W3C’s WCAG-EM 2.0 methodology, published in July 2026: define the scope, explore the product, select a representative sample, evaluate it and report the findings. Testing combines automated scans with keyboard and screen reader testing (NVDA, JAWS, VoiceOver and TalkBack), and the report maps each issue to its success criterion, severity and a recommended fix. The $2,000 Complete Audit is a full manual WCAG 2.2 audit of up to 25 templates or key flows; the $500 Quick Audit is a lighter health check of up to 5 page templates with a top-10 issues report. Request a sample report to see the format.
The main tools are the ones your users rely on: VoiceOver on iOS and TalkBack on Android, plus Switch Control, Voice Control, zoom and larger text settings. For a quick first pass we use Apple’s Accessibility Inspector in Xcode and Google’s Accessibility Scanner, which flags missing labels, small touch targets and low contrast. Google notes the scanner is not a replacement for manual testing, so every key flow is tested by hand. WCAG 2.2 was written for the web, so for native apps we apply it using the W3C’s WCAG2ICT guidance. See our mobile accessibility testing guide or start a Quick Audit for your app.
Yes. Automated tools can tell you whether a video has a caption track, but not whether the captions are accurate, whether key visual information needs audio description, or whether the player works with a keyboard. So we sample the library by channel, player and content type, then check each sample against WCAG 1.2.1 to 1.2.5: captions for prerecorded and live video, audio description or a media alternative, and transcripts for audio-only content. We also test player controls, autoplay and the ability to pause. The W3C guide to making audio and video media accessible covers the requirements, and our video accessibility glossary entry explains the terms. Large libraries are quoted after a free needs assessment.
Yes. Under the ADA Title II rule, public schools, community colleges and public universities must make their web content and mobile apps meet WCAG 2.1 Level AA by April 26, 2027 or April 26, 2028, depending on the population of the government entity they belong to (ADA.gov). Private colleges are generally covered by ADA Title III. We audit admissions pages, course pages, learning management systems, student portals and course documents. See our education accessibility services and the Interstride EdTech audit case study, or use the government accessibility audit request form for public institutions.
No. Our disability access audits cover digital products only: websites, web and mobile apps, software, documents and video. For physical premises such as entrances, parking and restrooms, you need an access consultant who audits against the 2010 ADA Standards for Accessible Design in the US, or your local building code elsewhere. If you need both, we can audit the digital side while your access consultant covers the buildings. Tell us what you need and we reply within 2 business days.
Yes. Application and product audits focus on what users do after they log in: onboarding, search, dashboards, data tables, forms, notifications, settings and admin tools. We test each user role with your test accounts, and our accessibility monitoring service can re-test after each release. For non-web software we apply WCAG 2.2 using the W3C’s WCAG2ICT guidance, and the results can support a VPAT or Accessibility Conformance Report for enterprise and government buyers. See how we scope SaaS and B2B software accessibility work, or get a free needs assessment.
