Email or username:

Password:

Forgot your password?
Top-level
[unowned RobWhitaker]

@ShellyBrisbin @ivory I love your apps and I really appreciate the work you’re doing. But this is a horrible response. It’s much easier to build accessibility in from the start than to try to add it later. Please don’t exclude people.
Accessibility is the ‘viable’ part of MVP.

5 comments
Scott Willsey

@RobW If Paul is manning that account, you probably can consider yourself blocked. 😂

But I agree with you 100%

[unowned RobWhitaker]

@scottaw I honestly don’t want a pile on. Many people don’t realise accessibility from the start is easier and this is why they think it’s hard. I just hope that knowledge helps a little. I don’t expect for a second that Paul wants to make an inaccessible app.

Scott Willsey

@RobW Oh, no, I agree. That's why I removed them from my reply. Paul was super block happy on Twitter though. He blocked me and I don't remember ever interacting with him.

[unowned RobWhitaker]

@scottaw that’s a real shame. Although I do understand why criticism can be difficult for a one person shop.

Bynkii (they/them)

@RobW @ShellyBrisbin @ivory so a “feature” that to work well has to be a part of everything in the UI/UX and can require significant code changes to account for is going to be bolted on? “Later”?

When? 1.1? 1.2? 5.X? 10.X?

Why, in 2022, would you say “we only want people with no disabilities to use our app until we “get around” to treating them like viable customers?”

Regardless of intent, that is what that decision says and does.

Go Up