- equivalent
-
From Web Content
Accessibility Guidelines 1.0 (1999-05-05)
| Glossary for
this source
Content is "equivalent" to other content
when both fulfill essentially the same function or purpose upon
presentation to the user. In the context of this document, the
equivalent must fulfill essentially the same function for the
person with a disability (at least insofar as is feasible, given
the nature of the disability and the state of technology), as the
primary content does for the person without any disability. For
example, the text "The Full Moon" might convey the same information
as an image of a full moon when presented to users. Note that
equivalent information focuses on fulfilling the same function. If
the image is part of a link and understanding the image is crucial
to guessing the link target, an equivalent must also give users an
idea of the link target. Providing equivalent information for
inaccessible content is one of the primary ways authors can make
their documents accessible to people with disabilities.As part of
fulfilling the same function of content an equivalent may involve a
description of that content (i.e., what the content looks like or
sounds like). For example, in order for users to understand the
information conveyed by a complex chart, authors should describe
the visual information in the chart.Since text content can be
presented to the user as synthesized speech, braille, and
visually-displayed text, these guidelines require text equivalents
for graphic and audio information. Text equivalents must be written
so that they convey all essential content. Non-text equivalents
(e.g., an auditory description of a visual presentation, a video of
a person telling a story using sign language as an equivalent for a
written story, etc.) also improve accessibility for people who
cannot access visual information or written text, including many
individuals with blindness, cognitive disabilities, learning
disabilities, and deafness.Equivalent information may be provided
in a number of ways, including through attributes (e.g., a text
value for the "alt" attribute in HTML and SMIL), as part of element
content (e.g., the OBJECT in HTML), as part of the document's
prose, or via a linked document (e.g., designated by the "longdesc"
attribute in HTML or a description link). Depending on the
complexity of the equivalent, it may be necessary to combine
techniques (e.g., use "alt" for an abbreviated equivalent, useful
to familiar readers, in addition to "longdesc" for a link to more
complete information, useful to first-time readers). The details of
how and when to provide equivalent information are part of the
Techniques Document ([TECHNIQUES]).A text transcript is a text
equivalent of audio information that includes spoken words and
non-spoken sounds such as sound effects. A caption is a text
transcript for the audio track of a video presentation that is
synchronized with the video and audio tracks. Captions are
generally rendered visually by being superimposed over the video,
which benefits people who are deaf and hard-of-hearing, and anyone
who cannot hear the audio (e.g., when in a crowded room). A
collated text transcript combines (collates) captions with text
descriptions of video information (descriptions of the actions,
body language, graphics, and scene changes of the video track).
These text equivalents make presentations accessible to people who
are deaf-blind and to people who cannot play movies, animations,
etc. It also makes the information available to search engines.One
example of a non-text equivalent is an auditory description of the
key visual elements of a presentation. The description is either a
prerecorded human voice or a synthesized voice (recorded or
generated on the fly). The auditory description is synchronized
with the audio track of the presentation, usually during natural
pauses in the audio track. Auditory descriptions include
information about actions, body language, graphics, and scene
changes.
-
equivalent (for content)
-
From User Agent
Accessibility Guidelines 1.0 (2002-12-17) |
Glossary for this
source
The term "equivalent" is used in this
document as it is used in the Web Content Accessibility Guidelines
1.0 [WCAG10]: Content is "equivalent" to other content when both
fulfill essentially the same function or purpose upon presentation
to the user. In the context of this document, the equivalent must
fulfill essentially the same function for the person with a
disability (at least insofar as is feasible, given the nature of
the disability and the state of technology), as the primary content
does for the person without any disability.Equivalents include text
equivalents (e.g., text equivalents for images, text transcripts
for audio tracks, or collated text transcripts for a movie) and
non-text equivalents (e.g., a prerecorded audio description of a
visual track of a movie, or a sign language video rendition of a
written text).Each markup language defines its own mechanisms for
specifying conditional content, and these mechanisms may be used by
authors to provide text equivalents. For instance, in HTML 4
[HTML4] or SMIL 1.0 [SMIL], authors may use the alt attribute to
specify a text equivalent for some elements. In HTML 4, authors may
provide equivalents and other conditional content in attribute
values (e.g., the summary attribute for the TABLE element), in
element content (e.g., OBJECT for external content it specifies,
NOFRAMES for frame equivalents, and NOSCRIPT for script
equivalents), and in prose. Please consult the Web Content
Accessibility Guidelines 1.0 [WCAG10] and its associated Techniques
document [WCAG10-TECHS] for more information about
equivalents.
- error
-
From Extensible Markup Language
(XML) 1.1 (2004-02-04) |
Glossary for this
source
A violation of the rules of this
specification; results are undefined. Unless otherwise specified,
failure to observe a prescription of this specification indicated
by one of the keywords MUST, REQUIRED, MUST NOT, SHALL and SHALL
NOT is an error. Conforming software MAY detect and report an error
and MAY recover from it.
- error
-
From XML Schema Part 2:
Datatypes (2001-05-02)
| Glossary
for this source
A violation of the rules of this
specification; results are undefined. Conforming software detect
and report an error and recover from it.
- error
-
From XPointer Framework (2003-03-25)
| Glossary
for this source
A violation of the syntactic rules of this
specification, or the failure of a pointer to identify
subresources.
- error
-
From Extensible Markup
Language (XML) 1.0 (2000-10-06) |
Glossary for this
source
A violation of the rules of this
specification; results are undefined. Conforming software may
detect and report an error and may recover from it.
- error
correction
-
From Architecture
of the World Wide Web, Volume One (2004-12-15) |
Glossary for this
source
An agent repairs an
error so that within the system, it is as though the error never
occurred.
- error
recovery
-
From Architecture
of the World Wide Web, Volume One (2004-12-15) |
Glossary for this
source
An agent invokes
exceptional behavior because it does not correct the
error.
- error
values
-
From XQuery 1.0: An XML Query
Language (2007-01-23) |
Glossary for this
source
In addition to its identifying QName, a
dynamic error may also carry a descriptive string and one or more
additional values called error values.
- error
values
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
In addition to its identifying QName, a
dynamic error may also carry a descriptive string and one or more
additional values called error values.
- escape
-
From Extensible Markup Language
(XML) 1.1 (2004-02-04) |
Glossary for this
source
Entity and character references MAY both be
used to escape the left angle bracket, ampersand, and other
delimiters. A set of general entities (amp, lt, gt, apos, quot) is
specified for this purpose. Numeric character references MAY also
be used; they are expanded immediately when recognized and MUST be
treated as character data, so the numeric character references <
and &MAY be used to escape < and & when they occur in
character data.
- escape
-
From Extensible Markup
Language (XML) 1.0 (2000-10-06) |
Glossary for this
source
Entity and character references can both be
used to escape the left angle bracket, ampersand, and other
delimiters. A set of general entities (amp, lt, gt, apos, quot) is
specified for this purpose. Numeric character references may also
be used; they are expanded immediately when recognized and must be
treated as character data, so the numeric character references <
and & may be used to escape < and & when they occur in
character data.
- event
-
From Voice
Extensible Markup Language (VoiceXML) Version 2.0 (2004-03-16)
| Glossary for
this source
A notification "thrown" by the
implementation platform , VoiceXML interpreter
context , VoiceXML interpreter , or VoiceXML code.
Events include exceptional conditions (semantic errors), normal
errors (user did not say something recognizable), normal events
(user wants to exit), and user defined events.
-
events and scripting, event handler, eventhandler,
-
From User Agent
Accessibility Guidelines 1.0 (2002-12-17) |
Glossary for this
source
User agents often perform a task when an
event having a particular "event type" occurs, including user
interface events, changes to content, loading of content, and
requests 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 when the event handler is
associated with that element through markup or the DOM. The term
"event bubbling" describes a programming style where a single event
handler dispatches events to more than one element. In this case,
the event handlers are not explicitly associated with the elements
receiving the events (except for the single element that dispatches
the events). Note: The combination of HTML, style sheets, the
Document Object Model (DOM), and scripting is commonly referred to
as "Dynamic HTML" or DHTML. However, as there is no W3C
specification that formally defines DHTML, this document only
refers to event handlers and scripts.
- executable
content
-
From Voice
Extensible Markup Language (VoiceXML) Version 2.0 (2004-03-16)
| Glossary for
this source
Procedural logic that occurs in
<block>, <filled>, and event handlers .
- expanded
name
-
From Namespaces in XML 1.1 (2004-02-04)
| Glossary
for this source
An expanded name is a pair consisting of a
namespace name and a local name.
- expanded
qName
-
From XQuery 1.0: An XML Query
Language (2007-01-23) |
Glossary for this
source
An expanded QName consists of an optional
namespace URI and a local name. An expanded QName also retains its
original namespace prefix (if any), to facilitate casting the
expanded QName into a string.
- expanded
qName
-
From XML Path Language (XPath)
2.0 (2007-01-23) |
Glossary for this
source
An expanded QName consists of an optional
namespace URI and a local name. An expanded QName also retains its
original namespace prefix (if any), to facilitate casting the
expanded QName into a string.
- expanded-name
-
From XML Path Language (XPath) (1999-11-16) |
Glossary for this
source
Some types of node also have an
expanded-name, which is a pair consisting of a local part and a
namespace URI. The local part is a string. The namespace URI is
either null or a string. The namespace URI specified in the XML
document can be a URI reference as defined in ; this means it can
have a fragment identifier and can be relative. A relative URI
should be resolved into an absolute URI during namespace
processing: the namespace URIs of expanded-names of nodes in the
data model should be absolute.
- expanded-QName
-
From XSL Transformations (XSLT)
2.0 (2007-01-23) |
Glossary for this
source
An expanded-QNamecontains a pair of values,
namely a local name and an optional namespace URI. It may also
contain a namespace prefix. Two expanded-QNames are equal if the
namespace URIs are the same (or both absent) and the local names
are the same. The prefix plays no part in the comparison, but is
used only if the expanded-QName needs to be converted back to a
string.