Skip to main content
Category: Standards and Guidelines

Electronic and Information Technology

Also known as: EIT, EIT, Electronic Information Technology
Simply put

Electronic and Information Technology (EIT) is a broad term for the electronic devices, software, systems, and digital information an organization uses, such as computer hardware and software, operating systems, web-based information and applications, and instructional or documentary materials. It was the category of technology addressed under the original Section 508 requirements. In the updated Section 508 rules (the '508 Refresh'), this term was replaced by 'Information and Communication Technology' (ICT).

Formal definition

Electronic and Information Technology (EIT) was the term used in the original Section 508 framework to describe covered technology, generally encompassing computer hardware and software, operating systems, web-based information and applications, and related documents, media, and information. Federal guidance indicates that the original law referred to EIT, while the Section 508 Refresh adopted 'Information and Communication Technology' (ICT) in its place; practitioners should treat EIT as largely superseded terminology when working under current Section 508 standards. The precise scope of what qualifies as covered EIT/ICT is determined by the applicable law, standard, and Federal Acquisition Regulation (FAR) provisions rather than by any single institutional definition, and individual agencies or institutions may define EIT for their own internal policies. This entry is informational and not legal advice; consult current Access Board standards and qualified counsel for compliance determinations.

Why it matters

Electronic and Information Technology (EIT) matters because it defined the scope of what federal agencies were required to make accessible under the original Section 508 framework. The term drew a boundary around the covered technology, computer hardware and software, operating systems, web-based information and applications, and related documents, media, and instructional materials, which in turn determined where accessibility obligations applied. Understanding this term helps practitioners interpret older policies, procurement records, and institutional documents that still use it.

The term is also significant because it has been largely superseded. Federal guidance indicates that the original law referred to EIT, while the Section 508 Refresh adopted 'Information and Communication Technology' (ICT) in its place. As a result, EIT is best treated as legacy terminology when working under current Section 508 standards. Practitioners who encounter EIT in existing agency or institutional policies should recognize that current compliance determinations generally rest on the updated ICT framework and the applicable Access Board standards.

Because the precise scope of covered technology is set by the applicable law, standard, and Federal Acquisition Regulation (FAR) provisions rather than by any single institutional definition, the practical meaning of EIT can vary between an agency's internal policy and the governing federal requirements. This entry is informational and not legal advice; organizations should consult current Access Board standards and qualified counsel to confirm what technology is covered and what obligations apply.

Who it's relevant to

Federal Agency Compliance and Procurement Staff
Personnel responsible for Section 508 compliance and technology acquisition may encounter EIT in older policies, contracts, and procurement records. They should understand that the term has generally been replaced by ICT in the Section 508 Refresh and that current obligations are defined by the applicable law, Access Board standards, and FAR provisions.
Higher Education and Institutional Policy Authors
Colleges, universities, and other institutions that adopted EIT in internal accessibility policies, covering items such as instructional materials, documents, media, web-based information, and related software, may still use the term. Policy owners should be aware that individual institutions may define EIT for their own purposes, and that these internal definitions do not override governing federal standards.
Legal Counsel and Accessibility Advisors
Attorneys and advisors interpreting Section 508 requirements should distinguish the original EIT terminology from the current ICT framework. Because scope is determined by the applicable law, standard, and FAR provisions, counsel should confirm which requirements apply in a given context and treat EIT as largely superseded terminology under current Section 508 standards.
Accessibility Engineers and Content Teams
Teams building or remediating covered technology, including software, web applications, operating systems, and documentary or instructional materials, benefit from recognizing how EIT scoped covered technology historically. When working under current standards, they should map legacy EIT references to the ICT framework and the relevant Access Board conformance requirements.

Inside EIT

Information Technology Systems
Hardware, software, and networked systems used to create, store, process, or transmit information, which fall within the scope of EIT when they present information or enable interaction.
Electronic Content
Digital documents, web pages, multimedia, and other electronically produced materials that convey information to users and must be perceivable and operable by people with disabilities.
Hardware and Devices
Physical equipment such as computers, kiosks, telecommunications equipment, and peripherals that may need accessible controls, displays, and connection points for assistive technology.
Software Applications
Programs and applications, including operating systems and productivity tools, that must support accessibility features and interoperate with assistive technologies.
Telecommunications Products
Equipment and services used for electronic communication, which may fall within EIT depending on the applicable authority and context.

Common questions

Answers to the questions practitioners most commonly ask about EIT.

