UI Technology Services Glossary

The terminology surrounding user interface technology services spans design disciplines, engineering frameworks, accessibility law, and procurement practice. This glossary defines the core terms encountered across the UI services landscape — from foundational design concepts to delivery models and compliance standards. Precise vocabulary reduces misalignment between clients, practitioners, and vendors, particularly in scoped engagements where ambiguity in a single term can shift project cost, timeline, or legal exposure.

Definition and scope

A glossary in the UI technology services context is a structured reference that assigns bounded, operationally consistent meanings to terms used across design, front-end engineering, accessibility, and service delivery. The scope of this glossary covers terminology applicable to UI technology services explained in full — from early-stage strategy through production deployment and ongoing quality assurance.

Terms are drawn from three primary source domains:

1. Design and UX standards — vocabulary defined by the Interaction Design Foundation and the Nielsen Norman Group, the two most widely cited practitioner-facing research bodies in the field.
2. Accessibility and legal compliance — terms governed by the Web Content Accessibility Guidelines (WCAG) 2.1, published by the W3C Web Accessibility Initiative, and by Section 508 of the Rehabilitation Act (29 U.S.C. § 794d).
3. Engineering and delivery — vocabulary aligned with RFC standards for web protocols, WHATWG living standards for HTML, and ECMA-262 for JavaScript specification.

Terms in this glossary are classified by domain tag: [Design], [Engineering], [Accessibility], or [Delivery]. Where a term straddles domains, the primary operational context governs its classification.

How it works

Glossary entries follow a structured format: the term, its domain tag, a definition, and where applicable, a contrast with a closely related term. This format is consistent with terminology management practices recommended by the ISO 704:2022 standard for terminology work and principles of concept formation.

Core term definitions:

Affordance [Design] — A perceptible property of a UI element that signals how it can be interacted with. A raised button affords clicking; a text field affords typing. The concept originates in Donald Norman's The Design of Everyday Things and is operationalized in UI design system documentation to specify when visual cues must match interaction capability.

Component Library [Engineering] — A versioned, distributable collection of reusable UI elements (buttons, modals, form inputs, navigation patterns) built in a specific framework such as React, Vue, or Angular. Distinguished from a Design System in that a component library is the code artifact; a design system includes design tokens, usage guidelines, governance processes, and brand rules in addition to the component code. See UI Component Library Development for service-level distinctions.

Design Token [Design/Engineering] — A named variable that stores a design decision — color, spacing, typography scale, or motion duration — in a format consumable by both design tools and code. The W3C Design Tokens Community Group published a draft specification in 2022 to standardize token interchange formats across toolchains.

WCAG Conformance Level [Accessibility] — One of three tiers of compliance under WCAG 2.1: Level A (minimum, 30 success criteria), Level AA (standard legal threshold, 50 success criteria), and Level AAA (enhanced, 78 success criteria). The U.S. Department of Justice has cited WCAG 2.1 Level AA as the operative standard in enforcement actions under Title II of the ADA (DOJ Final Rule, 28 CFR Part 35, 2024). Details on compliance services appear at WCAG and ADA Compliance in UI Services.

Responsive Design [Engineering] — A front-end architecture approach in which layout, typography, and interaction patterns adapt to the viewport dimensions of the rendering device, achieved through CSS media queries, fluid grids, and flexible images as defined in the CSS Snapshot 2023 published by the W3C.

Usability Testing [Design/Delivery] — A structured evaluation method in which representative users attempt predefined tasks within a UI, and their performance and errors are measured. Distinguished from Heuristic Evaluation, which involves expert reviewers assessing a UI against established heuristics (Nielsen's 10 heuristics being the most referenced framework) rather than live user sessions.

Time on Task [Design] — A quantitative usability metric measuring the elapsed time a user requires to complete a defined task. Benchmarked against baseline performance, it is one of the 5 measurable dimensions of usability defined by ISO 9241-11:2018: effectiveness, efficiency, and satisfaction.

Common scenarios

Glossary terms surface most frequently in three operational contexts:

1. Procurement and scoping — RFPs for UI usability testing services often conflate "usability testing" with "QA testing." The distinction matters: usability testing measures human performance against task goals; UI QA and testing services verify functional correctness, cross-browser rendering, and regression behavior against specifications.

2. Accessibility audits — WCAG conformance level requirements differ between public-sector and commercial contracts. Federal agencies procuring under Section 508 must meet the Revised 508 Standards (January 2017) aligned with WCAG 2.0 Level AA, while DOJ enforcement for state and local government under Title II references WCAG 2.1 Level AA.

3. Design system governance — Organizations distinguishing between a "design system" and a "component library" in vendor contracts avoid scope disputes when one deliverable is complete and the other is not. The Nielsen Norman Group's 2023 survey of 1,500 UX professionals found that 33% of teams reported misaligned expectations between design and engineering deliverables.

Decision boundaries

Term boundaries that cause the most frequent operational disputes:

Precise classification matters most when scoping UI prototyping services against full-build engagements. A prototype may satisfy design validation requirements at a fraction of the development cost, but it cannot substitute for a production front-end deployment.

References

• W3C Web Content Accessibility Guidelines (WCAG) 2.1
• U.S. Access Board — Revised Section 508 Standards
• DOJ Final Rule on Web Accessibility, 28 CFR Part 35 (2024)
• ISO 9241-11:2018 — Ergonomics of Human-System Interaction: Usability Definitions
• ISO 704:2022 — Terminology Work: Principles and Methods
• W3C Design Tokens Community Group
• WHATWG HTML Living Standard
• ECMA-262 — ECMAScript Language Specification
• W3C CSS Snapshot 2023
• Nielsen Norman Group — Design Systems 101