You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by sergioneves on 2013-05-15 10:09
There is a new way of providing CAPTCHAs, which is based on the
introduction of randomly distributed text nodes on the DOM of web pages, and employment of CSS to arrange these nodes (characters)
on the screen.
One known example of the implementation of this type of CAPTCHAs is on Packt Publishing book seller web site, where the following link leads to a particular example: http://www.packtpub.com/support/10503
If you analyse the CAPTCHA, you'll see that the order of characters announced by any screen reader (in particular NVDA) using the virtual cursor is not equal to the order of characters that really appears on the screen. I didn'tt analyse it thoroughly, but
I think the order is not coincident due to the CSS applied to text nodes.
This is one case where it's important to access and explore the web page with another ways other than the virtual cursor and probably to use low-level graphics functionality to inspect web page content; otherwise, I don't know any other way to discover the order of characters on these CAPTCHAs.
I think it's a long-term problem that is worth researching.
The text was updated successfully, but these errors were encountered:
Comment 1 by briang1 on 2013-05-21 07:48
Pardon my ignorance, but presumably then these are actually readable chars which are ordered by cascading style sheets for the visuual image, but not for us. I do wish these people would use special questions rather than these convoluted ways to prove humanity! Could what you propose be done though?
Hi, I’m wondering if OCR might come in handy or some other service. Thanks.
From: bhavyashah [mailto:notifications@github.com]
Sent: Tuesday, August 15, 2017 9:11 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [nvaccess/nvda] Research one way to discover captchas based on characters introduced in DOM (#3238)
A captcha solving service as part of NVDA and related topics have been discussed in #5979 <#5979> and #3305 <#3305> .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#3238 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkAeEtx9-DuBNG41NVbMiIIvJyDWWks5sYmvagaJpZM4O4ZmF> .
Reported by sergioneves on 2013-05-15 10:09
There is a new way of providing CAPTCHAs, which is based on the
introduction of randomly distributed text nodes on the DOM of web pages, and employment of CSS to arrange these nodes (characters)
on the screen.
One known example of the implementation of this type of CAPTCHAs is on Packt Publishing book seller web site, where the following link leads to a particular example:
http://www.packtpub.com/support/10503
If you analyse the CAPTCHA, you'll see that the order of characters announced by any screen reader (in particular NVDA) using the virtual cursor is not equal to the order of characters that really appears on the screen. I didn'tt analyse it thoroughly, but
I think the order is not coincident due to the CSS applied to text nodes.
This is one case where it's important to access and explore the web page with another ways other than the virtual cursor and probably to use low-level graphics functionality to inspect web page content; otherwise, I don't know any other way to discover the order of characters on these CAPTCHAs.
I think it's a long-term problem that is worth researching.
The text was updated successfully, but these errors were encountered: