This is a collection of glossary terms in several WAI documents, currently:
Terms are sorted alphabetically, and known variations of the term are shown in a list below. The first column is the, the second the definition, and the third the source it came from.
Because many specs define the same terms, there are duplicates with non-identical definitions. The alphabetical sort helps to find these.
Next steps are:
This document is also available for review in a google doc.
Term | Definition | Source |
---|---|---|
AI |
Artificial Intelligence | captcha |
ASCII art |
picture created by a spatial arrangement of characters or glyphs (typically from the 95 printable characters defined by ASCII) |
wcag-2 |
Accessibility API
|
Operating systems and other platforms provide a set of interfaces that expose information about |
aria-common |
Accessibility Subtree |
An accessible object in the accessibility tree and its descendants in that tree. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via |
aria-common |
Accessibility Tree |
Tree of |
aria-common |
Accessible Description |
An accessible description provides additional information, related to an interface element, that complements the accessible name. The accessible description might or might not be visually perceivable. |
aria-common |
Accessible Name
|
The accessible name is the name of a user interface element. Each platform accessibility API provides the accessible name property. The value of the accessible name may be derived from a visible (e.g., the visible text on a button) or invisible (e.g., the text alternative that describes an icon) property of the user interface element. See related accessible description. A simple use for the accessible name property may be illustrated by an "OK" button. The text "OK" is the accessible name. When the button receives focus, assistive technologies may concatenate the platform's role description with the accessible name. For example, a screen reader may speak "push-button OK" or "OK button". The order of concatenation and specifics of the role description (e.g., "button", "push-button", "clickable button") are determined by platform |
aria-common |
Accessible Name |
The accessible name is the programmatically determined name of a user interface element that is included in the accessibility tree. The accessible name is calculated using the accessible name and description computation. For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in HTML Accessibility API Mappings 1.0, Accessible Name and Description Computation (working draft) and SVG Accessibility API Mappings, Name and Description (working draft). For more details, see examples of accessible name.
Note: As per the accessible name and description computation, each element always has an accessible name. When no accessible name is provided, the element will nonetheless be assigned an empty ( Note: As per the accessible name and description computation, accessible names are flat string trimmed of leading and trailing whitespace. Notably, it is not possible for a non-empty accessible name to be composed only of whitespace since these must be trimmed. Accessibility Support for Accessible Name
|
act-rules |
Accessible object
|
A node in the accessibility tree of a platform accessibility API
. Accessible objects expose various |
aria-common |
Activation behavior |
The action taken when an event, typically initiated by users through an input device, causes an element to fulfill a defined role. The role may be defined for that element by the host language, or by author-defined variables, or both. The role for any given element may be a generic action, or may be unique to that element. For example, the activation behavior of an HTML or SVG
|
aria-common |
Adjectival rating
|
A system to report evaluation results as a set of human-understandable adjectives which represent groupings of scores. |
wcag-3 |
Age Related Forgetfulness
|
Sometimes called "Age Appropriate Forgetfulness" or "Age Related Memory Loss". People with age related forgefulness have impaired memory issues that can be a normal part of healthy aging. They may take longer to learn new things, forget something but remember it later, or occasionally forget particular words. (This differs from dementia where forgetfulness is due to a disorder and is more pronounced.) |
content-usable |
Alternative and Augmentative Communication System
|
Sometimes called “AAC”. Any method, device, or application that can be used to help those who cannot use spoken language and need additional support by means of symbols, images, and/or text. For example, a screen with symbols that the user can select to speak the appropriate words or add them to a document. |
content-usable |
Anxiety Disorders |
People who have anxiety disorders struggle with intense and uncontrollable feelings of anxiety, fear, worry, and/or panic. This is more than just feeling worried once in a while. This may last for a long time and can interfere with daily activities, such as concentration and executive function. |
content-usable |
Appropriate field for the form control |
The field name of the form control is appropriate if it is listed in the autocomplete fields table from the HTML 5.2 specification as applying to the specified control group. https://html.spec.whatwg.org/#inappropriate-for-the-control. |
act-rules |
Assistive Technologies
|
Hardware and/or software that:
This definition may differ from that used in other documents. Examples of assistive technologies that are important in the context of this document include the following:
|
aria-common |
Attention Deficit (Hyperactivity) disorder, AD(H)D
|
Sometimes called “attention deficit disorder”, “ADD”, and “attention deficit hyperactivity disorder”, “ADHD”. Attention deficit (hyperactivity) disorder or AD(H)D involves difficulty focusing on a single task, focusing for longer periods, or being easily distracted. It is marked by an ongoing pattern of inattention and/or hyperactivity-impulsivity that interferes with functioning or development. |
content-usable |
Attribute
|
In this specification, attribute is used as it is in markup languages. Attributes are structural features added to |
aria-common |
Attribute value |
The attribute value of a content attribute set on an HTML element is the value that the attribute gets after being parsed and computed according to specifications. It may differ from the value that is actually written in the HTML code due to trimming whitespace or non-digits characters, default values, or case-insensitivity. Some notable case of attribute value, among others:
This list is not exhaustive, and only serves as an illustration for some of the most common cases. The attribute value of an IDL attribute is the value returned on getting it. Note that when an IDL attribute reflects a content attribute, they have the same attribute value. |
act-rules |
Audio output |
This test aspect includes all auditory data output from the web page into an audio channel. |
act-rules |
Autistic
|
Sometimes called “autism spectrum disorder”, “ASD”, “autism”, “asperger syndrome”, and “pervasive developmental disorder”. Autistic people have some degree of impaired social behavior, communication and language abilities. This may also impact the person’s ability to regulate behavior and attention. Individuals can have a narrow range of interests and activities and they may rely on alternative communication methods. Some individuals may also experience episodes of sensory overload. See neurodiversity for an alternative approach to autism and learning and cognitive disabilities. |
content-usable |
Automated evaluation
|
Evaluation conducted using software tools, typically evaluating code-level features and applying heuristics for other tests. Automated testing is contrasted with other types of testing that involve human judgement or experience. Semi-automated evaluation allows machines to guide humans to areas that need inspection. The emerging field of testing conducted via machine learning is not included in this definition. |
wcag-3 |
Background Colors Of Text |
The colors of all pixels, excluding the foreground colors pixels, in the bounding box around a visible character in a text node. |
act-rules |
Bayesian filter
|
Recursive probabilistic heuristic to categorize content, typically used in spam filtering. | captcha |
Block of content |
A block of content in an HTML web page is a set of nodes from that page for which all the following are true:
Assumptions for Block of content This definition assumes that the rendering order of nodes on a page does not greatly differ from the DOM tree order. Otherwise, blocks of content as defined here may be different from what is visually perceived as "content in a close relationship". |
act-rules |
Block of repeated content |
A block of content B, inside an HTML web page P, is a block of repeated content if both the following are true:
Background for Block of repeated content This definition only considers pages at "distance 1" from the current page. The instrument leading there is usually a link, sometimes a button. In addition, P' can be any page and is not restricted, for example, to pages of the same website. The blocks of repeated content are not uniquely defined. For example |
act-rules |
Blocked event |
A blocked event makes no changes to the content of the web page. |
act-rules |
Bounding Box around Text |
The smallest rectangle that encloses all the visible pixels of a character (including anti-aliased pixels), plus one pixel on every edge (top, right, bottom, left), aligned on the horizontal and vertical axis. |
act-rules |
Brain Injury |
Brain injury including, traumatic brain injury (TBI) and acquired brain injury (ABI), are caused by damage to the brain which can lead to long-term impairment of executive function, memory, learning, coordination, speech, and emotions as well as other physical and sensory impairments. Brain injury can have many different causes such as a concussion or stroke, and can happen at any stage of life. |
content-usable |
CAPTCHA
|
“Completely Automated Public Turing Test to distinguish between Computers and Humans” relying on a challenge believed to be difficult for machines to satisfy correctly but relatively easy for humans. | captcha |
CAPTCHA |
initialism for "Completely Automated Public Turing test to tell Computers and Humans Apart" CAPTCHA tests often involve asking the user to type in text that is displayed in an obscured image or audio file. A Turing test is any system of tests designed to differentiate a human from a computer. It is named after famed computer scientist Alan Turing. The term was coined by researchers at Carnegie Mellon University. |
wcag-2 |
CSS pixel
|
visual angle of about 0.0213 degrees A CSS pixel is the canonical unit of measure for all lengths and measurements in CSS. This unit is density-independent, and distinct from actual hardware pixels present in a display. User agents and operating systems should ensure that a CSS pixel is set as closely as possible to the CSS Values and Units Module Level 3 reference pixel [[!css3-values]], which takes into account the physical dimensions of the display and the assumed viewing distance (factors that cannot be determined by content authors). |
wcag-2 |
Changes in content |
A event originated change in the content of a web page occurs when, by comparing the web page before and 1 minute after the event firing, at least one of the following occurs:
Assumptions:
|
act-rules |
Class
|
A set of instance |
aria-common |
Clearly labeled location |
Secondary information and alternative controls of functionality are often not displayed together with primary information or functionality. For example, an option to change a web page to dark mode may be placed on an options page instead of being available on every page and page state of a website. Another example is a maps application, where, instead of using GPS, an option is available in a dropdown menu to set the current location of the device. Such content should be placed in a clearly labeled location. The location of a target is said to be clearly labeled when the target can be found by activating "identifiable" instruments which either lead the user to find the target, or to another page or page state from which this action can be repeated until the target is found. Whether or not the content is "clearly labeled" depends on the starting point of the search. If page A has a link which clearly "identifies" some piece of content, then the location of the content is clearly labeled. Page B, which can be in the same website, may not have such a link or may have a link with a link text that does not "identify" target content or which can be interpreted to "identify" more than one target, and so the location of the content starting from page B is not clearly labeled. For the purpose of this definition, an instrument is identifiable if any text or other content with a text alternative, allows any user to identify an element with a semantic role that inherits from A web page changes state when the document's body changes without a change in the document's URL. |
act-rules |
Clipped by Overflow |
A node with an ancestor in the flat tree with a computed
overflow of Example of clipped by overflow for Clipped by Overflow This
|
act-rules |
Cognitive and Learning Disabilities
|
May include: cognitive disabilities, learning disabilities (LD), intellectual disabilities and specific learning disability. Cognitive disabilities and learning disabilities can mean different things in different locations. Taken together they refer to:
|
content-usable |
Cognitive function test
|
New A task that requires the user to remember, manipulate, or transcribe information. Examples include, but are not limited to:
|
wcag-2 |
Conformance
|
Satisfying all the requirements of the guidelines. Conformance is an important part of following the guidelines even when not making a formal Conformance Claim. See Conformance. |
wcag-3 |
Correct autocomplete field |
Any field name listed in the autocomplete fields table from the HTML 5.2 specification: https://html.spec.whatwg.org/#autofill-field |
act-rules |
Critical error
|
An accessibility problem that will stop a user from being able to complete a process. Critical errors include:
|
wcag-3 |
DOMString |
Sequence of 16-bit unsigned integers, typically interpreted as UTF-16 code units. This corresponds to the JavaScript primitive String type. | aria-common |
Default Page Language |
The default language of a web page is the most common language of its top-level browsing context document, if it is unique. If this document has either no or several most common languages, then it has no default language. For more details, see examples of default language. |
act-rules |
Deprecate
|
To declare something outdated and in the process of being phased out, usually in favor of a specified replacement. Deprecated documents are no longer recommended for use and may cease to exist in the future. |
wcag-3 |
Deprecated
|
A deprecated |
aria-common |
Desktop focus event
|
Event from/to the host operating system via the accessibility API, notifying of a change of input focus. |
aria-common |
Disabled Element |
An element is disabled when it has been rendered inoperable in one or more of the following ways:
Assumptions for Disabled Element This definition assumes that when the |
act-rules |
Early Stage Dementia |
Common impairments of early stage dementia include memory loss, difficulty concentrating, and struggling to follow a conversation or find the right word. These may appear before a diagnosis of dementia. At this stage, these symptoms are often mild. |
content-usable |
Easy to Understand Language
|
Sometimes called: “easy reading”, “easy to read”, “plain language”, “easy to understand”. Easy to Understand Language refers to text content that is in an accessible, easy to understand, form. It is often useful for people with learning disabilities, and is easier for many other people as well. |
content-usable |
Element
|
In this specification, element is used as it is in markup languages. Elements are the structural elements in markup language that contains the data profile for |
aria-common |
Embedded Image |
An element presents an embedded image when any of the following is true:
|
act-rules |
Equivalent resource |
Non-identical resources can still be equivalent resources by equally complying to the expectation formed by the user when navigating to them, thus serving an equivalent purpose. This would usually involve that the advertised key content is the same. Web pages and documents (e.g. PDFs, office formats etc.) may be equivalent resources, even if the resources:
If all resources cover the user's expectations equally well, the resources are considered to be equivalent. Note: The user's expectations for the resource can be formed by different things, e.g. the name of the link leading to the resource, with or without the context around the link. This depends on the accessibility requirement that is tested. Note: If the same content is presented in different formats or languages, the format or language itself is often part of the purpose of the content, e.g. an article as both HTML and PDF, an image in different sizes, or an article in two different languages. If getting the same content in different formats or languages is the purpose of having separate links, the resources are not equivalent. |
act-rules |
Evaluation |
The process of examining content for conformance to these guidelines. | wcag-3 |
Event
|
A programmatic message used to communicate discrete changes in the state of an object to other objects in a computational system. User input to a web page is commonly mediated through abstract events that describe the interaction and can provide notice of changes to the state of a document object. In some programming languages, events are more commonly known as notifications. |
aria-common |
Executive Function
|
The group of cognitive processes and skills required for planning, fulfilling tasks, and goals. It includes working memory and remembering details, impulse inhibition, organizing tasks, managing time, fluid reasoning, and solving problems. |
content-usable |
Explicit Semantic Role |
The explicit semantic role of an element is determined by its role attribute (if any). The role attribute takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from WAI-ARIA Specifications. If the element has no role attribute, or if it has one with no valid role, then this element has no explicit semantic role. Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the accessibility support base line. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. Accessibility Support for Explicit Semantic Role Some browsers and assistive technologies treat the tokens of the |
act-rules |
Expose |
Translated to platform-specific |
aria-common |
Filename |
A filename is a text string that identifies an electronically stored file. In a URL it is located at the end of the path, after the last slash and before any query strings. For example the |
act-rules |
Focusable |
Elements that can become the target of keyboard input as described in the HTML specification of focusable and can be focused. |
act-rules |
Focused |
An element is focused when that element matches the
|
act-rules |
Foreground Colors Of Text |
The colors of all the pixels of a visible character in a text node that change color when the CSS Note: Anti-aliasing is a technique in which the foreground color and background color are blended to create smooth edges. |
act-rules |
Form Field Error Indicator |
Any text, or non-text content, or an element that has presentation indicating that an error was identified which appears to be related to some user input into, or the lack of user input into some element. These could be different types of errors, for example:
Note: An error indicator can be a separate element in the page, but it can also be part of a form control. For example a red outline on a form control is often used to indicate an error. Not all red outlines are indicators of an error though. This depends on the presentation of the form control in relation to other elements on the page. |
act-rules |
Functional category
|
A conceptual grouping of functional needs that represent generalized sets of user groups. |
wcag-3 |
Functional need
|
A statement that describes a specific gap in one’s ability, or a specific mismatch between ability and the designed environment or context. |
wcag-3 |
Graphical Document
|
A document containing graphic representations with user-navigable parts. Charts, maps, diagrams, blueprints, and dashboards are examples of graphical documents. A graphical document is composed using any combination of symbols, images, text, and graphic primitives (shapes such as circles, points, lines, paths, rectangles, etc). |
aria-common |
Guideline
|
High-level, plain-language content used to organize outcomes. See Guidelines in the Explainer. |
wcag-3 |
Highest Possible Contrast |
The highest value of the contrast ratios between two sets of colors. |
act-rules |
How-to
|
Provides explanatory material for each guideline that applies across technologies. This plain language resource includes information on getting started, who the guideline helps and how, as well as information for designers and developers. See How-tos in the Explainer. |
wcag-3 |
Human evaluation
|
Evaluation conducted by a human, typically to apply human judgement to tests that cannot be fully automatically evaluated. Human evaluation is contrasted with automated evaluation which is done entirely by machine, though it includes semi-automated evaluation which allows machines to guide humans to areas that need inspection. Human evaluation involves inspection of content features, by contrast with user testing which directly tests the experience of users with content. |
wcag-3 |
Implicit Semantic Role |
The implicit semantic role of an element is a pre-defined value given by the host language which depends on the element and its ancestors. Implicit roles for HTML and SVG, are documented in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft). Accessibility Support for Implicit Semantic Role
|
act-rules |
Included in the accessibility tree |
Elements included in the accessibility tree of platform specific accessibility APIs. Elements in the accessibility tree are exposed to assistive technologies, allowing users to interact with the elements in a way that meet the requirements of the individual user. The general rules for when elements are included in the accessibility tree are defined in the core accessibility API mappings. For native markup languages, such as HTML and SVG, additional rules for when elements are included in the accessibility tree can be found in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft). For more details, see [examples of included in the accessibility tree][].
Note: Users of assistive technologies might still be able to interact with elements that are not included in the accessibility tree. An example of this is a focusable element with an |
act-rules |
Informative
|
Content provided for information purposes and not required for conformance. Content required for conformance is referred to as normative. |
aria-common |
Informative
|
Content provided for information purposes and not required for conformance. Content required for conformance is referred to as |
wcag-3 |
Inheriting Semantic Role |
An element with an inheriting semantic role of X is any element with a non-abstract semantic role that inherits from X, or is the same as X.
Example: An "inheriting semantic link" is any element that either has the semantic role of
|
act-rules |
Instrument to achieve an objective |
An HTML element that when activated allows an end-user to achieve an objective. Note: Any rule that uses this definition must provide an unambiguous description of the objective the instrument is used to achieve. Background About Instrument for Instrument to achieve an objective This definition is a more restrictive version of WCAG's definition of mechanism, notably restricting it to the current document. WCAG has a note that "The mechanism needs to meet all success criteria for the conformance level claimed." This includes all the level A criteria such as Success Criterion 2.1.1 Keyboard (the mechanism must be keyboard accessible) or Success Criterion 4.1.2 Name, Role, Value (the mechanism must be exposed to assistive technologies and have an accessible name). This definition, and the rules using it, leaves these extra requirements out. This avoids reporting the same component twice for the same reason (e.g., missing an accessible name) under two different rules and Success Criteria, and helps pinpoint the error related to each Success Criterion. Instruments should nonetheless be fully accessible at the correct conformance level (depending on the rule using them). |
act-rules |
Interactive Voice Response
|
Interactive voice response (IVR) systems allow the user to interact with a computer system through the use of a telephone keypad and/or audio input. Audio input can include speech, non-speech vocalizations or audio produced by AAC or other devices. Interactive voice response systems are often used to automate tasks by phone and in call centers. IVR systems often use standards such as VoiceXML [[voicexml21]]. |
content-usable |
Just before a node |
A node N is just before a node of perceivable content P if one of the following is true:
Several nodes may be just before a given node, especially if there are several non-perceivable content nodes next to each other. |
act-rules |
Keyboard Accessible |
Accessible to the user using a keyboard or assistive technologies that mimic keyboard input, such as a sip and puff tube. References in this document relate to WCAG 2.1 Guideline 2.1: Make all functionality available from a keyboard [[WCAG21]]. |
aria-common |
Landmark
|
A type of region on a page to which the user may want quick access. Content in such a region is different from that of other regions on the page and relevant to a specific user purpose, such as navigating, searching, perusing the primary content, etc. |
aria-common |
Large Scale Text |
Text nodes with a computed font-size of:
|
act-rules |
Live Region
|
Live regions are perceivable regions of a web page that are typically updated as a result of an external event when user focus may be elsewhere. These regions are not always updated as a result of a user interaction. Examples of live regions include a chat log, stock ticker, or a sport scoring section that updates periodically to reflect game statistics. Since these asynchronous areas are expected to update outside the user's area of focus, assistive technologies such as screen readers have either been unaware of their existence or unable to process them for the user. WAI-ARIA has provided a collection of properties that allow the author to identify these live regions and process them: aria-live, aria-relevant, aria-atomic, and aria-busy. |
aria-common |
Managed State
|
Accessibility API state that is controlled by the user agent, such as focus and selection. These are contrasted with "unmanaged states" that are typically controlled by the author. Nevertheless, authors can override some managed states, such as aria-posinset and aria-setsize. Many managed states have corresponding CSS pseudo-classes, such as :focus, and pseudo-elements, such as ::selection, that are also updated by the user agent. |
aria-common |
Marked as decorative |
An element is marked as decorative if one or more of the following conditions is true:
Elements are marked as decorative as a way to convey the intention of the author that they are pure decoration. It is different from the element actually being pure decoration as authors may make mistakes. It is different from the element being effectively ignored by assistive technologies as rules such as presentational roles conflict resolution may overwrite this intention. Elements can also be ignored by assistive technologies if they are programmatically hidden. This is different from marking the element as decorative and does not convey the same intention. Notably, being programmatically hidden may change as users interact with the page (showing and hiding elements) while being marked as decorative should stay the same through all states of the page. |
act-rules |
Matching characters |
A sequence of characters is considered to match another if, after removing leading and trailing space characters and replacing remaining occurrences of one or more space characters with a single space, the two sequences of characters are equal character-by-character, ignoring any differences in letter casing. |
act-rules |
Memory Impairment |
Memory impairment refers to an inability to recognize or recall pieces of information or skills that are usually remembered. It can affect:
|
content-usable |
Mental Health
|
May include: mental heath impairments. Mental health refers to our emotional, psychological, and social well-being. A mental health impairment/condition generally has some combination of disturbed thoughts, emotions, and ability to relate to others that impairs daily functioning. Examples include depression, anxiety, and post-traumatic stress disorder. These conditions may cause temporary or long term issues with accessing information, such as difficulty focusing on information, processing information, or understanding it. |
content-usable |
Method
|
Detailed information, either technology-specific or technology-agnostic, on ways to meet the outcome as well as tests and scoring information. See Methods in the Explainer. |
wcag-3 |
Mild Cognitive Impairment (MCI)
|
Mild cognitive impairment (MCI) can involve problems with memory, language, thinking, and judgment that are greater than normal age-related challenges. It is sometimes considered the stage between the common and expected age related forgetfulness and the more serious decline of dementia, although many or most people with MCI will not develop dementia. |
content-usable |
Most Common Language of an Element |
The most common language of an element is determined by counting the number of words in the text inheriting its programmatic language from this element that are part of any of the languages in the language subtag registry. The same word can be part of multiple languages. In case of ties, the element has several most common languages. If there are no words in the text inheriting its programmatic language from the element, then it has no most common language. For more details, see examples of most common language. |
act-rules |
Namespaced Element |
An element with a specific namespaceURI value from HTML namespaces. For example an "SVG element" is any element with the "SVG namespace", which is Namespaced elements are not limited to elements described in a specification. They also include custom elements. Elements such as |
act-rules |
Nemeth Braille |
The Nemeth Braille Code for Mathematics is a braille code for encoding mathematical and scientific notation. See Nemeth Braille on Wikipedia. |
aria-common |
Neurodiversity |
Neurodiversity is a term that refers to the different ways the brain can work and interpret information. It highlights that people naturally think about things differently. Autistic people, attention deficit (hyperactivity) disorder (AD(H)D), dyslexia, and people with other diagnoses or labels may prefer the term “neurodiverse” as they are part of normal and healthy variation in the human population, bringing diverse skills and perspectives. |
content-usable |
Node |
Basic type of |
aria-common |
Non-repeated content after repeated content |
A node is non-repeated content after repeated content if all the following are true:
|
act-rules |
Non-streaming media element |
A non-streaming media element is an HTML Media Element for which the |
act-rules |
Normative |
Required for conformance. By contrast, content identified as informative or "non-normative" is not required for conformance. |
aria-common |
Normative |
Content whose instructions are required for conformance. Content identified as |
wcag-3 |
Object
|
In the context of user interfaces, an item in the perceptual user experience, represented in markup languages by one or more classes and interfaces which define the general characteristics of similar objects. An object in an accessibility API
may represent one or more DOM objects. Accessibility APIs have defined interfaces that are distinct from DOM interfaces. |
aria-common |
Object
|
An item in the perceptual user experience. Objects include user interface widgets and identifiable blocks of content. |
wcag-3 |
Ontology |
A description of the characteristics of |
aria-common |
Operable |
Usable by users in ways they can control. References in this document relate to WCAG 2.1 Principle 2: Content must be operable [[WCAG21]]. See Keyboard Accessible. |
aria-common |
Outcome
|
Result of practices that reduce or eliminate barriers that people with disabilities experience. See Outcomes. |
wcag-3 |
Outcome |
An outcome is a conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:
Note: A rule has one
Note: Implementations using the EARL10-Schema can express the outcome with the outcome property. In addition to |
act-rules |
Owned Element
|
An 'owned element' is any DOM descendant of the element, any element specified as a child via |
aria-common |
Owned by |
An element A is owned by element B if element A is a child of element B in the accessibility tree. Being a child in the accessibility tree is different from being a child in the DOM tree. Some DOM nodes have no corresponding node in the accessibility tree (for example, because they are marked with This definition is different from the definition of "owned element" in WAI-ARIA. Because browsers have different accessibility trees, which element owns which other elements can vary between browsers. Until there is a standard accessibility tree, testing with multiple accessibility trees may be necessary. |
act-rules |
Owning Element
|
An 'owning element' is any DOM ancestor of the element, or any element with an |
aria-common |
Perceivable |
Presentable to users in ways they can sense. References in this document relate to WCAG 2.1 Principle 1: Content must be perceivable [[WCAG21]]. |
aria-common |
Perceivable content |
A node is perceivable content if all the following are true:
Perceivable content corresponds to nodes that contain information and are perceived by some categories of users. Assumptions for Perceivable content This definition assumes that elements with a semantic role of |
act-rules |
Perimeter |
New continuous line forming the boundary of a shape not including shared pixels, or the minimum bounding box of a complex shape, whichever is shortest. For example, the perimeter calculation for a rectangle is 2h+2w -4, where h is the height and w is the width and the corners are not counted twice. The perimeter of a circle is 2𝜋r. |
wcag-2 |
Primary Content Element |
An implementing host language's primary content element, such as the |
aria-common |
Printable characters |
A printable character is a character that occupies a printing position on a display. These characters correspond to the following Unicode categories:
|
act-rules |
Process
|
A sequence of steps that need to be completed in order to accomplish an activity / task from end-to-end. |
wcag-3 |
Programmatic Label |
Element L is a programmatic label of target element T if either:
For more details, see examples of programmatic label. Note: a given element may have more than one programmatic label. |
act-rules |
Programmatically Determined Link Context |
The programmatically determined context of a link (or programmatically determined link context) is the set of all elements that are included in the accessibility tree, and have one or more of the following relationships to the link:
This definition is based on the WCAG definition of programmatically determined link context. This definition assumes that the HTML document with the link is a document using HTML according to the specification. |
act-rules |
Property
|
|
aria-common |
RFC 2119 |
A publication of the Internet Engineering Task Force (IETF) on Key words for use in Request for Comments (RFC) to Indicate Requirement Levels. The key words are "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" . This information is provided for explanation. UAAG 2.0 does not use these terms as defined in RFC 2119. | uaag-2 |
Relationship
|
A connection between two distinct things. Relationships may be of various types to indicate which object labels another, controls another, etc. |
aria-common |
Rendered Image Resource |
A rendered image resource in a web page is any resource with visible pixels that has been specified in the list of image sources of an embedded image. |
act-rules |
Role
|
Main indicator of type. This |
aria-common |
Root WAI-ARIA node |
The primary element containing non-metadata content. In many languages, this is the document element but in HTML, it is the |
aria-common |
Rubric
|
An approach to evaluation that defines a set of criteria for conformance and describes the result qualitatively. |
wcag-3 |
Same key events |
Two keyboard events are same key events if they have the same value for all the following attributes:
|
act-rules |
Same resource |
Two or more resources can be the same resource even though the URLs for them are different. This can be due to URL parsing, server settings, redirects and DNS aliasing. If the parsed URLs for two resources are identical, the resources are the same resource. Depending on the server, URLs can either be case-sensitive or case-insensitive, meaning that Fully parsed URLs can be different, but still lead to the same resource after making the HTTP request, due to redirects and DNS aliasing. For example, these URLs are all fully normalized: http://example.com/, http://www.example.com/, https://www.example.com/. The server can however be configured to serve the same site for http and https, and the same site for example.com and www.example.com. This is common, but not guaranteed. Some types of redirects are also caused by user agents, e.g. ensuring that http://example.com/ and http://example.com resolve to the same resource. On the other hand, identical relative URLs do not necessarily resolve to the same resource, even if they are in the same web page (HTML). This happen because external content can be included through |
act-rules |
Scale
|
An way of reporting results of evaluation using quantitative values. |
wcag-3 |
Scrollable Elements |
A scrollable element is an element with a horizontal scroll distance or a vertical scroll distance greater than 0.
note: Elements such as |
act-rules |
Semantic Role |
The semantic role of an element is determined by the first of these cases that applies:
This definition can be used in expressions such as "semantic Accessibility Support for Definition of Semantic Role for Semantic Role
|
act-rules |
Semantics
|
The meaning of something as understood by a human, defined in a way that computers can process a representation of an object, such as |
aria-common |
Semi-Automated Evaluation |
Evaluation conducted using machines to guide humans to areas that need inspection. Semi-automated evaluation involves components of automated evaluation and human evaluation. |
wcag-3 |
Set of clearly labeled instruments |
A set of clearly labeled instruments is a set of instruments, where each instrument is in the same web page as the test target or can be found in a clearly labeled location from that web page. |
act-rules |
Single page Web application
|
New Pages obtained from a single URI that provide navigation which changes the meaning of the Web page |
wcag-2 |
Standard keyboard navigation |
Standard keyboard navigation entails using one or more of the following:
Expected behavior of standard keyboard navigation keys:
|
act-rules |
State
|
A state is a dynamic |
aria-common |
Sub-document |
Any document created from a |
aria-common |
Success criterion
|
Testable statements that compose the normative aspects of WCAG 2. The closest counterpart to success criteria in WCAG 3 are outcomes. |
wcag-3 |
Target Element |
An element specified in a WAI-ARIA relation. For example, in |
aria-common |
Taxonomy |
A hierarchical definition of how the characteristics of various |
aria-common |
Technique
|
Technology-specific approach to follow a method. |
wcag-3 |
Test
|
Mechanism to evaluate implementation of a method. Tests can include true / false evaluation or various types of rating scales as appropriate for the guideline, outcome, or technology. |
wcag-3 |
Text Inheriting its Programmatic Language from an Element |
The text inheriting its programmatic language from an element E is composed of all the following texts:
An element F is an element inheriting its programmatic language from an element E if at least one of the following conditions is true (recursively):
|
act-rules |
Text alternative
|
Text that is programmatically associated with non-text content or referred to from text that is programmatically associated with non-text content. Programmatically associated text is text whose location can be programmatically determined from the non-text content. An image of a chart is described in text in the paragraph after the chart. The short text alternative for the chart indicates that a description follows. |
wcag-3 |
Text node |
Type of DOM
|
aria-common |
Tooltip attribute |
Any host language attribute that would result in a user agent generating a tooltip such as in response to a mouse hover in desktop user agents. |
aria-common |
Turing test
|
A test to determine whether responses provided by a software application are distinguishable from the responses of human individuals. | captcha |
Understandable |
Presentable to users in ways they can construct an appropriate meaning. References in this document relate to WCAG 2.1 Principle 3: Information and the operation of user interface must be understandable [[WCAG21]]. |
aria-common |
Unicode Braille Patterns
|
In Unicode, braille is represented in a block called Braille Patterns (U+2800..U+28FF). The block contains all 256 possible patterns of an 8-dot braille cell; this includes the complete 6-dot cell range which is represented by U+2800..U+283F. In all braille systems, the braille pattern dots-0 (U+2800) is used to represent a space or the lack of content; it is also called a blank Braille pattern. See Braille Patterns on Wikipedia. |
aria-common |
User Agent
|
Any software that retrieves, renders and facilitates end user interaction with Web content. This definition may differ from that used in other documents. |
aria-common |
User interaction |
A user interaction is any action that causes the user agent to fire one of the following DOM events:
This list comprises the User Interface event that are generated by the user agent as a result of user interaction. |
act-rules |
User need
|
The end goal a user has when starting a process through digital means. |
wcag-3 |
User testing |
Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant outcomes. |
wcag-3 |
VPN |
Virtual Private Network | captcha |
Valid IDREF |
A reference to a target element in the same document that has a matching ID |
aria-common |
Valid Language Tag |
A language tag is valid if its primary language subtag exists in the language subtag registry with a Type field whose field-body value is A "language tag" is here to be understood as in the first paragraph of the BCP 47 language tag syntax, i.e. a sequence of subtags separated by hyphens, where a subtag is any sequence of alphanumerical characters. Thus, this definition intentionally differs from the strict BCP 47 syntax (and ABNF grammar) as user agents and assistive technologies are more lenient in what they accept. The definition is however consistent with the behavior of the Subtags, notably the primary language subtag, are case insensitive. Hence comparison with the language subtag registry must be done in a case insensitive way. |
act-rules |
View
|
All content visually and programmatically available without a substantive change. Views vary based on the technology being tested. While these guidelines provide guidance on scoping a view, the tester will determine what constitutes a view, and describe it. Views will often vary by technology. Views typically include state permutations that are based on that view such as dialogs and alerts, but some states may deserve to be treated as separate views. |
wcag-3 |
Visible |
Content perceivable through sight. Content is considered visible if making it fully transparent would result in a difference in the pixels rendered for any part of the document that is currently within the viewport or can be brought into the viewport via scrolling. For more details, see examples of visible. |
act-rules |
Visible Text Content |
The visible text content of an element is a set of all visible text nodes that are descendants in the flat tree of this element |
act-rules |
Visual Context |
The visual context of a node is everything that is visually or logically located near it when the document containing it is rendered. Only visible information may be part of the visual context. The logical distance is the distance in the structure of the document: either the tree distance within the DOM tree, or the semantic relation. For example, headings are logically near the content that follows (until the next heading of the same or higher level) even though they might be far away visually or in the DOM tree. The visual context may include, but is not limited to, headings, text in the same sentence or paragraph. Note: As a rule of thumb, visual context should be close enough to be displayed on the device at the same time as the element it relates to. Because device sizes vary wildly and content can further be zoomed and moved around, this is however not a strong requirement. Note: Visual context that is located before (in reading order) the element it relates to is often more useful than visual context located after. Indeed, it is easier for users to use context that they have already read than context that is yet to be read. |
act-rules |
Visual Contrast |
The combination of foreground and background colors along with font weight and size that make text readable. |
wcag-3 |
Visual Reference Words |
Any word in a text node that is included in the translated version of the following lists, where the language of the translation is the programmatically determinable language of the text node. Some words can be translated in multiple ways or have plural forms. In such cases each translation or form must be included. Some words can be spelled in multiple ways (For example: sometimes the word is capitalized and sometimes it isn't). In such cases each spelling must be included. Note: This list is not exhaustive. As soon as more visual reference words are found they can be added to this list. Visual location:
Shape:
Size:
Orientation:
Color
|
act-rules |
Voice User Interfaces |
Sometimes called: Conversational interfaces. Voice user interfaces (VUIs) allow the user to interact with a computer system based on audio input and/or output. Audio input can include speech, non-speech vocalizations or audio produced by AAC or other devices. Audio-based interaction may include both input from the user, and output from the system in response to the input. Examples include: Siri, Google Assistant, and Alexa. |
content-usable |
WAI-ARIA specifications |
The WAI ARIA Specifications group both the WAI ARIA W3C Recommendation and ARIA modules, namely:
Note: depending on the type of content being evaluated, part of the specifications might be irrelevant and should be ignored. |
act-rules |
Web page
|
a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other. For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page. A Web resource including all embedded images and media. A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URI of the page as a whole. A customizable portal site, where users can choose content to display from a set of different content modules. When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move around in a store dragging products off of the shelves around you and into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside. This might be a single-page Web site or just one page within a Web site. |
wcag-2 |
Web page (HTML) |
An HTML web page is the set of all fully active documents which share the same top-level browsing context.
Note: Nesting of browsing context mostly happens with Note: Web pages as defined by WCAG are not restricted to the HTML technology but can also include, e.g., PDF or DOCX documents. Note: Although web pages as defined here are sets of documents (and do not contain other kind of nodes), one can abusively write that any node is "in a web page" if it is a shadow-including descendant of a document that is part of that web page. |
act-rules |
Whitespace |
Whitespace are characters that have the Unicode "White_Space" property in the Unicode properties list. This includes:
|
act-rules |
Widget
|
Discrete user interface |
aria-common |
abbreviation
|
shortened form of a word, phrase, or name where the abbreviation has not become part of the language This includes initialisms and acronyms where:
Some companies have adopted what used to be an initialism as their company name. In these cases, the new name of the company is the letters (for example, Ecma) and the word is no longer considered an abbreviation. |
wcag-2 |
accessibility information (WCAG) |
Information that web content must contain in order to meet a WCAG 2.0 success criterion (Level A, AA or AAA). Examples include: programmatically associated alternative content (e.g. text alternatives for images), role, and state information for widgets, relationships within complex tables). Note: For the purposes of ATAG 2.0, only programmatically determinable accessibility information qualifies. For additional examples, see Appendix A of the Implementing ATAG 2.0 document. |
atag-2 |
accessibility problems |
ATAG 2.0 recognizes two types of accessibility problems:
|
atag-2 |
accessibility supported
|
supported by users' assistive technologies as well as the accessibility features in browsers and other user agents To qualify as an accessibility-supported use of a Web content technology (or feature of a technology), both 1 and 2 must be satisfied for a Web content technology (or feature):
The Accessibility Guidelines Working Group and the W3C do not specify which or how much support by assistive technologies there must be for a particular use of a Web technology in order for it to be classified as accessibility supported. (See Level of Assistive Technology Support Needed for "Accessibility Support".) Web technologies can be used in ways that are not accessibility supported as long as they are not relied upon and the page as a whole meets the conformance requirements, including Conformance Criterion 4 and Conformance Criterion 5, are met. When a Web Technology is used in a way that is "accessibility supported," it does not imply that the entire technology or all uses of the technology are supported. Most technologies, including HTML, lack support for at least one feature or use. Pages conform to WCAG only if the uses of the technology that are accessibility supported can be relied upon to meet WCAG requirements. When citing Web content technologies that have multiple versions, the version(s) supported should be specified. One way for authors to locate uses of a technology that are accessibility supported would be to consult compilations of uses that are documented to be accessibility supported. (See Understanding Accessibility-Supported Web Technology Uses.) Authors, companies, technology vendors, or others may document accessibility-supported ways of using Web content technologies. However, all ways of using technologies in the documentation would need to meet the definition of accessibility-supported Web content technologies above. |
wcag-2 |
accessible content support features |
Any features of an authoring tool that directly support authors in increasing the accessibility of the web content being edited. These are features that must be present to meet the success criteria in Part B of ATAG 2.0. | atag-2 |
activate |
To carry out the behaviors associated with an enabled element in the rendered content or a component of the UA user interface. | uaag-2 |
alternative content |
Web content that user agents can programmatically determine is usable in place of other content that some people are not able to access. Alternative content fulfills essentially the same function or purpose as the original content. There are several general types of alternative content:
|
uaag-2 |
alternative content |
Web content that is used in place of other content that some people are not able to access. Alternative content fulfills essentially the same function or purpose as the original content. WCAG 2.0 recognizes several general types of alternative content:
|
atag-2 |
alternative for time-based media |
document including correctly sequenced text descriptions of time-based visual and auditory information and providing a means for achieving the outcomes of any time-based interaction A screenplay used to create the synchronized media content would meet this definition only if it was corrected to accurately represent the final synchronized media after editing. |
wcag-2 |
alternative text |
Text that is associated with, and provides a brief description or label of, non-text content. | captcha |
ambiguous to users in general |
the purpose cannot be determined from the link and all information of the Web page presented to the user simultaneously with the link (i.e., readers without disabilities would not know what a link would do until they activated it) The word guava in the following sentence "One of the notable exports is guava" is a link. The link could lead to a definition of guava, a chart listing the quantity of guava exported or a photograph of people harvesting guava. Until the link is activated, all readers are unsure and the person with a disability is not at any disadvantage. |
wcag-2 |
animation |
Graphical content rendered to automatically change over time, giving the user a visual perception of movement. Examples include video, animated images, scrolling text, programmatic animation (e.g. moving or replacing rendered objects). | uaag-2 |
application programming interface (API) |
A mechanism that defines how communication can take place between applications. | uaag-2 |
assistive technology
|
Hardware and / or software that acts as a stand-alone user agent, or alongside a mainstream user agent to meet the functional requirements of users with disabilities that go beyond those provided by mainstream user agents alone. | captcha |
assistive technology |
For the purpose of UAAG 2.0 conformance, assistive technology meets the following criteria:
|
uaag-2 |
assistive technology |
Software (or hardware), separate from the authoring tool, that provides functionality to meet the requirements of people with disabilities (authors and end users). Some authoring tools may also provide direct accessibility features. Examples include:
|
atag-2 |
assistive technology (as used in this document)
|
hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible). Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs. The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles. Assistive technologies that are important in the context of this document include the following:
|
wcag-2 |
audio |
the technology of sound reproduction Audio can be created synthetically (including speech synthesis), recorded from real world sounds, or both. |
wcag-2 |
audio |
The technology of sound transmission. Audio can be created synthetically (including speech synthesis), streamed from a live source (e.g. a radio broadcast), or recorded from real world sounds. There can be multiple audio tracks in a presentation. | uaag-2 |
audio |
The technology of sound reproduction. Audio can be created synthetically (including speech synthesis), recorded from real-world sounds, or both. | atag-2 |
audio description
|
narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone Audio description of video provides information about actions, characters, scene changes, on-screen text, and other visual content. In standard audio description, narration is added during existing pauses in dialogue. (See also extended audio description.) Where all of the video information is already provided in existing audio, no additional audio description is necessary. Also called "video description" and "descriptive narration." |
wcag-2 |
audio description |
A type of alternative content that takes the form of narration added to the audio to describe important visual details that cannot be understood from the main soundtrack alone. Audio description of video provides information about actions, characters, scene changes, on-screen text, and other visual content. In standard audio description, narration is added during existing pauses in dialogue.
|
uaag-2 |
audio track |
All or part of the audio portion of a presentation (e.g. each instrument can have a track, or each stereo channel can have a track). | uaag-2 |
audio-only |
a time-based presentation that contains only audio (no video and no interaction) |
wcag-2 |
author |
A person who works alone or collaboratively to create content (e.g. content author, designer, programmer, publisher, tester). | uaag-2 |
author actions preventing generation of accessible web content |
When the actions of authors prevent authoring tools from generating accessible web content (WCAG). Examples include: turning off accessible content support features, ignoring prompts for accessibility information (WCAG), providing faulty accessibility information (WCAG) at prompts, modifying the authoring tool (e.g. via scripting, macros), and installing plug-ins. | atag-2 |
author permission |
Authorization that allows modification of given web content. | atag-2 |
authoring action |
Any action that authors can take using the authoring tool user interface that results in editing web content (e.g. typing text, deleting, inserting an element, applying a template). In contrast, most authoring tool user interfaces also enable actions that do not edit content (e.g. saving, publishing, setting preferences, viewing documentation).
|
atag-2 |
authoring outcome |
The content or content modifications that result from authoring actions. Authoring outcomes are cumulative (e.g. text is entered, then styled, then made into a link, then given a title). | atag-2 |
authoring practice |
An approach that authors follow to achieve a given authoring outcome (e.g. controlling presentation with style sheets). Depending on the design of an authoring tool, authoring practices may be chosen by authors or by the authoring tool. Authoring practices may or may not be:
|
atag-2 |
authoring session |
A state of the authoring tool in which web content can be edited by an author.
|
atag-2 |
authoring tool |
Any web-based or non-web-based application(s) that can be used by authors (alone or collaboratively) to create or modify web content for use by other people (other authors or end users). Note 1: "application(s)": ATAG 2.0 may be conformed to by stand-alone applications or by collections of applications. If a conformance claim is made, then the claim must provide identifying information for each application and also for any required extensions, plug-ins, etc. Note 2: "alone or collaboratively": Multiple authors may contribute to the creation of web content and, depending on the authoring tool, each author may work with different views of the content and different author permissions. Note 3: "to create or modify web content": This clause rules out software that collects data from a person for other purposes (e.g. online grocery order form) and then creates web content from that data (e.g. a web-based warehouse order) without informing the person (however, WCAG 2.0 would still apply). This clause also rules out software used to create content exclusively in non-web content technologies. Note 4: "for use by other people": This clause rules out the many web applications that allow people to modify web content that only they themselves experience (e.g. web-based email display settings) or that only provide input to automated processes (e.g. library catalog search page). Examples of software that are generally considered authoring tools under ATAG 2.0:
|
atag-2 |
authoring tool user interface |
The display and control mechanism that authors use to operate the authoring tool software. User interfaces may be non-web-based or web-based or a combination (e.g. a non-web-based authoring tool might have web-based help pages):
|
atag-2 |
authors |
People who use authoring tools to create or modify web content. The term may cover roles such as content authors, designers, programmers, publishers, testers, etc. (see Part B Conformance Applicability Note 6: Multiple authoring roles). Some authoring tools control who may be an author by managing author permissions. | atag-2 |
available printing devices |
Printing devices that are identified as available to applications via the platform. | uaag-2 |
blinking |
switch back and forth between two visual states in a way that is meant to draw attention See also flash. It is possible for something to be large enough and blink brightly enough at the right frequency to be also classified as a flash. |
wcag-2 |
blocks of text |
more than one sentence of text |
wcag-2 |
captions |
synchronized visual and/or text alternative for both speech and non-speech audio information needed to understand the media content Captions are similar to dialogue-only subtitles except captions convey not only the content of spoken dialogue, but also equivalents for non-dialogue audio information needed to understand the program content, including sound effects, music, laughter, speaker identification and location. Closed Captions are equivalents that can be turned on and off with some players. Open Captions are any captions that cannot be turned off. For example, if the captions are visual equivalent images of text embedded in video. Captions should not obscure or obstruct relevant information in the video. In some countries, captions are called subtitles. Audio descriptions can be, but do not need to be, captioned since they are descriptions of information that is already presented visually. |
wcag-2 |
captions |
A type of alternative content that takes the form of text presented and synchronized with time-based media to provide not only the speech, but also non-speech information conveyed through sound, including meaningful sound effects and identification of speakers. In some countries, the term "subtitle" is used to refer to dialogue only and "captions" is used as the term for dialogue plus sounds and speaker identification. In other countries, "subtitle" (or its translation) is used to refer to both.
|
uaag-2 |
changes of context
|
major changes in the content of the Web page that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously Changes in context include changes of:
A change of content is not always a change of context. Changes in content, such as an expanding outline, dynamic menu, or a tab control do not necessarily change the context, unless they also change one of the above (e.g., focus). Opening a new window, moving focus to a different component, going to a new page (including anything that would look to a user as if they had moved to a new page) or significantly re-arranging the content of a page are examples of changes of context. |
wcag-2 |
checking, accessibility |
The process by which web content is evaluated for web content accessibility problems (WCAG). ATAG 2.0 recognizes three types of checking, based on increasing levels of automation of the tests:
|
atag-2 |
commands |
Actions made by users to control the user agent. These include:
|
uaag-2 |
conformance
|
satisfying all the requirements of a given standard, guideline or specification |
wcag-2 |
conforming alternate version
|
version that
In this definition, "can only be reached" means that there is some mechanism, such as a conditional redirect, that prevents a user from "reaching" (loading) the non-conforming page unless the user had just come from the conforming version. The alternate version does not need to be matched page for page with the original (e.g., the conforming alternate version may consist of multiple pages). If multiple language versions are available, then conforming alternate versions are required for each language offered. Alternate versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version would need to be fully conformant in order to meet conformance requirement 1. The conforming alternative version does not need to reside within the scope of conformance, or even on the same Web site, as long as it is as freely available as the non-conforming version. Alternate versions should not be confused with supplementary content, which support the original page and enhance comprehension. Setting user preferences within the content to produce a conforming version is an acceptable mechanism for reaching another version as long as the method used to set the preferences is accessibility supported. |
wcag-2 |
content (Web content) |
information and sensory experience to be communicated to the user by means of a user agent, including code or markup that defines the content's structure, presentation, and interactions |
wcag-2 |
content (structured) |
Web content that includes machine-readable internal structure (e.g. markup elements), as opposed to unstructured content, such as raster image formats or plain human language text. | atag-2 |
content (web content) |
Information and sensory experience to be communicated to the user by means of a user agent, including code or markup that defines the content's structure, presentation, and interactions. | uaag-2 |
content (web content) |
Information and sensory experience to be communicated to the end user by means of a user agent, including code or markup that defines the content's structure, presentation, and interactions. In ATAG 2.0, the term is primarily used to refer to the output that is produced by the authoring tool. Content produced by authoring tools may include web applications, including those that act as web-based authoring tools. Content may or may not be:
|
atag-2 |
content generation (content authoring, content editing) |
The act of specifying the actual web content that will be rendered, played or executed by the end user's
user agent. While the precise details of how content is created in any given system may vary widely, responsibility for the generation of content can be any combination of the following:
|
atag-2 |
content properties |
The individual pieces of information that make up the web content (e.g. the attributes and contents of elements, style sheet information). | atag-2 |
content rendering |
User interface functionality that authoring tools present if they render, play or execute the web content being edited. ATAG 2.0 recognizes several types of content renderings:
|
atag-2 |
content transformations |
Processes that take content in one web content technology or non-web content technology (e.g. a word processing format) as input and produce content that has been optimized, restructured or recoded:
|
atag-2 |
context-sensitive help |
help text that provides information related to the function currently being performed Clear labels can act as context-sensitive help. |
wcag-2 |
continuous authentication |
Mechanism to determine that a user is still the one previously verified without requiring interactive re-authentication. | captcha |
continuous scale |
When interacting with a time-based media presentation, a continuous scale allows user (or programmatic) action to set the active playback position to any time point on the presentation time line. The granularity of the positioning is determined by the smallest resolvable time unit in the media timebase. | uaag-2 |
contrast ratio |
(L1 + 0.05) / (L2 + 0.05), where
Contrast ratios can range from 1 to 21 (commonly written 1:1 to 21:1). Because authors do not have control over user settings as to how text is rendered (for example font smoothing or anti-aliasing), the contrast ratio for text can be evaluated with anti-aliasing turned off. For the purpose of Success Criteria 1.4.3 and 1.4.6, contrast is measured with respect to the specified background over which the text is rendered in normal usage. If no background color is specified, then white is assumed. Background color is the specified color of content over which the text is to be rendered in normal usage. It is a failure if no background color is specified when the text color is specified, because the user's default background color is unknown and cannot be evaluated for sufficient contrast. For the same reason, it is a failure if no text color is specified when a background color is specified. When there is a border around the letter, the border can add contrast and would be used in calculating the contrast between the letter and its background. A narrow border around the letter would be used as the letter. A wide border around the letter that fills in the inner details of the letters acts as a halo and would be considered background. WCAG conformance should be evaluated for color pairs specified in the content that an author would expect to appear adjacent in typical presentation. Authors need not consider unusual presentations, such as color changes made by the user agent, except where caused by authors' code. |
wcag-2 |
control settings |
Settings that relate to how authors operate the authoring tool, for example using the keyboard or mouse. | atag-2 |
correct reading sequence |
any sequence where words and paragraphs are presented in an order that does not change the meaning of the content |
wcag-2 |
default |
see properties | uaag-2 |
developer |
Any entities or individuals responsible for programming the authoring tool. This includes the programmers of any additional software components included by the Claimant in the conformance claim. In some cases, development of the authoring tool is complete before authors can use it to publish web content. However, in other cases (e.g. some web-based authoring tools), the developer may continue to modify the authoring tool even after content has been published, such that the content experienced by the end user is modified. | atag-2 |
direct accessibility features |
Features of an authoring tool that provide functionality to meet the requirements of authors with disabilities (e.g. keyboard navigation, zoom features, text-to-speech). Additional or specialized functionality may still be provided by external assistive technology. | atag-2 |
directly |
using a direct command | uaag-2 |
disabled element |
see element | uaag-2 |
display settings |
Settings that relate to how authors perceive the authoring tool. These include:
|
atag-2 |
document character set |
The internal representation of data in the source content by a user agent. | uaag-2 |
document object |
The internal representation of data in the source by a non-web based authoring tool or user agent. The document object may form part of a platform accessibility service that enables communication with assistive technologies. Web-based authoring tools are considered to make use of the document object that is maintained by the user agent. | atag-2 |
document object, Document Object Model (DOM) |
A platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The document can be further processed and the results of that processing can be incorporated back into the presented page. Overview of DOM-related materials: http://www.w3.org/DOM/#what. | uaag-2 |
documentation |
Any information that supports the use of a user agent. This information can be provided electronically or otherwise and includes help, manuals, installation instructions, tutorials, etc. Documentation can be accessed in various ways (e.g. as files included in the installation, available on the web). Note: The level of technical detail in documentation for users should match the technical level of the feature. For example, user documentation for a browser's zoom function should not refer users to the source code repository for that browser. |
uaag-2 |
documentation |
Any information that supports the use of an authoring tool. This information may be provided electronically or otherwise and includes help, manuals, installation instructions, sample work flows, tutorials, etc. | atag-2 |
down-event |
platform event that occurs when the trigger stimulus of a pointer is depressed The down-event may have different names on different platforms, such as "touchstart" or "mousedown". |
wcag-2 |
dragging movement
|
New an operation where the pointer engages with an element on the down event and the element (or a representation of its position) follows the pointer The element could be, for example, a list item, a text element, or an image. |
wcag-2 |
element |
Primarily, a syntactic construct of a document type definition (DTD) for its application. This is the sense employed by the XML 1.0 specification (
[XML]
, section 3). UAAG 2.0 also uses the term "element" more generally to refer to any discrete unit within the content (e.g. a specific image, video, sound, heading, list, or list item).
|
uaag-2 |
element |
A pair of markup tags and its content, or an "empty tag" (one that requires no closing tag or content). | atag-2 |
emergency |
a sudden, unexpected situation or occurrence that requires immediate action to preserve health, safety, or property |
wcag-2 |
enabled element |
see element | uaag-2 |
end user |
A person who interacts with web content once it has been authored. This includes people using assistive technologies. | atag-2 |
essential |
if removed, would fundamentally change the information or functionality of the content, and information and functionality cannot be achieved in another way that would conform |
wcag-2 |
events and scripting, event handler, event type |
User agents often perform a task when an event having a particular "event type" occurs, including a user interface event, a change to content, loading of content, or a request from the operating environment. Some markup languages allow authors to specify that a script, called an event handler , be executed when an event of a given type occurs. An event handler is explicitly associated with an element through scripting, markup or the DOM . | uaag-2 |
explicit user request |
An interaction by the user through the UA user interface, the focus, or the selection. User requests are made, for example, through user agent user interface controls and keyboard commands. Some examples of explicit user requests include when the user selects "New viewport," responds "yes" to a prompt in the user agent's user interface, configures the user agent to behave in a certain way, or changes the selection or focus with the keyboard or pointing device. Note: Users can make errors when interacting with the user agent. For example, a user can inadvertently respond "yes" to a prompt instead of "no." This type of error is still considered an explicit user request. | uaag-2 |
extended audio description |
audio description that is added to an audiovisual presentation by pausing the video so that there is time to add additional description This technique is only used when the sense of the video would be lost without the additional audio description and the pauses between dialogue/narration are too short. |
wcag-2 |
extended audio description |
see audio description | uaag-2 |
flash
|
a pair of opposing changes in relative luminance that can cause seizures in some people if it is large enough and in the right frequency range See general flash and red flash thresholds for information about types of flash that are not allowed. See also blinking. |
wcag-2 |
focus
|
New the point where the user’s input interacts with the web page. For example, tabbing through a page with a keyboard moves the focus. Clicking or tapping on the page would move the focus for mouse and touchscreen usage. Different inputs can be used by a user, but at any one time there would be one point of focus for the user with the last input used. |
wcag-2 |
focus cursor |
Visual indicator that highlights a user interface element to show that it has input focus (e.g. the dotted line around a button, outline around a pane, or brightened title bar on a window).
|
uaag-2 |
focus indicator |
New the pixels that are changed to visually indicate when a user interface component is in a focused state. |
wcag-2 |
focus, input focus |
The location where input will occur if a viewport is active. Examples include:
|
uaag-2 |
focusable element |
Any element capable of having input focus (e.g. a link, text box, or menu item). In order to be accessible and fully usable, every focusable element should take keyboard focus, and ideally would also take pointer focus. | uaag-2 |
functionality |
processes and outcomes achievable through user action |
wcag-2 |
general flash and red flash thresholds |
a flash or rapidly changing image sequence is below the threshold (i.e., content passes) if any of the following are true:
where:
Exception: Flashing that is a fine, balanced, pattern such as white noise or an alternating checkerboard pattern with "squares" smaller than 0.1 degree (of visual field at typical viewing distance) on a side does not violate the thresholds. For general software or Web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field for standard screen sizes and viewing distances (e.g., 15-17 inch screen at 22-26 inches). (Higher resolutions displays showing the same rendering of the content yield smaller and safer images so it is lower resolutions that are used to define the thresholds.) A transition is the change in relative luminance (or relative luminance/color for red flashing) between adjacent peaks and valleys in a plot of relative luminance (or relative luminance/color for red flashing) measurement against time. A flash consists of two opposing transitions. The current working definition in the field for "pair of opposing transitions involving a saturated red" is where, for either or both states involved in each transition, R/(R+ G + B) >= 0.8, and the change in the value of (R-G-B)x320 is > 20 (negative values of (R-G-B)x320 are set to zero) for both transitions. R, G, B values range from 0-1 as specified in “relative luminance” definition. [[HARDING-BINNIE]] Tools are available that will carry out analysis from video screen capture. However, no tool is necessary to evaluate for this condition if flashing is less than or equal to 3 flashes in any one second. Content automatically passes (see #1 and #2 above). |
wcag-2 |
globally, global configuration |
A setting is one that applies to the entire user agent or all content being rendered by it, rather than to a specific feature within the user agent or a specific document being viewed. | uaag-2 |
graphical |
Information (e.g. text, colors, graphics, images, or animations) rendered for visual consumption. | uaag-2 |
heuristic
|
Way to solve a problem with high reliability though not perfection. | captcha |
highlight, highlighted, highlighting |
Emphasis indicated through the user interface. For example, user agents highlight content that is selected, focused, or matched by a search operation. Graphical highlight mechanisms include dotted boxes, changed colors or fonts, underlining, adjacent icons, magnification, and reverse video. Synthesized speech highlight mechanisms include alterations of voice pitch and volume ( i.e. speech prosody). User interface items can also be highlighted, for example a specific set of foreground and background colors for the title bar of the active window. Content that is highlighted may or may not be a selection. | uaag-2 |
honeypot
|
A decoy service intended to elicit interaction from web robots. | captcha |
human language
|
language that is spoken, written or signed (through visual or tactile means) to communicate with humans See also sign language. |
wcag-2 |
human language |
Language that is spoken, written or signed (through visual or tactile means) to communicate with humans. | atag-2 |
idiom
|
phrase whose meaning cannot be deduced from the meaning of the individual words and the specific words cannot be changed without losing the meaning idioms cannot be translated directly, word for word, without losing their (cultural or language-dependent) meaning. In English, "spilling the beans" means "revealing a secret." However, "knocking over the beans" or "spilling the vegetables" does not mean the same thing. In Japanese, the phrase "さじを投げる" literally translates into "he throws a spoon," but it means that there is nothing he can do and finally he gives up. In Dutch, "Hij ging met de kippen op stok" literally translates into "He went to roost with the chickens," but it means that he went to bed early. |
wcag-2 |
image |
Pictorial content that is static (i.e. not moving or changing). Also see animation. | uaag-2 |
image of text
|
text that has been rendered in a non-text form (e.g., an image) in order to achieve a particular visual effect This does not include text that is part of a picture that contains significant other visual content. A person's name on a nametag in a photograph. |
wcag-2 |
informative |
for information purposes and not required for conformance Content required for conformance is referred to as "normative." |
wcag-2 |
informative |
For information purposes and not required for conformance. | atag-2 |
informative (non-normative) |
see normative | uaag-2 |
input error |
information provided by the user that is not accepted This includes:
|
wcag-2 |
jargon |
words used in a particular way by people in a particular field The word StickyKeys is jargon from the field of assistive technology/accessibility. |
wcag-2 |
keyboard |
The letter, symbol and command keys or key indicators that allow a user to control a computing device. Assistive technologies have traditionally relied on the keyboard interface as a universal, or modality independent interface. In this document references to keyboard include keyboard emulators and keyboard interfaces that make use of the keyboard's role as a modality independent interface (see Modality Independence). Keyboard emulators and interfaces can be used on devices which do not have a physical keyboard, such as mobile devices based on touchscreen input. | uaag-2 |
keyboard command (keyboard binding, keyboard shortcuts, accesskey, access key, accelerator keys, direct keyboard command) |
A key or set of keys that are tied to a particular UI control or application function, allowing the user to navigate to or activate the control or function without traversing any intervening controls (e.g. CTRL+"S" to save a document). It is sometimes useful to distinguish keyboard commands that are associated with controls that are rendered in the current context (e.g. ALT+"D" to move focus to the address bar) from those that can be able to activate program functionality that is not associated with any currently rendered controls (e.g. "F1" to open the Help system). Keyboard commands can be triggered using a physical keyboard or keyboard emulator (e.g. on-screen keyboard or speech recognition). (See Modality Independent Controls). Sequential keyboard commands require multiple keystrokes to carry out an action (e.g. a series of Tab or arrow presses followed by Enter, or a sequence like ALT-F, V to drop down a File menu and choose Print Preview). | uaag-2 |
keyboard interface |
interface used by software to obtain keystroke input A keyboard interface allows users to provide keystroke input to programs even if the native technology does not contain a keyboard. A touchscreen PDA has a keyboard interface built into its operating system as well as a connector for external keyboards. Applications on the PDA can use the interface to obtain keyboard input either from an external keyboard or from other applications that provide simulated keyboard output, such as handwriting interpreters or speech-to-text applications with "keyboard emulation" functionality. Operation of the application (or parts of the application) through a keyboard-operated mouse emulator, such as MouseKeys, does not qualify as operation through a keyboard interface because operation of the program is through its pointing device interface, not through its keyboard interface. |
wcag-2 |
keyboard interface |
Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. A keyboard interface can allow keystroke input even if particular devices do not contain a hardware keyboard (e.g. a touchscreen-controlled device can have a keyboard interface built into its operating system to support onscreen keyboards as well as external keyboards that can be connected). Note: Keyboard-operated mouse emulators, such as MouseKeys, do not qualify as operation through a keyboard interface because these emulators use pointing device interfaces, not keyboard interfaces. |
uaag-2 |
keyboard interface |
Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. A keyboard interface can allow keystroke input even if particular devices do not contain a hardware keyboard (e.g. a touchscreen-controlled device can have a keyboard interface built into its operating system to support onscreen keyboards as well as external keyboards that may be connected). Note: Keyboard-operated mouse emulators, such as MouseKeys, do not qualify as operation through a keyboard interface because these emulators use pointing device interfaces, not keyboard interfaces. |
atag-2 |
keyboard shortcut
|
alternative means of triggering an action by the pressing of one or more keys |
wcag-2 |
keyboard trap |
A user interface situation in which a keyboard interface may be used to move focus to, but not from, a user interface component or group of components. | atag-2 |
label
|
text or other component with a text alternative that is presented to a user to identify a component within Web content A label is presented to all users whereas the name may be hidden and only exposed by assistive technology. In many (but not all) cases the name and the label are the same. The term label is not limited to the label element in HTML. |
wcag-2 |
label |
Text or other component with a text alternative that is presented to users to identify a component. A label is presented to all users whereas the name may be hidden and only exposed by assistive technology. In many (but not all) cases the name and the label are the same. | atag-2 |
large scale (text)
|
with at least 18 point or 14 point bold or font size that would yield equivalent size for Chinese, Japanese and Korean (CJK) fonts Fonts with extraordinarily thin strokes or unusual features and characteristics that reduce the familiarity of their letter forms are harder to read, especially at lower contrast levels. Font size is the size when the content is delivered. It does not include resizing that may be done by a user. The actual size of the character that a user sees is dependent both on the author-defined size and the user's display or user-agent settings. For many mainstream body text fonts, 14 and 18 point is roughly equivalent to 1.2 and 1.5 em or to 120% or 150% of the default size for body text (assuming that the body font is 100%), but authors would need to check this for the particular fonts in use. When fonts are defined in relative units, the actual point size is calculated by the user agent for display. The point size should be obtained from the user agent, or calculated based on font metrics as the user agent does, when evaluating this success criterion. Users who have low vision would be responsible for choosing appropriate settings. When using text without specifying the font size, the smallest font size used on major browsers for unspecified text would be a reasonable size to assume for the font. If a level 1 heading is rendered in 14pt bold or higher on major browsers, then it would be reasonable to assume it is large text. Relative scaling can be calculated from the default sizes in a similar fashion. The 18 and 14 point sizes for roman texts are taken from the minimum size for large print (14pt) and the larger standard font size (18pt). For other fonts such as CJK languages, the "equivalent" sizes would be the minimum large print size used for those languages and the next larger standard large print size. |
wcag-2 |
legal commitments |
transactions where the person incurs a legally binding obligation or benefit A marriage license, a stock trade (financial and legal), a will, a loan, adoption, signing up for the army, a contract of any type, etc. |
wcag-2 |
link purpose
|
nature of the result obtained by activating a hyperlink |
wcag-2 |
live |
information captured from a real-world event and transmitted to the receiver with no more than a broadcast delay A broadcast delay is a short (usually automated) delay, for example used in order to give the broadcaster time to cue or censor the audio (or video) feed, but not sufficient to allow significant editing. If information is completely computer generated, it is not live. |
wcag-2 |
live |
Information captured from a real-world event that is published with no more than a broadcast delay. Note: A broadcast delay is a short (usually automated) delay, for example used in order to give the broadcaster time to queue or censor the audio (or video) feed, but not sufficient to allow significant editing. |
atag-2 |
lower secondary education level |
the two or three year period of education that begins after completion of six years of school and ends nine years after the beginning of primary education This definition is based on the International Standard Classification of Education [[UNESCO]]. |
wcag-2 |
markup language |
A system of text annotations (e.g. elements in HTML) and processing rules that may be used to specify the structure, presentation or semantics of content. Examples of markup languages include HTML and SVG.
|
atag-2 |
mechanism |
process or technique for achieving a result The mechanism may be explicitly provided in the content, or may be relied upon to be provided by either the platform or by user agents, including assistive technologies. The mechanism needs to meet all success criteria for the conformance level claimed. |
wcag-2 |
media alternative for text |
media that presents no more information than is already presented in text (directly or via text alternatives) A media alternative for text is provided for those who benefit from alternate representations of text. Media alternatives for text may be audio-only, video-only (including sign-language video), or audio-video. |
wcag-2 |
minimum bounding box |
New the smallest enclosing box within which all the points of a shape lie. Where a component consists of disconnected parts, such as a link that wraps onto multiple lines, each part is considered to have its own bounding box. |
wcag-2 |
motion animation |
addition of steps between conditions to create the illusion of movement or to give a sense of a smooth transition For example, an element which moves into place or changes size while appearing is considered to be animated. An element which appears instantly without transitioning is not using animation. Motion animation does not include changes of color, blurring, or opacity which do not change the perceived size, shape, or position of the element. |
wcag-2 |
name |
text by which software can identify a component within Web content to the user The name may be hidden and only exposed by assistive technology, whereas a label is presented to all users. In many (but not all) cases, the label and the name are the same. This is unrelated to the name attribute in HTML. |
wcag-2 |
name |
Text by which software can identify a user interface component to the author or end user. The name may be hidden and only exposed by assistive technology, whereas a label is presented to all users. In many (but not all) cases, the label and the name are the same. | atag-2 |
navigated sequentially |
navigated in the order defined for advancing focus (from one element to the next) using a keyboard interface |
wcag-2 |
non-interactive |
@@ | captcha |
non-text content |
any content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language This includes ASCII Art (which is a pattern of characters), emoticons, leetspeak (which uses character substitution), and images representing text |
wcag-2 |
non-text content |
Any content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language. This includes ASCII Art (which is a pattern of characters), emoticons, and images representing text. | atag-2 |
non-text content (non-text element, non-text equivalent) |
see text | uaag-2 |
normative |
required for conformance One may conform in a variety of well-defined ways to this document. Content identified as "informative" or "non-normative" is never required for conformance. |
wcag-2 |
normative |
Required for conformance. One may conform in a variety of well-defined ways to ATAG 2.0. Content identified as "informative" or "non-normative" is never required for conformance. | atag-2 |
normative, informative (non-normative) |
Required (or not required) for conformance. Abilities identified as "normative" are required for conformance (noting that one can conform in a variety of well-defined ways to UAAG 2.0). Abilities identified as "informative" (or, "non-normative") are never required for conformance. | uaag-2 |
notify |
To make the user aware of events or status changes. Notifications can occur within the UA user interface (e.g. a status bar) or within the content display. Notifications can be passive and not require user acknowledgment, or they can be presented in the form of a prompt requesting a user response (e.g. a confirmation dialog). | uaag-2 |
obscure |
To render a visual element in the same screen space as a second visual element in a way that prevents the second visual element from being visually perceived. Note: The use of transparent backgrounds for the overlaying visual element (e.g., video captions) is an acceptable technique for reducing obscuration, if space is available. |
uaag-2 |
on a full-screen window |
on the most common sized desktop/laptop display with the viewport maximized Since people generally keep their computers for several years, it is best not to rely on the latest desktop/laptop display resolutions but to consider the common desktop/laptop display resolutions over the course of several years when making this evaluation. |
wcag-2 |
operating environment |
The software environment that governs the user agent's operation, whether it is an operating system or a programming language environment such as Java. | uaag-2 |
operating system (OS) |
Software that supports a device's basic functions, such as scheduling tasks, executing applications, and managing hardware and peripherals. Note: Many operating systems mediate communication between executing applications and assistive technology via a platform accessibility service. |
uaag-2 |
option |
When an author is presented with choices.
|
atag-2 |
override |
When one configuration or behavior preference prevails over another. Generally, the requirements of UAAG 2.0 involve user preferences prevailing over author preferences and user agent default settings and behaviors. Preferences can be multi-valued in general (e.g. the user prefers blue over red or yellow), and include the special case of two values (e.g. turn on or off blinking text content). | uaag-2 |
page break locators
|
New programmatically determinable destination markers that are arranged in a meaningful sequence to determine the location of a page in relation to others in the set. Examples would be:
|
wcag-2 |
paused
|
stopped by user request and not resumed until requested by user |
wcag-2 |
placeholder |
Content generated by the user agent to replace author-supplied content. A placeholder can be generated as the result of a user preference (e.g. to not render images) or as repair content (e.g. when an image cannot be found). A placeholder can be any type of content, including text, images, and audio cues. A placeholder should identify the technology of the replaced object. | uaag-2 |
platform |
The software and hardware environment(s) within which the user agent operates. Platforms provide a consistent operational environment. There can be layers of software in an hardware architecture and each layer can be considered a platform. Native platforms include desktop operating system (e.g. Linux, Mac OS, Windows, etc.), mobile operating systems (e.g. Android, Blackberry, iOS, Windows Phone, etc.), and cross-OS environments (e.g. Java). Web-based platforms are other user agents. User agents can employ server-based processing, such as web content transformations, text-to-speech production, etc. Note 1: A user agent can include functionality hosted on multiple platforms (e.g. a browser running on the desktop can include server-based pre-processing and web-based documentation). Note 2: Accessibility guidelines for developers exist for many platforms. |
uaag-2 |
platform |
The software environment within which the authoring tool operates. Platforms provide a consistent operational environment on top of lower level software platforms or hardware. For web-based authoring user interfaces, the most relevant platform will be a user agent (e.g. browser). For non-web-based user interfaces, the range of platforms includes, but may not be limited to, desktop operating systems (e.g. GNOME desktop on Linux,
Mac OS, Windows), mobile operating systems (e.g. Android, BlackBerry, iOS, Windows Phone), or cross-OS environments (e.g. Java), etc. Note 1: Many platforms mediate communication between applications operating on the platform and assistive technology via a platform accessibility service. Note 2: Accessibility guidelines for developers exist for many platforms. |
atag-2 |
platform accessibility service |
A programmatic interface that is engineered to enhance communication between mainstream software applications and assistive technologies (e.g. MSAA, UI Automation, and IAccessible2 for Windows applications, AXAPI for Mac OSX applications, Gnome Accessibility Toolkit API for GNOME applications, Java Access for Java applications). On some platforms it can be conventional to enhance communication further by implementing a DOM. | uaag-2 |
platform accessibility service |
A programmatic interface that is specifically engineered to provide communication between applications and assistive technologies (e.g. MSAA, IAccessible2 and UI Automation for Windows applications, AXAPI for Mac OS X applications, GNOME Accessibility Toolkit API for GNOME applications, Java Access for Java applications). On some platforms, it may be conventional to enhance communication further by implementing a document object. | atag-2 |
plug-in |
see user agent | uaag-2 |
plug-in |
A program that runs as part of the authoring tool (e.g. a third-party checking and repair tool) and that is not part of web content being edited. Authors generally choose to include or exclude plug-ins from their authoring tool. | atag-2 |
point of regard |
The position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard can vary. For example,it can be a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport), or a point (e.g. a moment during an audio rendering or a cursor position in a graphical rendering), or a range of text (e.g. focused text), or a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport). The point of regard is almost always within the viewport, but it can exceed the spatial or temporal dimensions of the viewport (see the definition of rendered content for more information about viewport dimensions). The point of regard can also refer to a particular moment in time for content that changes over time (e.g. an audio-only presentation). User agents can determine the point of regard in a number of ways, including based on viewport position in content, keyboard focus, and selection. | uaag-2 |
pointer |
see focus cursor | uaag-2 |
pointer input
|
input device that can target a specific coordinate (or set of coordinates) on a screen, such as a mouse, pen, or touch contact See also Pointer Events pointer definition [[!pointerevents]]. |
wcag-2 |
pre-authored content |
Pieces of web content, created prior to an authoring session, that the authoring tool developer makes available to authors to use in the content being edited. Examples include clip art, sample videos, user interface widgets. Note 1: For templates, an incomplete form of pre-authored content, see Guideline B.2.4. Note 2: If the authoring tool uses pre-authored content automatically, see Guideline B.1.1.
|
atag-2 |
pre-authored content selection mechanism |
A function beyond standard file selection that allows authors to select pre-authored content to use in an authoring session (e.g. clip art gallery, widget palette). | atag-2 |
prerecorded |
information that is not live |
wcag-2 |
presentation |
rendering of the content in a form to be perceived by users |
wcag-2 |
presentation |
Rendering of the content in a form to be perceived by authors or end users. | atag-2 |
primary education level
|
six year time period that begins between the ages of five and seven, possibly without any previous education This definition is based on the International Standard Classification of Education [[UNESCO]]. |
wcag-2 |
process
|
series of user actions where each action is required in order to complete an activity Successful use of a series of Web pages on a shopping site requires users to view alternative products, prices and offers, select products, submit an order, provide shipping information and provide payment information. An account registration page requires successful completion of a Turing test before the registration form can be accessed. |
wcag-2 |
profile |
A named and persistent representation of user preferences that can be used to configure a user agent. Preferences include input configurations, style preferences, and natural language preferences. In operating environments with distinct user accounts, profiles enable users to reconfigure software quickly when they log on. Users can share their profiles with one another. Platform-independent profiles are useful for those who use the same user agent on different devices. | uaag-2 |
programmatically available |
Information that is encoded in a way that allows different software, including assistive technologies, to extract and use the information relying on published, supported mechanisms, such as, platform accessibility services, APIs, or the document object models (DOM). For web-based user interfaces, this means ensuring that the user agent can pass on the information (e.g. through the use of WAI-ARIA). Something is programmatically available if the entity presenting the information does so in a way that is explicit and unambiguous, in a way that can be understood without reverse-engineering or complex (and thus potentially fallible) heuristics, and only relying on methods that are published, and officially supported by the developers of the software being evaluated. | uaag-2 |
programmatically determined (programmatically determinable)
|
determined by software from author-supplied data provided in a way that different user agents, including assistive technologies, can extract and present this information to users in different modalities Determined in a markup language from elements and attributes that are accessed directly by commonly available assistive technology. Determined from technology-specific data structures in a non-markup language and exposed to assistive technology via an accessibility API that is supported by commonly available assistive technology. |
wcag-2 |
programmatically determined (programmatically determinable) |
Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts:
|
atag-2 |
programmatically determined link context |
additional information that can be programmatically determined from relationships with a link, combined with the link text, and presented to users in different modalities In HTML, information that is programmatically determinable from a link in English includes text that is in the same paragraph, list, or table cell as the link or in a table header cell that is associated with the table cell that contains the link. Since screen readers interpret punctuation, they can also provide the context from the current sentence, when the focus is on a link in that sentence. |
wcag-2 |
programmatically set |
set by software using methods that are supported by user agents, including assistive technologies |
wcag-2 |
prominence |
A heuristic measure of how likely authors are to notice a user interface component in a user interface that they are operating. Prominence is affected by numerous factors, including: the number of navigation steps required, the reading order position, visual properties (e.g. size, spacing, color), and even the modality of use (e.g. mouse vs. keyboard use).
|
atag-2 |
prompt |
Any user agent-initiated request for a decision or piece of information from a user. | uaag-2 |
prompt |
Any authoring tool initiated request for a decision or piece of information from authors. The term covers both requests that must be responded to immediately (e.g. modal dialog boxes) as well as less urgent requests (e.g. underlining a misspelled word). | atag-2 |
properties, values, and defaults |
A user agent renders a document by applying formatting algorithms and style information to the document's elements. Formatting depends on a number of factors, including where the document is rendered (e.g. on screen, on paper, through loudspeakers, on a braille display, on a mobile device). Style information (e.g. fonts, colors, synthesized speech prosody) can come from the elements themselves (e.g. certain font and phrase elements in HTML), from stylesheets, or from user agent settings. For the purposes of these guidelines, each formatting or style option is governed by a property and each property can take one value from a set of legal values. Generally in UAAG 2.0, the term "property" has the meaning defined in CSS 2.1 Conformance (
[CSS21]
, ). A reference to "styles" in UAAG 2.0 means a set of style-related properties.
|
uaag-2 |
public-key infrastructure |
Authentication of the entity which has encrypted content via a registered decryption key. | captcha |
publishing |
Any point at which the authors or authoring tool make web content available to end users (e.g. uploading a web page, committing a change in a wiki, live streaming). | atag-2 |
pure decoration |
serving only an aesthetic purpose, providing no information, and having no functionality Text is only purely decorative if the words can be rearranged or substituted without changing their purpose. The cover page of a dictionary has random words in very light text in the background. |
wcag-2 |
range |
More than one item within a multi-item set. Informative Note: ATAG 2.0 uses the term "range" where absolute measurements may not be practical (e.g. the set of all help documentation examples, the set of all templates). While the strict testable requirement is the definition "More than one item within a multi-item set", implementers are strongly encouraged to implement the success criteria more broadly. |
atag-2 |
real-time event
|
event that a) occurs at the same time as the viewing and b) is not completely generated by the content A Webcast of a live performance (occurs at the same time as the viewing and is not prerecorded). An on-line auction with people bidding (occurs at the same time as the viewing). Live humans interacting in a virtual world using avatars (is not completely generated by the content and occurs at the same time as the viewing). |
wcag-2 |
recognize |
Information or events that can be identified unambiguously by user agents. recognized content : Information that is encoded within content in a way that can be unambiguously recognized by user agents. Authors encode information in many ways, including in markup languages, style sheet languages, scripting languages, and protocols. When the information is encoded in a manner that allows the user agent to process it with certainty, the user agent can "recognize" the information. For instance, HTML allows authors to specify a heading with the H1 element, so a user agent that implements HTML can recognize that content as a heading. If the author creates a heading using a visual effect alone (e.g. just by increasing the font size), then the author has encoded the heading in a
manner that does not allow the user agent to recognize it as a heading. Some requirements of UAAG 2.0 depend on content roles, content relationships, timing relationships, and other information supplied by the author. These requirements only apply when the author has encoded that information in a manner that the user agent can recognize. See the section on conformance for more information about applicability. User agents will rely heavily on information that the author has encoded in a markup language or style sheet language. Behaviors, style, meaning encoded in a script, and markup in an unfamiliar XML namespace can not be recognized by the user agent as easily or at all. recognized actions : Actions or events that can be unambiguously identified by a user agent. This can include actions or events initiated by users, scripts, add-ons, or other sources. For example, if the keyboard focus is on a web page when the user presses a key, the user agent can recognize the keystroke and can act upon it. If the keyboard focus is on an embedded media player when the user presses a key, the host user agent may or may not be able to detect the keystroke, depending on the embedding architecture. Similarly, when the user activates an INPUT element with type="submit", the user agent will recognize this as a form submission action and carry out the proper interchange with the server. However, if a page includes a custom control that looks like a button labeled "Submit**" but whose actions are entirely handled by an author-provided script, the user agent would not be able to recognize the user action as equivalent to a form submission. Actions such as opening of new browser window would always be implemented by the user agent, so the action would be recognized regardless of whether it was initiated by the user clicking a button or by a script calling a browser function. |
uaag-2 |
reflowable content |
Web content that can be arbitrarily wrapped over multiple lines. The primary exceptions to reflowable content are graphics and video. | uaag-2 |
region
|
perceivable, programmatically determined section of content In HTML, any area designated with a landmark role would be a region. |
wcag-2 |
relationships |
meaningful associations between distinct pieces of content |
wcag-2 |
relationships |
Meaningful associations between distinct pieces of content. | atag-2 |
relative luminance |
the relative brightness of any point in a colorspace, normalized to 0 for darkest black and 1 for lightest white For the sRGB colorspace, the relative luminance of a color is defined as L = 0.2126 * R + 0.7152 * G + 0.0722 * B where R, G and B are defined as:
and RsRGB, GsRGB, and BsRGB are defined as:
The "^" character is the exponentiation operator. (Formula taken from [[IEC-4WD]]). Before May 2021 the value of 0.04045 in the definition was different (0.03928). It was taken from an older version of the specification and has been updated. It has no practical effect on the calculations in the context of these guidelines. Almost all systems used today to view Web content assume sRGB encoding. Unless it is known that another color space will be used to process and display the content, authors should evaluate using sRGB colorspace. If using other color spaces, see Understanding Success Criterion 1.4.3. If dithering occurs after delivery, then the source color value is used. For colors that are dithered at the source, the average values of the colors that are dithered should be used (average R, average G, and average B). Tools are available that automatically do the calculations when testing contrast and flash. A MathML version of the relative luminance definition is available. |
wcag-2 |
relative time units |
Time intervals for navigating media relative to the current point (e.g. move forward 30 seconds). When interacting with a time-based media presentation, a user can find it beneficial to move forward or backward via a time interval relative to their current position. For example, a user can find a concept unclear in a video lecture and elect to skip back 30 seconds from the current position to review what had been described. Relative time units can be preset by the user agent, configurable by the user, and/or automatically calculated based upon media duration (e.g. jump 5 seconds in a 30-second clip, or 5 minutes in a 60-minute clip). Relative time units are distinct from absolute time values such as the 2 minute mark, the half-way point, or the end. | uaag-2 |
relied upon (technologies that are) |
the content would not conform if that technology is turned off or is not supported |
wcag-2 |
rendered content |
The presentation generated by the user agent based on the author supplied code. This includes:
|
uaag-2 |
repair (accessibility) |
The process by which web content accessibility problems that have been identified within web content are resolved. ATAG 2.0 recognizes three types of repair, based on increasing levels of automation:
|
atag-2 |
repair content, repair text |
Content generated by the user agent to correct an error condition. "Repair text" refers to the text portion of repair content. Error conditions that can lead to the generation of repair content include:
|
uaag-2 |
restrictions, restricted web content authoring |
When the web content that authors can specify with an authoring tool either must include or must not include certain content (e.g. elements, attributes, widgets). Many authoring tools restrict authoring in some way, which can either benefit accessibility (e.g. if text alternatives for non-text content are required) or detract from accessibility (e.g. if attributes for defining text alternatives are not available). In contrast, authoring tools that allow unrestricted web content authoring do not require any particular content to be included or not included (e.g. many source editing-views). | atag-2 |
robot
|
Software application that performs automated tasks on web content. | captcha |
role |
text or number by which software can identify the function of a component within Web content A number that indicates whether an image functions as a hyperlink, command button, or check box. |
wcag-2 |
role |
Text or a number by which software can identify the function of a component within web content (e.g. a string that indicates whether an image functions as a hyperlink, command button, or check box). | atag-2 |
same functionality |
same result when used A submit "search" button on one Web page and a "find" button on another Web page may both have a field to enter a term and list topics in the Web site related to the term submitted. In this case, they would have the same functionality but would not be labeled consistently. |
wcag-2 |
same relative order |
same position relative to other items Items are considered to be in the same relative order even if other items are inserted or removed from the original order. For example, expanding navigation menus may insert an additional level of detail or a secondary navigation section may be inserted into the reading order. |
wcag-2 |
satisfies a success criterion
|
the success criterion does not evaluate to 'false' when applied to the page |
wcag-2 |
screen reader
|
Assistive technology that renders content as speech or Braille. | captcha |
script |
Instructions to create dynamic web content that are written in a programming (scripting) language. In guidelines referring to the written (natural) language of content, as referenced in Unicode [UNICODE] ), script can also refer to "a collection of symbols used to represent textual information in one or more writing systems". Information encoded in (programming) scripts can be difficult for a user agent to recognize. For instance, a user agent is not expected to recognize that, when executed, a script will calculate a factorial. The user agent will be able to recognize some information in a script by virtue of implementing the scripting language or a known program library (e.g. the user agent is expected to recognize when a script will open a viewport or retrieve a resource from the web). | uaag-2 |
section |
a self-contained portion of written content that deals with one or more related topics or thoughts A section may consist of one or more paragraphs and include graphics, tables, lists and sub-sections. |
wcag-2 |
selection |
A user agent mechanism for identifying a (possibly empty) range of content that will be the implicit source or target for subsequent operations. The selection can be used for a variety of purposes, including for cut-and-paste operations, to designate a specific element in a document for the purposes of a query, and as an indication of point of regard (e.g. the matched results of a search can be automatically selected). The selection should be highlighted in a distinctive manner. On the screen, the selection can be highlighted in a variety of ways, including through colors, fonts, graphics, and magnification. When rendered using synthesized speech, the selection can be highlighted through changes in pitch, speed, or prosody. | uaag-2 |
sequential keyboard access |
Using a keyboard interface to navigate the focus one-by-one through all of the items in an ordered set (e.g. menu items, form fields) until the desired item is reached and activated. This is in contrast to direct keyboard access methods such as keyboard shortcuts and the use of bypass links. | atag-2 |
set of web pages |
collection of web pages that share a common purpose and that are created by the same author, group or organization Examples include a publication which is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages. Different language versions would be considered different sets of Web pages. |
wcag-2 |
sign language |
a language using combinations of movements of the hands and arms, facial expressions, or body positions to convey meaning |
wcag-2 |
sign language interpretation |
translation of one language, generally a spoken language, into a sign language True sign languages are independent languages that are unrelated to the spoken language(s) of the same country or region. |
wcag-2 |
single pointer |
pointer input that operates with one point of contact with the screen, including single taps and clicks, double-taps and clicks, long presses, and path-based gestures |
wcag-2 |
source text |
Text that the user agent renders upon user request to view the source of specific viewport content (e.g. selected content, frame, page). | uaag-2 |
spam filter
|
Software that processes email messages to separate undesired, usually automated, messages from desired messages. | captcha |
specific sensory experience |
a sensory experience that is not purely decorative and does not primarily convey important information or perform a function Examples include a performance of a flute solo, works of visual art etc. |
wcag-2 |
spider
|
Robot that processes web content and recursively follows links to process the content at the link target. | captcha |
state
|
dynamic property expressing characteristics of a user interface component that may change in response to user action or automated processes States do not affect the nature of the component, but represent data associated with the component or user interaction possibilities. Examples include focus, hover, select, press, check, visited/unvisited, and expand/collapse. |
wcag-2 |
status message
|
change in content that is not a change of context, and that provides information to the user on the success or results of an action, on the waiting state of an application, on the progress of a process, or on the existence of errors |
wcag-2 |
structure |
wcag-2 | |
style properties |
Properties whose values determine the presentation (e.g. font, color, size, location, padding, volume, synthesized speech prosody) of content elements as they are rendered (e.g. onscreen, via loudspeaker, via braille display) by user agents. Style properties can have several origins:
|
uaag-2 |
style property
|
property whose value determines the presentation (e.g. font, color, size, location, padding, volume, synthesized speech prosody) of content elements as they are rendered (e.g. onscreen, via loudspeaker, via braille display) by user agents Style properties can have several origins:
|
wcag-2 |
style sheet |
A mechanism for communicating style property settings for web content, in which the style property settings are separable from other content resources. This separation allows author style sheets to be toggled or substituted, and user style sheets defined to apply to more than one resource. Style sheet web content technologies include Cascading Style Sheets (CSS) and Extensible Stylesheet Language (XSL).
|
uaag-2 |
supplemental content
|
additional content that illustrates or clarifies the primary content An audio version of a Web page. An illustration of a complex process. A paragraph summarizing the major outcomes and recommendations made in a research study. |
wcag-2 |
synchronize |
The act of time-coordinating two or more presentation components (e.g. a visual track with captions, several tracks in a multimedia presentation). For authors, the requirement to synchronize means to provide the data that will permit sensible time-coordinated rendering by a user agent. For example, web content developers can ensure that the segments of caption text are neither too long nor too short, and that they map to segments of the visual track that are appropriate in length. For user agent developers, the requirement to synchronize means to present the content in a sensible time-coordinated fashion under a wide range of circumstances including technology constraints (e.g. small text-only displays), user limitations (e.g. slow reading speeds, large font sizes, high need for review or repeat functions), and content that is sub-optimal in terms of accessibility. | uaag-2 |
synchronized media |
audio or video synchronized with another format for presenting information and/or with time-based interactive components, unless the media is a media alternative for text that is clearly labeled as such |
wcag-2 |
target
|
region of the display that will accept a pointer action, such as the interactive area of a user interface component If two or more touch targets are overlapping, the overlapping area should not be included in the measurement of the target size, except when the overlapping targets perform the same action or open the same page. |
wcag-2 |
target offset
|
New the distance measured from the farthest point of a target to the nearest point of the second target. Offset includes the target and spacing around the target. The target offset from A to B may be different then the offset from B to A, if the size of these targets differ. |
wcag-2 |
technology (Web content)
|
mechanism for encoding instructions to be rendered, played or executed by user agents As used in these guidelines "Web Technology" and the word "technology" (when used alone) both refer to Web Content Technologies. Web content technologies may include markup languages, data formats, or programming languages that authors may use alone or in combination to create end-user experiences that range from static Web pages to synchronized media presentations to dynamic Web applications. Some common examples of Web content technologies include HTML, CSS, SVG, PNG, PDF, Flash, and JavaScript. |
wcag-2 |
technology (web content technology) |
A mechanism for encoding instructions to be rendered, played or executed by user agents. Web content technologies can include markup languages, data formats, or programming languages that authors can use alone or in combination to create end-user experiences that range from static web pages to multimedia presentations to dynamic web applications. Some common examples of web content technologies include HTML, CSS, SVG, PNG, PDF, Flash, and JavaScript. | uaag-2 |
technology (web content) |
A mechanism for encoding instructions to be rendered, played or executed by user agents. Web content technologies may include markup languages, data formats, or programming languages that authors may use alone or in combination to create end user experiences that range from static web pages to multimedia presentations to dynamic web applications. Some common examples of web content technologies include HTML, CSS, SVG, PNG, PDF, Flash, Silverlight, Flex, and JavaScript. | atag-2 |
template |
Content patterns that are filled in by authors or the authoring tool to produce web content for end users (e.g. document templates, content management templates, presentation themes). Often templates will pre-specify at least some authoring decisions.
|
atag-2 |
template selection mechanism |
A function beyond standard file selection that allows authors to select templates to use as the basis for new content or to apply to existing content. | atag-2 |
text |
sequence of characters that can be programmatically determined, where the sequence is expressing something in human language |
wcag-2 |
text |
A sequence of characters that are programmatically available, where the sequence is expressing something in human language.
|
uaag-2 |
text alternative |
Text that is programmatically associated with non-text content or referred to from text that is programmatically associated with non-text content. Programmatically associated text is text whose location can be programmatically determined from the non-text content. An image of a chart is described in text in the paragraph after the chart. The short text alternative for the chart indicates that a description follows. Refer to Understanding Text Alternatives for more information. |
wcag-2 |
text transcript |
A type of alternative content that takes the form of text equivalents of audio information (e.g. an audio-only presentation or the audio track of a movie or other animation). A text transcript provides text for both spoken words and non-spoken sounds such as sound effects. Text transcripts make audio information accessible to people who have hearing disabilities and to people who cannot play the audio. Text transcripts are usually created by hand but can be generated on the fly (e.g. by voice-to-text converters). | uaag-2 |
time limit |
The amount of time that an authoring tool provides to authors to perform a task (e.g. read a message, select an item, save a change). Examples include: authoring session timeouts, time-based presentations (e.g. tutorial video). | atag-2 |
top-level viewport |
see viewport | uaag-2 |
tutorial |
A type of documentation that provides step-by-step instructions for performing multi-part tasks. | atag-2 |
up-event |
platform event that occurs when the trigger stimulus of a pointer is released The up-event may have different names on different platforms, such as "touchend" or "mouseup". |
wcag-2 |
used in an unusual or restricted way |
words used in such a way that requires users to know exactly which definition to apply in order to understand the content correctly The term "gig" means something different if it occurs in a discussion of music concerts than it does in article about computer hard drive space, but the appropriate definition can be determined from context. By contrast, the word "text" is used in a very specific way in WCAG 2.1, so a definition is supplied in the glossary. |
wcag-2 |
user agent |
Any software that retrieves, renders and facilitates end user interaction with web content. | captcha |
user agent
|
any software that retrieves and presents Web content for users Web browsers, media players, plug-ins, and other programs — including assistive technologies — that help in retrieving, rendering, and interacting with Web content. |
wcag-2 |
user agent |
Any software that retrieves, renders and facilitates end user interaction with web content. UAAG 2.0 identifies the following user agent architectures:
Note 2: Many web applications retrieve, render and facilitate interaction with very limited data sets (e.g. online ticket booking). In such cases, WCAG 2.0, without UAAG 2.0, can be appropriate for assessing the application's accessibility. Examples of software that are generally considered user agents under UAAG 2.0:
|
uaag-2 |
user agent |
Any software that retrieves, renders and facilitates end user interaction with web content (e.g. web browsers, browser plug-ins, media players)
|
atag-2 |
user agent add-on (add-in, extension, plug-in) |
Software installed into a user agent that adds one or more additional features that modify the behavior of the user agent. Extensions and plug-ins are types of add-ons. See embedded user agent and applicability note on Add-ons (Extensions and Plug-ins) for additional information. Two common capabilities for user agent add-ons are the ability to
|
uaag-2 |
user inactivity |
any continuous period of time where no user actions occur The method of tracking will be determined by the web site or application. |
wcag-2 |
user interface |
For the purposes of UAAG 2.0, the user interface includes both:
|
uaag-2 |
user interface component
|
a part of the content that is perceived by users as a single control for a distinct function Multiple user interface components may be implemented as a single programmatic element. "Components" here is not tied to programming techniques, but rather to what the user perceives as separate controls. User interface components include form elements and links as well as components generated by scripts. What is meant by "component" or "user interface component" here is also sometimes called "user interface element". An applet has a "control" that can be used to move through content by line or page or random access. Since each of these would need to have a name and be settable independently, they would each be a "user interface component." |
wcag-2 |
user interface component |
A part of the user interface or content display (including content renderings) that is perceived by authors as a single control for a distinct function. | atag-2 |
user interface control |
A component of the user agent user interface or the content user interface, distinguished where necessary. | uaag-2 |
user-controllable |
data that is intended to be accessed by users This does not refer to such things as Internet logs and search engine monitoring data. Name and address fields for a user's account. |
wcag-2 |
video |
the technology of moving or sequenced pictures or images Video can be made up of animated or photographic images, or both. |
wcag-2 |
video |
The technology of moving pictures or images. Video can be made up of animated or photographic images, or both. | uaag-2 |
video |
The technology of moving pictures or images. Video can be made up of animated or photographic images, or both. | atag-2 |
video-only |
a time-based presentation that contains only video (no audio and no interaction) |
wcag-2 |
view |
A user interface function that lets users interact with web content. UAAG 2.0 recognizes a variety of approaches to presenting the content in a view, including:
|
uaag-2 |
view |
A user interface function that authors use to interact with the web content being edited. ATAG 2.0 categorizes views according to whether they support editing:
|
atag-2 |
viewport |
object in which the user agent presents content The user agent presents content through one or more viewports. Viewports include windows, frames, loudspeakers, and virtual magnifying glasses. A viewport may contain another viewport (e.g., nested frames). Interface components created by the user agent such as prompts, menus, and alerts are not viewports. This definition is based on User Agent Accessibility Guidelines 1.0 Glossary [[UAAG10]]. |
wcag-2 |
viewport |
A mechanism for presenting only part of a visual or tactile view to the user via a screen or tactile display. There can be multiple viewports on to the same underlying view (e.g. when a split-screen is used to present the top and bottom of a document simultaneously) and viewports can be nested (e.g. a scrolling frame located within a larger document). When the viewport is smaller than the view it is presenting, some of the view will not be presented. Mechanisms are typically provided to move the view or the viewport such that all of the view can be brought into the viewport (e.g. scrollbars). | uaag-2 |
viewport dimensions |
The onscreen size of a viewport, or the temporal duration of a viewport displaying time-based media. When the dimensions (spatial or temporal) of rendered content exceed the dimensions of the viewport, the user agent provides mechanisms such as scroll bars and advance and rewind controls so that the user can access the rendered content "outside" the viewport (e.g. when the user can only view a portion of a large document through a small graphical viewport, or when audio content has already been played). | uaag-2 |
viewport size |
The viewport size is the width and height at which a page is rendered. The viewport size is equal to the innerWidth and innerHeight of the window of the top-level browsing context. Note: The viewport size is not to be confused with the "resolution" of the operating system. Often a browser will be a single window in the operating system, with a width and height different from the resolution of the operating system. Often browsers also include additional user interface components, such as a URL bar, tab bar, and a bookmarks bar. None of these are included in the viewport size. In full screen mode the viewport size might be the same as the resolution of the operating system. Note: The viewport size includes, if rendered, all scrollbars. |
act-rules |
visual track |
Content rendered through a graphical viewport. Visual objects include graphics, text, and visual portions of movies and other animations. A visual track is a visual object that is intended as a whole or partial presentation. A visual track does not necessarily correspond to a single physical object or software object. | uaag-2 |
visual-only |
Content consisting exclusively of one or more visual tracks presented concurrently or in series (e.g. a silent movie is an example of a visual-only presentation). | uaag-2 |
visually customized |
the font, size, color, and background can be set |
wcag-2 |
voice browser |
A device (hardware and software) that interprets voice markup languages to generate voice output, interpret voice input, and possibly accept and produce other modalities of input and output. Definition from "Introduction and Overview of W3C Speech Interface Framework" [VOICEBROWSER] . | uaag-2 |
web resource |
Anything that can be identified by a Uniform Resource Identifier (URI). | uaag-2 |
workflow |
A customary sequence of steps or tasks that authors follow to produce a content deliverable. If an authoring tool is composed of a collection of applications (e.g. markup editor, image editor, and validation tool), then its workflows may include use of one or more of the applications. | atag-2 |