Every compliance question your organization
has about language access and digital accessibility.

Title VI of the Civil Rights Act of 1964 prohibits discrimination based on race, color, and national origin in programs and activities receiving federal financial assistance. The Department of Justice and other federal agencies interpret "national origin" discrimination to include discrimination based on limited English proficiency (LEP). Any entity receiving federal funds must take reasonable steps to ensure that LEP individuals have meaningful access to their programs and services.

Executive Order 13166, "Improving Access to Services for Persons with Limited English Proficiency," was signed by President Clinton in August 2000. It requires all federal agencies to develop and implement a system to provide meaningful language access to LEP individuals. It also requires federal agencies to extend those same obligations to entities that receive federal financial assistance — including state agencies, school districts, healthcare providers, courts, and nonprofits that operate with federal grant funding.

If your organization receives any federal financial assistance — including federal grants, federal program funding, Medicare/Medicaid reimbursements, Title I education funds, CDBG grants, or any other federal award — you are covered. This includes most state agencies, county and city governments, public school districts, public hospitals and health centers, publicly funded legal services, and nonprofits that receive federal grants. If you are unsure, the answer is almost certainly yes.

Meaningful access means LEP individuals can understand the nature of the services available and participate fully in programs and activities. It requires more than token compliance — a phone number for interpretation is not sufficient if wait times are excessive or interpreters are unqualified. Meaningful access requires qualified interpreters (not bilingual staff pressed into service), accurate translation of vital documents, and timely language assistance that doesn't result in denial or delay of services.

A Language Access Plan is a written policy document that describes how an organization will provide language access to LEP individuals. Federal agencies are required to have one under EO 13166. Many federal grant programs require recipient organizations to have a LAP as a condition of funding. Even where not explicitly required, having a LAP is the most defensible evidence of good-faith compliance efforts. We can help develop a LAP as part of our compliance services.

The DOJ recommends translating "vital documents" — those that are critical for accessing services or understanding rights, including intake forms, applications, notices of rights, letters with adverse actions, consent forms, complaint procedures, and notices about available language assistance. The threshold for translation is generally when a language group constitutes 5% or 1,000 individuals (whichever is less) of the eligible population served. State agencies often have specific thresholds set by their own regulations.

Bilingual staff can assist with basic communications, but relying on untrained bilingual staff for high-stakes interpretation (medical, legal, benefits eligibility) creates significant risk. DOJ guidance requires qualified interpreters — those with demonstrated proficiency in both languages and training in the ethics and techniques of interpretation. Using a child or family member to interpret for medical or legal matters is generally inappropriate and may violate informed consent requirements.

The DOJ's "four-factor analysis" guides this determination: (1) number of LEP individuals served, (2) frequency of contact, (3) nature and importance of the service, and (4) resources available. Practically, start with the languages spoken by 5% or 1,000+ of your service population, then prioritize by frequency of encounter. Census data, American Community Survey data, and your own intake records are the right starting point. We help organizations conduct this analysis as part of Language Access Plan development.

Section 508 of the Rehabilitation Act requires federal agencies to make all electronic and information technology (ICT) accessible to people with disabilities — both employees and members of the public. This applies to all ICT that is developed, procured, maintained, or used by federal agencies. The 2018 Section 508 refresh updated the technical standards to incorporate WCAG 2.0 Level AA as the baseline for web content and software.

Section 508 directly applies only to federal agencies. However, state and local governments are covered by ADA Title II (see that section below), which was updated in 2024–2026 to require WCAG 2.1 AA compliance. Additionally, many state and local agencies are recipients of federal grant funds, and their funding agreements may include Section 508 compliance requirements. Federal contractors are also covered.

A VPAT (Voluntary Product Accessibility Template) is a document in which a vendor describes the accessibility conformance of their product or service. Federal agencies are required to request and review VPATs — more formally called Accessibility Conformance Reports (ACRs) — before purchasing ICT products. If you sell products or services to federal agencies, you need a current VPAT for each product. VPATs must be updated when products change significantly.

Section 508 covers: websites and web applications, software applications and operating systems, electronic documents (PDFs, Word, Excel, PowerPoint), video and multimedia content, kiosks and transaction machines, telecommunications products, and any other electronic or information technology procured by federal agencies. This includes internal systems used by federal employees, not just public-facing content.

