Industry news, advice and insights from our experts.

A prime contractor wins a multi-year federal contact center contract. The proposal named a small business staffing subcontractor as the talent arm of the program. The award comes through in March. Go-live is set for mid-May. By the end of April, the prime’s program manager is on daily calls with the subcontractor, clearance packets are stalled, and fifteen seats still have no names next to them.

Nobody bid this way on purpose. But this is how federal subcontracting programs break, and it usually happens in the gap between what the subcontracting plan says and what the workforce pipeline can actually deliver.

For prime contractors running programs out of Northern Virginia, San Antonio, Huntsville, Colorado Springs, and every other federal contracting hub, subcontractor performance is not a compliance line item. It is a risk exposure that shows up in CPARS ratings, in liquidated damages, and in the next recompete.

This article walks through what these programs are supposed to do, where they most often fail, and what federal subcontractor staffing compliance should look like when the workforce side is handled by a partner who understands how primes get measured.

What Subcontracting Programs Are Supposed to Do

The federal government directs a share of its contracting dollars to small businesses every year. The statutory goals sit at 23 percent of prime contract dollars to small businesses overall, with additional targets for small disadvantaged businesses, women-owned small businesses, service-disabled veteran-owned small businesses, and HUBZone firms.¹ The SDVOSB goal was raised to 5 percent under the FY24 NDAA.² The SDB goal was returned to its statutory minimum of 5 percent in early 2025.³

On contracts that exceed the Simplified Acquisition Threshold, primes that are not themselves small businesses must prepare a subcontracting plan under FAR 52.219-9.⁴ The plan sets dollar and percentage goals by socioeconomic category, names the small business concerns the prime intends to use, and commits the prime to semi-annual reporting through the Electronic Subcontracting Reporting System (eSRS) via the Individual Subcontract Report (ISR) and the Summary Subcontract Report (SSR).⁴

Failure to comply in good faith with an approved subcontracting plan is treated as a material breach of the prime contract.⁴ It also feeds directly into past performance evaluations, which means it follows the prime into future competitions.

That is what the regulations say. The operational picture is less tidy.

Where Programs Break: Seven Failure Points for Prime Contractor Workforce Oversight

1. The Sub Is Named in the Proposal but Absent From the Work

The most documented failure mode in federal subcontracting is the named-but-unused small business. A prime teams with a WOSB, SDVOSB, HUBZone, or 8(a) firm during capture, features the firm in the proposal, wins the award, and then routes the actual scope to a different subcontractor or self-performs it quietly.

From the prime’s side, it can feel like a small decision. A recruiting partner is slower than expected. Another vendor already has candidates on the bench. The subcontracting plan still gets filed.

From the contracting officer’s side, this is the pattern the SBA has been trying to close for more than a decade. Prior surveys of federal subcontractors have found that roughly one in three report being named in a winning proposal and then effectively cut out of the work.⁵ Primes are expected to make a good-faith effort to use the firms they named, and a gap between plan and performance is a CPARS exposure. On staffing-heavy contracts, it is also the fastest way to lose continuity on a program that relies on high-volume cleared recruiting.

2. Teaming Built on Certification, Not Capability

Subcontracting plans exist to promote small business participation, and socioeconomic goals make specific certifications valuable to primes during capture. The problem starts when the teaming decision is driven by certification alone.

A WOSB certification does not tell a prime whether the firm can run background investigations at volume. An 8(a) designation does not guarantee that the firm can stand up a training cohort in three weeks. The paperwork closes the gap in the proposal. The workforce delivery closes it in real life.

When primes build teaming arrangements from a certification checklist rather than from operational capability, the first month of performance becomes a stress test that the program rarely passes cleanly.

3. Ramp-Up Math That Ignores Clearance Timelines

Federal contact center work typically requires Public Trust or higher. Even with an efficient vendor, Public Trust clearance runs roughly two months on a good day, and longer when adjudication queues at OPM or agency-specific security offices are backed up.⁶ Secret and Top Secret timelines run considerably longer than that. Adjudication queues in Maryland, Virginia, and Texas have all shown regional variation that affects actual ramp speed.

A typical ramp-up plan sets a go-live date sixty or ninety days from award. Prime subcontractor workforce oversight breaks here more often than anywhere else, because the clearance schedule was built backwards from the go-live date instead of forwards from the reality of agency processing times.

The math that works is a pipeline started before contract award, with fingerprinting, SF-85 or SF-86 submissions, and conditional offers moving in parallel. The math that does not work assumes the subcontractor will catch up in week two. By week two, the program is already behind.

