W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2000

Re: SVG, Style, Resizing, Etc.

From: Ian Jacobs <ij@w3.org>
Date: Thu, 05 Oct 2000 08:30:10 -0400
Message-ID: <39DC7452.11D79557@w3.org>
To: Al Gilman <asgilman@iamdigex.net>
CC: w3c-wai-ua@w3.org
Al Gilman wrote:
> 
> At 04:51 AM 2000-10-05 -0400, Ian Jacobs wrote:
> >>
> >> 3. The resizing of vector graphics like SVG I do not think are addressed
> >> in the guidelines.  I think the group should discuss this. I will add it
> >> to the issue list for discussion on 10 October.
> >
> >IJ: Please help me understand the issue at hand.
> >
> >1) For the case of SVG, the requirement in question (the ability to
> >   recsize content) is part of conformance (and thus covered by
> >   UAAG 1.0 checkpoint 6.2). Refer to section G.7 [1]:
> >
> >   "For interactive user environments, facilities must exist for
> >    zooming and panning of standalone SVG documents or
> >    SVG document fragments embedded within parent XML documents."
> >
> >   There are other relevant conformance requirements in that section.
> >
> 
> AG::
> 
> [There's nothing to keep us from clarifying the issue by mail prior to the
> telecon.]
> 
> This is good.
> 
> Do the "other ... conformance requirements" determine what happens about
> the boundary in the layout canvas between the SVG content of an embedded
> SVG object and the other content of the parent XML document? 

1) Section G4 [1] talks about conformance for included SVG fragments. I
don't
   see any mention of rendering requirements for this case.

   [1]
http://www.w3.org/TR/2000/CR-SVG-20000802/conform.html#ConformingSVGIncludedDocuments

2) I think it's not the SVG spec that should be concerned with how
rendering
   happens at the boundary around the SVG object - that's the realm of
the 
   englobing language (some languages may have different boundary
semantics).

 - Ian


> Turning a
> navigation button into a scroll region because the user asked for it larger
> would not exactly be swift.
> 
> Al
> 
> >2) For other cases, any user agent that implements a scalable data
> >format that doesn't allow the user to scale the data is a worthless
> >tool. The accessibility of a worthless tool should not be our primary
> >concern.
> >
> >I think that the proposed requirements (below)
> >for vector graphics control are thus unnecessary.
> >
> > - Ian
> >
> >[1]
> >http://www.w3.org/TR/2000/CR-SVG-20000802/conform.html#ConformingSVGViewers
> >
> >> I think the issue that the group would need to discuss is adding a section
> >> in guidelines line 4 for graphics:
> >>
> >> Three prossible checkpoints:
> >> 4.x Allow the user to configure and control the reference size of rendered
> >> vector graphics with an option to override author specified reference
> >> sizes and default user agent sizes. [Priority 1 or 2]
> >>
> >> 4.y Allow the user to configure the foreground color of vector graphics,
> >> including the use of gray scale for mapping colors. [Priority 1 or 2]
> >>
> >> 4,z Allow the user to configure the background color of vector graghics.
> >> [Priority 1 or 2]

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783
Received on Thursday, 5 October 2000 08:30:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:21 GMT