I'm looking for benchmarks.
For @mucConf we want to provide accessibility information online.
Please send me links to events/conferences that did a good job communicating accessibility information!
>>
I use Markdown a lot & it works well for me. Having recently moved to Wordpress, I find the Gutenberg-type editors very nice for fancy effects, but not for just writing.
Unsurprisingly, I'm facing 24 WP plugins that promise Markdown heaven, and I'd rather not try them all.
Anyone out there would like to share experiences in this matter, please do. @wordpress perhaps?
@RolfBly@wordpress Yeah, it would be easier having #WordPress adding an option to upload #MarkDown files directly with an "upload file" button; many plugins claim to do that but they're not so accessible and #a11y matters. JetPack had such plugin once, but I'd like to less rely on JetPack even if it's still important for followers I have there.
@talksina Come to think about it, named links in markdown are probably best to make things orderly. If you know what I mean (I can explain if you want).
Something else: How do you pronounce #a11y , or what is it an abbreviation of?
I gather the context is Alt-text, which I do write wherever possible. I know hashtag alt 4 me and hashtag alt 4 you, but this one is new to me.
At least 3 things missing from UC's Global Accessibility Awareness Day event:
The idea that there's any accessibility issues beyond the type digital technology tools could potentially help with
and
Actual diversely disabled UC community leading the event.
Statement up front as to what accessible options are available for this event.
Keeping the emphasis on digital tools allows abled people to continue their hegemony by simply training to be "experts" on accessibility, keeping jobs & control in abled hands. It allows UC to keep refusing to hire human captioners, human notetakers, as well as keep NOT addressing making things as accessible as possible as the default at UC.
I always use the advanced Web interface for Mastodon to do my "boosting thang" efficiently.
Normally I don't comment on the software. But a sudden change to the Notifications tab in the v4.3.0-nightly.2024-03-18 build is really pissing me off.
I can now only choose between viewing "All" and "Mentions." Gone is the ability to easily filter by notification type in the column header.
WTF?!? This is a hostile UI simplification. Please revert this. Thank you.
I know that the mastodon team are suggesting you turn on #hCaptcha for signups to your instance, to combat the spam wave provided by a rudimentary script that doesn't have the smarts to get around it.
I vaguely remember, however, that people have previously raised #accessibility concerns about it. Does anyone have any experience with the accessibility or lack there of, of signing up to instances that use this feature?
If it is indeed inaccessible, I don't consider this to be a reasonable solution.
@james I tried just yesterday to register an account on a site that uses HCaptcha. I use a screen reader on Windows and Firefox as my browser. It was completely unusable. It asked me for an 'accessibility cookie' that requires to give them a 'real email' address, refusing to accept my Firefox Relay alias. After caving in and giving them an address that i had given them a few years back and getting my accessibility cookie, the bloody captcha refused to recognise the cookie. Checking their support pages and tinkering with Firefox settings, none of which worked, I gave up and had to wait for a housemate to arrive after her work to help me solve the captcha.
There is an ongoing spam attack on the fediverse for the last couple of days. It's more widespread than before, as attackers are targeting smaller servers to create accounts. Before, usually only mastodon.social was targeted and our team could take care of it. For server administrators out there: If you don't need open registrations, switch over to approval mode. If you do, blocking disposable e-mail providers is a massive stopgap to the problem. Mastodon also supports hCaptcha.
@james we recently were in touch with some #a11y consultants and hCaptcha was one of the points raised.
According to them hCaptcha's accessible method for confirming human use is to have them enter an email to which a magic link is sent, and a cookie is sent (like a magic login link). That's not so good from a data privacy perspective.
Did you find a way to address the issues presented while keeping #IconFonts?
Basically:
When our friends with #Dyslexia overrides your fonts, font icons turn into black boxes since the font they're using doesn't have support for those Unicode code blocks.
When screenreaders, or voice assistance, reads a site with icon fonts, they read the icon fonts really weird.
For No.2, a site with properly marked aria labels, or marked as hidden for assistive tech, is the solution I can think of.
However, for No.1, I can't think of a way since once the browser forces the user font, all fonts on the site will rely on the user's custom font.
The only other way I can think of is to provide an option to switch the site's font right from the website, so they don't have to override the site's font.
For me, the most accommodating environment is one where I can get things done "eventually" - not on a timer.
This makes finding tech work hard - the output is often sold well in advance, with a promise to deliver that logically, it feels is futile - even if you did everything in your power, weather and worse happens and can't always be accounted for.
It's even worse when folks assume my capability is the same as theirs - another thing that feels like an obvious error, from my point of view.
I recommend not publishing on Medium, for starters.
Full disclosure, I opened the article to see if its 2024 #accessibility recommendations were the same as the 2004 or 2014 recommendations (headings, alt text, contrast, etc.) but now I cannot be sure what new insights it contains. #a11y
I want to make a collapsable tree structure of categories containing sections and sections containing sections or items.
Can I use a list of many disclosure elements that contain lists of disclosure elements?
These kinds of little details and putting love into every corner of the experience are what makes working on @elementary OS so rewarding for me. Also, welcome back to Marius!
This branch will complete our project to make settings that were previously hidden in a separate #a11y section more broadly available. Some of the explanation text was previously not great so hopefully this is much clearer! https://github.com/elementary/switchboard-plug-keyboard/pull/446
It’s #DisabilityPrideMonth and through sheer coincidence we’re releasing some cool new #a11y features this month and have more currently in preview for next month. Special shoutouts to @lenemter here for working on color assistance filters, fixing the screen reader shortcut on the greeter, and more. Can’t wait to write up everything we’ve been doing to make @elementary OS more inclusive and accessible!