Read More:  Prime Contractor Guide to Staffing Ramp-Ups 

4. Bill Rates Set Without Recruiting Reality

On competitively priced federal proposals, the staffing bill rate is negotiated to win. The prime needs margin. The sub is asked to deliver fully loaded candidates at a rate that, once taxes, benefits, training hours, and attrition are backed out, leaves a recruiting budget thin enough to hurt.

This breaks programs in a predictable way. At a thin bill rate, the sub cannot afford to source candidates who are already cleared or clearable. It has to recruit to a price point, which means longer time-to-fill, higher attrition during onboarding, and a candidate quality gap that eventually shows up in call handle times and quality assurance scores.

The compliance paperwork still gets filed. The program still drifts off plan.

5. ISR and SSR Reporting Treated as an Afterthought

The ISR is due thirty days after March 31 and September 30 each year. The SSR is due thirty days after the end of the fiscal year. Both are filed in eSRS, with subcontractor goal data feeding in from the next tier down.⁴

When primes treat these reports as a year-end compliance chore rather than a quarterly management tool, two things go wrong. First, the reported numbers and the actual spend numbers stop matching, which creates audit risk. Second, the prime loses the early warning that a sub is underperforming against its goal contribution, because the data is only being looked at when the report is due.

The primes who handle this well run internal subcontracting dashboards monthly and use the ISR cycle to confirm what they already know. The primes who get caught use the ISR cycle to find out.

6. Prime-to-Sub Communication Goes Dark Mid-Performance

The capture phase produces daily calls, shared war rooms, and tight message alignment. The award phase produces a signed subcontract and a kickoff. Then, for many programs, the operational communication layer thins out.

Small business subs are often excluded from the prime’s program management reviews. They learn about scope changes, staffing adjustments, or client concerns through a contracts officer rather than through the PMO. When a COR raises a performance flag, the prime hears it first, debates it internally, and only brings the sub in once the response plan is already drafted.

This is a risk management failure even when nothing else goes wrong. For programs supporting agencies concentrated in the DC metro, Denver, Atlanta, and San Antonio hubs, the communication gap between prime PMO and staffing sub is where the first week of workforce issues usually hides. The subcontractor is closest to the workforce. Cutting that visibility out of PMO reviews guarantees that workforce problems surface later than they should.

7. The 50 Percent Self-Performance Rule Handled on Paper, Not in Practice

Under FAR 52.219-14, a small business prime on a set-aside services contract must pay no more than 50 percent of the government’s contract dollars to subcontractors that are not similarly situated entities.⁹ The intent is to prevent small business set-asides from becoming pass-throughs for larger firms.

On a contact center program, the 50 percent calculation is straightforward on a spreadsheet and messy in practice. A staffing-heavy scope can tilt the ratio quickly if the small business prime leans too hard on a staffing subcontractor. The fix is not a tighter compliance memo. It is a teaming arrangement that routes staffing through a similarly situated sub where possible, and a self-performance plan that is realistic about what the prime’s own recruiting function can absorb.

What Broken Programs Actually Cost Prime Contractors

On a contact center contract, the downstream costs of a broken subcontracting program are concrete. Staffing shortfalls trigger SLA penalties, often in the range of 10 to 20 percent of the period’s payment schedule.⁷ Quality metrics drop. The COR documents issues in the monthly report, which rolls into CPARS, which follows the prime into every recompete for the next three years.

Subcontracting plan failures add a second layer. A prime that misses its small business goals without documented good-faith effort exposes itself to liquidated damages under FAR 19.705-7, negative past performance ratings, and in repeat cases, referral to FAPIIS for late or reduced payments to subcontractors.⁸

The reputational cost is harder to quantify and longer lasting. Small business partners talk to each other. A prime that becomes known for bait-and-switch teaming, or for squeezing subs on bill rates, loses access to the talent networks that make high-clearance recruiting work at all.

What Prime Subcontractor Workforce Oversight Should Look Like

The primes who run clean subcontracting programs tend to share a few operational habits.

They engage staffing subs during capture, not after award. The workforce plan is built into the proposal with realistic bill rates and clearance timelines. They maintain shared visibility through the PMO, not just through contracts. The staffing sub sits in program reviews, sees the same metrics the prime sees, and flags pipeline risk before it becomes a performance issue.

