W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2001

Re: problems with Checkpoint 2.1

From: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
Date: Thu, 01 Feb 2001 12:48:19 -0600
Message-Id: <4.3.1.2.20010201124057.038f0008@staff.uiuc.edu>
To: Al Gilman <asgilman@iamdigex.net>, w3c-wai-ua@w3.org
Responses in JRG:

  An example would be an SVG graphic used in a web page.  The SVG
>actually containts a lot of words, and the words are internally stored in a
>legible form following the suggestions of the access note for SVG.  But the
>User Agent doesn't implement SVG.  The user should be able to glance at the
>SVG
>source as text and find the natural language embedded there even 'though they
>don't get the graphic rendition.  In addition to this, if the user has a
>player
>for the format of any object in the content, then the user must have the
>option
>to have that content rendered with that player.

JRG: So this would require source views for unsupported or unrecognized 
formats.  Is XML based formats a special case?


>Another application scenario is that if what the author of the SMIL thought
>the
>user didn't need is an audio track, then the user must have access to an audio
>rendering of that object if the User Agent supports that type of audio format
>at all.  The user should be able to chose from the full range of feasible
>options, based on the formatting of the data and the formats implemented by
>the
>player.
>
>The user must have their choice including a) if it is a format that the User
>Agent implements, the user must have the choice of formatted rendering and b)
>if the format is a text format and the User Agent implements Internet Media
>Type text/plain, then the user must have the choice of text presentation.  The
>requirement is the union of these two, not the intersection.
>
>Another example:  If the document links to a stylesheet in text/css , and the
>User Agent implements text/plain, then the user must be able to view the text
>of the stylesheet whether or not the User Agent implements CSS.

JRG:
Are you saying that the UA must provide source views of linked resources?
Is an image SRC considered link information?
Do you know of anything that does this?
Amaya?


><possible new>
>
>    2.1 Make all [158]content available through the user interface. For 
> formats
>that the User Agent implements (see [162]checkpoint 6.2), make the content
>available through the implemented rendering process   In addition, for all
>[new
>ref]text formats, make a source text view available. [Priority 1]

JRG: should "implemented" be "specified".  If the rendering is not 
specified anywhere, do we want to include the concept of using conventions?

>[edit to reduce the note, perhaps.]
>
>           Note: In general, user agents render content through the user
>           interface according to the instructions of implemented
>           specifications (see [162]checkpoint 6.2). However, some users
>           may not be able to access this content, even when the user
>           agent renders it according to specification (e.g., for scripts
>           or style sheets). Therefore, this checkpoint includes the
>           requirement that user agents make available raw text content
>           (including attributes, style sheets, etc.) through the user
>           interface. Although this view (which may be a [163]document
>           source view) is an important part of a solution for providing
>           access to content, it is not a sufficient solution on its own
>           for all content. This checkpoint does not require that all
>           content be available through every [164]viewport. See
>           [165]guideline 5 for more information about programmatic access
>           to content.
>           [166]Techniques for checkpoint 2.1
>
>
>AG::  Insert definition at end of [new ref]
>
>Text formats:  This includes the following two subcategoies.  First,all media
>objects given an Internet Media Type of 'text', that is text/plain, text/HTML,
>text/* or text/anything.  Second, all SGML and XML applications regardless of
>Internet Media Type, including HTML 4.01, XHTML 1.1, SMIL, SVG, etc.
>

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL  61820

Voice: (217) 244-5870
Fax: (217) 333-0248

E-mail: jongund@uiuc.edu

WWW: http://www.staff.uiuc.edu/~jongund
WWW: http://www.w3.org/wai/ua
Received on Thursday, 1 February 2001 13:46:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:29 UTC