User Agent User Interface vs Rendered Content vs User Interface

note codes preceding Principles, Guidelines, SC, and definition:
RC - Rendered Content
UAUI - user agent user interface
anything that does not have one of the above designations uses only "user
interface"

User Agent User Interface  used 27 times, (2 GL, 12 SC,  6 definitions)

Rendered Content used 23 times (1 Principle,   12 SC, 3 definitions)

User Interface used 74 times (3 principles, 2GL, 18 SC. 11 definitions

2 SC overlap, 2 def. overlap between UAUI&RC

RC PRINCIPLE 1 - Ensure that the user interface and rendered content are
perceivable

UAUI GL 1.4 Note 3: The success criteria in guideline 1.4 can be met
through user stylesheets. For platforms without user stylesheets, text
configuration needs to be provide to users through the user agent's main
user interface.

PRINCIPLE 2. Ensure that the user interface is operable

PRINCIPLE 3: Ensure that the user interface is understandable

Guideline 3.3 - Document the user agent user interface including
accessibility features

other common terms for UAUI used are: application user interface, default
user interface, user interface component, user interface setting, user
agent feature (change to component?), user interface event, user interface
element,

other term for rendered content: content display,

RC.1.2 Indicate Unrendered Alternative Content: The user can specify that
indicators be displayed along with rendered content when recognized
unrendered alternative content is present. (Level A)

RC 1.4.4 Configured and Reflowed Text Printing: The user can print the
rendered content, and the following are all true: (Level AA)
any rendered, visual, non-time-based content can be printed
the user can choose between available printing devices
the user can have content printed as it is rendered on screen, reflecting
any user scaling, highlighting, and other modifications
the user can have printed content reflow as if the top-level viewport had
been resized to match the horizontal dimension of the printing device's
printable area

RC 1.8.3 Provide Viewport Scrollbars: When the rendered content extends
beyond the viewport dimensions, users can have graphical viewports include
scrollbars, overriding any values specified by the author. (Level A)

RC 1.8.4 Indicate Viewport Position: The user can determine the viewport's
position relative to the full extent of the rendered content. (Level A)

1.8.13 Allow Same User Interface: The user can specify that all top-level
viewports (e.g. windows or tabs) follow the defined user interface
configuration. (Level AA)

RC 1.9.1 Outline View: Users can view a navigable outline of the rendered
content that allows focus to be moved to the corresponding element in the
main viewport. (Level AA)

Note: The elements reflected in the outline view depend on the web content
technology, and may include headings, table captions, and content sections.

UAUI 2.1.6 Make Keyboard Access Efficient: The user agent user interface
includes mechanisms to make keyboard access more efficient than sequential
keyboard access. (Level A)

RC 2.3.1 Allow Direct Navigation to Enabled Elements: The user can move
keyboard focus directly to any enabled element in the rendered content.
(Level AA)

RC 2.3.2 Allow Direct Activation of Enabled Elements: The user can, in a
single action, move keyboard focus directly to any enabled element in the
rendered content and perform an activation action on that element. (Level
AA)

RC 2.3.3 Present Direct Commands from Rendered Content: The user can have
any recognized direct commands in rendered content (e.g. accesskey,
landmark) be presented with their associated elements (e.g. Alt+R to reply
to a web email). (Level AA)

UAUI 2.3.4 Present Direct Commands in User Interface: The user can have any
direct commands in the user agent user interface (e.g. keyboard shortcuts)
be presented with their associated user interface controls (e.g. "Ctrl+S"
displayed on the "Save" menu item and toolbar button). (Level AA)

UAUI 2.3.5 Allow Customized Keyboard Commands: The user can remap any
keyboard shortcut including recognized author supplied shortcuts (e.g.
accesskeys) and user agent user interface controls, except for conventional
bindings for the operating environment (e.g. arrow keys for navigating
within menus). (Level AA)

RC 2.4.1 Text Search: The user can perform a search within rendered
content, including rendered text alternatives and rendered generated
content, for any sequence of printing characters from the document
character set. (Level A)

RC 2.4.2 Search Direction: The user can search forward or backward in
rendered content. (Level A)

UAUI 2.7.4 Allow Preference Changes from outside the User Interface: The
user can adjust any preference settings required to meet the User Agent
Accessibility Guidelines (UAAG) 2.0 from outside the user agent user
interface. (Level AAA)

UAUI 2.8.1 Customize Display of Controls for User Interface Commands,
Functions, and Extensions: The user can customize which user agent
commands, functions, and extensions are displayed within the user agent
user interface as follows: (Level AA)
Show: The user can choose to display any controls available within the user
agent user interface, including user-installed extensions. It is acceptable
to limit the total number of controls that are displayed onscreen.
Simplify: The user can simplify the default user interface by choosing to
display only commands essential for basic operation (e.g. by hiding some
controls).
Reposition: The user can choose to reposition individual controls within
containers (e.g. toolbars or tool palettes), as well as reposition the
containers themselves to facilitate physical access (e.g. to minimize hand
travel on touch screens, or to facilitate preferred hand access on handheld
mobile devices).
Assign Activation Keystrokes or Gestures: The user can choose to view,
assign or change default keystrokes or gestures used to activate controls.
Reset: The user has the option to reset the containers and controls to
their default configuration.

UAUI 2.9.1 Adjustable Time Limits: The user agent user interface does not
include time limits or at least one of the following is true: (Level A)
Turn Off: Users are allowed to turn off the time limit before encountering
it; or
Adjust: Users are allowed to adjust the time limit before encountering it
over a wide range that is at least ten times the length of the default
setting; or
Extend: Users are warned before time expires and given at least 20 seconds
to extend the time limit with a simple action (e.g. "press the space bar"),
and users are allowed to extend the time limit at least ten times; or
Real-time Exception: The time limit is a required part of a real-time event
and no alternative to the time limit is possible; or
Essential Exception: The time limit is essential and extending it would
invalidate the activity; or
20 Hour Exception: The time limit is longer than 20 hours.

2.10.1 Three Flashes or Below Threshold: In its default configuration, the
user agent does not display any user interface components that flashes more
than three times in any one-second period, unless the flash is below
general flash and red flash thresholds. (Level A)

2.10.2 Three Flashes: In its default configuration, the user agent does not
display any user interface components that flashes more than three times in
any one-second period (regardless of whether not the flash is below the
general flash and red flash thresholds). (Level AAA)

3.2.5 Settings Changes can be Reversed or Confirmed: If the user agent
provides mechanisms for changing its user interface settings, it either
allows the user to reverse the setting changes, or the user can require
user confirmation to proceed. (Level A)

UAUI 3.3.2 Describe Accessibility Features: For each user agent feature
that is used to meet UAAG 2.0, at least one of the following is true:
(Level A)
Described in the Documentation: Use of the feature is explained in the user
agent's documentation; or
Described in the Interface: Use of the feature is explained in the user
agent user interface; or
Platform Service: The feature is a service provided by an underlying
platform; or
Not Used by Users: The feature is not used directly by users (e.g., passing
information to a platform accessibility service).

UAUI 3.3.x Document All Features: For each user agent feature, at least one
of the following is true: (Level AA)
Described in the Documentation: Use of the feature is explained in the user
agent's documentation; or
Described in the Interface: Use of the feature is explained in the user
agent user interface; or
Platform Service: The feature is a service provided by an underlying
platform; or
Not Used by Users: The feature is not used directly by users (e.g., passing
information to a platform accessibility service).

UAUI&RC 4.1.2 Expose Basic Properties: For all user interface components,
including user agent user interface, rendered content, and generated
content, the user agent makes available the following via a platform
accessibility service: (Level A)
Name
Role
State
Value
Selection
Focus

UAUI 4.1.3 Provide Equivalent Accessible Alternatives: If a component of
the user agent user interface cannot be exposed through platform
accessibility services, then the user agent provides an equivalent
alternative that is exposed through the platform accessibility service.
(Level A)

4.1.5 Make Write Access Programmatically Available: If the user can modify
the state or value of a piece of content through the user interface (e.g.
by checking a box or editing a text area), the same degree of write access
is programmatically available. (Level A)

UAUI&RC 4.1.6 Expose Additional Properties: For all user interface
components, including the user agent user interface, rendered content, and
generated content, the user agent makes available the following, via a
platform accessibility service, if the properties are supported by the
service: (Level AA)
Bounding dimensions and coordinates
Font family of text
Font size of text
Foreground and background color for text
Change state/value notifications
Highlighting
Keyboard commands

UAUI 5.1.1 Comply with WCAG: Web-based user agent user interfaces meet the
WCAG 2.0 success criteria. (Level A to meet WCAG 2.0 Level A success
criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; and
Level AAA to meet WCAG 2.0 Level A, AA, and AAA success criteria)

Note: This success criterion does not apply to non-web-based user agent
user interfaces, but does include any parts of non-web-based user agents
that are web-based (e.g. help systems). However, it is recommended that
developers of non-web-based user agent user interfaces follow the Guidance
on Applying WCAG 2.0 to Non-Web Information and Communications Technologies
(WCAG2ICT) [WCAG2ICT].

5.1.3 Implement Accessibility Features of the Platform: If the user agent
contains non-web-based user interfaces, then those user interfaces follow
user interface accessibility guidelines for the platform. (Level A)

UAUI&RC activate -To carry out the behaviors associated with an enabled
element in the rendered content or a component of the user agent user
interface.

enabled element: An element with associated behaviors that can be activated
through the user interface or through an API. The set of elements that a
user agent enables is generally derived from, but is not limited to, the
set of elements defined by implemented markup languages.

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.

UAUI explicit user request - An interaction by the user through the user
agent 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
may inadvertently respond "yes" to a prompt instead of "no." This type of
error is still considered an explicit user request.

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).

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 may 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.

