---
id: hif.glossary
title: "HIF Glossary"
kind: standard-part
standard: hif
part: reference
domain: design
description: "The terms HIF uses, each with one meaning: the vocabulary of the Constitution, of evaluation and conformance, of the rule model and the two-level profile model, and the terms that decide a verdict in the other parts, such as material, essential, key task, representative participants and high-risk."
status: draft
last_reviewed: 2026-11-21
review_every: 12
sidebar:
  order: 38
---

## Summary

A term is defined once, here, and used with that meaning everywhere in HIF. This glossary covers the vocabulary of the
[Interface Constitution](/hif/constitution/), of [Evaluation and Conformance](/hif/evaluation/) and of the rule model
and the two-level profile model, and the terms that decide a verdict in the other parts. A term of another part is added
in the same change that brings that part to the rule model. Defined terms are written in italics inside other
definitions. Where the rules use a term in two senses, the entry gives the main sense first and names the other as a
variant. A definition describes how the rules use a term and sets no requirement.

## Terms

### Accessibility baseline

The minimum accessibility standard that a *Product Profile* adopts before the product claims conformance. The profile
names it; the default for web surfaces is WCAG 2.2 Level A and Level AA ([Accessibility and
Inclusion](/hif/accessibility/), `HIF-ACC-001`). The baseline is *confirmed* when the *conformance claim* states the
result of evaluating it: for every applicable Level A and Level AA criterion, whether it is met, failed or excepted
under `HIF-EVL-024` (`HIF-EVL-015`). Confirmed means that this result is stated. It does not say that the baseline is
met; whether a failed criterion bars the level *HIF-Conformant* is not decided by this term.

### Accessibility Conformance Report

A supplier's report of how far a product meets an accessibility standard, criterion by criterion, in a published
format such as a VPAT. HIF treats it as evidence to assess and not as proof (`HIF-ACC-102`, `HIF-ACC-103`).

### Accessibility records

The records in which the accessibility part holds its evidence. The *assurance record* is the Accessibility Assurance
and Conformance Record, one per product release or audit scope, built from the
[template](/hif/accessibility-assurance-template/) in 24 sections (`HIF-ACC-043`, `HIF-ACC-089`, `HIF-ACC-104`). It
contains three records of its own. The *criteria matrix* (section 8) gives one outcome (pass, fail, not applicable
with a reason, not tested or cannot tell) for each applicable requirement and success criterion, with the method, the
scope of the evidence and the finding or exception that goes with it. The *keyboard test log* (section 11) shows, for
each control type, the keys of its model that were exercised and not only Tab (`HIF-ACC-075`). The *finding register*
(section 18) holds each finding with its severity and priority (`HIF-ACC-087`, `HIF-ACC-089`). The *design record*
lies outside the assurance record: it is the product's own record of its design decisions, such as a *design
hypothesis record*, in which the barriers examined and the adaptations chosen for each user need are noted
(`HIF-ACC-035`).

### Adapter

A part of an inspection tool that observes one bounded representation of a product and yields evidence for the rules
whose check it can carry: the URL source adapter (the HTML response and selected headers of a public URL), the image
adapter (a decoded image file), the *browser worker* (rendered states) and the journey and human adapters (scripted
journeys, expert and participant records) ([Inspection Tooling](/hif/inspection-tooling/) §4). What an adapter did not
observe is stated in the *coverage boundary*.

Variants: a platform adapter of a design system renders a component on one target and keeps its semantics
(design-systems-engineering §2.8); the brand-expression adapter maps *semantic tokens* to an approved brand package,
one *layer* of the white-label stack (`HIF-BRD-042`).

### AI-mediated

Of an interface, path, step or action: part of what the person gets or does is inferred, generated or decided by a
model, and is not fixed by a rule the person can read. Generated content, a recommendation, an automated answer and an
agent acting for the person are examples. An AI-mediated interface is an *automation* (`HIF-AUT-006`, `HIF-ACC-083`).

### Applicable requirement

A requirement that the product's *Product Profile* selects for it, because the product has the thing the requirement
governs. A conformance claim covers the applicable requirements and no others.

### Application Profile

A class of products for which HIF fixes the required, permitted and invariant behaviour, for example a web product or a
desktop application. Application Profiles ship with HIF and are listed in [Application Profiles](/hif/profiles/).
Compare *Product Profile*.

### Asset

A file or item that a product takes in from a source and that carries rights: a font, icon, image, illustration,
audio, voice or haptic file, template, code, palette, dataset or model-generated item. Each asset has an asset record
(identity, checksum, source, licence) and, if it is externally sourced or commissioned, an entry in the *rights
ledger* (`HIF-BRD-027`, `HIF-BRD-054`). The *production library* is where the assets that can reach users are kept.

### Assistive technology

