wheelsonfire wrote:

I just want to chime in from the Scratch Team and say that I appreciate the points that many of you are raising. It is indeed very important to pay attention first and foremost to actual users, not just to written guidelines or rules like the color contrast standards of the WCAG. I didn't work on the color contrast blocks project, but I know that they engaged in both approaches. I'm not sure what will eventually happen with block colors, but I agree that it would be very useful if the color sets were options that users could choose.

So that means it will be toggleable?

Huge support. I hate the new blocks and dislike the star/heart change, so this tab would be great.

move ()ewd steps
move (aw) steps
move (w) steps
move (dewd) steps
move () steps
move (wad) steps
move () steps
move () steps
move () steps

Paddle2see wrote:

Well - any time we change anything, we get suggestions like this to make it an option. More options makes for more complexity and a product that is harder to learn and harder to maintain. So I think it's best to try and live with the change for a while and see if it really is so bothersome.

We have to wait for this to be added. Right now it's a new thing which means ST will wait for us to fully review the changes and see if it should be toggleable. Note that does not mean it won't be added. It just won't happen yet rn. For now, we have to wait until the full site is vision-friendly Then it can be added.

I support this however though. This can be good for people who don't need this. But I suggest the vision-friendly should be default for those who have vision problems.

along with a settings page for this, there should also be an option to toggle accessibility settings when creating account, which would say something like:
Enable accessibility settings? This includes colorblind support, etc.

:]::#00289A// This is my pet Noobles! He protects my signature from [i]unwanted guests[/i]

B){

}::#800080//This is Noobles' big brother, Probles. He has returned and Noobles is happy to see him!
//oh, yeah, he is also cool so he wears sunglasses.

:P::cap sensing//This is their little brother, Doobles

99999999999999999999% support, I dislike the new colors
ST PLEASE MAKE IT OPTIONAL

When (::red) clicked :: events hat
repeat until <key [all v] pressed?>{
destroy this sprite::control cap
when @greenFlag misclicked::events hat
become idiot::custom}::control
(╯°□° ╯︵ ┻━┻::red)::#000000 reporter//this is brad, he creates cursed scripts like the one you saw above
(ㆆ_ㆆ)//this is max, he stares at you with that expression if you say you don't support my suggestion

wolfburrito95 wrote:

Huge support. I hate the new blocks and dislike the star/heart change, so this tab would be great.

Same!

OH NO, THEY CHANGED THE REMIX BUTTON!

When (::red) clicked :: events hat
repeat until <key [all v] pressed?>{
destroy this sprite::control cap
when @greenFlag misclicked::events hat
become idiot::custom}::control
(╯°□° ╯︵ ┻━┻::red)::#000000 reporter//this is brad, he creates cursed scripts like the one you saw above
(ㆆ_ㆆ)//this is max, he stares at you with that expression if you say you don't support my suggestion

support, i hate the changes, the were many complaints in the questions forum about it anyways

qwerty_wasd_gone wrote:

99999999999999999999% support, I dislike the new colors
ST PLEASE MAKE IT OPTIONAL

