W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2012

Re: UAWG Action 727 - Write glossary item for top-level viewport

From: Kim Patch <kim@redstartsystems.com>
Date: Fri, 27 Apr 2012 11:46:31 -0400
Message-ID: <4F9ABF57.7030504@redstartsystems.com>
To: "Richards, Jan" <jrichards@ocadu.ca>
CC: "w3c-wai-ua@w3.org" <w3c-wai-ua@w3.org>
Nice.

1. Minor editorial comment -- there's a word left out near the end of 
the outline views sentence:

Original:
- outline views: The view presents only a subset of the rendered 
content, composed of labels for important structural. The important...

Corrected:
- outline views: The view presents only a subset of the rendered 
content, composed of labels for important structural *elements*. The 
important structural...


2. Suggestion: I'd like to see the ability to enlarge a viewport be a 
choice we mention in addition to scrollbars (when screen real estate 
permits, enlarging is often better for cognitive and mobility reasons -- 
you can see more of the content at once, and you can cut down on 
scrolling actions).

Original:
Note 1: When the viewport is smaller in extent than the content it is 
presenting, user agents typically provide mechanisms for the user to 
bring the occluded content into the viewport (e.g., onscreen scrollbars, 
printed page turning, audio advance and rewind).
Suggested change:
Note 1: When the viewport is smaller in extent than the content it is 
presenting, user agents typically provide mechanisms for the user to 
bring the occluded content into the viewport (e.g., onscreen scrollbars 
*and resizzable viewports*, printed page turning, audio advance and rewind).

Cheers,
Kim

On 4/26/2012 5:09 PM, Richards, Jan wrote:
> https://www.w3.org/WAI/UA/tracker/actions/727
>
> It seemed so easy...
>
> It turns out that there already is a definition, but it doesn't mention rendering content and view/viewport as a whole is a bit bloated, so I decided to dive in and
> attempt a major rewording (including bringing in the ATAG 2.0 term "view" - http://www.w3.org/TR/ATAG20/#def-View). I'm actually quite happy with how it has finally put audio and printed viewports on a coherent footing:
>
> 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:
> - rendered views: The content is presented in rendered form, typically according to the web content technology specification. This is the default view of most user agents.
> - source views: The content is presented in unrendered form. The source view may be plain text (i.e., "View Source") or it may include some other organization (e.g., presenting the markup in a tree).
> - outline views: The view presents only a subset of the rendered content, composed of labels for important structural. The important structural elements will depend on the web content technology, but may include headings, table captions, and content sections.
> - property views: Only selected properties of the content are presented, separate from their source or rendered forms (e.g., image properties, JavaScript errors).
>
> VIEWPORT
> The part of a view that the user agent is currently presenting to the user, such that the user can attend to any part of it without further action (scrolling, etc.) by the user agent. : A user agent may include more than on viewport and they can be onscreen (e.g., windows, frames, panes, dialog boxes), printed (e.g. ink on paper, [ed. branded on cattle]), audio (e.g., sound from a speaker) or tactile (e.g. state of a Braille display). [ed. I'm assuming olfactory UIs are still not prime-time]
> - NESTED Viewport: A viewport that is contained within another viewport (e.g. a frame within a document).
> - TOP-LEVEL (USER AGENT) VIEWPORT: The highest-level viewport in a user agent application.
> - AUTOMATICALLY-ADVANCING Viewport:  Some viewports automatically advance in one or more dimension (spatially or temporally). Audio viewports typically advance automatically (temporally), otherwise they would not produce coherent output, and so do some onscreen viewports (e.g. rendering video or animations or auto-scrolling) and tactile viewports.
> Note 1: When the viewport is smaller in extent than the content it is presenting, user agents typically provide mechanisms for the user to bring the occluded content into the viewport (e.g., onscreen scrollbars, printed page turning, audio advance and rewind).
> Note 2: Because user agent applications can be nested, the top-level viewport in a nested user agent will not be the top-level viewport in the full user agent stack.
> Note 3: The user agent's own user interface controls (menus, alerts, etc.) are not considered viewports, though if the user agent is nested the user interface controls  may in fact be implemented using viewports of the higher-level user agent.
>
> Ed. So we would replace "top-level content viewports (e.g. windows or tabs)" in the document with "top-level user agent viewports"
> Ed. We should also replace "Graphical" in most instances with "onscreen"
>
> CURRENT WORDING:
> http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120419/#def-viewport
>
> Cheers,
> Jan
>
>
>

-- 
___________________________________________________

Kimberly Patch
President
Redstart Systems, Inc.
(617) 325-3966
kim@redstartsystems.com

www.redstartsystems.com <http://www.redstartsystems.com>
- making speech fly

Blog: Patch on Speech
+Kim Patch
Twitter: RedstartSystems
www.linkedin.com/in/kimpatch <http://www.linkedin.com/in/kimpatch>
___________________________________________________
Received on Friday, 27 April 2012 15:47:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 15:47:02 GMT