Software or hardware that people use to operate or perceive an interface in place of, or beside, its default means:
screen readers, magnifiers, switch devices, voice control and similar.

### Authority

The permission to act on something, granted to a person, a process or an *automation*. The scope of an authority is
what it covers.

### Automation

A process that acts for a person or without their direct command, including software that infers, generates or decides.
An AI-mediated interface is an automation.

### Baseline gamut

The range of colours that every supported display can show. Each required colour value exists in it, and a wider
*gamut* only adds expression on top.

### Brand Profile

The record in which one brand or one brand package states its identity: strategy, assets, colour, type, voice,
imagery, white-label packaging, portfolio relationship and rights ([Brand Profile](/hif/brand-profile-template/)). The
*Product Profile* names it in its visual profile section. It is not a profile of products; see *Profile*.

### Brand seed

The colour, or the small set of colours, from which a brand starts and from which a palette is derived: a seed hue, a
set of anchors or a preferred swatch. A brand seed does not decide what a colour role means (`HIF-COL-001`).

### Browser worker

The *adapter* of an inspection tool that runs a browser. It executes named states at controlled mobile and desktop
device settings and collects the accessibility tree, computed styles, geometry, screenshots, console output, network
records and performance traces. Each run records browser, engine, viewport, input capabilities, locale, preferences
and authentication boundary (`HIF-INS-009`, `HIF-INS-010`).

### Capture state

A *state* in which the interface takes the keyboard, the pointer or the whole screen for itself, so that the person's
usual ways of moving away do not apply: a full-screen mode, a field that records a key combination, a pointer lock, a
modal that keeps focus. Together with a temporary mode (a state in which input means something other than usual until
it is left) and a *temporary layer*, it is a state the person has to be able to leave (`HIF-NAV-005`).

### Check

The field of a *rule* that says how it is verified: the method, the *evidence classes* it yields and the *oracle*.

### Colour system

The colour roles of a product and their meanings, the values and *tokens* that realise them in every mode, state,
theme, medium and *display class*, the contrast, gamut and conversion policy, and the source of every external asset.
It starts from communication, task and environment and not from swatches (`HIF-COL-001`, `HIF-COL-002`,
`HIF-CLR-001`). The record of a colour system is its *Colour System Profile*. Compare *Theme*.

### Colour System Profile

The record in which a product commissions, generates, reviews and releases its *colour system* ([Colour System
Profile](/hif/colour-system-profile-template/)). It is neither an *ICC profile* nor an *Application Profile*; see
*Profile*.

### Command

A named action with defined preconditions, effects, *authority*, reversibility and outcomes, independent of the gesture
that triggers it. A command that has consequences is a *consequential action* offered as a command.

### Command catalogue

The list of a product's *commands*, held in a registry, a schema or a table, in which each command is defined by its
preconditions, effects, *authority*, reversibility and outcomes (`HIF-CMD-001`). The commands section of the *Product
Profile* is where the product names them.

Variant: the command model is the whole arrangement of which the catalogue is the list: the commands, their bindings
to input, validation, state transitions and the representation of outcomes (`HIF-IXM-001`).

### Compensating action

An action that restores an equivalent outcome when literal undo is impossible, such as a refund after a payment.

### Confirmshaming

Wording that shames a person for refusing, such as "No thanks, I don't like saving money". It is a *dark pattern*.

### Conformance level

One of the three levels at which a product can claim conformance: *HIF-Declared*, *HIF-Conformant* or *HIF-Validated*.
Compare *level*, which is the strength of a rule.

### Conformance claim

A product's statement that it meets HIF at a stated level. It names the HIF version and the *Product Profile*, and
states the scope, the date, the evidence and the exceptions. The levels are *HIF-Declared*, *HIF-Conformant* and
*HIF-Validated* ([Evaluation and Conformance](/hif/evaluation/) §7).

### Consequential

Of an action, decision, outcome, error, relationship, use, review, visualisation or research participation: it bears
on a person's rights, data, money, safety or relationships, the test of *Consequential action*. The test is put to the
result of getting it wrong, and the product's risk record (`HIF-CTX-003`) is where the judgement is written down.

A decision is consequential when a wrong result harms people in one of those five ways or is hard to reverse
(`HIF-DPR-002`, `HIF-FEV-022`). An outcome is consequential when it is the result of a consequential action, such as a
payment taken or an item deleted (`HIF-PAT-030`). A use of colour or a relationship between elements is consequential
when misreading it leads to such an outcome (`HIF-CLR-018`, `HIF-LAY-004`).

A visualisation is consequential when people take an action or decision on its basis that leads to such an outcome,
and its review record says so (`HIF-DVZ-043`). A review is consequential when its decision leads to such an action or
decision (`HIF-DRC-005`). Research participation is consequential when it carries risk or cost for the person beyond
the session, such as collecting personal data or exposing them to a changed experience in a consequential area
(`HIF-MET-020`).