Is 'Electronic and Information Technology (EIT)' the same thing as 'Information and Communication Technology (ICT)'?
They are related but not identical. 'Electronic and Information Technology' is the terminology historically associated with the original Section 508 framework covering federal agencies, while 'Information and Communication Technology (ICT)' is the term used in the refreshed Section 508 standards, which were aligned with broader international terminology. The shift in language reflects an effort to harmonize with other standards and to more clearly encompass communication technologies. When reading older versus newer materials, be aware that the term applied to your context may depend on when the guidance was written. This entry describes terminology and does not constitute legal advice; consult current Access Board materials for the language in force.
Does the term EIT mean the ADA legally mandates specific technical requirements for this technology?
No. The concept of Electronic and Information Technology is most closely tied to Section 508 of the Rehabilitation Act, which applies to federal agencies and certain covered federal contexts, rather than to the Americans with Disabilities Act. The ADA is a civil rights law and does not itself contain the detailed EIT or ICT technical specifications found in the Section 508 standards. Courts and settlements interpreting the ADA have often referenced technical benchmarks such as WCAG, but that is distinct from EIT as a Section 508 concept. Keep these authorities separate, and consult qualified legal counsel regarding which framework applies to your organization.
What kinds of products and systems generally fall within Electronic and Information Technology?
EIT commonly encompasses a broad range of technology used to create, store, transmit, or process information, which may include websites, software applications, electronic documents, and hardware such as computers and related equipment. The precise scope depends on the applicable standard and how it defines covered technology. Because the term originates in the Section 508 context, its practical boundaries are best determined by reference to current Access Board standards and any agency-specific guidance rather than assumed to cover every possible system uniformly.
How does an organization begin assessing whether its EIT is accessible?
Organizations often start by inventorying the covered technology, then evaluating it against the applicable technical standard. In the Section 508 context, the refreshed standards incorporate WCAG success criteria as part of their requirements for web content and certain software. Assessment generally combines automated testing with manual review and testing using assistive technologies, since automated tools detect only a portion of potential issues. Meeting technical criteria supports accessibility but does not by itself guarantee a fully accessible experience for all users.
How is procurement of EIT typically handled to support accessibility?
Accessibility is commonly addressed during procurement by including accessibility requirements in solicitations and by evaluating vendor documentation of conformance. Vendors may provide accessibility conformance documentation describing how their product meets applicable criteria. Such documentation is a starting point rather than a guarantee, and organizations often verify claims through their own testing. Requirements and expectations evolve through regulation and agency guidance, so procurement practices should reference current standards.
What role does manual testing play in evaluating EIT beyond automated checks?
Manual testing is generally considered essential because automated tools can identify only a subset of accessibility issues. Manual and assistive technology testing, such as evaluating keyboard navigation and screen reader interaction, helps surface barriers that automated scans may miss. A combined approach of automated and manual testing is commonly recommended to give a more complete picture of how EIT performs for people using a range of assistive technologies. Conformance findings from this process inform, but do not alone determine, legal compliance.

Common misconceptions

EIT is the same thing as "web content" and only concerns websites.
EIT is a broader category that can encompass hardware, software, telecommunications equipment, and electronic content, not just websites. Web content is one subset of the technologies that may be considered EIT.
The term EIT and its scope are uniform across all US accessibility laws.
Terminology and scope depend on the applicable authority. Section 508 applies to federal agencies and covered federal contexts, while the ADA's Title II (state and local government) and Title III (public accommodations) address different scopes. Which technologies are covered, and how, depends on the specific law and any relevant regulation or guidance, and this material is not legal advice.
If a piece of EIT passes automated accessibility checks, it is fully accessible and legally safe.
Automated testing detects only a portion of accessibility issues. Manual review and assistive technology testing are generally required, and conformance does not by itself guarantee an accessible experience for all users or immunity from legal claims.

Best practices

Inventory all forms of EIT in your environment, including hardware, software, electronic content, and telecommunications products, rather than focusing only on websites.
Identify which authority applies to your context (for example Section 508 for covered federal contexts versus ADA Title II or Title III) and scope accessibility requirements accordingly.
Combine automated testing with manual review and testing using assistive technologies, since automated tools catch only a portion of issues.
Where WCAG is used as a benchmark, confirm the target version and conformance level (AA is the level most commonly cited) and document it in procurement and development requirements.
Address accessibility early in procurement and design so that EIT supports interoperability with assistive technology from the outset.
Consult qualified legal counsel and monitor current agency rulemaking and case law, as requirements evolve and this guidance is not a substitute for legal advice.