From: "Aalekh Nigam"<aalekh1993(a)rediffmail.com>
Sent: Mon, 03 Mar 2014 20:35:14
To: "design(a)lists.wikimedia.org"<design(a)lists.wikimedia.org>
Subject: Fw: Captcha Idea Proposal for GSOC 2014
From: "Aalekh Nigam"<aalekh1993(a)rediffmail.com>
Sent: Sun, 02 Mar 2014 15:37:42
To: "wikitech-l(a)lists.wikimedia.org"<wikitech-l(a)lists.wikimedia.org>
Cc: "mediawiki-i18n(a)lists.wikimedia.org"<mediawiki-i18n(a)lists.wikimedia.org>
Subject: Captcha Idea Proposal for GSOC 2014
Hello,
I have been looking for Multilingual and effective captcha as a project for GSOC 2014 .....and made out some points and wire-frames to show my approach regarding this ,shown below:
1)Captcha on the basis of selection of particular object:In this type of captcha the questions will be shown as shown here: https://commons.wikimedia.org/wiki/File:Proposal6correction.png ;other possible questions can be:"Select the images in which man is wearing sunglasses",now problem i encountered while making such captcha request is that a bot could easily use Google images or third eye to find the look for images of man wearing sunglasses from the Wikimedia Commons .....so to encounter this problem we can use a random numbering over the images and then ask user to to select the images in order of numbering for example the only answer to the sample question i provided above is :https://commons.wikimedia.org/wiki/File:Proposal7correction.png ;one of the wrong answer to the given question is:https://commons.wikimedia.org/wiki/File:Proposal8correction.png ; because it is not arranged in correct order which is 1,4,12 (in increasing numeric order).....ps:i did forgot to specify "increasing" numeric order in the question i provided but the plan is to provide the question as "Select human among the given photograph's and select it in increasing numeric order?".
Providing increasing numeric order might make bot guess wrong answer 90% of time,which is quite comparable to the current captcha system that uses OCR as provided in the given algorithm: http://www.gizmag.com/captcha-beating-ai/29559/ .
2)Ask User to click on the same image as provided:The question for this type of captcha looks like this:https://commons.wikimedia.org/wiki/File:Proposal5correction.png we can ask user to click on the options showing equivalent image to that provided in the question.For the question provided the answer is :https://commons.wikimedia.org/wiki/File:Proposal9correction.png .Ps:we ca use more than four options probably eight options since it would be harder of bot to make a guess.
3)For blind and visually impaired users:We can use and audio captcha system which ask user to select the number as it is asked in the audio .For example the visual equivalent of the audio asked by the user will be : https://commons.wikimedia.org/wiki/File:Proposal11correction.png .Now when audio asked user to select number "0" our user will use arrow key to move across different blocks like a slide show....with different voice speaking out the options and pressing enter will select the word spoken....hence verifying that the user is human.....although the above shown image is visual equivalent the actual image visible will be: https://commons.wikimedia.org/wiki/File%3AProposal4correction.png ;....to make the captcha reload we can user to by pressing key "r" which will be instructed in the audio while the captcha starts playing.
Please give your response to idea provided and also the idea is listed here:https://www.mediawiki.org/wiki/Talk:CAPTCHA
Thank You
Aalekh Nigam
aalekhN
https://www.mediawiki.org/wiki/User:AalekhN
--
Get your own FREE website, FREE domain & FREE mobile app with Company email. Know More >
Get your own FREE website, FREE domain & FREE mobile app with Company email. Know More >
From: "Aalekh Nigam"<aalekh1993(a)rediffmail.com>
Sent: Sun, 02 Mar 2014 15:37:42
To: "wikitech-l(a)lists.wikimedia.org"<wikitech-l(a)lists.wikimedia.org>
Cc: "mediawiki-i18n(a)lists.wikimedia.org"<mediawiki-i18n(a)lists.wikimedia.org>
Subject: Captcha Idea Proposal for GSOC 2014
Hello,
I have been looking for Multilingual and effective captcha as a project for GSOC 2014 .....and made out some points and wire-frames to show my approach regarding this ,shown below:
1)Captcha on the basis of selection of particular object:In this type of captcha the questions will be shown as shown here: https://commons.wikimedia.org/wiki/File:Proposal6correction.png ;other possible questions can be:"Select the images in which man is wearing sunglasses",now problem i encountered while making such captcha request is that a bot could easily use Google images or third eye to find the look for images of man wearing sunglasses from the Wikimedia Commons .....so to encounter this problem we can use a random numbering over the images and then ask user to to select the images in order of numbering for example the only answer to the sample question i provided above is :https://commons.wikimedia.org/wiki/File:Proposal7correction.png ;one of the wrong answer to the given question is:https://commons.wikimedia.org/wiki/File:Proposal8correction.png ; because it is not arranged in correct order which is 1,4,12 (in increasing numeric order).....ps:i did forgot to specify "increasing" numeric order in the question i provided but the plan is to provide the question as "Select human among the given photograph's and select it in increasing numeric order?".
Providing increasing numeric order might make bot guess wrong answer 90% of time,which is quite comparable to the current captcha system that uses OCR as provided in the given algorithm: http://www.gizmag.com/captcha-beating-ai/29559/ .
2)Ask User to click on the same image as provided:The question for this type of captcha looks like this:https://commons.wikimedia.org/wiki/File:Proposal5correction.png we can ask user to click on the options showing equivalent image to that provided in the question.For the question provided the answer is :https://commons.wikimedia.org/wiki/File:Proposal9correction.png .Ps:we ca use more than four options probably eight options since it would be harder of bot to make a guess.
3)For blind and visually impaired users:We can use and audio captcha system which ask user to select the number as it is asked in the audio .For example the visual equivalent of the audio asked by the user will be : https://commons.wikimedia.org/wiki/File:Proposal11correction.png .Now when audio asked user to select number "0" our user will use arrow key to move across different blocks like a slide show....with different voice speaking out the options and pressing enter will select the word spoken....hence verifying that the user is human.....although the above shown image is visual equivalent the actual image visible will be: https://commons.wikimedia.org/wiki/File%3AProposal4correction.png ;....to make the captcha reload we can user to by pressing key "r" which will be instructed in the audio while the captcha starts playing.
Please give your response to idea provided and also the idea is listed here:https://www.mediawiki.org/wiki/Talk:CAPTCHA
Thank You
Aalekh Nigam
aalekhN
https://www.mediawiki.org/wiki/User:AalekhN
--
Get your own FREE website, FREE domain & FREE mobile app with Company email. Know More >
I'm adding the design list. I talked about this recently with a couple
of the designers.
Matt Flaschen
On 02/28/2014 12:07 PM, Mansi Gokhale wrote:
> hello,
>
> These are some approaches i can think of instead of a text based captcha.
>
> The image idea where users are asked to spot the odd one out like
> demonstrated or find all the similar images like mentioned in
> here<https://www.mediawiki.org/wiki/CAPTCHA>
> .
>
> Also a picture with a part chipped in could be shown and chipped pictures
> could be given as options
>
> like find the missing part from a jigsaw puzzle.
>
> The image which would be shown is http://imgur.com/uefeb08
>
> http://imgur.com/KEJqCg3 is the picture which would be the correct option.
>
> The other options could be rotated versions of this , which would not be so
> easy for the bot to match. (unless it somehow worked some digital
> processing algorithm and matched the color gradients or something like
> that).
>
> This is a good option for people who do not know english or are illiterate
> and maybe would not understand questions like : is this a bird , plane ,
> superman? after being shown a picture.
>
> Tell me what you think
>
> (Sorry to upload those images on imgur. i dont know how to put them on the
> wiki .Hope that is ok)
>
>
> have posted this on the CAPTCHA
> page<https://www.mediawiki.org/wiki/Talk:CAPTCHA>also
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
In the old days (2011), the WMF had design guidelines that discussed
accessibility issues such as appropriate font sizes, use of colors, and
text contrast. These guidelines were later replaced with the Agora
guidelines (https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design)
which specify only that "We must enable access for users with impairments."
Accessibility is central to our mission as an organization and very
important to our community. In fact the en.wiki community has enacted their
own comprehensive accessibility guidelines for content:
https://en.wikipedia.org/wiki/Wikipedia:Accessibilityhttps://en.wikipedia.org/wiki/Wikipedia:Accessibility_dos_and_don'ts
Mediawiki developers also have a set of published accessibility guidelines:
https://www.mediawiki.org/wiki/Accessibility_guide_for_developers
The issue of accessibility in MediaWiki UX design has been raised numerous
times in the recent past, most commonly in regard to font sizes and colors.
I'm personally aware of it coming up at least 5 times in the past year
(Typography Refresh, Flow, Echo, Mobile, NavPopups). Rather than rehashing
the same discussions each time, I would encourage the design team to come
up with a new set of accessibility guidelines that everyone can refer to
and agree on. I would encourage stealing ideas from the en.wiki guidelines
and the WCAG guidelines (http://www.w3.org/TR/UNDERSTANDING-WCAG20/). I
would also suggest that the design team invest in a pair of scratched-up
coke-bottle glasses that each design mock-up can be tested with :)
Ryan Kaldari
> -
> > >
> > > What's the Publish/Discuss/Translate/etc blocks for? They look like
> > > navigation but don't seem to go anywhere or correspond to anything.
> >
> > They attempt to summarize the best features that MediaWiki can offer.
> > Indeed, there are no detailed product descriptions to link to, but this
> > is because we don't have them. I would say this is better than nothing.
> > Currently you either know what MediaWiki plus selected extensions can
> > offer, or you guess it by becoming a Wikipedia power user, or you need
> > to connect many pages in mediawiki.org.
>
When i read that page it makes it seem like these features are available
out of the box, which is kind of misleading. In particular claiming we have
wysiwyg editing without mentioning visual editor is extremely difficult to
install doesnt seem like a good idea.
Personally i thought the translate box meant that the mediawiki interface
is translated into many languages (something we can certainly brag about).
Overall i like the idea of the redesign that you have in the uploaded file.
> > > Bugzilla should have a prominent link. Sysadmins and other users who
> > > found bugs are not necessarily looking to 'get involved'. They found
> > > bugs and want to report them or find fixes. They're looking for a bug
> > > thing. Where is that?
>
+1 bugzilla is very important for downstream users who have bugs.
> > "Support" links to https://www.mediawiki.org/wiki/Project:Support_desk ,
> > which is where many MediaWiki sysadmins go when they have/find problems.
> > Bugzilla is not visibly featured there, and it probably should be.
Getting support is different from filing bugs.
-bawolff
<quote name="Federico Leva (Nemo)" date="2014-02-15" time="22:52:31 +0100">
> And surely, before WMF/"MediaWiki" tell the world that no free fonts
> of good quality exist, there will be some document detailing exactly
> why and based on what arguments/data/research the numerous free
> alternatives were all rejected? Free fonts developers are an
> invaluable resource for serving Wikimedia projects' content in all
> languages, we shouldn't carelessly slap them in their face.
I just skimmed the entire thread again, and yes, this has been requested
a few times but no one from the WMF Design team has responded with that
analysis (or if would respond with an analysis). The first time it was
requested the person was told to ask the Design list, then the next
message CC'd the design list, but no response on that point.
I don't see much on https://www.mediawiki.org/wiki/Typography_refresh
nor it's talk page. Nor
https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Typography
cc'ing the Design list :)
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
This is really a UX question, not design per se.
https://gerrit.wikimedia.org/r/#/c/104926/ (an under-review change) adds
a warning if you choose a username that needs to be
reformatted/canonicalized. For example, "my username" is changed to "My
username".
It displays the warning, puts the new username ("My username") in the
box, then you have to retype your password (twice), then press enter to
confirm.
The main potential benefit, as I see it, is that if you don't like "My
username" (the reformatted version), you can choose a different username
entirely.
User experience feedback would be welcome; you can post on the change or
here.
Matt Flaschen