### Consequential action

An action whose effect matters to a person's rights, data, money, safety or relationships, as opposed to a harmless
one. Its safeguards are set in proportion to its risk. See *Consequential* for the other things that are called
consequential.

### Constitution

The [Interface Constitution](/hif/constitution/): the universal requirements of HIF, in fifteen sections, which a
*Product Profile* may strengthen and does not weaken without a recorded *exception*.

### Context of use

The users, goals, tasks, equipment and environments in which a product is used.

### Contrast contract

The contrast ratios a *Product Profile* requires for text, boundaries, focus and states, at least those of WCAG 2.2
success criteria 1.4.3 and 1.4.11, and the modes and states in which they hold.

### Contrast mode

A presentation mode in which the platform or the person changes contrast: the default, increased or high contrast, and
*forced colours*. A dark theme is not a contrast mode (`HIF-ACC-063`). A colour mode (light or dark) and a contrast
mode are crossed in the state matrix of a *status family* (`HIF-CLR-013`).

### Coverage boundary

What an inspection run covers and what it leaves out: the inputs observed and the final target, the rules evaluated
and passed, the *adapters* used, the states and requirements that were not observed, the warnings and errors of the
run, the assumptions about the environment and the manual follow-ups. "No findings" is read only together with it
(`HIF-INS-015`).

### Dark pattern

An interface design that steers a choice by concealment, obstruction, false urgency, *confirmshaming*, disguised
advertising or asymmetric friction.

### Delivery contract

The conditions of one output for which colour is delivered: its colour space and gamut, precision, medium and
conversion (`HIF-COL-002`). A palette colour is classified against it as valid in the baseline gamut, enhanced with a
fallback, output-specific and unavailable in a required medium, or invalid for it (`HIF-CLR-009`). Compare *display
class*.

### Density profile

A named setting of spacing and information density for a view or component, such as compact or comfortable. A density
profile keeps semantics and operability: a compact one reduces spacing and shows more comparable data, and keeps
accessible names, focus visibility, error recovery and necessary state (`HIF-DFN-019`). It is not a *Product Profile*;
see *Profile*.

### Design claim

A statement that a design choice has an effect on stated people in a stated context, such as "moving the delivery
estimate above the button helps first-time buyers understand the date before paying". A claim is stated with seven
entries, among them the mechanism, the evidence, the assumptions that make the evidence transferable, the way the
claim can be falsified, and the remaining uncertainty and its owner (`HIF-FEV-001`). A high-risk design claim names
its evidence and assumptions (`HIF-FEV-031`).

### Design hypothesis record

The record kept for a *material* design decision: the decision and its owner, the people, task and context, the
problem and desired outcome, the claim and its classification, the alternatives considered, the success, guardrail and
failure measures, the result and uncertainty, the chosen option and the reason for it, and the effect on tokens,
components, content, accessibility and localisation (`HIF-DFN-002`). It keeps what was observed apart from what was
inferred and what was decided (`HIF-DFN-025`). Compare *evidence record*.

### Destructive action

A *consequential action* that deletes, or irreversibly changes, data, access or state.

### Display class

A category of display or output on which the product is shown, set apart by what matters for colour and legibility,
for example gamut, brightness range, size and the ambient conditions of use. The *Colour System Profile* lists the
display classes the product supports (`HIF-CLR-001`). Compare *delivery contract*.

### Distributed cognition

The view that knowing and remembering are spread across people, tools and representations, not held in one head. It is
why *state* and *provenance* must be visible where a decision is taken.

### Durable refusal

A person's refusal of an offer, consent or prompt that the product keeps as their decision until the person changes
it, and not only until the next visit, session or release. A prompt that comes back after a durable refusal is a
repeated prompt (`HIF-BRD-059`).

### Effective severity

The *severity* a *finding* carries in a report after the default consequence severity of the rule has been set against
the function and the audience that the finding affects (`HIF-EVL-013`). It is reported apart from the confidence in
the finding (`HIF-INS-007`, `HIF-INS-015`).

### Emphasis level

A step in the visual prominence that a product gives to a role, status or element, such as high, medium and low. The
*Colour System Profile* states how many levels stand together on a screen, and each *status family* is defined across
the levels (`HIF-CLR-013`).

### Engagement record

The record made before an audit starts: the commissioning organisation and authorised contact, the purpose and the
decisions the report supports, what is included and excluded, the permitted accounts, methods and prohibited actions,
the dates and limits, confidentiality and retention, the standards and target level, the deliverables and the explicit
authority for any action that could change data or service state (`HIF-WAP-003`).

### Essential

