- output modalities
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This document does not include requirements for braille rendering. Some requirements are specific to graphical rendering and others specific to audio output or synthesized speech output. Speech rendering requirements are made by checkpoint 4.9 to checkpoint 4.13. Many of the requirements of this document are generic enough to apply to a variety of output modalities, including braille. User agents conform to this document by supporting some combination of graphical and audio/speech rendering output; see the section on Content type labels for more information.
- override
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, the term "override" means that one configuration or behavior preference prevails over another. Generally, the requirements of this document involve user preferences prevailing over author preferences and user agent default settings and behaviors. Preferences may 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).
- placeholder
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
A placeholder is content generated by the user agent to replace author-supplied content. A placeholder may 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). Placeholders can be any type of content, including text, images, and audio cues.
- plug-in
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
A plug-in is a program that runs as part of the user agent and that is not part of content. Users generally choose to include or exclude plug-ins from their user agent.
- point of regard
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
The point of regard is a position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard may vary. For example, it may be 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 may 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 may also refer to a particular moment in time for content that changes over time (e.g., an audio-only presentation). User agents may determine the point of regard in a number of ways, including based on viewport position in content, content focus, and selection. The stability of the point of regard is addressed by guideline 5 and checkpoint 9.4.
- pointer
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This input modality label refers to all of the generic input device requirements of this document as well as those specific to the keyboard, except for the requirements of checkpoint 11.4. This label is an indication that these requirements have been satisfied for the pointing device.
- priority 1 (P1)
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
If the user agent does not satisfy this checkpoint, one or more groups of users with disabilities will find it impossible to access the Web. Satisfying this checkpoint is a basic requirement for enabling some people to access the Web.
- priority 2 (P2)
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
If the user agent does not satisfy this checkpoint, one or more groups of users with disabilities will find it difficult to access the Web. Satisfying this checkpoint will remove significant barriers to Web access for some people.
- priority 3 (P3)
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
If the user agent satisfies this checkpoint, one or more groups of users with disabilities will find it easier to access the Web.
- profile
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
A profile is a named and persistent representation of user preferences that may 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 may share their profiles with one another. Platform-independent profiles are useful for those who use the same user agent on different platforms.
- prompt
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, "to prompt" means to require input from the user. The user agent should allow users to configure how they wish to be prompted. For instance, for a user agent functionality X, configurations might include: "always prompt me before doing X," "never prompt me before doing X," "never do X but tell me when you could have," and "never do X and never tell me that you could have."
- properties, values, and defaults
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
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: on screen, on paper, through loudspeakers, on a braille display, or on a mobile device. Style information (e.g., fonts, colors, and synthesized speech prosody) may come from the elements themselves (e.g., certain font and phrase elements in HTML), from style sheets, or from user agent settings. For the purposes of these guidelines, each formatting or style option is governed by a property and each property may take one value from a set of legal values. Generally in this document, the term "property" has the meaning defined in CSS 2 ([CSS2], section 3). A reference to "styles" in this document means a set of style-related properties. The value given to a property by a user agent at installation is called the property's default value.
- recognize
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
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 this document 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.In practice, user agents will rely heavily on information that the author has encoded in a markup language or style sheet language. On the other hand, behaviors, style, meaning encoded in a script, and markup in an unfamiliar XML namespace may not be recognized by the user agent as easily or at all. The Techniques document [UAAG10-TECHS] lists some markup known to affect accessibility that user agents can recognize.
- rendered content, rendered text
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
Rendered content is the part of content that the user agent makes available to the user's senses of sight and hearing (and only those senses for the purposes of this document). Any content that causes an effect that may be perceived through these senses constitutes rendered content. This includes text characters, images, style sheets, scripts, and anything else in content that, once processed, may be perceived through sight and hearing.The term "rendered text" refers to text content that is rendered in a way that communicates information about the characters themselves, whether visually or as synthesized speech.In the context of this document, invisible content is content that is not rendered but that may influence the graphical rendering (e.g., layout) of other content. Similarly, silent content is content that is not rendered but that may influence the audio rendering of other content. Neither invisible nor silent content is considered rendered content.
- repair content, repair text
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, the term "repair content" refers to content generated by the user agent in order to correct an error condition. "Repair text" refers to the text portion of repair content. Some error conditions that may lead to the generation of repair content include: Erroneous or incomplete content (e.g., ill-formed markup, invalid markup, or missing conditional content that is required by format specification);Missing resources for handling or rendering content (e.g., the user agent lacks a font family to display some characters, or the user agent does not implement a particular scripting language).This document does not require user agents to include repair content in the document object. Repair content inserted in the document object should conform to the Web Content Accessibility Guidelines 1.0 [WCAG10]. For more information about repair techniques for Web content and software, refer to "Techniques for Authoring Tool Accessibility Guidelines 1.0" [ATAG10-TECHS].
- script
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, the term "script" almost always refers to a scripting (programming) language used to create dynamic Web content. However, in checkpoints referring to the written (natural) language of content, the term "script" is used as in Unicode [UNICODE] to mean "A collection of symbols used to represent textual information in one or more writing systems."Information encoded in (programming) scripts may 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).
- selection, current selection
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, the term "selection" refers to a user agent mechanism for identifying a (possibly empty) range of content. Generally, user agents limit the type of content that may be selected to text content (e.g., one or more fragments of text). In some user agents, the value of the selection is constrained by the structure of the document tree. On the screen, the selection may be highlighted in a variety of ways, including through colors, fonts, graphics, and magnification. The selection may also be highlighted when rendered as synthesized speech, for example through changes in speech prosody. The dimensions of the rendered selection may exceed those of the viewport.The selection may 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.The selection has state, i.e., it may be "set," programmatically or through the user interface.In this document, each viewport is expected to have at most one selection. When several viewports coexist, at most one viewport's selection responds to input events; this is called the current selection.See the section on the Selection label for information about implementing a selection and conformance.Note: Some user agents may also implement a selection for designating a range of information in the user agent user interface. The current document only includes requirements for a content selection mechanism.
- serial access, sequential navigation
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
In this document, the expression "serial access" refers to one-dimensional access to rendered content. Some examples of serial access include listening to an audio stream or watching a video (both of which involve one temporal dimension), or reading a series of lines of braille one line at a time (one spatial dimension). Many users with blindness have serial access to content rendered as audio, synthesized speech, or lines of braille. The expression "sequential navigation" refers to navigation through an ordered set of items (e.g., the enabled elements in a document, a sequence of lines or pages, or a sequence of menu options). Sequential navigation implies that the user cannot skip directly from one member of the set to another, in contrast to direct or structured navigation (see guideline 9 for information about these types of navigation). Users with blindness or some users with a physical disability may navigate content sequentially (e.g., by navigating through links, one by one, in a graphical viewport with or without the aid of an assistive technology). Sequential navigation is important to users who cannot scan rendered content visually for context and also benefits users unfamiliar with content. The increments of sequential navigation may be determined by a number of factors, including element type (e.g., links only), content structure (e.g., navigation from heading to heading), and the current navigation context (e.g., having navigated to a table, allow navigation among the table cells).Users with serial access to content or who navigate sequentially may require more time to access content than users who use direct or structured navigation.
- size and color of non-text content
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This document includes some checkpoints to ensure that the user is able to control the size and color of visually rendered text content (checkpoints 4.1 and 4.3). This document does not in general address control of the size and color of visually rendered non-text content (e.g., images).Note: A user agent may implement resizing functionalities as part of conformance to other specifications (e.g., Scalable Vector Graphics [SVG]).
- speech
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17)
This content type label refers to all of the requirements related to synthesized speech for the following checkpoints: 4.9, 4.10, 4.11, 4.12, and 4.13. When this label is part of a conformance profile, the user agent must support synthesized speech.