microblog.at ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Dies ist die private Mastodon Instanz von Robert Lender

Verwaltet von:

Serverstatistik:

1
aktive Profile

#accessibility

19 Beiträge18 Beteiligte3 Beiträge heute

seeing discussions around how "members of the public (tm)" are prevented from taking part in standards development, because tools like github (where discussion/development happens) may not be familiar to them. while i understand the sentiment, i'd hazard a guess that these members of the public won't understand how the sausage is made, and will be frustrated by the consensus-driven standards development ... it's not just a "let me tell you about MY lived experience" thing #a11y #accessibility

Watching a video on the new third-party keyboard support for #KompleteKontrol. I can already say this is not going to be great for most fully #blind #musicians mostly because actually browsing through your entire KK library is not supported. You can browse through presets once an instrument is loaded, you can usually modify plugin parameters although that isn't always the case for some Kontakt instruments apparently, you CAN do a search and move through the seaerch resuls though, so provided you can do accessibly do a search that hacks around that issue. The main thing I'm not sure about is, amusingly, if you can toggle #accessibility support. I'm leaning towards probably not, so you'd need Bobby from down the block to hook up their KK keyboard and turn it on for you but after that I do think it may actually talk if you use a 3rd-party controller :)

It's fascinating how even within the #accessibility community, some people feel the need to bet on blatant apologism and chastise people for taking a contrary opinion to dev teams, responding to said opinions almost like they were personal attacks. The answer to user frustration is calling users stupid for not knowing how things work in dev teams and how dare they have unrealistic expectations born from being ignored for decades and finally hoping for a change.
Personally I think there's a place for both extremes, but watching people stuck in their own beliefs get mad at other people stuck in their own beliefs where this is concerned always seems ... interesting.

Was laid off a month ago from my #accessibility lead position. I've only gotten one callback in that month so far. Trying #getfedihired (#fedihire ?) - been working fulltime in accessibility since 2016, experienced with cross-team collaborations, & had input on design systems and component libraries in addition. #UX is also something I'm familiar with, as that's the closest field aside from accessibility. I'm US based, speak EN but learning JP & beginning FR. Remote/ teletravail please!

Ever wanted to style HTML form controls with custom CSS? A new @w3c #CSS specification is underway: "CSS Form Control Styling Level 1" #FPWD #timetogiveinput
▶️ w3.org/TR/css-forms-1/

This spec. aims to standardize form styling, improving design consistency and #accessibility while giving web #designers more control.
Feedback welcome! github.com/w3c/csswg-drafts/la

Need a demo? Check this one by @argyleink! nerdy.dev/customize-a-select

Fortgeführter Thread

The more I look into this carousels-via-CSS thing the more it worries me.
developer.chrome.com/blog/caro

I’ve found that:
• it is based on the APG carousel, which, ugh;
• it is the impetus for a CSS `inert` property, which, uh oh;
#a11y pros have raised concerns, which, well yeah.

Chrome for DevelopersCarousels with CSS  |  Blog  |  Chrome for DevelopersSupport scroll experiences with navigation buttons and markers with just a few lines of CSS.

“Here is a list of WCAG 2.2 Level A and AA success criteria that I think cannot be completely tested with automated tools. These criteria require manual testing because they involve meaning, usability, intent, or user experience that automated tools cannot fully evaluate.”
html5accessibility.com/stuff/2

@SteveFaulkner with the automation-to-WCAG-pipeline fatberg.

html5accessibility.comA TOOL’S ERRAND – HTML Accessibility

Building accessible applications is not about respect.

It‘s about a goddamn human right and also avoiding technical debt by following standards and convetions. Stop downplaying this. And stop making yourselves look like you care about people. #accessibility #a11y

Sometimes I wonder if me writing up trivial issues like the following is making a difference. I mean, if you are a developer, and you don’t see what is wrong here in like half of a 10th of a second, what are you even doing? Respectfully.

<input
type="radio"
id="radio-abcd"
aria-label="[object Object]. "
checked=""
value="1"
/>
<label for="radio-abcd">Useful label</label>