Of information, a function, a motion, a way of presenting something or an artefact: taking it away, or presenting it
another way, would fundamentally change the information or the functionality, and it cannot be provided by other
means. This is the sense of WCAG 2.2, where the word marks an exception. The reviewer judges it on the task and the
content, and shows the alternative that fails; an item is not essential because it is hard or costly to change.

The rules use the word for these things: *essential motion* (`HIF-ACC-013`); *essential information*, which the
*Product Profile* names and which remains available in poor conditions (`HIF-ACC-081`); and the *essential artefact*
of `HIF-ACC-005`, an image of text in which the particular presentation of the text is itself the information, such as
a specimen or a scan of a historical document. A logotype is named apart from it in the same rule.

Variant: essential complexity is the complexity inherent in the task and is defined where it is used (`HIF-DFN-015`).
See also *Non-essential option*.

### Evidence class

A kind of evidence that a *check* yields, ordered by the assurance it gives: E0 (declaration, not evidence), E1 (design
review), E2 (static and automated verification), E3 (interactive expert review), E4 (evaluation with representative
users) and E5 (operational evidence). The definitions in [Evaluation and Conformance](/hif/evaluation/) §2 are normative.

### Evidence record

The record kept for a *material* decision that shows the basis of the decision: the identifier, the decision and its
owner, the dates, the applicable requirements, the people, tasks and context, the claim and the decision threshold,
the sources, the method and protocol, the sample, the measures and analysis, the result with its uncertainty, the
limitations, conflicting evidence, the decision taken, the residual risk and where the data are kept (`HIF-FEV-032`).
It keeps observations, participant statements, analyst interpretations and product decisions apart (`HIF-FEV-033`).
Compare *design hypothesis record*.

### Exception

A recorded, dated decision that a product does not satisfy a requirement, with its reason, risk, alternative, owner and
expiry. See [Evaluation and Conformance](/hif/evaluation/) §10.

### Fetcher

The part of an inspection service that retrieves a URL on request. Because it can be made to reach internal systems,
it is bound by the controls of `HIF-INS-022`. A failed fetch is not a passed audit (`HIF-INS-015`).

### Finding

A defect or observation recorded by an evaluation, with a *severity* and the consequence that justifies it.

### Fixture

A recorded input with a stated expected outcome, passed, failed, inapplicable or malformed, on which a
*machine-addressable rule* is tested (`HIF-INS-012`, `HIF-INS-024`).

### Focus

The element that receives keyboard input and is the current point of attention for *assistive technology*. The Constitution
also uses "outside the current focus" for what the person is attending to.

### Forced colours

A platform mode in which the system replaces the colours chosen by a page with a palette the person chose.

### Gamut

The range of colours a display or colour space can represent. *Gamut mapping* brings a colour outside it back inside.

### Gamut mapping

The policy by which a colour outside a target *gamut* is converted to one inside it.

### Guidance

The part of a document that explains how to apply its *rules*. It is *informative* and adds no requirement.

### Hard constraint

A condition that an option or candidate has to meet to be considered at all. A failed hard constraint rejects the
option, and a better score elsewhere does not offset it. In colour selection the hard constraints are the hard
failures of `HIF-CLR-029`, such as out-of-contract gamut, failed required contrast and missing non-colour cues. In a
design comparison they are the constraints recorded before the options are compared, which no option wins by breaking
(`HIF-DRC-016`, `HIF-DRC-017`).

### Heuristic number

A number given as a starting value and supported only as a heuristic, not by a standard requirement, empirical
evidence or a platform convention, such as a measure of 45 to 80 characters. It is not presented as a biological
constant or as a conformance threshold (`HIF-TYP-001`).

### HIF-Conformant

The second conformance level: all applicable `MUST` requirements are satisfied, exceptions to `SHOULD` requirements are
justified, automated and expert checks have passed and the *accessibility baseline* is confirmed.

### HIF-Declared

The first conformance level: a *Product Profile* is in place, a *requirements matrix* is compiled and the exceptions
are known. It marks the beginning of a process and says nothing about quality.

### HIF-Validated

The third conformance level: HIF-Conformant, with *key tasks* evaluated with *representative participants*, sufficient
evidence for *high-risk* flows and operational monitoring defined.

### High-chroma

Of a colour: its chroma is at or above the level that the product's chroma policy names as high, measured in the
colour space the *colour system* declares. HIF fixes no number; the boundary is whatever the policy states
(`HIF-COL-002`, `HIF-COL-003`).

### High-risk

Of an action, command, flow, claim, finding or change: the product's recorded risk assessment places it in the high
tier of `HIF-CTX-003` (the effect cannot be undone in full, or it commits money, affects safety or legal standing,
changes the data or access of other people, or removes a container of stored data). The assessment weighs the
probability and severity of the domain risks that the *Product Profile* lists, among them loss of data, an incorrect
target, privilege escalation, privacy, a financial or legal commitment, physical safety, publication or release,
automation and exclusion through inaccessibility. The reviewer checks the placement against the record and against the
test of *Consequential action*. The evidence held for high-risk items is not lower than for items of lower risk (`HIF-EVL-001`,
`HIF-EVL-016`).

