Re: Error Handling Best Practice?

An old school fix is to insert the error message inside the label tag for
the label association with the input with the error

David & Kirsten MacDonald




On Tue, Dec 22, 2015 at 12:43 PM, David MacDonald <david100@sympatico.ca>
wrote:

> Android/talkback is way behind on for accessibility. It's like Apple was
> in 2007.
>
> It is not currently taken seriously by the blind community from what I can
> see. Google needs to figure this out... When you say "due to the number of
> users on Android..." I wouldn't say there are many blind users, and those
> who do, use Android  as a second device ...
>
> Working people and serious students who are blind currently use iPhone.
> There is no other option, really...
>
> I wish this wasn't the case but it is, I think.
>
> David & Kirsten MacDonald
>
>
>
>
> On Tue, Dec 22, 2015 at 11:45 AM, Patrick H. Lauke <redux@splintered.co.uk
> > wrote:
>
>> On 22/12/2015 16:34, Alistair Garrison wrote:
>>
>>> Thanks for the suggestion. It's really the where and how to present the
>>> error message that I suppose I'm searching for - be it:
>>>
>>
>> So your dismissal of aria-describedby earlier in the thread is a red
>> herring then, as that attribute can be used to tie the error message
>> programmatically to the form control - it's orthogonal to where/how to
>> present the message (as it's not a hidden attribute or anything, like
>> aria-label)...
>>
>>
>> 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
>>
>>
>

Received on Tuesday, 22 December 2015 18:18:12 UTC