- From: <josh@interaccess.ie>
- Date: Wed, 02 Nov 2016 11:20:52 +0000
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, w3c-wai-gl@w3.org
------ Original Message ------ From: "Patrick H. Lauke" <redux@splintered.co.uk> To: "josh@interaccess.ie" <josh@interaccess.ie>; w3c-wai-gl@w3.org Sent: 02/11/2016 11:14:17 Subject: Re: Colour Luminosity/Contrast for form inputs/controls/components [...] >>Going in the right direction - I like calling out 'states' but aren't >>there also the need to have the components themselves perceivable? Say >>scrollbars for example that don't change state? > >That would be the default state of the element, no? Roger. >(and scrollbars do often have an active state when the user grabs the >scroller, or when the focus is somehow set on them, etc) > Yes - some dont change (custom builds) at all though - so having a clear default is definitely needed. Thanks Josh > > >>In terms of states we could define ratios for active/inactive for >>sure. >> >>Thanks >> >>Josh >> > > >-- 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
Received on Wednesday, 2 November 2016 11:18:05 UTC