### ICC profile

A data file that describes how a device, medium or image maps its numbers to colours, in the format of the
International Color Consortium. It is not an *Application Profile*, a *Product Profile* or a *Colour System Profile*;
see *Profile*.

### Idempotent

Of a *command*: repeating it has the same effect as doing it once.

### Important control

A control through which a *key task* is done or a *consequential action* is triggered; the *command catalogue*
identifies them (`HIF-DFN-020`).

### Informative

Text that explains and adds no requirement: guidance, explanation, examples and sources. Compare *normative*.

### Input aspects

In the contract of a *machine-addressable rule*, the aspects of the target that the rule reads, for example the HTTP
response, the document tree, the computed styles, the accessibility tree, the rendered image or the language
declaration (`HIF-INS-012`).

### Interactive readiness

The moment when a control really responds, as opposed to the moment it appears.

### Invoked design rule

A principle, law, guideline or heuristic that a design decision or a review cites as its ground, such as a law of
perception, a usability heuristic or a platform convention. Each is classified as a standard requirement, empirical
result, predictive model, explanatory theory, heuristic, convention, product policy or hypothesis (`HIF-FEV-021`).

### Key task

A task of the *task corpus* that a *primary function* of the product depends on, or that the evidence of use shows
people come to the product to do. The task corpus marks the key tasks, and the evaluator checks the marking against
the *Product Profile* (its users, goals and contexts) and the evidence of use: support data, search logs, analytics,
research. A task whose failure blocks a primary function is key whether or not it is marked. The rules say *key task*,
*primary task* and *core task* for this notion (`HIF-EVL-016`, `HIF-CIA-001`).

Variants: a critical journey is a key task followed across screens, sessions or systems from its start to its success
state; a key screen is a screen on which a key task is done or its state is shown (`HIF-ACC-032`, `HIF-ACC-049`). A
top task is a key task ranked by evidence of how many people come to do it (`HIF-CIA-003`). A frequent task is one
that evidence shows is done often, whether or not it is key (`HIF-LAY-018`).

### Layer

One level of the white-label stack, ordered from the top: HIF obligations, product and domain semantics, platform and
component contracts, *semantic tokens*, the brand-expression *adapter* and the approved brand package. A lower layer
is one that comes later in this list, and it does not override an obligation of a layer above it (`HIF-BRD-042`).

Variants: a *temporary layer* is content shown above the page. A layer of nested containers in a layout is one level
of enclosure that has its own *semantic contract* (`HIF-LAY-017`).

### Layout mode

A named arrangement of a layout with defined regions, navigation and state mapping. It is not a device name, and a
media query is not a reliable way to tell which mode applies (`HIF-RSP-001`, `HIF-RSP-002`).

### Legacy citation

The way a part was cited before its requirements had ids: the part and the number of its section, such as
`accessibility §4.2`. Section numbers stay as anchors, and the *rule register* gives each rule the legacy citation of
the section it stands in.

### Level

The strength of a *rule* (its rule level): `MUST`, `SHOULD` or `MAY`. A rule has one level, the strongest keyword of its *statement*.

### Localisation

Adapting a product to a language and region: not only the strings but also direction, formats and conventions, while
meaning, normative force and hierarchy are kept.

### Machine-addressable rule

A rule of an inspection engine written in a form a program can apply: it has a stable identifier and version,
applicability, a test procedure, expected outcomes, a default consequence severity, an evidence level, mapped HIF and
external requirements and *fixtures* (`HIF-INS-012`). It is not a HIF *rule*. A HIF rule can map to several
machine-addressable rules, or to none when no program can decide it.

### Material

Of a fact, difference, consequence, change, edit, uncertainty, choice, finding or series: it is material when removing
the difference would make a representative person, in the context of the rule that uses the word, take a different
decision or a different action. That is the test. Put the same task to *representative participants* with and without
the item; if what they decide or do does not change, the item is not material. The reviewer or evaluator that the rule
names applies the test and records the evidence for it: a task observation or a comparison with representative users
(E4), or, where no people were observed, the reasoning written down and marked as a judgement at E1 or E3. A reviewer
who cannot say which decision or action would change has not shown that the item is material.

The words "materially", "material fact", "material finding", "material consequence", "material uncertainty", "material
decision" (also "material direction" and "material choice") and "material change" all apply the same test to the
person the rule has in view: the user of the product, the reader of a visualisation, the participant, or the person
who approves a release.

Not this sense: material as stuff or content (sales material, third-party material, source material), and Material
Design, the design system of Google.

