Digital Accessibility for Employers

Why Employers Encounter Digital Accessibility

Most of the work an organization does now runs through digital systems. People apply for jobs through online portals, onboard through document workflows, learn through training platforms, collaborate through shared tools, and manage their pay, benefits, and schedules through employee self-service systems.

When those systems are not accessible, the effect is not limited to inconvenience. A candidate may be unable to submit an application. An employee may be unable to complete required training, enroll in benefits, or participate in a meeting on equal terms.

This page looks at digital accessibility from an employer's perspective. It sits alongside the Employment and Workplace Accommodations resource, which covers the reasonable accommodation process and assistive technology in the workplace in detail. This page focuses on the systems themselves and on the legal distinctions employers most often get wrong.

The Legal Picture, Stated Carefully

Employers frequently ask whether they are legally required to meet a particular version of WCAG. For most private employers the honest answer is that no federal regulation currently names a WCAG version and level as the technical standard for employment technology.

That is not the same as saying there are no obligations.

Title I of the Americans with Disabilities Act applies to covered employers and prohibits disability discrimination in the application process, hiring, advancement, training, compensation, and other terms and conditions of employment. It requires reasonable accommodation for qualified applicants and employees with disabilities, absent undue hardship. Those duties apply regardless of whether a barrier is physical or digital. Equal Employment Opportunity Commission guidance on the hiring process is framed in terms of nondiscrimination and accommodation rather than conformance to a technical standard.

Three specific claims should be avoided because they are inaccurate.

Title II's WCAG 2.1 Level AA rule does not apply generally to private employers. It applies to state and local government entities and to the web content and mobile applications they provide as public entities.

Section 508 does not apply generally to private businesses. It applies to federal agencies and reaches suppliers through federal procurement.

There is no current federal regulation requiring every private employer's website to meet a named WCAG version under Title I.

Where Specific Requirements Do Apply

Some employers do face named technical requirements, and it is worth identifying whether an organization is in one of these categories.

Federal agencies as employers are covered by Section 508 for their information and communication technology, which includes systems used by their own employees. The Revised Section 508 Standards incorporate WCAG 2.0 Level A and Level AA for electronic content. Section 501 of the Rehabilitation Act addresses federal employment nondiscrimination and affirmative action.

Federal contractors and subcontractors may have obligations under Section 503 of the Rehabilitation Act. When supplying ICT to a federal agency, they may also be required by the solicitation or contract to satisfy applicable Revised Section 508 requirements. A contractor's own internal ICT is not automatically subject to Section 508 merely because the organization holds a federal contract.

State and local government employers are public entities. The Title II web and mobile accessibility rule applies to web content and mobile apps that a public entity provides or makes available, subject to the rule's scope and exceptions, and uses WCAG 2.1 Level A and Level AA as its technical standard. State and local government employers also have employment-discrimination and reasonable-accommodation obligations, so their employment systems may implicate more than one legal framework.

Employers operating in other jurisdictions, or under state procurement rules, grant conditions, or customer contracts, may have further requirements that name a standard directly.

Recruitment and Online Applications

The application process is where digital barriers most often exclude people before any human review takes place.

Common problems include application forms that cannot be completed with a keyboard alone, required fields whose labels are not programmatically associated with their inputs, error messages conveyed only by color, timed sessions that expire during a longer application, resume parsers that reject accessible document formats, and assessment or video interview tools that were never tested with assistive technology.

Two practical points matter here. A barrier in a third-party applicant tracking system is still a barrier in the employer's hiring process, and the employer is the one making the hiring decision. Providing an alternative route, such as a monitored email address or phone number for an applicant who cannot use the online system, may be an effective accommodation in an individual case. As an organizational accessibility strategy, however, relying only on ad hoc alternatives leaves the underlying digital barrier in place.

Internal Systems and Employee Portals

Once someone is hired, the systems they must use to do their job and to manage their employment become the relevant surface.

This includes human resources self-service, payroll and benefits enrollment, time and scheduling, expense and travel tools, performance management, internal ticketing and request systems, and the intranet.

These systems are usually purchased rather than built, which places most of the leverage at procurement and renewal rather than in remediation. Where an employee cannot use a core system, reasonable accommodation obligations may be triggered, and an accommodation that requires a colleague to complete tasks on the employee's behalf is rarely a satisfactory long-term answer for something like viewing a payslip or enrolling in benefits.

Training Platforms and Materials

Required training is a frequent source of complaints because completion is often mandatory and tracked.

The platform and the content inside it raise separate questions. A learning management system may be accessible while the course loaded into it is not. Recorded modules need accurate captions rather than automatic captions left unchecked, and audio description where visual information carries meaning that the narration does not. Interactive modules built in authoring tools need keyboard operability and correct labeling. Knowledge checks and assessments need to be usable with assistive technology, and timed assessments raise their own issues.

Where training is a condition of employment or advancement, an inaccessible module can become an access barrier to the job itself rather than a content inconvenience.

Collaboration Tools and Meetings

Day-to-day collaboration tools shape whether someone can participate on equal terms.

Practical considerations include whether the meeting platform supports captioning and whether captions are enabled by default, whether screen sharing has an accessible alternative for conveying the same information, whether chat and reaction features are usable with a screen reader, whether recordings are captioned before distribution, and whether shared documents are created in accessible formats rather than as scanned images or screenshots of text.

Meeting practice matters alongside the tooling. Describing visual content aloud, sharing materials in advance, and not relying solely on chat for decisions all reduce barriers without requiring a product change.

Documents and Communications

Most employers generate a large volume of internal documents, and these are generally the least governed part of the digital estate.

