W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2015

Re: Error Handling Best Practice?

From: Alistair Garrison <alistair.j.garrison@gmail.com>
Date: Tue, 22 Dec 2015 17:24:26 +0000
Cc: Michiel Bijl <michiel@agosto.nl>, David MacDonald <david100@sympatico.ca>, "Balusani, Shirisha" <sirib@uillinois.edu>, "ajaysharma89003@gmail.com" <ajaysharma89003@gmail.com>, Jonathan Avila <jon.avila@ssbbartgroup.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-Id: <E56689DA-462D-4C3E-AA12-34B3B822F9DB@gmail.com>
To: "Patrick H. Lauke" <redux@splintered.co.uk>
I've just found this.  http://ux.stackexchange.com/questions/26173/what-is-best-practice-for-designing-form-error-messages Which might hold what I'm looking for.

There's also http://www.w3.org/WAI/tutorials/forms/notifications/, it's just not focused on best methods for small screens.

All the best 


On 22 Dec 2015, at 17:00, Alistair Garrison wrote:

> I cannot use aria.  The range of devices popularly supported when making mobile apps rules it out.  No red herrings - I've been very clear from my first message asking for "old school" success story solutions.
> Alistair
> On 22 Dec 2015, at 16:45, Patrick H. Lauke 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 17:24:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 December 2015 17:24:59 UTC