### Mental model

A person's working belief about how a thing behaves and what it will do.

### Non-essential option

A choice that the *primary function* the person came for does not depend on, such as optional tracking, marketing
messages, an extra product or data sharing beyond the function. Accepting and refusing it are compared in steps,
prominence, wording and accessibility (`HIF-TRU-002`). Compare *Essential*.

### Normative

Text that sets requirements: the *rules*, and the definitions that rules rely on, such as the *evidence classes*. Compare
*informative*.

### Object

A thing that a person recognises and acts on and that keeps its identity across its *representations*.

### Optimistic presentation

Showing an expected outcome before it is confirmed.

### Oracle

What decides whether a *check* passes or fails: a threshold, a reference result, a success criterion of another standard
or a stated expert judgement. A rule without an oracle cannot pass or fail.

### Out-of-contract

Of a colour value: outside the *delivery contract* it is delivered under, for example outside the declared gamut. It
is a hard failure of the *selection engine* (`HIF-CLR-027`, `HIF-CLR-029`).

### Panel

The group of reviewers who examine the work in a design review, each through a discipline (`HIF-DRC-004`,
`HIF-DRC-005`).

Variants: a research panel is a standing group of people recruited for studies; a panel in an interface is a region of
a screen.

### Part

One document of HIF. A part is *normative*, a method, a profile, a reference or a template; only normative, method and
profile parts define rules.

### Persistence

How long and where state is kept: for a session, on a device, in an account or shared with others.

### Primary command

A *command* that serves a *primary function*, so that the function cannot be completed without it. The *Product
Profile* lists the product's commands, and the primary commands are those among them that serve its primary functions
(`HIF-INP-002`, `HIF-IXM-001`).

### Primary function

A function without which the stated purpose of the product is not served.

### Product Profile

One product's declaration: the *Application Profile* it follows, its scope, its exceptions and its *conformance claim*.
Compare *Application Profile*, which is a class and not one product.

### Production library

The collection of *assets* from which a release is built and from which they can therefore reach users, as against
files on a disk or in a download folder. A file enters it with an asset record (`HIF-BRD-027`).

### Production pattern

A pattern that the product or its design system ships and maintains in production, as against an idea, a screenshot or
an example. A pattern is a reusable response to a recurring problem in a stated context. A production pattern is
defined by nine items: problem, context and user intent; relevant objects, commands and states; preconditions and
effects; accessibility semantics and input equivalence; content responsibilities; responsive and localisation
behaviour; failure and recovery; evidence, limitations and known misuses; and acceptance tests (`HIF-PAT-001`).

### Profile

HIF does not use "profile" alone. Each kind is named in full: *Application Profile*, *Product Profile*, *Colour System
Profile*, *Brand Profile*, *ICC profile* and *density profile*. A run profile, the set of device settings that a
*browser worker* runs a page under (`HIF-INS-009`), is named by that use. Until the part is corrected, a bare
"profile" in a rule is read as the nearest named kind in its context.

### Proportionate

Of a safeguard, evidence or effort: matched to the size of what it answers, such as a risk, a finding or a change. The
rules read it as an order. Of two actions or functions, the one in the higher tier of `HIF-CTX-003` gets prevention,
confirmation, recovery and evidence not lower than the other (`HIF-CTX-003`, `HIF-EVL-001`); the low tier has no
confirmation before the act. A safeguard that is too weak for deletion and too heavy for browsing is not proportionate. The measure is the product's own risk assessment;
the reviewer compares the safeguards with the recorded risk of each action.

### Prototype fidelity

How much of the behaviour of the final product a prototype instantiates, judged by the questions it can answer. The
table of `HIF-DPR-010` pairs each question with a minimum artefact: a narrative, storyboard or service scenario for
whether a concept is meaningful; a labelled content model or linked wireframe for the information structure; an
interactive prototype with realistic data and states for whether a task can be completed; a coded prototype in the
target accessibility stack for focus and semantics; a representative implementation and infrastructure for
performance; executable failure states and persistence behaviour for recovery. A low-fidelity artefact is one below
the minimum for the question (`HIF-EVL-008`; the table is that of `HIF-DPR-010`).

### Provenance

Where something came from: who made it, under what terms and in which version.

### Public surface

What a consumer may depend on: a major version may remove or alter it, and a minor version may only add to it. It is: rule ids and their levels, document ids and
URLs, conformance levels and the claim format, the Application Profile names, the JSON schemas and the *rule register*.

### Qualified reader

A person who has the training and experience to judge the validity of a study or an expert review of that kind and who
did not carry it out. A report is written so that such a reader can follow the method well enough to judge validity
(`HIF-DPR-026`).

### Rationale

The field of a *rule* that says why it exists.

### Reflow

