Re: Spacing SC

Laura,
I think your cases look good. I think we should research web components a
little. HTML5 might not be as easy to address as people think.

Wayne

On Mon, Jan 16, 2017 at 2:19 PM, Wayne Dick <wayneedick@gmail.com> wrote:

> I think that the LVTF should support SC's for spacing and font-family even
> if we cannot come up with an example of HTML that does not allow a
> JavaScript modification.
>
> The reason is this. This level of support should have been part of 1.3.1.
> It wasn't because WCAG WG used an intersection model. if a necessary
> accommodation was not supported by all technologies, we could not make an
> SC blocking certain authoring techniques.
>
> Our language lets the author off the hook on a platform or in a file
> language that can't support the change. This is a union model. If there is
> one user agent that supports the feature then authors must write design
> their page so that it does not conflict with that support. We can even say
> one commonly used agent.
>
> This model means that we should combine our techniques into one, so that
> a  person can get feature x only on browser A but needs to go to browser B
> for feature y.
>
> I think we need a group statement on this.
>
> Wayne
>
> On Mon, Jan 16, 2017 at 1:52 PM, Jim Allan <jimallan@tsbvi.edu> wrote:
>
>> Acrobat DC (not Acrobat reader) allows changes to line, character, and
>> paragraph spacing, in editable PDFs. you can also change the font, font
>> color, and font size.
>>
>> Jim
>>
>> On Wed, Jan 11, 2017 at 9:42 AM, Jonathan Avila <
>> jon.avila@ssbbartgroup.com> wrote:
>>
>>> > I tested in Safari and it respects user styles over author inline
>>> styles. Jon,  the Stylish extension on Chrome and Firefox didn't respect
>>> user styles over author inline styles for me.
>>>
>>> Yes, that is the point I was attempting to make-- from what I know
>>> stylish adds in the styles as document level styles and they are not seen
>>> as "user level styles".  Many browsers don't let you add user level styles
>>> and thus we are stuck with tools that only allow us to enter document level
>>> styles.
>>>
>>> Jonathan
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Laura Carlson [mailto:laura.lee.carlson@gmail.com]
>>> Sent: Tuesday, January 10, 2017 4:05 PM
>>> To: Wayne Dick; Jonathan Avila
>>> Cc: public-low-vision-a11y-tf; Shawn Henry
>>> Subject: Re: Spacing SC
>>>
>>> Hi Wayne, Jon and all,
>>>
>>> Thanks for your comments on the Github Issue.
>>>
>>> I put together a simple test case:
>>> http://www.d.umn.edu/~lcarlson/wcagwg/tests/user_styles/impo
>>> rtant_spacing.html
>>>
>>> A spacing user stylesheet is also available. It uses Wayne's CSS
>>> declarations. (Thanks Wayne!) http://www.d.umn.edu/~lcarlson
>>> /wcagwg/tests/user_styles/spacing.css
>>>
>>> Please test it and let me know your results.
>>>
>>> I tested in Safari and it respects user styles over author inline
>>> styles. Jon,  the Stylish extension on Chrome and Firefox didn't respect
>>> user styles over author inline styles for me.
>>>
>>> Kindest Regards,
>>> Laura
>>>
>>> On 1/9/17, Laura Carlson <laura.lee.carlson@gmail.com> wrote:
>>> > Hi Wayne,
>>> >
>>> > Thank you for checking the verbiage. Yes, I posted a first attempt at
>>> > new language in a comment on the GitHub issue. It is at:
>>> > https://github.com/w3c/wcag21/issues/78#issuecomment-270716413
>>> >
>>> > According to the SC Managers Phase1 Wiki page, GitHub is the main
>>> > platform for commenting on SCs. @mbgower proposed refining it a bit:
>>> >
>>> >> For all text presented in the content, each of the following is true:
>>> >>
>>> >> * word spacing can be adjusted by the user
>>> >>* line spacing can be adjusted by the user
>>> >>* paragraph spacing can be adjusted by the user "
>>> > https://github.com/w3c/wcag21/issues/78#issuecomment-270822241
>>> >
>>> > Mike's language seems simpler. To me the word "adjusted" makes more
>>> > sense than the word "selected".
>>> >
>>> > @patrickhlauke did some user style sheet testing. His findings:
>>> >
>>> >> providing that a user stylesheet is
>>> >> written appropriately, !important in
>>> >> the author's styles and style
>>> >> attributes do NOT override the user
>>> >> styles."
>>> > https://github.com/w3c/wcag21/issues/78#issuecomment-271170859
>>> >
>>> > Wayne and Shawn, do either of you have an example of where !important
>>> > can't be overwritten by users? If so please comment in the GitHub
>>> > issue.
>>> > https://github.com/w3c/wcag21/issues/78
>>> >
>>> > Thank you!
>>> >
>>> > Kindest Regards,
>>> > Laura
>>> >
>>> >
>>> > On Jan 8, 2017 10:50 AM, "Wayne Dick" <wayneedick@gmail.com> wrote:
>>> >
>>> >> Laura,
>>> >> This is exactly right.
>>> >>
>>> >> A mechanism does exist- User Style Sheets for Accommodation.
>>> >>
>>> >> Did you post this language?
>>> >>
>>> >> Wayne
>>> >>
>>> >> PS: I will attend to font family.
>>> >>
>>> >> On Thu, Jan 5, 2017 at 1:29 PM, Laura Carlson
>>> >> <laura.lee.carlson@gmail.com> wrote:
>>> >> > Hi again,
>>> >> >
>>> >> > I added a first attempt at rewording the SC with exemptions.
>>> >> >
>>> >> > For the visual presentation of blocks of text:
>>> >> >
>>> >> > * character spacing can be selected by the user
>>> >> > * word spacing can be selected by the user
>>> >> > * line spacing can be selected by the user
>>> >> > * paragraph spacing can be selected by the user
>>> >> >
>>> >> > with following the exceptions:
>>> >> >
>>> >> > * If spacing of content is essential to that contents use, that
>>> >> > part of the content is exempt.
>>> >> > * If the user agent prohibits spacing adjustments the content is
>>> >> > exempt.
>>> >> >
>>> >> > https://github.com/w3c/wcag21/issues/78#issuecomment-270716413
>>> >> >
>>> >> > Ideas for improvement?
>>> >> >
>>> >> > Kindest Regards,
>>> >> > Laura
>>> >> >
>>> >> >
>>> >> > On 1/5/17, Laura Carlson <laura.lee.carlson@gmail.com> wrote:
>>> >> >> Hello Low Vision Task Force,
>>> >> >>
>>> >> >> Thank you for the discussion on the Spacing SC at today's meeting.
>>> >> >> Much appreciated.
>>> >> >>
>>> >> >> I commented on the Github Issue to get people's thoughts on the
>>> >> >> mobile exception approach.
>>> >> >> https://github.com/w3c/wcag21/issues/78#issuecomment-270716413
>>> >> >>
>>> >> >> Please chime in with your perspective if you have something to add.
>>> >> >> Shawn, it would be terrific to have your thoughts in the GitHub
>>> issue.
>>> >> >> https://github.com/w3c/wcag21/issues/78
>>> >> >>
>>> >> >> Thanks.
>>> >> >>
>>> >> >> Kindest Regards,
>>> >> >> Laura
>>> >> >>
>>> >> >> --
>>> >> >> Laura L. Carlson
>>> >> >>
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Laura L. Carlson
>>> >> >
>>> >>
>>> >
>>>
>>>
>>> --
>>> Laura L. Carlson
>>>
>>
>>
>>
>> --
>> Jim Allan, Accessibility Coordinator
>> Texas School for the Blind and Visually Impaired
>> 1100 W. 45th St., Austin, Texas 78756
>> voice 512.206.9315 <(512)%20206-9315>    fax: 512.206.9264
>> <(512)%20206-9264>  http://www.tsbvi.edu/
>> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>>
>
>