RC outline view: A view where only a subset of the rendered
content is presented, usually composed of labels or placeholders for
important structural elements. The important structural elements will
depend on the web content technology, but may include headings, table
captions, and content sections.

UAUI notify - To make the user aware of events or status changes.
Notifications can occur within the user agent user interface (e.g. a status
bar) or within the content display. Notifications may be passive and not
require user acknowledgment, or they may be presented in the form of a
prompt requesting a user response (e.g. a confirmation dialog)
RC point of regard - The 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 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 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, keyboard focus, and selection.

RC rendered content - The presentation generated by the user agent based on
the author supplied code. This includes text characters, images,
stylesheets, scripts, and any other content that, once processed, may be
perceived.

UAUI&RC user interface - For the purposes of UAAG 2.0, the user interface
includes both:
user agent user interface: The controls (e.g. menus, buttons, prompts,
native audio/video player controls, and other components for input and
output) and mechanisms (e.g. selection and focus) provided by the user
agent that are not created on the basis of the author-supplied content. The
user agent user interface may include extensions that become part of the
user agent user interface (e.g. toolbars, additional menus).

content user interface: The user interface that emerges from the user agent
rendering of the author-supplied content. It includes all rendered content
(e.g. text, headings, enabled elements, disabled elements, author-supplied
audio/video controls).

Note: There may be a mix of recognized and unrecognized user interface
controls depending on the author-supplied content.
This document distinguishes user agent user interface and content user
interface only where required for clarity.

UAUI user interface control - A component of the user agent user interface
or the content user interface, distinguished where necessary.

UAUI top-level viewport: A viewport that is not contained within another
viewport of a platform-based user agent. Web-based user agents are always
displayed inside another viewport, and therefore are never top-level
viewports. A popular browser implementation is to provide a window that
includes some user agent user interface elements (e.g., menus) and a series
of tabbed panels, each of which contains additional user agent user
interface elements (e.g., address bar, bookmarks, back/forward buttons) and
a top-level viewport for rendering a view of the addressed web resource.

RC 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).





-- 
[image: http://www.tsbvi.edu] <http://www.tsbvi.edu>Jim Allan,
Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964