WEBSTANDARDS Archives

UofMN Web Standards

WEBSTANDARDS@LISTS.UMN.EDU

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
UofMN CSS Web Development <[log in to unmask]>
Date:
Mon, 2 Nov 2009 12:17:48 -0600
Reply-To:
UofMN CSS Web Development <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset=ISO-8859-1; format=flowed
From:
Peter Wiringa <[log in to unmask]>
Parts/Attachments:
text/plain (37 lines)
Here are some approaches that should help to reduce form spam 
without introducing accessibility problems.

http://webaim.org/blog/spam_free_accessible_forms/

Also, if it's an internal-only form that doesn't purport to take in 
confidential responses, you could always add cookieauth to it, so 
users are forced to login. Yes, it *could* be an extra step for your 
users, but it's the simplest approach I know of, if you don't 
already have a set of form handlers you can use.

Jake LaSota wrote:
> Hi all,
> 
> I've got a form that's receiving a bunch of ugly automated submissions. 
> Does anyone know of a good captcha code/plug-in?
> 
> I've found a few, but I'm sure there's something better floating around 
> out there.
> 
> Perhaps there's a better technique than using a captcha to stop these 
> submissions?
> 
> Thanks,
> Jake

-- 
Peter Wiringa
Electronic Communications
University Relations
University of Minnesota
(612) 625-3252
[log in to unmask]

"I gotta hold on to my angst. I preserve it because I need it. It 
keeps me sharp, on the edge, where I gotta be." - V. Hanna

ATOM RSS1 RSS2