Re-arranging content to fit a narrower viewport, or larger text, without losing content or function and without
two-dimensional scrolling.

### Release gate

The conditions that a release satisfies before it ships ([Evaluation and Conformance](/hif/evaluation/) §9).

### Representation

One way an *object* is shown or reached: a list row, a detail view, a tab, an export, a notification.

### Representative participants

People who stand for the intended audience of the *key tasks* being evaluated. They are drawn from the users that the
*Product Profile* names (primary, secondary, and users at increased risk of exclusion), use the devices, input
methods, *assistive technology* and languages of the *context of use*, and do the tasks in a setting like real use.
The evaluator judges this from the recruitment record: how each participant was chosen and which named user group each
stands for. A group that leaves a named user group out is representative of the others only, and the report says which
are missing. The rules also say "representative users" and "representative people" (`HIF-EVL-016`, `HIF-DFN-008`).

Variant: representative tasks, devices, content, compositions and samples are chosen to cover the supported range, its
least favourable end included, and the plan says how they were chosen; for an audit the sample is that of WCAG-EM
(`HIF-WAP-012`).

### Required pair

A foreground and a background, or two adjacent elements, in one mode and state, whose contrast has to meet a threshold
as rendered, such as body text on its surface in light mode at rest. The required pair matrix of the *Colour System
Profile* lists them for every state and not only the default (`HIF-COL-006`, `HIF-CLR-008`, `HIF-CLR-015`).

### Required region

The part of a gradient, image or video on which text or a non-text element can fall in the supported layouts. Its
least favourable region is the one where contrast is lowest, and the text is measured there (`HIF-CLR-008`).

### Required token

A *token* that the *Colour System Profile* lists as needed and that resolves, without a cycle, in every mode, platform
and gamut; its baseline sRGB value is recorded (`HIF-CLR-004`, `HIF-CLR-033`).

### Requirements matrix

The table in which each applicable requirement of the *Product Profile* is followed through the chain of `HIF-EVL-021`
(product requirement, object or component, automated check, manual scenario, research task, current evidence,
exceptions) and given its means of verification (`HIF-EVL-022`). It is compiled before a *HIF-Declared* claim
(`HIF-EVL-014`). It is the traceability matrix of [Evaluation and Conformance](/hif/evaluation/) §8. The *criteria
matrix* of the *accessibility records* is its accessibility part, with one outcome per criterion.

### Responsive regime

A range of viewport, zoom, orientation or input conditions in which the product shows one *layout mode*. An audit
takes the supported locales and the responsive regimes as dimensions of its sample (`HIF-WAP-012`). Compare *supported
mode*.

### Reusable component

A component, pattern implementation or template of a design system or code library that is built once and used in more
than one place or product. It carries its accessibility into every use (`HIF-ACC-084`).

### Review owner

In a design review, the person who defines the decision the review serves and acts on its outcome. The review owner
provides the input packet (`HIF-DRC-003`).

### Rights ledger

The ledger in which each externally sourced or commissioned name, mark, font, icon, image, illustration, audio, voice
or haptic *asset*, template, code, palette, dataset and model-generated asset is recorded with its checksum, source,
licence, owners, territory, channel and duration, rights, attribution, releases and expiry (`HIF-BRD-054`). Unknown
rights are recorded as unknown (`HIF-BRD-027`).

### Rights model

The product's account of who holds which rights over a person's data and content and what the person and the product
can do with them: access, change, sharing, export and deletion, and on what terms. It is kept beside the *persistence*
of the same data (`HIF-DPR-015`, `HIF-STA-004`).

### Rule

A requirement with an id of the form `HIF-<CAT>-<NNN>`, a *statement* and the fields Level, Rationale, Source, Check
and Example. Ids are stable and never reused.

### Rule register

The machine-readable list of every rule with its level, document, address, *check* and *legacy citation*, generated from
the rules and served as `/hif/rules.json`.

### Scope

The set of things a statement covers, named by its parts. A conformance claim and an evaluation name the surfaces,
journeys and releases they cover and the parts they leave out (`HIF-EVL-018`, `HIF-EVL-019`, `HIF-ACC-043`). An
*authority*, a persistence or a search result names the objects, people, time or place it reaches (`HIF-AUT-002`,
`HIF-STA-004`). Scope is always the scope of something, and the entry or rule says whose.

Variant: the scope of a success criterion is the content it applies to, with its exceptions (`HIF-CLR-015`).

### Selection engine

The generator or procedure that proposes and chooses candidates for a *colour system*. It applies the hard gates first
and ranks the candidates that pass (`HIF-CLR-029`).

### Semantic contract

What a component, layer or screen keeps whatever its presentation: its role and name, its states and relationships,
the commands it offers and their outcomes. It is the *semantic model* at the scale of one component (`HIF-LAY-017`).

### Semantic model

