Re: group task GL 1.7

> JR: First, the supporting definitions aren't very helpful...
>
> style profile: An identifiable collection of style rules is a style profile.
> JR: What does identifiable mean? At a URI? If this is meant to mean stylesheets (either directly or via some UI abstraction) lets put that in.
>
Agree. this was intended to abstract style sheet to other (future?)
technologies that have a style mechanism but not style sheets.

> style rule: An assignment of presentation properties to a style profile is a style rule.
> JR: Why refer back to style profile (creating a circularity)? Isn't it just a statement that a certain part of the content will be presented with a certain style (whether visual, sonic or haptic)?

Agree. what about the case of inline styles.
perhaps...
style rule: An assignment of presentation properties to an element in
content is a style rule.
>
>> 1.7.1 Support User Style Profiles:  User agents that support a mechanism for authors to supply style profiles shall also provide an equally effective mechanism for users to supply profiles. (Level A)
>
> JR: Not sure what is meant by "equally effective". If we think users should have the same level of style control as authors, eg. down to styling by ID etc. then we really do just mean stylesheets and we should return to the original wording..
>
Agree. we should remove 'equally effective'
as to stylesheet vs style profile ... will bring it up on the call today

>> 1.7.2 Apply User Style Profiles: The user can turn on the use of user style profiles and for every user style profile defined, the user can choose whether or not it should be applied to: (Level A)
>    (a) the current page, or
>    (b) all pages on specified web sites, or
>    (c) all pages.
>
> JR: Could this be AA?

I think it could be AA. currently user style sheets are for (c) all
pages. Chrome has an extension that applies to (b) all pages in a
website. it is called Stylish. It is also available for Firefox

>
>> 1.7.3 Author Style Sheets: The user can turn off the use of author style profiles, and for every author style sheet defined the user can choose whether or not it should be applied to: (Level A)
>    (a) the current page, or
>    (b) all pages for which it is defined.
>
> JR: We mix style profile and style sheet in this SC. So there needs to be a UI where all the stylesheets can be toggled?

Right, we need to decide on a term. And there need to be a UI to
toggle for a) and b). I believe stylish could cover b), if it is all
pages in a site. this could a large undertaking for a UA to manage.
all pages and per site makes sense, random pages in a site seems far
fetched.

>
>> 1.7.4 Save copies of style profiles: The user can save copies of the style profiles referenced by the current page, so that they can edit and load them as user style profiles. (Level AA)
>
> JR: So the ability to capture style sheets so they can tweek them as the basis for their own styling?
>
yes. This one almost reads like an intent. should loose everything
after the comma, SC should provide for what the user can or cannot do,
not what they will do with the style sheet after they save it.
propose:
1.7.4 Save copies of style profiles: The user can save copies of the
style profiles referenced by the current page. (Level AA)

Jim

> Cheers,
> Jan



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

Received on Thursday, 26 April 2012 17:03:03 UTC