They treat ISR and SSR as management checkpoints. Subcontractor spend, goal contribution, and tier-one attribution are tracked monthly, not once every six months. They match certification with capability. The WOSB, SDVOSB, HUBZone, or 8(a) partner on the contract is there because the firm can deliver the scope, and the certification is the part that makes the accounting work.

FAQ: Subcontractor Accountability in Federal Staffing Programs

What is FAR 52.219-9, and who has to follow it?

FAR 52.219-9 is the clause that requires non-small business prime contractors on covered contracts to maintain a small business subcontracting plan.⁴ The plan sets dollar and percentage goals across small business categories, identifies named subcontractors, and commits the prime to reporting through eSRS. It applies to contracts above the Simplified Acquisition Threshold that offer subcontracting opportunities.

Who is responsible if a subcontractor fails to deliver staff on a federal contract?

Under the prime contract, the prime is accountable to the government. Subcontract language determines how responsibility flows between prime and sub, but from the contracting officer’s view, the prime owns the delivery. This is why prime subcontractor workforce oversight matters operationally as well as contractually.

How often are ISR and SSR reports submitted?

The Individual Subcontract Report is due semi-annually, thirty days after March 31 and September 30. The Summary Subcontract Report is due thirty days after fiscal year end. Both are filed through eSRS at esrs.gov.⁴

Can a prime contractor replace a named small business subcontractor after award?

Yes, with caveats. The prime must document a good-faith effort to use the named firm, and any replacement still has to fit the approved subcontracting plan. Repeated substitution of named small business subs is a pattern that contracting officers track, and it can feed into past performance evaluations.

What happens if a prime misses its small business subcontracting goals?

If the prime cannot demonstrate a good-faith effort, consequences can include liquidated damages under FAR 19.705-7, negative CPARS ratings, and entry into FAPIIS for payment-related issues.⁸ Missing the goal is not an automatic penalty. Failing to show the effort to meet it is what triggers exposure.

How long does it take to clear a contact center agent for federal work?

Public Trust positions typically run around two months under normal conditions, and longer when adjudication queues are backed up.⁶ Secret and Top Secret clearances run considerably longer. Clearance timelines should be built into the ramp-up plan from the proposal stage, not after award.

What is the 50 percent rule for small business primes?

Under FAR 52.219-14, a small business prime on a services set-aside must pay no more than 50 percent of the government contract dollars to subcontractors that are not similarly situated entities.⁹ Work performed by a similarly situated sub counts toward the 50 percent the prime is allowed to subcontract.

Moving From Paperwork to Performance

Small business subcontracting is one of the most consistent pressure points in federal programs, and on staffing-heavy contracts, it is where delivery risk and compliance risk meet. The primes who manage this well do not rely on the subcontracting plan to carry the weight. They build workforce delivery into the program from the start and treat their staffing sub as a performance partner, not a checkbox on the compliance matrix.

If you are building a capture team for a federal contact center program, or running a program that is not keeping up with its ramp-up plan, Salem Solutions is worth a conversation. We support prime contractors across DHA, VA, IRS, DoD, HHS, and DHS programs with cleared contact center talent at the scale these contracts actually require.

Start a conversation: https://bit.ly/HireSalem

References

1. U.S. Small Business Administration. “SBA Goaling Guidelines.” March 5, 2025. https://www.sba.gov/document/report-sba-goaling-guidelines.
2. Congressional Research Service. “An Overview of Small Business Subcontracting: In Brief.” Report R47585. March 26, 2026. https://www.congress.gov/crs_external_products/R/PDF/R47585/R47585.6.pdf.
3. U.S. Small Business Administration. “SBA Moves to Terminate Over 620 Firms in 8(a) Federal Contracting Program That Refused to Turn Over Financial Data.” March 4, 2026. https://www.sba.gov/article/2026/03/04/sba-moves-terminate-over-620-firms-8a-federal-contracting-program-refused-turn-over-financial-data.
4. Federal Acquisition Regulation. “52.219-9 Small Business Subcontracting Plan.” Acquisition.gov. Accessed April 20, 2026. https://www.acquisition.gov/far/52.219-9.
5. New, Catherine. “Small Federal Subcontractors Suffer From ‘Bait And Switch’ Schemes.” HuffPost, June 19, 2012. https://www.huffpost.com/entry/small-subcontractors-bait-and-switch_n_1609505.
6. Salem Solutions. “Prime Contractor Guide to Staffing Ramp-Ups.” November 26, 2024. https://salemsolutions.com/prime-contractor/.
7. Salem Solutions. “Prime Contractors: Scale Contact Centers.” October 13, 2025. https://www.salemsolutions.com/scale-contact-centers/.
8. Wiley Rein LLP. “SBA Final Rule Attempts to Prevent the Use of ‘Bait and Switch’ Tactics with Small Business Subcontractors.” July 19, 2013. https://www.wiley.law/alert-2780.
9. Federal Acquisition Regulation. “52.219-14 Limitations on Subcontracting.” Acquisition.gov. Accessed April 20, 2026. https://www.acquisition.gov/far/52.219-14.