The account of what the interface contains and offers, apart from how it looks: its *objects*, their *commands* and
*states*, and the roles, names and relationships through which programs and *assistive technology* read it. The
accessibility tree is built from it, and a *theme* expresses it without changing it (`HIF-A11Y-001`, `HIF-LAY-002`,
`HIF-VIS-004`). Compare *task model*.

### Semantic token

A named design value that carries a meaning, such as a text colour for primary text, as opposed to a primitive value
such as a colour literal or a palette entry.

### Severity

The consequence of a *finding*, on the scale S0 Blocker, S1 Critical, S2 Major, S3 Moderate and S4 Minor, with
Observation for an unconfirmed defect.

### Source of truth

The single place from which a piece of *state* is read and in which it is changed. Every *representation* derives from
it.

### State

The condition of an *object* or of the interface at a moment: active, selected, focused, checked, expanded, enabled,
pending, completed, in error.

### Statement

The sentence or sentences of a *rule* that carry the requirement. The fields of the rule explain, source and verify the
statement and add no requirement.

### Status family

A group of related colour roles for one kind of status, such as danger, warning, success or information, defined
across *emphasis level*, element (foreground, background, border, icon), interaction state, colour mode and *contrast
mode* (`HIF-CLR-013`).

### Status list

The list of statuses that a capability of a product can have, such as available, prototype, demonstration, planned and
external dependency. Each visible capability carries the status it actually has (`HIF-CTX-002`).

### Supported combination

A combination of operating system and version, browser or application runtime and version, *assistive technology* and
version, input or output device, and language and relevant settings, that the *Product Profile* lists as supported.
"Works with ARIA" names a technique and not a combination (`HIF-ACC-046`).

### Supported locale

A language together with its region, direction, numbering system and conventions of date, time, currency and units,
that the *Product Profile* lists under its languages and markets as supported. See *Localisation*.

### Supported mode

A layout mode, colour or contrast mode, writing mode or input mode that the *Product Profile* lists as supported. A
layout mode is a named arrangement with defined regions, navigation and state mapping, and not a device name. A rule
that speaks of "every supported mode" is applied to each one listed (`HIF-RSP-002`, `HIF-LAY-002`, `HIF-COL-006`).

### Task corpus

The recorded set of tasks against which a product is evaluated ([Evaluation and Conformance](/hif/evaluation/) §4).

### Task model

The account of what people do with the product: their tasks, the steps and the order in which each is done, from
context through instruction and input to action and result or recovery, and the objects and commands each step uses.
It is the structure behind the *task corpus*, which records the tasks that are evaluated. An order, a grouping or a
navigation follows the task model when it follows the sequence and grouping of the tasks and not the structure of the
organisation (`HIF-LAY-002`, `HIF-CIA-003`). Compare *semantic model*.

### Temporary layer

Content shown above the page or screen that the person enters and leaves again: a modal dialog, a popover or a menu
(`HIF-PAT-024`, `HIF-PAT-025`), and other content of the same kind. A temporary layer has a trigger, a way to dismiss
it, a place where *focus* starts and a place where it returns (`HIF-NAV-004`, `HIF-NAV-005`). A modal layer also takes
control of the page behind it. Whether a layer hides its trigger or the focused item is the subject of `HIF-PAT-026`.

### Tenant

In a white-label product, one organisation, brand or distributor served from the same core product. Its identity is
applied through an approved brand package and runtime values that are checked against a schema (`HIF-BRD-042`,
`HIF-BRD-046`).

### Theme

A set of values that changes the visual expression of an interface and keeps its information, interaction, state and
accessibility semantics.

### Token

A named design value, such as a colour, size, duration or radius, that code and tools read by name and not as a
literal. The kinds, from the raw value outward: a primitive token is a scale entry such as `azure.60`; a *semantic
token* carries a meaning; a component token is the value for one part of a component and refers to semantic tokens; a
derived token is computed from another, such as an opaque equivalent of a translucent colour; a relationship token
names a relationship in a layout, such as the space between a label and its field (`HIF-LAY-026`); a *required token*
is one the *Colour System Profile* lists as needed; the canonical tokens are the released token set of one release,
versioned with the profile and the evidence (`HIF-CLR-033`). A session or access token of a login is not a design
token.

### Traceability

The ability to follow a requirement to the product requirement, the checks and the evidence that show it is met, and to
the exceptions that apply.

### Type role

A named use of text in the type system, such as heading, body, caption or label. A role is a contract, not a point
size: it includes the family, fallback, size, line height and the other fields of the role contract (`HIF-TYP-002`).
Adjacent roles are two roles that sit next to each other in a layout (`HIF-TYP-013`).

### Use error

An action or omission that leads to an outcome other than the one the person intended. HIF uses the term in place of
"user error", which puts the fault on the person.
