Bug 465 - captcha is hard to read
Summary: captcha is hard to read
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: identity.mageia.org (show other bugs)
Version: trunk
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Atelier Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-20 12:07 CET by Michael Scherer
Modified: 2023-09-23 18:18 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Michael Scherer 2011-03-20 12:07:16 CET
When a user is asked to subscribe to identity, he must pass a test based on a captcha. While the test is not as unreadable as some others, it can be quite hard to read for someone who has vision problems, and sometime ( for example, when a vertical bar happen to be at the right spot near a 3 or a 8 ) difficult to pass even for a normal sighted human.

What about replacing this with a simple mathematic question, as seen on some blog ( statusnet one, for example ) ?

( there is no plugin for this, unfortunately )

Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2011-10-07 22:14:43 CEST
Any news on this bug?

CC: (none) => marja11

Comment 2 Marja Van Waes 2012-01-09 21:23:09 CET
(In reply to comment #0)

> 
> What about replacing this with a simple mathematic question, as seen on some
> blog ( statusnet one, for example ) ?
> 

I can't find such a question on http://status.net/blog, or is it a different site?
Comment 3 Wolfgang Bornath 2012-01-10 07:53:13 CET
http://status.net/user/register?destination=open-source is an example

CC: (none) => molch.b

Rémi Verschelde 2015-09-10 16:10:45 CEST

Summary: captcha is annoying => captcha is hard to read

Comment 4 Marja Van Waes 2023-09-23 18:18:22 CEST
The captcha was much better readable earlier today, than some years ago. I assume it is good enough now.

Please reopen this report if it is still to hard to read for some.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.