At an overview level, accessible documents have real heading structure rather than text formatted to look like headings, a logical reading order, meaningful alternative text on images that carry information, properly structured tables, descriptive link text, and sufficient contrast. Accessibility work is substantially cheaper in the source file than in an exported PDF, because the export carries the structure of the source.

For more detailed guidance, see Accessible Documents. The point for employers here is narrower: policy documents, benefits summaries, safety information, and handbooks are frequently the materials employees most need to read independently.

Remote and Hybrid Work

Remote and hybrid arrangements increase dependence on digital systems, which raises the impact of any inaccessibility.

They also change the accommodation picture. Equipment and software that an employer provided in an office may need to be available at home. Assistive technology that an employee uses must be compatible with the remote access method, and virtual desktop or remote session software is a common point of failure for screen readers and speech recognition. Security controls, including multifactor authentication, can introduce barriers, which is one reason the accessible authentication criterion added in WCAG 2.2 is relevant to employers even where it is not legally required.

Assistive Technology Compatibility

Employers do not need to test every assistive technology, but they do need systems that are capable of working with them.

The underlying properties are the same ones WCAG describes. Controls need accessible names so speech recognition can target them and screen readers can announce them. Interfaces need full keyboard operability for switch and keyboard users. Content needs to reflow and remain functional under magnification. Structure needs to be exposed correctly so navigation by heading, landmark, or form field works.

Where a specific employee uses a specific tool, testing with that combination is more informative than a general conformance claim, and it is often the fastest route to a workable accommodation.

Accommodation Versus Systemic Accessibility

Employers benefit from holding two related but different obligations apart.

Reasonable accommodation is individual, reactive, and triggered by a particular person's needs. It is a legal duty under the ADA for covered employers, and it can involve providing software, equipment, alternative formats, or changes in how work is done.

Systemic digital accessibility is organizational and proactive. It concerns whether the systems an employer chooses and deploys are usable by disabled people in general.

An organization that relies only on accommodation ends up solving the same barrier repeatedly, one person at a time, often under time pressure and sometimes after a candidate has already been lost. An organization that builds accessibility into procurement and deployment reduces both the volume of accommodation requests and the difficulty of meeting the ones that remain.

Procurement and Vendors, at Overview Level

Because most employment technology is bought, procurement is where an employer has the most influence.

At an overview level, the useful practices are asking for current accessibility conformance information for the specific version being purchased and reading it critically rather than treating its existence as proof, writing the applicable standard and conformance level into the contract rather than relying on a marketing claim, testing high-use systems before purchase where possible, and tracking remediation commitments to the renewal date.

A claim of Revised Section 508 conformance should not be read as simply a WCAG 2.0 Level A and AA claim. The Revised 508 Standards incorporate those WCAG criteria and also contain additional requirements that can apply depending on the type of ICT. An employer may also choose an accessibility target beyond the minimum required by a particular contract or legal framework. For more detailed guidance on conformance reports, see VPAT and Accessibility Conformance Reports. For the full purchasing process, from requirements through contracts, acceptance, and renewal, see Accessible Procurement.

Practical Starting Points

Employers often ask where to begin when the whole estate seems in scope.

Identifying the systems a person must use to be hired, to be paid, and to keep their job narrows the field quickly. Those systems carry the highest consequence when they fail. Establishing who owns accessibility for each of them prevents the common situation where a barrier is everyone's concern and no one's responsibility. Adding accessibility criteria to procurement affects every future purchase rather than only the current problem. Creating a clear, low-friction route for applicants and employees to report barriers surfaces issues before they become disputes.

Related AssistiveTechnology.org Resources

For the reasonable accommodation process, the interactive process, and assistive technology in the workplace, see Employment and Workplace Accommodations. For what WCAG is and how conformance levels work, see WCAG Overview. For how WCAG relates to United States law, see WCAG vs ADA vs Section 508. For the differences between recent WCAG versions, see WCAG 2.1 vs 2.2. For public entity obligations, see ADA Title II Digital Accessibility for State and Local Governments. For a general orientation, see Digital Accessibility, and for further reading across topics, see Resources.

Request accessibility services

Authoritative Sources

U.S. Equal Employment Opportunity Commission: guidance on job applicants and the ADA, and enforcement guidance on reasonable accommodation and undue hardship under the ADA.

U.S. Equal Employment Opportunity Commission: Titles I and V of the Americans with Disabilities Act of 1990.

U.S. Access Board: Revised Section 508 Standards, including the incorporation of WCAG 2.0 Level A and Level AA for electronic content.

Section508.gov: Laws and Policies, for the scope of Section 508 and related Rehabilitation Act provisions.

28 CFR part 35, subpart H, and U.S. Department of Justice, ADA.gov: Fact Sheet on the rule for web content and mobile applications of state and local government entities.

World Wide Web Consortium, Web Accessibility Initiative: WCAG 2 Overview.

Last Regulatory Review

Last regulatory review: September 21, 2026. On that date the scope of ADA Title I employer obligations, the current federal regulatory treatment of technical accessibility standards for private-employer technology, the scope of Section 508 and its incorporated WCAG version, the Title II rule standard, and the framing of Equal Employment Opportunity Commission guidance on the hiring process were verified against current Equal Employment Opportunity Commission, Department of Justice, U.S. Access Board, and Section508.gov sources.

About This Page

This page provides general educational information about digital accessibility in employment settings in the United States. It is prepared by The Accessibility Clinic Inc. as educational information only. It is not legal advice, it does not determine which laws apply to any particular employer, and it does not evaluate whether any specific system, platform, or document meets a legal requirement or technical standard. Employers should evaluate their own obligations in light of their specific circumstances and consult qualified counsel when needed. Regulations and standards change; the last regulatory review date above indicates when the statements on this page were most recently verified against primary sources.