Re: Subgroups proposal for support personlization and important request from coga

​Hi Alastair,

>I think a wider-scope SC at AAA using open-taxonomy could be useful with a
service such as this demo uses:

https://www.widgit.com/support/insite/index.htm



Sitting

at

home

and

wondering

how


to

apply

the

Home

key
The problem here (that I see) will be that sometimes a word will have more
than one context, and so I would think that a set of 'navigation' symbols
would perhaps need to be different than 'conversational' symbols. But I'd
want to verify that with other folks from the COGA TF.

JF

​


On Mon, Jul 17, 2017 at 5:17 PM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> I’m in general agreement with John, I think there’s an AA level SC to be
> had here, perhaps with a wider scoped SC at AAA.
>
>
>
> Particularly this bit:
>
> > I will continue to assert that it is because without a fixed taxonomy
> you get contextual information, but presented to the end user in prose,
> which is hard to then transform (personalize).
>
>
>
> If the pre-defined parts of coga-personalisation are cherry-picked, that’s
> good source material at AA.
>
>
>
> We need to start with the most widely applicable (across sites) and most
> important (to users) pre-defined terms, and (very importantly) get some
> sort of user-agent software going that makes use of it (e.g. a browser
> extension).
>
>
>
> I think a wider-scope SC at AAA using open-taxonomy could be useful with a
> service such as this demo uses:
>
> https://www.widgit.com/support/insite/index.htm
>
>
>
> However, as a starting point (and at AA) I think the concrete terms are
> most obvious and most likely to get traction. In W3C a context (essentially
> the web-ecosystem), starting with small concrete steps is always more
> effective than moon-shots.
>
>
>
> Cheers,
>
>
>
> -Alastair
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion