Comments for Web Axehttp://www.webaxe.org
blog and podcast on web accessibilityWed, 29 Jul 2015 05:13:22 +0000hourly1http://wordpress.org/?v=4.2.3Comment on Proper Use of Buttons and Links by Proper Use of Buttons and Links | accessibility newshttp://www.webaxe.org/proper-use-buttons-links/#comment-106150
Wed, 29 Jul 2015 05:13:22 +0000http://www.webaxe.org/?p=1597#comment-106150[…] (curated by Lifekludger from Proper Use of Buttons and Links) Complete article at source: http://www.webaxe.org/proper-use-buttons-links/ […]
]]>Comment on Google’s No Captcha Shows Some Progress by ReCAPTCHA Reboot | Adrian Rosellihttp://www.webaxe.org/google-no-captcha-some-progress/#comment-105598
Mon, 20 Jul 2015 19:01:07 +0000http://www.webaxe.org/?p=1738#comment-105598[…] at Web Axe, Dennis Lembree has shared his thoughts in the post Google’s No Captcha Shows Some Progress. He notes that No CAPTCHA fails with JAWS / Internet Explorer, requires JavaScript, and […]
]]>Comment on Google’s No Captcha Shows Some Progress by Dennishttp://www.webaxe.org/google-no-captcha-some-progress/#comment-105386
Thu, 16 Jul 2015 02:37:01 +0000http://www.webaxe.org/?p=1738#comment-105386Thanks for the update, Terry! Sorry it took over a week to approve.
]]>Comment on Google’s No Captcha Shows Some Progress by Terrill Thompsonhttp://www.webaxe.org/google-no-captcha-some-progress/#comment-104953
Mon, 06 Jul 2015 18:58:51 +0000http://www.webaxe.org/?p=1738#comment-104953It’s been a while since you reported that Google’s reCAPTCHA fails with JAWS and IE (and commenters agreed). Testing just now with JAWS 16.0.4350 and IE11, it seems to work well. Navigating through a form in forms mode, I land on the checkbox and JAWS announces it as “I am not a robot, checkbox not checked” and after checking the box, JAWS announces it as checked. There’s also a visually hidden ARIA live region that results in JAWS announcing “You are verified”, and that text can easily be found again later beneath a visually hidden H1 heading that says “reCaptcha Status”. Seems to work really well from my perspective!
]]>Comment on Vestibular Issues in Parallax Design by Dennishttp://www.webaxe.org/vestibular-issues-parallax-design/#comment-104843
Fri, 03 Jul 2015 18:09:24 +0000http://www.webaxe.org/?p=1632#comment-104843Why Apple’s next operating systems are already making users sick: http://www.alphr.com/apple/1001057/why-apple-s-next-operating-systems-are-already-making-users-sick
]]>Comment on Detecting Screen Readers – No by Dennishttp://www.webaxe.org/detecting-screen-readers-no/#comment-104333
Mon, 22 Jun 2015 23:00:48 +0000http://www.webaxe.org/?p=1442#comment-104333In this regard, creating conditionals is not much different than a separate code base; still adds code complexity and creates a second /separate experience. It’s ideal to have the same experience for all users (well, as much as possible).

And again, there are also privacy issues with detecting a screen reader user.

About the point about CSS, all users including screen reader users do have a need for CSS. For example, in today’s web dev, often times content is hidden with CSS (usually display:none) which needs to be hidden for all users, otherwise it makes no sense and is unusable.

I recommend that sticking with best practices for front-end development (especially light, semantic markup) should be the priority for website content and speed.