No, the response you provided is just fine.
And that bank account situation fortifies why it will be a long time
coming before I willing place my finances there.
I asked about captcha because there was? a plug in for Firefox to help
gather such information.
Presently I am personally impacted by the hacking of fanfiction.net
The Captcha verification process they are seeming to incorporate will be a
barrier for writers and readers alike.
Unfortunately those involved in web access guidelines are far too silent
on this, much as they have been with keeping options for open source
development where web tools are concerned part of the inclusion
landscape.
Thanks again,
Kare
On Sun, 20 Dec 2020, Jonathan Cohn wrote:
I doubt there is any way for a browser to address Captcha, what they have been
working on is making Firefox respond to VoiceOver commands much like it does for
Safari. The way Firefox could be better than Safari is the places where Apple has
decided not to follow standards. If you review the MDN element and javascript
methods. For example the summary element
<https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary> is not
supported by Safari. You can see this in the supported matrix on the linked page.
Chrome and Firefox seem to support a lot more of these features.
Captcha is a process to push random puzzles to a user to solve. The assumption
being that these puzzles are too difficult for AI on a personal computer to
resolve. The protocols that allow one to authenticate with an Apple, Google, or
Facebook ID generally from my observation don't usually have Captcha as a block
item. The best solution would be a USB authentication but this still has all
sorts of issues.Did you see the hacking of bank accounts that IBM announced
this week was discovered? The criminals had 20 or so cell phone simulators and
were able to break into thousands of accounts. I did not read the details, but
I believe they were able to steal UUIDs from real cell phones and break
security. Wow, I'm getting really off topic here, sorry.
Best wishes,
Jonathan Cohn
On Dec 19, 2020, at 20:11, Karen Lewellen <klewel...@shellworld.net> wrote:
Hi Jonathan,
Thanks for providing this article. Its interesting because on another list
folks having paypal problems indicate Firefox is the only windows solution.
I hope talent on this list help them out. Specifically, how are they
addressing Captcha problems in this new Firefox?
best,
Karen
On Sat, 19 Dec 2020, Jonathan C. Cohn wrote:
I finally tracked down the article.
https://blog.mozilla.org/accessibility/voiceover-preview-for-macos-firefox/
VoiceOver Preview for macOS Firefox
Asa DotzlerDecember 15, 2020
For the better part of two decades, Mozilla has been building browsers that are
highly accessible for users with disabilities. While we???ve worked to ensure
that people with a wide range of disabilities can participate on the web, much
of our engineering effort has been focused on improvements for screen readers,
an assistive technology that allows blind users to engage with computers
through synthesized speech or a braille display.
On Windows, Firefox supports the two most popular screen readers, NVDA and
JAWS. On Linux, Firefox works with the Orca screen reader. On Android, Firefox
users have their pick of Google???s Talkback or Samsung???s Voice Assistant.
And on iOS, Firefox users can work with the built-in VoiceOver screen reader.
That brings us to macOS. About 15 years ago, Apple introduced a built-in screen
reader to macOS called VoiceOver. There were a couple of efforts to get Firefox
working with VoiceOver but it never reached a usable state. Mac was the one
major Firefox platform that simply wasn???t accessible to blind users.
At the beginning of 2020, we set out to fix that. Three members of the
accessibility engineering team, Morgan, Eitan, and Marco, put together a one
year plan to deliver solid VoiceOver screen reader support on macOS. In
February, the team started work in earnest. The first steps were to build tools
for reverse engineering the under-documented macOS and VoiceOver APIs. Over the
next ten versions of Firefox, the team would implement VO features, fix bugs,
and perform all kinds of testing to verify that features and fixes were working
as expected and to document the remaining gaps.
Now here we are at Firefox 85 Beta and we???re almost done. Firefox supports
all the most common VoiceOver features and with plenty of performance. Users
should be able to navigate through most web content and all of the browser???s
primary interface without problems. But we???re not quite done yet. The web is
huge and the browser interface is wide and deep so we need more people putting
Firefox and VoiceOver to the test and letting us know what???s working and not
working before we can call it done.
This is where you come in. If you???re a part time or full time screen reader
user on macOS, we???d love for you to update to Firefox 85 Beta and give it a
spin with VoiceOver. We expect you???ll find it pretty solid but there are a
few known issues, like VoiceOver search not working, and Firefox sub-menus and
tree views expanded/collapsed state not being announced. And there are no doubt
use cases we haven???t considered or tested so you may find additional bugs or
feature gaps and we???re counting on you to tell us all about those so we can
complete this work as soon as possible. Please report any bugs you find to
Bugzilla and if you???d like to chat about what???s working and not working for
you, you can find us on Matrix. We look forward to hearing from you.
What???s next? We???re going to watch for your feedback and address any
significant issues that you surface. With your help, in a release or two
we???ll be able to call VoiceOver support complete and we can move on to other
features and fixes from our roadmap.
Sent from my iPhone
--
The following information is important for all members of the Mac Visionaries
list.
If you have any questions or concerns about the running of this list, or if you
feel that a member's post is inappropriate, please contact the owners or
moderators directly rather than posting on the list itself.
Your Mac Visionaries list moderator is Mark Taylor. You can reach mark at:
mk...@ucla.edu and your owner is Cara Quinn - you can reach Cara at
caraqu...@caraquinn.com
The archives for this list can be searched at:
http://www.mail-archive.com/macvisionaries@googlegroups.com/
---
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to macvisionaries+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/macvisionaries/33D9AC5A-2063-473B-88E2-0473A14D434A%40gmail.com.
--
The following information is important for all members of the Mac Visionaries
list.
If you have any questions or concerns about the running of this list, or if you
feel that a member's post is inappropriate, please contact the owners or
moderators directly rather than posting on the list itself.
Your Mac Visionaries list moderator is Mark Taylor. You can reach mark at:
mk...@ucla.edu and your owner is Cara Quinn - you can reach Cara at
caraqu...@caraquinn.com
The archives for this list can be searched at:
http://www.mail-archive.com/macvisionaries@googlegroups.com/
---
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to macvisionaries+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/macvisionaries/87D68AF4-EA7B-4EAA-8978-C04FD1697DAC%40gmail.com.
