- accessibility
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
Within these guidelines, "accessible Web content" and "accessible authoring tool" mean that the content and tool can be used by people regardless of disability.To understand the accessibility issues relevant to authoring tool design, consider that many authors may be creating content in contexts very different from your own: They may not be able to see, hear, move, or may not be able to process some types of information easily or at all;They may have difficulty reading or comprehending text;They may not have or be able to use a keyboard or mouse;They may have a text-only display, or a small screen.Accessible design will benefit people in these different authoring scenarios and also many people who do not have a physical disability but who have similar needs. For example, someone may be working in a noisy environment and thus require an alternative representation of audio information. Similarly, someone may be working in an eyes-busy environment and thus require an audio equivalent to information they cannot view. Users of small mobile devices (with small screens, no keyboard, and no mouse) have similar functional needs as some users with disabilities.
- accessibility information
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
"Accessibility information" is content, including information and markup, that is used to improve the accessibility of a document. Accessibility information includes, but is not limited to, equivalent alternative information.
- accessibility problem
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
Inaccessible Web content or authoring tools cannot be used by some people with disabilities. The Web Content Accessibility Guidelines 1.0 [WCAG10] describes how to create accessible Web content.
- accessible authoring practice
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
"Accessible authoring practices" improve the accessibility of Web content. Both authors and tools engage in accessible authoring practices. For example, authors write clearly, structure their content, and provide navigation aids. Tools automatically generate valid markup and assist authors in providing and managing appropriate equivalent alternatives.
- alert
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
An "alert" draws the author's attention to an event or situation. It may require a response from the author.
- alternative information
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
Content is "equivalent" to other content when both fulfill essentially the same function or purpose upon presentation to the user. Equivalent alternatives play an important role in accessible authoring practices since certain types of content may not be accessible to all users (e.g., video, images, audio, etc.). Authors are encouraged to provide text equivalents for non-text content since text may be rendered as synthesized speech for individuals who have visual or learning disabilities, as braille for individuals who are blind, or as graphical text for individuals who are deaf or do not have a disability. For more information about equivalent alternatives, please refer to the Web Content Accessibility Guidelines WCAG 1.0 [WCAG10].
- attribute
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
This document uses the term "attribute" as used in SGML and XML ([XML]): Element types may be defined as having any number of attributes. Some attributes are integral to the accessibility of content (e.g., the "alt", "title", and "longdesc" attributes in HTML).
- auditory description
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
An "auditory description" provides information about actions, body language, graphics, and scene changes in a video. Auditory descriptions are commonly used by people who are blind or have low vision, although they may also be used as a low-bandwidth equivalent on the Web. An auditory description is either a pre-recorded human voice or a synthesized voice (recorded or automatically generated in real time). The auditory description must be synchronized with the auditory track of a video presentation, usually during natural pauses in the auditory track.
- authoring tool
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
An "authoring tool" is any software that is used to produce content for publishing on the Web. Authoring tools include: Editing tools specifically designed to produce Web content (e.g., WYSIWYG HTML and XML editors);Tools that offer the option of saving material in a Web format (e.g., word processors or desktop publishing packages);Tools that transform documents into Web formats (e.g., filters to transform desktop publishing formats to HTML);Tools that produce multimedia, especially where it is intended for use on the Web (e.g., video production and editing suites, SMIL authoring packages);Tools for site management or site publication, including tools that automatically generate Web sites dynamically from a database, on-the-fly conversion and Web site publishing tools;Tools for management of layout (e.g., CSS formatting tools).
- captions
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
"Captions" are essential text equivalents for movie audio. Captions consist of a text transcript of the auditory track of the movie (or other video presentation) that is synchronized with the video and auditory tracks. Captions are generally rendered graphically and benefit people who can see but are deaf, hard-of-hearing, or cannot hear the audio.
- check for
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
As used in checkpoint 4.1, "check for" can refer to three types of checking: In some instances, an authoring tool will be able to check for accessibility problems automatically. For example, checking for validity (checkpoint 2.2) or testing whether an image is the only content of a link.In some cases, the tool will be able to "suspect" or "guess" that there is a problem, but will need confirmation from the author. For example, in making sure that a sensible reading order is preserved a tool can present a linearized version of a page to the author.In some cases, a tool must rely mostly on the author, and can only ask the author to check. For example, the tool may prompt the author to verify that equivalent alternatives for multimedia are appropriate. This is the minimal standard to be satisfied. Subtle, rather than extensive, prompting is more likely to be effective in encouraging the author to verify accessibility where it cannot be done automatically.
- conversion tool
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
A "conversion tool" is any application or application feature (e.g., "Save as HTML") that transforms convent in one format to another format (such as a markup language).
- document
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
A "document" is a series of elements that are defined by a markup language (e.g., HTML 4 or an XML application).
- editing view
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
An "editing view" is a view provided by the authoring tool that allows editing.
- element
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
An "element" is any identifiable object within a document, for example, a character, word, image, paragraph or spreadsheet cell. In [HTML4] and [XML], an element refers to a pair of tags and their content, or an "empty" tag - one that requires no closing tag or content.
- inform
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
To "inform" is to make the author aware of an event or situation through alert, prompt, sound, flash, or other means.
- markup language
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
Authors encode information using a "markup language" such as HTML [HTML4], SVG [SVG], or MathML [MATHML].
- presentation markup
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
"Presentation markup" is markup language that encodes information about the desired presentation or layout of the content. For example, Cascading Style Sheets ([CSS1], [CSS2]) can be used to control fonts, colors, aural rendering, and graphical positioning. Presentation markup should not be used in place of structural markup to convey structure. For example, authors should mark up lists in HTML with proper list markup and style them with CSS (e.g., to control spacing, bullets, numbering, etc.). Authors should not use other CSS or HTML incorrectly to lay out content graphically so that it resembles a list.
- prompt
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
A "prompt" is a request for author input, either information or a decision. A prompt requires author response. For example, a text equivalent entry field prominently displayed in an image insertion dialog would constitute a prompt. Prompts can be used to encourage authors to provide information needed to make content accessible (such as alternative text equivalents).
- property
-
From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03)
A "property" is a piece of information about an element, for example structural information (e.g., it is item number 7 in a list, or plain text) or presentation information (e.g., that it is marked as bold, its font size is 14). In XML and HTML, properties of an element include the type of the element (e.g., IMG or DL), the values of its attributes, and information associated by means of a style sheet. In a database, properties of a particular element may include values of the entry, and acceptable data types for that entry.