Accessibility compliance in federal contact centers is statutory, and it spans Section 508, Section 504, Title IV, and increasingly state Title II obligations layered on top. 

If you are staffing federal contact center work, you need to know what actual compliance looks like operationally, because “we have policies” does not answer phones.

The legal framework, and what each law actually requires of your call floor

Four statutes carry most of the weight for federal contact center operations.

Section 508 of the Rehabilitation Act (29 U.S.C. § 794d) requires federal agencies to make their information and communication technology accessible to people with disabilities. Section 508 applies when federal agencies develop, procure, maintain, or use ICT¹. The Revised 508 Standards, which took effect in 2018, incorporate WCAG 2.0 Level AA and are built into Federal Acquisition Regulation Subpart 39.2². That means contact center platforms, IVRs, knowledge bases, agent desktops, chat interfaces, and any customer-facing digital tool your agents touch fall directly under Section 508 contact center requirements.

Section 504 of the Rehabilitation Act prohibits disability discrimination in programs that receive federal financial assistance or are conducted by a federal agency. HHS issued a major Section 504 rule update in May 2024. The communications requirements under that rule are nearly identical to ADA Title II, and they explicitly cover digital communications³. For any federal health, benefits, or social services program, this is the civil rights backbone that every contact center sits under.

ADA Title IV mandates telecommunications relay service. Dialing 711 connects callers to a communications assistant who bridges between a text telephone and a standard voice line. Relay types include TTY-based TRS, Video Relay Service (VRS), IP Relay, Captioned Telephone Service (CTS), IP Captioned Telephone Service (IP CTS), and Speech-to-Speech relay. The 711 code works for TTY-based TRS.

It does not work for VRS, IP Relay, IP CTS, or CTS, which route through the internet and require direct calling⁴. Federal contact centers must accept relay calls and handle them equivalently to standard voice calls⁵.

Section 503 requires federal contractors with contracts above $10,000 to take affirmative action in employing individuals with disabilities⁶. This is an employment law, but it directly shapes staffing models for anyone bidding into federal contact center work.

A fifth line of exposure is worth tracking even though it does not apply directly to federal agencies. The DOJ’s April 2024 final rule under ADA Title II requires state and local governments, and the vendors who serve them, to meet WCAG 2.1 Level AA for web and mobile content. The compliance deadline for entities serving populations of 50,000 or more is April 24, 2026.

For smaller entities and special districts, the deadline is April 26, 2027⁷. Federal programs routinely operate through state administrative partners including Medicaid, SNAP, unemployment insurance, and workforce programs. Contact centers supporting those hybrid models inherit the Title II obligation through the state side of the contract.

The scale of the population you are actually serving

The American Community Survey put the civilian non-institutionalized population with disabilities at 44.68 million in 2023, or roughly 13.5% of the country. That includes about 12.07 million Americans with a hearing disability, 8.29 million with a vision disability, 17.97 million with a cognitive disability, and 15.79 million with an independent living disability.⁸

The GSA’s FY 2023 Governmentwide Section 508 Assessment found that fewer than 30% of the federal government’s most-viewed electronic documents, intranet and internet pages, and videos fully conformed to Section 508 standards.⁹ The FY 2025 Assessment continues to document that the federal government is not meeting its statutory obligations.¹⁰

These are the baseline conditions under which federal contact centers receive inbound calls and digital traffic from the public. A contact center that handles accessibility well is immediately operating above the federal baseline.

What compliance actually requires inside a contact center

Written policies do not answer phones. Operational design does. Real ADA compliance in a federal call center shows up in eight places.

1. IVR and voice menu design. An IVR is ICT under Section 508, and it is also telecommunications equipment covered by FCC Section 255 guidelines.¹¹ Menus must be navigable without visual cues. Speech recognition must tolerate variance in pronunciation, cadence, and speech-disability patterns. Callers who cannot complete an IVR path must reach a live agent quickly, with no penalty and no dead-ends. Timeout windows must be generous enough for relay-assisted calls, where typing and interpretation add latency.

