You know you're part of a project that cares about #accessibility when your business analyst writes "If accessibility is not given for [...] then the requirement must be withdrawn, bc. WCAG rules". That's why it is important to include accessibility in the entire software development cycle: identify and solve potential issues before the actual implementation.
=> More informations about this toot | More toots from darekkay@fosstodon.org
@darekkay I have never seen this yet, even on projects that claim that accessibility is a requirement...
=> More informations about this toot | More toots from sapegin@mastodon.cloud
@sapegin I can imagine that, and that's why I love my project. It's not perfect of course, but I am actively being asked for accessibility feedback early on and my concerns are not just dismissed (as the quote shows). But I'm sure many other companies don't see the benefits of something "invisible" as accessibility, ignoring the fact that it affects everyone (similar to security, performance, etc...)
=> More informations about this toot | More toots from darekkay@fosstodon.org
@darekkay Yup, and even the fact that we must comply with the European Accessibility Act until next summer doesn't seem to change the overall attitude.
I also experience a lot of hesitancy for esthetical reasons, even for things that aren't even visible for most users (like focus-visible) or the change is clearly better than before even if it's not ideal.
=> More informations about this toot | More toots from sapegin@mastodon.cloud This content has been proxied by September (3851b).Proxy Information
text/gemini