Accessibility work is often sold as a legal risk project.
That is only half the story.
For small businesses, accessibility can also be a budget project. The IRS has a federal Disabled Access Credit for eligible small businesses, and the IRS says those businesses may claim it every year they incur qualifying access expenditures. The IRS also lists a separate architectural barrier removal deduction of up to $15,000 a year for qualified expenses.
This guide is written for business owners, web professionals, and finance teams trying to answer a practical question: if we pay to make our website easier for people with disabilities to use, is there a tax incentive that can help offset the cost?
Short answer: possibly, but you need documentation, a tax professional, and a clean scope of work. Do not treat this as tax advice. Treat it as a field guide you can bring to your CPA before you approve the accessibility budget.
The two federal incentives to know
There are two federal incentives that usually come up in ADA accessibility planning.
| Incentive | Who it is for | Amount | Source |
|---|---|---|---|
| Disabled Access Credit | Eligible small businesses | 50% of eligible access expenses over $250 and up to $10,250, for a maximum credit of $5,000 | Department of Justice ADA tax credit archive and IRS Form 8826 page |
| Barrier Removal Tax Deduction | Businesses of any size | Up to $15,000 per year for qualified expenses | IRS tax benefits page and 26 U.S. Code § 190 |
The Disabled Access Credit is the one most small business website projects should ask about first. The IRS says eligible small businesses use Form 8826 to claim the disabled access credit, and the IRS describes it as a non-refundable credit for small businesses that incur expenses to provide access to people with disabilities.
The deduction is different. The IRS describes the Barrier Removal Tax Deduction as an incentive for businesses of any size to remove architectural and transportation barriers, and 26 U.S. Code § 190 caps the deduction at $15,000 per taxable year. That language is more clearly tied to physical and transportation barriers, so do not assume it covers website work without tax advice.
Who qualifies for the Disabled Access Credit?
The threshold is smaller than many owners expect.
The IRS says an eligible small business is one that earned $1 million or less or had no more than 30 full-time employees in the previous year. The DOJ ADA archive gives the same threshold: total revenues of $1,000,000 or less in the previous tax year or 30 or fewer full-time employees.
That “or” matters. A business can be above $1 million in revenue and still potentially qualify if it had 30 or fewer full-time employees, based on the way the IRS and DOJ describe eligibility.
The credit is not a one-time coupon. The IRS says eligible small businesses may take the credit each and every year they incur access expenditures. That makes it worth discussing before you turn accessibility into a recurring maintenance line item.
How the Disabled Access Credit math works
The simplest way to think about the Disabled Access Credit is this:
- Add eligible accessibility expenses for the year.
- Subtract the first $250.
- Take 50% of the remaining amount, capped at $5,000.
The ADA National Network explains the credit as 50% between $250 and $10,250, with a maximum of $5,000. The DOJ ADA archive says the credit can cover 50% of eligible access expenditures in a year up to $10,250, with a maximum credit of $5,000.
Here is what that means in plain numbers.
| Accessibility spend | Potential credit calculation | Potential credit |
|---|---|---|
| $250 | No amount above first $250 | $0 |
| $1,250 | 50% of $1,000 | $500 |
| $5,250 | 50% of $5,000 | $2,500 |
| $10,250 | 50% of $10,000 | $5,000 |
| $18,000 | Credit capped after $10,250 of expenses | $5,000 |
The tax value depends on the final return. The IRS describes the Disabled Access Credit as non-refundable, which means you need your CPA to explain how it applies to your specific tax liability.
Can website accessibility work count?
This is where the conversation needs to be careful.
The official sources were written before most business happened through websites, so they do not read like a modern web development scope. The DOJ ADA archive says the credit can offset costs for barrier removal, alterations to improve accessibility, accessible formats, sign language interpreters or readers, and certain adaptive equipment. The ADA National Network says the Small Business Tax Credit covers most expenses to comply with the ADA, including barrier removal, auxiliary aids and services, and accommodating employees.
A website accessibility project may involve auxiliary aids, accessible communication, usability for assistive technology, and access to goods or services. That is why many businesses ask their tax professional whether website audits, remediation, accessible documents, captions, form fixes, and user testing belong in the conversation.
Do not have your web vendor promise the credit. Have them write a scope your CPA can evaluate.
A strong website accessibility invoice should separate the work into tax-review-friendly categories:
- Accessibility audit against WCAG criteria, including manual keyboard and screen reader testing.
- Remediation of barriers such as missing labels, low-contrast text, inaccessible navigation, missing alt text, broken focus states, inaccessible PDFs, missing captions, or unusable forms.
- Verification, documentation, and ongoing monitoring tied to access for customers, prospects, applicants, or employees with disabilities.
That kind of detail gives your accountant something better than “website redesign” to review.
Why this deserves attention in 2026
Accessibility is not a fringe issue, and the data is blunt.
The CDC reported that more than 1 in 4 U.S. adults, over 70 million people, had a disability in 2022. Globally, the World Health Organization estimates that 1.3 billion people, or 16% of the global population, experience a significant disability.
Websites are still failing the basics. In its 2026 analysis of the top 1,000,000 home pages, WebAIM found 56,114,377 distinct accessibility errors, averaging 56.1 errors per page. WebAIM also found that 95.9% of home pages had detected WCAG failures, and that home page complexity increased to an average of 1,437 elements in February 2026.
That complexity matters. Every extra pop-up, carousel, tracking script, form field, menu state, and third-party widget can introduce another way for someone to get blocked.
Legal pressure is also not theoretical. The American Bar Association reported that nearly 2,500 federal digital accessibility lawsuits were filed across the United States in 2024, citing Seyfarth Shaw data. For public sector websites and mobile apps, the DOJ Title II web rule requires state and local government web content and mobile apps to meet WCAG 2.1 Level AA, with updated compliance dates of April 26, 2027 for larger entities and April 26, 2028 for smaller entities and special district governments.
Private businesses are not covered by that Title II rule in the same way, but the market signal is clear. WCAG is no longer just a developer preference. It is the reference point regulators, plaintiffs, procurement teams, schools, municipalities, and enterprise buyers keep circling back to.
What website work is easiest to defend as access work?
The cleaner the tie to access, the easier the conversation.
A full brand redesign that happens to include some accessibility fixes is harder to evaluate than a dedicated accessibility remediation project. A new homepage concept is a marketing expense. Fixing keyboard traps, adding form labels, correcting heading order, improving color contrast, captioning videos, replacing inaccessible PDFs, and testing checkout with assistive technology are access improvements.
The WebAIM Million methodology says WAVE detects end-user accessibility barriers that have a high likelihood of being WCAG 2.2 Level A/AA conformance failures. That gives web teams a practical way to document automated findings, but WebAIM also warns that automated tools have limitations and absence of detected errors does not indicate a page is accessible or conformant. Manual testing still matters.
For 2026 projects, use WCAG as the organizing standard. The W3C says WCAG 2.2 was published as a W3C Recommendation on October 5, 2023, while the DOJ Title II rule specifically points state and local governments to WCAG 2.1 Level AA. Many private businesses use WCAG 2.2 AA as the working target because it includes newer criteria while building on 2.1.
A practical documentation packet for your CPA
Do not wait until tax season to reconstruct the project. Build the file as the work happens.
Give your tax professional a short packet with these items:
- The signed accessibility scope, separated from general redesign, SEO, hosting, ads, and brand work.
- Before-and-after audit results, including WCAG criteria, affected URLs, screenshots, user impact, fixes completed, and retest dates.
- Paid invoices that label accessibility work clearly, plus notes for captions, accessible PDFs, manual testing, assistive technology testing, or employee/customer accommodation work.
That packet does not guarantee the credit. It does reduce the fog.
It also helps operationally. If a customer, vendor, insurer, buyer, or attorney asks what you did, you are not relying on memory. You have a dated record.
Sample scope language for web professionals
Here is a plain-English version you can adapt for proposals. Have a lawyer or CPA review it before you rely on it.
Accessibility audit and remediation for customer-facing website access. Work includes WCAG-oriented review of selected templates and user flows, keyboard testing, screen reader spot checks, contrast review, form label review, heading structure review, image alternative text review, PDF accessibility review where applicable, remediation of identified barriers, documentation of changes, and post-remediation verification. Accessibility work is itemized separately from design, marketing, hosting, and non-accessibility development services.
That wording avoids a common mistake: burying the access work inside a generic “website update” invoice. When the work is mixed together, the tax review gets harder.
Common mistakes that weaken the claim
The first mistake is assuming every website cost counts. It probably does not. A new logo, new photography, new sales copy, and new analytics setup may be useful, but they are not automatically accessibility expenses.
The second mistake is buying an overlay and calling the site compliant. WebAIM’s 2026 report found that home pages with accessibility overlays averaged 87.6 detected errors, compared with 55.8 on pages without detectable overlays. Overlays may have narrow uses, but they do not replace fixing the underlying site.
The third mistake is ignoring documents and media. If your service pages link to PDFs that screen reader users cannot read, or your sales videos need captions to be understood, your “accessible website” still has holes.
The fourth mistake is skipping retesting. Accessibility work without verification is just a promise. Test the pages after the fixes ship.
A small business example
Say a local medical equipment company has 18 full-time employees and spends $9,750 on accessibility work. The project includes an audit, form remediation, keyboard navigation fixes, alt text improvements, contrast fixes, captioning core product videos, and retesting.
If the CPA determines the full $9,750 is eligible for the Disabled Access Credit, the rough calculation would be $9,750 minus the first $250, then 50% of $9,500. That points to a potential $4,750 credit.
If the company spends $14,000 and the CPA determines the expenses qualify, the credit still maxes out at $5,000 because the DOJ ADA archive says the credit covers eligible access expenditures up to $10,250, with a maximum credit of $5,000.
That is real money. It may not cover the whole project, but it can make a proper accessibility sprint easier to approve than another round of cosmetic homepage tweaks.
FAQ
Is the Disabled Access Credit the same as a deduction?
No. The IRS calls the Disabled Access Credit a non-refundable credit, while the Barrier Removal Tax Deduction is described separately as a deduction of up to $15,000 a year for qualified expenses.
Can I claim the credit every year?
The IRS says eligible small businesses may take the Disabled Access Credit each and every year they incur access expenditures. Your CPA should confirm how that applies to your return.
Does a website overlay qualify?
Do not assume that. An overlay subscription is not the same as remediating barriers in your website’s code, content, media, documents, and forms. WebAIM’s 2026 data found higher average detected errors on pages with overlays than pages without detectable overlays, so an overlay alone is a weak accessibility strategy.
Should we target WCAG 2.1 AA or WCAG 2.2 AA?
The DOJ Title II rule points state and local governments to WCAG 2.1 Level AA. The W3C published WCAG 2.2 as a Recommendation on October 5, 2023. For private small businesses, many teams use WCAG 2.2 AA as a practical target, then document what was tested and what remains.
Who should decide whether my website project qualifies?
Your CPA or tax advisor. Your web team can document the access work, but tax treatment belongs with a qualified tax professional.
The smart move
If your site has accessibility problems, do not wait until a complaint forces your hand. Build a small, focused accessibility project, document it cleanly, and ask your CPA about Form 8826 before the invoice is paid.
Your customers get a site they can use. Your team gets a clearer maintenance standard. Your accountant gets better records. And if the credit applies, the project may cost less than you expected.
If you want help scoping accessibility work in a way your team and accountant can understand, start a conversation with Your Web Team. We can audit the site, separate access fixes from general web work, and give you a practical remediation plan instead of a vague compliance scare pitch.