2. Relay call handling at the agent level. Agents have to recognize the opening phrase “Hello, this is the relay service” and respond correctly. They cannot hang up. They cannot ask the communications assistant to summarize. They cannot refuse to repeat information.⁵ Relay calls typically run two to four times longer than standard voice calls, so any average handle time rubric has to flex, or QA will end up penalizing the agents who are doing accessibility correctly.

3. Contact center platform conformance. The agent desktop, CRM, knowledge base, ticketing system, call recording UI, and supervisory dashboard all have to meet WCAG 2.0 Level AA at minimum under the Revised 508 Standards.² If an agent with low vision cannot read the case notes on their own screen, you have a Section 501 employment failure and a Section 508 procurement failure at the same time.

4. Plain language and cognitive accessibility. Scripts written in agency-speak fail cognitive accessibility by design. Obligations under the Plain Writing Act of 2010¹² and the Section 504 effective communication standard³ point in the same direction: ordinary words, shorter constructions, and content that a caller can absorb in real time while under stress. This matters especially for federal benefits lines, where callers are often navigating unfamiliar terminology during a vulnerable moment.

5. Agent training that actually mentions disability. Generic customer service training does not prepare an agent for a VRS call, a caller using speech-to-speech relay, a caller who needs information read aloud, or a caller requesting a specific auxiliary aid. Training has to cover each relay type, the legal expectation of equivalent service, and the agent’s authority to offer alternate communication channels without escalating.

6. Auxiliary aids and alternate formats. Under Section 504 and the ADA effective communication rules, covered entities must offer auxiliary aids and services. These include qualified interpreters, assistive listening devices, text telephones, Braille, large print, and accessible electronic formats.⁵ Contact center workflows need a documented path for an agent to flag, request, and deliver these on demand during and after a call.

7. Post-call digital communications. Follow-up emails, SMS, self-service portal links, and PDF attachments are all ICT. They must meet Revised Section 508 Standards.² This is where audits most often find accessibility gaps after the voice channel has already been cleaned up. A compliant call that ends with an inaccessible PDF confirmation is still a compliance failure.

8. Documentation. Section 508 Assessments, Accessibility Conformance Reports built on the Voluntary Product Accessibility Template, and procurement market research records are mandatory under FAR 7.103(q) and FAR 39.2.¹ If a vendor cannot produce ACRs for every tool in their stack, the prime cannot complete its own 508 compliance documentation, and the agency inherits that gap.

FAQs

What ADA accommodations are required in federal programs?

Federal programs are governed primarily by Section 504 and Section 508 rather than the ADA directly, but the accommodation standards are closely aligned. A federal program, or a program receiving federal financial assistance, must provide auxiliary aids and services to ensure effective communication with individuals who have speech, hearing, or vision disabilities.

Accepted aids include qualified sign language interpreters (often delivered via Video Relay Service for phone interactions), real-time captioning, TTY and TRS access, Braille and large-print materials, screen reader-compatible digital documents, and accessible electronic formats.⁵

Programs must also provide reasonable modifications to policies and procedures when needed, absent a fundamental alteration of the program or an undue burden on the agency.

In a contact center setting, that translates into specific operational requirements: accepting all relay call types without distinguishing treatment, offering a live-agent bypass from any IVR, producing written follow-ups in accessible formats, and honoring a caller’s stated communication preference without requiring justification.

How does accessibility affect staffing?

Accessibility reshapes contact center staffing in four ways that show up directly on contract pricing and performance metrics.

The first is handle time. Relay calls take longer, and any capacity plan that does not budget for this will mispredict headcount and miss service level agreements in the field.

The second is training investment. Onboarding has to include relay protocols, disability-inclusive communication, and plain language coaching, which adds real hours to the training curriculum and shifts the ramp-to-productivity timeline.

The third is QA design. Scorecards that measure average handle time and wrap time without adjusting for relay and accommodation calls will quietly push agents toward non-compliant behavior, because agents optimize for whatever the rubric rewards. Rubrics have to separate accessibility-related duration from operational inefficiency.

The fourth is hiring itself. Section 503 creates affirmative action obligations for federal contractors around hiring people with disabilities.⁶

Beyond the legal floor, a staffing pool that includes people with disabilities produces better internal testing of the tools agents use and better calibration on what accessible service actually feels like from the caller’s side.

The state administrative partner question

Federal programs rarely operate only at the federal level. Medicaid managed care organizations, Health Insurance Marketplace navigators, state workforce systems, unemployment insurance, and SNAP all sit at the federal-state intersection, with contact centers that serve callers under both federal and state obligations simultaneously.

