Blind Main
The main community at rblind.com, for discussion of all things blindness.
You can find the rules for this community, and all other communities we run, here: https://ourblind.com/comunity-guidelines/ Lemmy specifics: By participating on the rblind.com Lemmy server, you are able to participate on other communities not run, controlled, or hosted by us. When doing so, you are expected to abide by all of the rules of those communities, in edition to also following the rules linked above. Should the rules of another community conflict with our rules, so long as you are participating from the rblind.com website, our rules take priority. Should we receive complaints from other instances or communities that you are repeatedly, knowingly, and maliciously breaking there rules, we may take moderator action against you, even if your posts comply with all of the rblind.com rules linked above.
view the rest of the comments
Orca is not installed by default on Debian. But I would be interested in seeing what the built-in tools do. In Firefox I hit F12 » Elements and saw an “accessibility” tab. From there I expanded a quite long tree of nested elements and got down to the hyperlinked image. Then I looked at the console frame with the link highlighted. There were over 30 messages with 6 errors. It’s very noisy. None of the errors or warnings indicate that the object would not be readable by a screen reader. It’s stuff like net::ERR_BLOCKED_BY_CLIENT and JSON parsing syntax errors.
EDIT: this error looks interesting:
city:60 GET https://cdn.equalweb.com/core/4.5.6/accessibility.js net::ERR_BLOCKED_BY_CLIENT
If I understand correctly, ~~Firefox is trying to run
accessibility.js
~~ but becausecdn.equalweb.com
is a #Cloudflare site, I am blocked (Cloudflare is Tor-hostile). There’s a bit of irony here that a domain name “equalweb” leads to a discriminatory web server. I’m guessing this blocks Tor-using Firefox users from checking the accessibility of a webpage using FF’s built-in features.EDIT 2: it turns out accessibility.js is loaded by the site, not FF. So I’m not sure how to use the built-in functionality to answer the question.
I wouldn’t expect a JS file dedicated to accessibility to be necessary, but it could indicate a bad retrofit. Or not, who knows.
If you want to get deeper into testing with Firefox, you can check out this guide. Either way, I’m kinda curious about looking at the website myself, if you wouldn’t mind sharing a link.
I appreciate the link, though the steps in that article are incompatible with my Firefox installation. Perhaps these are new features. When I right-click on an object, there is no “accessibility” option.