Please take a deep breath.
(Now before you think I disagree it can happen in a while be patient right not it's a new thing and ST needs reviews do see if this should be toggleable or not)

Support! Tho I don’t REALLY mind the new changes (in my opinion, I actually quite like the darker border on the heart, star, and other buttons. idk just more details and stuff looks way better to me), the darker remix button just doesn’t look good at all to me and I’d like to change it if I had a option.

they changed that thing when you're not signed in
I think this will get bad

When (::red) clicked :: events hat
repeat until <key [all v] pressed?>{
destroy this sprite::control cap
when @greenFlag misclicked::events hat
become idiot::custom}::control
(╯°□° ╯︵ ┻━┻::red)::#000000 reporter//this is brad, he creates cursed scripts like the one you saw above
(ㆆ_ㆆ)//this is max, he stares at you with that expression if you say you don't support my suggestion

So, this will let you change back the OG heart, star, and remix buttons, as well as reverting to the OG block colors?
Support, customizability is always a good thing, people can change stuff to their liking.
Perhaps you can also change to dark mode when that gets implemented!

I support. I don’t really think more settings = more complexity. It is more settings = more customization. The fact of adding more setting meaning more complexity didn’t stop ST of adding the modes to April Fools, right? I imagine it would be like this April Fools modes, accessed in the project editor by a button on the up bar.

Note the new blocks may not be added

wheelsonfire wrote:

The design process is still underway, there's no specific decision on how to make the alternate block colors available.

Additionally to what was covered in the OP, I have issues with the front page when the user is logged off. See this post.

The bug-green color does not look very nice upon the cerulean background. But the issue is, you can’t get user-specific with that because that’s the logged-off screen. That’s why I think it should apply to the IP. In other words, if on Account Settings, the last user to sign into the IP prefers to have the accessibility updates off, then the accessibility features will be off until someone else signs in with the preferences on.

This method would actually work out really well, because most people do not have vision problems, and if there really is a house where someone prefers the features on and another user prefers the features off, and they fight over it, that means that there must logically be people in the house that are able to help this user to see the donation box until they log in.

Plus, most users don’t donate anyway, so it’s not too big of an issue. Most colorblind people will not bother. Many of them are children who do not have money. If it is an adult who wants to donate, then it’s fine; they can always sign in, and they will be able to see the button then, plus there is a link at the bottom of every page on the site where you can donate.

I think since this topic is about changing all accessibility features, I think you should add this into the OP. Does this make any sense to you? Is there anything that I should change?

Sliverus wrote:

-snip-

I think since this topic is about changing all accessibility features, I think you should add this into the OP. Does this make any sense to you? Is there anything that I should change?

It is too broad for this, Usually, it will affect an entire organization instead of one person. That's why IP bans are not that common, and usually are issued in severe cases. I feel hardware would be better, that way it affecting only 1 or two people, depending on if you share a computer. I have no idea if that is possible.

I like these changes, personally. (I like how they look). I could understand how you would hate them. So, a toggle is really nice. Only problem. Where do we put the toggle? As Sliverus mentioned, the changes also appear when logged out. So, we can't put it in account settings. The footer maybe? It might take up too much space, and it will be a semicolon glitch but worse.

PGBFLITE6373 wrote:

I like these changes, personally. (I like how they look). I could understand how you would hate them. So, a toggle is really nice. Only problem. Where do we put the toggle? As Sliverus mentioned, the changes also appear when logged out. So, we can't put it in account settings. The footer maybe? It might take up too much space, and it will be a semicolon glitch but worse.

Maybe a separate page like “scratch.mit.edu/accessibility”, with a link in the footer?

for \({
set [i v] to [0]
}; <(i) < [10]>; {
change [i v] by (1)
}) \{{
think (i) for (1) secs
}} :: control

The Scratch Forums support bf +-<>[],.

donotforgetmycode wrote:

PGBFLITE6373 wrote:

I like these changes, personally. (I like how they look). I could understand how you would hate them. So, a toggle is really nice. Only problem. Where do we put the toggle? As Sliverus mentioned, the changes also appear when logged out. So, we can't put it in account settings. The footer maybe? It might take up too much space, and it will be a semicolon glitch but worse.

Maybe a separate page like “scratch.mit.edu/accessibility”, with a link in the footer?

I think it will run into the same problem as the forums, not noticed enough. Maybe a link on the banner? It might look stupid, though. I might make a mock-up of it.

donotforgetmycode wrote:

Maybe a separate page like “scratch.mit.edu/accessibility”, with a link in the footer?

I guess there should be some kind of a settings icon at the header, along with “My stuff” and “Messages” icons-

PGBFLITE6373 wrote:

donotforgetmycode wrote:

PGBFLITE6373 wrote:

I like these changes, personally. (I like how they look). I could understand how you would hate them. So, a toggle is really nice. Only problem. Where do we put the toggle? As Sliverus mentioned, the changes also appear when logged out. So, we can't put it in account settings. The footer maybe? It might take up too much space, and it will be a semicolon glitch but worse.

Maybe a separate page like “scratch.mit.edu/accessibility”, with a link in the footer?

I think it will run into the same problem as the forums, not noticed enough. Maybe a link on the banner? It might look stupid, though. I might make a mock-up of it.

Maybe when you’re signed out it can go at the top and take you for settings?would it be possible for it to only be for that one device?

Sliverus wrote:

Additionally to what was covered in the OP, I have issues with the front page when the user is logged off. See this post.

The bug-green color does not look very nice upon the cerulean background. But the issue is, you can’t get user-specific with that because that’s the logged-off screen. That’s why I think it should apply to the IP. In other words, if on Account Settings, the last user to sign into the IP prefers to have the accessibility updates off, then the accessibility features will be off until someone else signs in with the preferences on.

This method would actually work out really well, because most people do not have vision problems, and if there really is a house where someone prefers the features on and another user prefers the features off, and they fight over it, that means that there must logically be people in the house that are able to help this user to see the donation box until they log in.

Plus, most users don’t donate anyway, so it’s not too big of an issue. Most colorblind people will not bother. Many of them are children who do not have money. If it is an adult who wants to donate, then it’s fine; they can always sign in, and they will be able to see the button then, plus there is a link at the bottom of every page on the site where you can donate.

I think since this topic is about changing all accessibility features, I think you should add this into the OP. Does this make any sense to you? Is there anything that I should change?

It does make sense, but I think doing it for the Ip address might not work as well if people go places.so if it’s possible it could just be for that one device and stay like that until it’s turned off.