Re: CSS vs personalization

I actually wasn't just thinking about WCAG 2.x but Silver primarily. This
was a long range comment. WCAG 2.1 is doing about as much as author's can
handle.

The next step is to look at the whole. Some clear examples are support for
color and font family which seem to be beyond the capability of the current
process.

Style sheets are a good start for the structure of user profiles. They are
syntax directed translations of documents that specify visual presentation.
They are more useful for development than accommodation, but don't
underestimate their power at present for accomodations.

Right now I have retargeted the output of my style generator to apply to
specific applications like survey user agent and epub readers. They work
quite well. Using CSS for accommodation is not most effective but it is a
quick way to see if a concept works before one writes an extension, and at
present they work for all of the text in EPUBs. Nothing else really does.

Wayne.



On Wed, Jan 3, 2018 at 2:24 PM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 03/01/2018 21:37, Wayne Dick wrote:
> [...]
>
> The issue is flexible visual format. Content needs enough semantic markup
>> to support visual transformations. User agents need to combine this
>> information with user profiles to create accessible visual interfaces for
>> sighted people with print disabilities. It is all very doable.
>>
>
> But if this requires both content authors AND user agent developers to
> make changes, it can't just be made a requirement for content authors in
> WCAG in the hope that user agents will then follow suit and actually
> support whatever is proposed here.
>
> It's, yet again, a chicken and egg problem...which can't be tackled by
> just mandating that authors need to do something speculatively in the hope
> that user agents will then act on it eventually.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>