The DOJ’s April 2024 Title II final rule adds a second accessibility layer on top of Section 504 and Section 508 for these contact centers. State and local government entities serving populations of 50,000 or more must meet WCAG 2.1 Level AA for all web and mobile content by April 24, 2026.

Entities serving smaller populations have until April 26, 2027.⁷ For contact centers supporting state-administered federal programs, the implication is direct: the digital artifacts the contact center produces (confirmation emails, portal links, PDFs, forms, SMS links) fall under both the federal Section 508 obligation through procurement and the state Title II obligation through the administering entity.

The most populous states, including California, New York, Texas, Florida, and Illinois, all hit the April 2026 deadline first. State procurement teams in those jurisdictions are already pushing accessibility warranties, ACR requirements, and audit rights into the contact center agreements that govern their federal program call centers.

Agencies and primes placing work through those administrative partners need a contact center vendor whose accessibility capability satisfies both regimes simultaneously, not just one.

What this means when evaluating contact center vendors

Inclusive operations is a procurement question, not a feature checkbox. When agencies and primes evaluate vendors for federal contact center work, the questions that separate serious operators from stated commitments are specific:

• How is average handle time adjusted for relay calls in your QA rubric?
• What training hours are dedicated to disability-inclusive communication and relay protocols?
• Can you produce Accessibility Conformance Reports for every customer-facing tool in your stack?
• How do agents flag and fulfill auxiliary aids requests during a call?
• What is your escalation path when a caller reports an accessibility barrier?
• How does your staffing model satisfy Section 503 affirmative action obligations?

These questions expose whether a vendor has operationalized accessibility or written it into the statement of work and hoped it would take care of itself.

Ready to staff a federal contact center that meets the accessibility bar on day one? Reach out at https://bit.ly/HireSalem.

References

1. U.S. General Services Administration, “IT Accessibility Laws and Policies,” Section508.gov, accessed April 19, 2026, https://www.section508.gov/manage/laws-and-policies/.
2. U.S. Access Board, “Revised 508 Standards and 255 Guidelines,” accessed April 19, 2026, https://www.access-board.gov/ict/.
3. U.S. Department of Health and Human Services, “Section 504 of the Rehabilitation Act of 1973 Final Rule: Section by Section Fact Sheet for Recipients of Financial Assistance from HHS,” HHS.gov, May 2024, https://www.hhs.gov/civil-rights/for-individuals/disability/section-504-rehabilitation-act-of-1973/ocr-detailed-504-fact-sheet/index.html.
4. Federal Communications Commission, “711 for Telecommunications Relay Service,” FCC.gov, accessed April 19, 2026, https://www.fcc.gov/consumers/guides/711-telecommunications-relay-service.
5. U.S. Department of Justice, Civil Rights Division, “ADA Requirements: Effective Communication,” ADA.gov, accessed April 19, 2026, https://www.ada.gov/resources/effective-communication/.
6. U.S. Department of Labor, Office of Federal Contract Compliance Programs, “Section 503 of the Rehabilitation Act of 1973, as Amended,” DOL.gov, accessed April 19, 2026, https://www.dol.gov/agencies/ofccp/section-503.
7. U.S. Department of Justice, Civil Rights Division, “State and Local Governments: First Steps Toward Complying with the Americans with Disabilities Act Title II Web and Mobile Application Accessibility Rule,” ADA.gov, accessed April 19, 2026, https://www.ada.gov/resources/web-rule-first-steps/.
8. NIDRLRR, Annual Disability Statistics Compendium: 2025, Institute on Disability, University of New Hampshire, March 2025, https://www.researchondisability.org/sites/default/files/media/2025-03/pdf-online_full-compendium-with-title-acknowledgement-pages.pdf.
9. “What You Need to Know About Section 508 and OMB M-24-08 Compliance,” Propio, October 7, 2025, https://propio.com/2025/10/07/what-you-need-to-know-about-section-508-and-omb-m-24-08-compliance/.
10. U.S. General Services Administration, “FY 2025 Governmentwide Section 508 Assessment Report,” Section508.gov, 2026, https://www.section508.gov/.
11. Mid-Atlantic ADA Center, “Telecommunications,” AdaInfo.org, May 15, 2023, https://www.adainfo.org/ada-information/telecommunications/.
12. “Plain Writing Act of 2010,” Public Law 111-274, 124 Stat. 2861, October 13, 2010, https://www.plainlanguage.gov/law/.