The most common failures are: PDFs without proper tag structure (making them unreadable by screen readers), images without alt text descriptions, data tables without proper header markup, forms without labeled input fields, color used as the only means of conveying information, insufficient color contrast between text and background, and videos without captions. Most legacy government document libraries fail on the first two issues alone.

A compliant PDF requires: proper tag structure (Title, Heading, Paragraph, List, Table tags), alt text on all meaningful images, table header cells marked correctly, a logical reading order that matches visual order, document language specified in properties, no scanned pages (must be text-based or OCR'd), sufficient color contrast, form fields labeled and properly structured, and a document title set in properties. Most PDFs require professional remediation — automated tools alone cannot fully remediate a complex document.

A tagged PDF has structural tags that allow screen readers and assistive technology to navigate the document. An accessible PDF meets the full PDF/UA (ISO 14289) standard, which requires correct tagging plus proper reading order, alt text, language specification, tab order, security settings that allow accessibility, and other requirements. A tagged PDF may still fail accessibility standards if the tags are in the wrong order or are semantically incorrect. Professional remediation is the only reliable path to full PDF/UA compliance.

Section 508 recognizes two exceptions: (1) undue burden — where compliance would impose significant difficulty or expense, though the agency must still provide the information via an alternative accessible means; and (2) fundamental alteration — where compliance would fundamentally alter the nature of the program or activity. These exceptions are narrowly construed and require documented justification. They are not a routine escape hatch.

On April 24, 2024, the Department of Justice published a final rule under ADA Title II requiring state and local government entities to ensure their websites and mobile applications conform to WCAG 2.1 Level AA. Compliance deadlines: April 24, 2026 for entities with a population of 50,000 or more, and April 26, 2027 for smaller entities. This is now law — not a proposed rule.

All "public entities" under ADA Title II: state agencies, county agencies, city and town governments, public school districts and universities, public transit authorities, public housing agencies, and other state or local government entities. This includes entities that are instrumentalities of state or local government, even if they operate independently.

The rule covers websites (including web-based services, web content, and web applications) and native mobile applications offered by the public entity to the public or open to public participation. This includes all web pages accessible to the public, documents published to those web pages, and mobile apps. Archived web content, content posted by third parties not under the entity's control, and certain legacy content have limited exceptions.

WCAG 2.1 AA covers 50 success criteria organized around four principles — Perceivable (information can be perceived by all users), Operable (interface components are operable), Understandable (content is understandable), Robust (compatible with assistive technology). Level AA requirements include: minimum 4.5:1 color contrast ratio for text, captions for pre-recorded video, audio descriptions or media alternatives, keyboard accessibility for all functions, no content that flashes more than 3 times per second, visible focus indicators, and more. WCAG 2.1 added 17 new criteria beyond WCAG 2.0, including mobile-specific requirements.

WCAG 2.2 was published by W3C in September 2023 and became an ISO standard in 2024. It adds 9 new success criteria to WCAG 2.1, focused primarily on cognitive accessibility and mobile usability. The current ADA Title II rule requires WCAG 2.1 AA. However, organizations targeting best practice — or those whose populations include significant numbers of users with cognitive disabilities or mobile-primary access — should target WCAG 2.2 AA. Our audits cover both.

Non-compliant organizations are subject to DOJ enforcement, including investigation and potential findings, compliance agreements, and referral to the Department of Justice for litigation. Private individuals can also file complaints under ADA Title II, which can result in injunctions and attorney fees (though not damages under Title II). The most important action for any organization that missed the deadline is to immediately begin documented remediation — organizations actively working toward compliance are treated differently in enforcement than those with no action taken.

Yes. Web content includes documents posted to government websites — PDFs, Word documents, Excel files, and other content accessible via the web are covered. Documents must meet WCAG 2.1 AA requirements, which for PDFs means they must be properly tagged, have alt text for images, include captions for any embedded video, and be structured to support screen reader navigation. Documents created before the compliance deadline may have limited exceptions, but newly created or updated documents must be compliant.

Under Title VI and EO 13166, agencies must translate "vital documents" — those essential to accessing services, understanding legal rights, or making critical decisions. This includes: intake forms and applications, notices of rights and benefits, adverse action letters, consent forms, complaint procedures, and language access notices. Many states have specific lists. The safest approach is to translate any document that, if misunderstood, would deny, delay, or impair access to services.

There is no single federal minimum language list. The threshold commonly used is the "5% or 1,000 individuals" standard — translate into any language spoken by 5% or 1,000 eligible individuals (whichever is less) of the service population. Many state regulations set different thresholds. In practice, most government agencies in large metro areas must support at least Spanish, and many must also support Mandarin, Vietnamese, Arabic, Somali, Tagalog, Haitian Creole, or Portuguese depending on their service population.

A certified translation includes a signed declaration from the translator stating their competency in both languages and that the translation is complete and accurate. Certification is required by USCIS for immigration documents, by courts for legal proceedings, and by many academic institutions for foreign credentials. For government communications, "certified" is not always legally required but is strongly recommended for documents with legal effect (benefit determinations, adverse actions, legal rights notices).

Machine translation tools, including Google Translate and AI translation systems, are not adequate for official government documents with legal significance. They produce errors — sometimes subtle, sometimes significant — that can deny rights, create liability, or cause harm. Machine translation may be acceptable for informal informational content (website general information) when clearly labeled as machine-translated and a human review process is available. For vital documents, legal notices, benefit letters, and medical communications, human certified translation is required.

Translated documents should be updated whenever the source document is updated in a way that changes meaning, process, rights, or requirements. Many organizations batch-update translations on a quarterly or annual schedule. A simple tracking system — logging which translations exist and when source documents were last modified — is the minimum best practice. Documents with legal significance (benefit notices, rights disclosures) should be updated within 30 days of any substantive source change.

Translation converts the words of a document from one language to another. Localization adapts the content — not just the language — for a specific culture, region, or audience. This may include adapting idioms, cultural references, date formats, currency, units of measurement, and examples. For government communications to immigrant communities, localization often improves comprehension significantly. For legal documents with specific technical language, strict translation (not adaptation) is appropriate. Our team advises on the right approach for each document type.

When an LEP individual encounters a government agency service — whether in person, by phone, or in a meeting — the agency must provide free interpreter services upon request, and in many circumstances proactively (without waiting for a request). This includes benefit interviews, hearings, community meetings with direct service implications, and any interaction where the individual's ability to understand or communicate materially affects their access to services or their legal rights.

No. Under Title VI and EO 13166, federally assisted programs may not charge LEP individuals for the cost of interpretation services as a condition of receiving services. Requiring an LEP person to bring their own interpreter — or to pay for one — violates the meaningful access requirement and constitutes national origin discrimination.

In consecutive interpretation, the speaker pauses after each sentence or thought, and the interpreter renders the statement in the target language. It is used for most meetings, appointments, and interviews. In simultaneous interpretation, the interpreter renders the speech into the target language in real time, without pauses, using specialized equipment. Simultaneous interpretation is used for conferences, large public meetings, and legal proceedings where consecutive pausing would be impractical.

OPI (over-the-phone interpretation) connects a three-way phone call between the LEP individual, the agency, and an interpreter. It is available on-demand 24/7 and is appropriate for most routine service interactions. VRI (video remote interpretation) adds a visual component via video — important for ASL, for settings where facial expressions and gestures are significant (mental health, medical), and for IEP meetings. In-person interpretation is required for certain legal proceedings, complex medical situations, and events where physical presence is legally mandated or practically necessary.

Yes. IDEA requires that IEP meetings include the parents or guardians as active participants. When parents are LEP, this means providing a qualified interpreter in their language. Using a school staff member who "speaks some Spanish" is not sufficient — qualified interpretation means someone trained in interpretation ethics and technique, with fluency in both the educational and LEP individual's home language. Failure to provide meaningful parental participation can invalidate the IEP.

Under ADA Title II, public entities must provide effective communication for Deaf and Hard-of-Hearing individuals, which includes ASL interpretation when requested in advance. For public events — town halls, school board meetings, community hearings — proactive provision of ASL interpretation (announced in advance) is best practice. For legal proceedings, ASL interpretation is generally required whether or not it was requested in advance. RID-certified ASL interpreters are the professional standard.

School districts receiving federal funding (virtually all public school districts) are subject to: Title VI (language access for LEP families), IDEA (meaningful parental participation including interpretation for IEP meetings), Title III of ESEA (English learner programs and parent communication), FERPA (parent rights notices in a language they understand), and ADA Title II (accessible digital communications). The combined effect is among the most comprehensive language access obligations of any sector.

FERPA requires that schools provide parents with annual notification of their rights. The Department of Education interprets FERPA to require that this notice be provided in a language the parents can understand — meaning translation is required when a significant portion of the parent population is LEP. Additionally, any communication about a student's educational records that involves rights or decisions (discipline, enrollment, special education) should be communicated in the parent's primary language.

Title III of the Elementary and Secondary Education Act requires that school districts notify parents of English learner (EL) students about the EL program, the student's placement, and options for alternative placement. These notices must be provided in a language the parent can understand. Schools must notify parents within 30 days of the beginning of the school year, and for mid-year placements, within 2 weeks. Translation services are required to fulfill this obligation.

IDEA does not explicitly require that the IEP document itself be translated in all cases. However, it requires meaningful parental participation and informed consent. If a parent cannot understand the IEP document, their consent is not truly informed and their participation is not meaningful. DOJ and OCR have consistently found that meaningful participation under IDEA requires translation of key IEP documents for LEP parents. Districts are strongly advised to provide translated IEP documents whenever the parent's primary language is not English.

At minimum, the following must be provided in a language parents can understand: enrollment and registration materials, parent rights notices (FERPA, IDEA), EL placement notices (Title III), discipline notices and hearing procedures, special education eligibility and IEP process documents, report cards and progress reports when they affect placement decisions, emergency and safety communications, and community event notices for events requiring parental action or decision.

Section 504 of the Rehabilitation Act requires school districts to hold eligibility and placement meetings for students with disabilities. Like IDEA, meaningful parental participation is required, which means qualified interpretation must be provided for LEP parents. The interpreter for a 504 meeting should be familiar with disability-related educational terminology, not just a general interpreter. In-person or VRI interpretation is strongly preferred over OPI for 504 meetings given the complexity and emotional stakes.

Healthcare organizations receiving federal financial assistance (including Medicare/Medicaid, federally qualified health centers, and most hospitals) are subject to: Title VI (language access for LEP patients), Section 1557 of the ACA (non-discrimination including language access), Section 504 (accessibility for people with disabilities, including new 2026 digital accessibility rules), and state laws that often exceed federal minimums. HIPAA applies to confidentiality of health information accessed through interpreters and translation services.

Section 1557 prohibits discrimination in health programs and activities receiving federal financial assistance on the basis of race, color, national origin (including LEP status), sex, age, and disability. For language access, it requires covered entities to provide qualified oral language assistance services for LEP individuals free of charge, and to provide translated vital documents. The 2024 Section 1557 rule strengthened these requirements and added explicit provisions for digital accessibility.

Yes. Medical interpreters and translators who access protected health information (PHI) in the course of providing services are considered business associates under HIPAA. Healthcare organizations must have Business Associate Agreements (BAAs) with interpretation and translation vendors who access PHI. Reputable language service providers operating in healthcare maintain HIPAA-compliant workflows and will execute BAAs as a standard part of contracting. We have executed BAAs with numerous health systems.

Under Section 1557, vital documents must be translated into the languages of LEP populations that meet the 5% threshold. Healthcare vital documents include: consent forms, discharge instructions, patient rights notices, advance directive forms, insurance information and enrollment forms, appointment reminders (when they contain health-critical information), medication instructions, and notices about available language assistance services.

The HHS final rule under Section 504, effective May 11, 2026, requires healthcare organizations receiving federal financial assistance to ensure their electronic and information technology — including patient portals, telehealth platforms, appointment scheduling systems, and digital health records — is accessible to people with disabilities. The technical standard is WCAG 2.1 Level AA. This is a significant new obligation that requires healthcare IT systems to be audited and remediated.

No. Telehealth platforms are subject to the same language access obligations as in-person healthcare. Healthcare organizations must provide qualified interpreter services for telehealth encounters with LEP patients. VRI (video remote interpretation) is well-suited to telehealth contexts and can be integrated into most telehealth platforms. The platform itself must also be accessible under Section 504 and ADA requirements.

The GSA Multiple Award Schedule (MAS) is a long-term government-wide contract that pre-establishes pricing, terms, and conditions for commercial products and services. Federal agencies can order directly from GSA Schedule contractors without conducting a full competitive procurement. This saves weeks or months in the contracting process. Language Access Hub — powered by Taika Translations — holds an active GSA Schedule contract for language services.

NASPO ValuePoint is the cooperative purchasing program of the National Association of State Procurement Officials. It establishes master contracts through a lead-state competitive solicitation process. State agencies in participating states can issue task orders against NASPO master contracts without running their own competitive procurement. We hold an active NASPO ValuePoint cooperative contract for language services, with Participating Addendum agreements in multiple states.

If your state has a Participating Addendum with our NASPO contract, your school district, county agency, or local government can issue a task order directly against that PA. Contact us with your state and agency type and we will confirm your ordering path the same day. If your state does not have a PA, we can help navigate alternative vehicles or initiate the PA process.

We accept government purchase cards (P-cards), electronic funds transfer (EFT), purchase orders, and ACH payments. For large agencies or ongoing contracts, we support net-30 payment terms through an established contract vehicle. GSA SmartPay cards are accepted for GSA Schedule orders. We issue compliant invoices with all required contract line item numbers (CLINs) and agency-required references.

A Participating Addendum is a bilateral agreement between a state and the NASPO ValuePoint contractor (us) that allows agencies within that state to use the master NASPO contract. The PA specifies any state-specific terms, pricing adjustments, or scope modifications. We have active PAs in multiple states. Contact us to confirm whether your state has a PA and if not, whether your agency can initiate one.

No. Ordering from a GSA Schedule contract does not require a sole-source justification — the GSA competitive process already satisfies the competitive requirements of FAR Part 8. For orders under the micro-purchase threshold ($10,000 for most agencies), you can order from any GSA Schedule contractor without further competition. For larger orders, simplified ordering procedures apply depending on the order value. We can walk your contracting officer through the ordering procedures.

The Office for Civil Rights (OCR) at DOJ, HHS, DOE, or the relevant federal funding agency can investigate a Title VI complaint. If non-compliance is found, agencies typically enter into resolution agreements requiring corrective action plans, policy changes, staff training, and monitoring. Continued non-compliance can result in referral to DOJ for litigation. In egregious cases, termination of federal financial assistance is possible — though rarely the first remedy. The most significant practical risk is reputational and operational: the investigation process itself is disruptive.

Under Title VI, courts have held that there is no private right of action for disparate impact claims (the basis of most language access claims). However, ADA Title II does allow private lawsuits, including for web accessibility failures. Individuals can also file administrative complaints with federal OCR offices. Additionally, some states have broader state-law protections that do allow private suits for language access failures. The pattern of enforcement action and litigation in the WCAG/digital accessibility space is significant and increasing.

More than 5,000 ADA digital accessibility lawsuits were filed in federal court in 2025 — a 20% increase over 2024. State court filings add thousands more. Approximately 46% of defendants had previously been sued for similar violations, demonstrating that one-time remediation without ongoing compliance programs is insufficient. The average settlement for mid-size organizations has grown to $25,000–$50,000, not including attorney fees, remediation costs, and internal staff time.

A documented, actively pursued remediation plan does not create an absolute defense, but it is a significant mitigating factor in both enforcement actions and litigation. OCR and DOJ consistently demonstrate more flexibility with organizations that have a current compliance assessment, a written remediation plan with milestones, and evidence of active progress. Organizations with no action taken receive very different treatment than those demonstrating good-faith compliance efforts. Starting today — even if you've missed a deadline — matters.

Multiple federal agencies enforce language access requirements within their domains: DOJ Office for Civil Rights (general Title VI and ADA), HHS Office for Civil Rights (healthcare and education), DOE Office for Civil Rights (education), DOT Civil Rights Office (transportation), HUD Office of Fair Housing (housing), and USDA Office of Civil Rights (agriculture programs and nutrition programs). Each agency has its own investigation process but coordinates on shared standards. Complaints to any of these offices can trigger an investigation.