Re: Important - we need consensus on what is sufficient support

The exact wording is Exception: Information does not need to be exposed when there is not a standardized technique of exposing it in the technology or the platform.


Does that meet it Gregg? 


All the best

Lisa Seeman

LinkedIn, Twitter





---- On Tue, 07 Feb 2017 17:54:13 +0200 lisa.seeman<lisa.seeman@zoho.com> wrote ---- 

Yup we added an exception if the there is no standardized  semantics support  for the platform , or something like that

All the best

Lisa Seeman

LinkedIn, Twitter





---- On Mon, 06 Feb 2017 22:31:28 +0200 Gregg C Vanderheiden<greggvan@umd.edu> wrote ---- 

Hi Lisa

1) We are also working on an open source browser extension that will do a number of things like line spacing, word spacing, contrast, font, size, etc.


2)  However they only work with HTML.    So any SC would have to be limited to HTML.    We tried to avoid all technology specific SC in WCAG  (we did have one restricted to markup languages).  
But if you phrase it as ‘for all technologies that ….”  but I’m not sure what goes after “that”  


hmmmm


g





 Gregg C Vanderheiden
greggvan@umd.edu



 
 
On Feb 6, 2017, at 3:16 PM, lisa.seeman <lisa.seeman@zoho.com> wrote:


Hi Folks

We urgently need consensus on what is sufficient support. This will help us know what we can put to pull request and what we need to rewrite (we may need to rewrite for other reasons but that is a diffrent issue)




For example for personalization (issues #6) we have
 1. an editors draft that is reasonably mature of the semantics. (at https://w3c.github.io/personalization-semantics/) for now let us assume it will be a working draft by the time WCAG 2.1 gets to CR.
2. An open source script for an implementation that any author can import into their page to enable personalization in any browser) It has some old semantics but it is being refracted now and that should be done by the end of february - see  https://github.com/ayelet-seeman/coga.personalisation
3. We have volunteers working on a free, open source browser extension for chrome so the user can apply personalization to any page using the semantics - that should be done by the end of march. It would have three  personalization skins for different types of users. 


We also have two industry partners who intend to implement it, but these solutions may be closed. We also have an EU project (SMART4MD) who are designing an APP for people living with dementia who will be compatible with it. (work started over a year ago)


What else exactly do we need for the group to feel we met the minimum bar.


Note that I am sure we all want a lot more implementations. But it will be easier to get implementations when we are in WCAG. What we need to know is what is the minimum. 

All the best

Lisa Seeman

LinkedIn, Twitter