Scratch_Cat_Coder8 wrote:

other users can block the bully until the bully can’t bully no more.

SockAlternative wrote:

Scratch_Cat_Coder8 wrote:

other users can block the bully until the bully can’t bully no more.

I don't think every single person on scratch would all collectively decide to block some rude person

Za-Chary wrote:

AliMASTER430258 wrote:

-snip with safety scissors-

It's unclear where you got this link; this particular link is not in TOLORS. Here is the link explaining why there will be no list of accepted suggestions: https://scratch.mit.edu/discuss/post/4426090/

Za-Chary wrote:

(#3577)

kChiaEC19 wrote:

Za-Chary wrote:

9.5 An official list of accepted suggestions
As a counterpart to the list of rejected suggestions, some Scratchers have expressed interest in compiling a list of features of Scratch that were suggested by someone, and eventually implemented. But it is not easy to tell whether a suggestion was implemented because it was suggested by Scratchers in the forums, Scratchers elsewhere, a Scratch Team member, a teacher, or someone else. In other words, every feature currently in Scratch was suggested by somebody, so such a list would just be a list of all features of Scratch.

I already reported this topic to be deleted because I regret making the topic and now it's been deleted. Can you remove this from the list?

I think this is a useful suggestion to keep on the list since you're not the only one who's asked for it, but I agree that there is no point in keeping a link to a deleted topic. I'm wondering if someone else could find another topic where someone else has suggested this.

UserBlockedYou wrote:

Scratchedbyyou wrote:

UserBlockedYou wrote:

add file checking please

(file::sensing)
ask file []::sensing

This isn't the place to suggest. Make a new topic instead

i meant add file checking into the rejected suggestions list

100blacktak wrote:

Make sure to add the “remove followers” followers

50_scratch_tabs wrote:

Could you please link to https://scratch.mit.edu/discuss/topic/780031 as not rejected for 7.1?

SockAlternative wrote:

teamsonic2011 wrote:

Uploading Scratch projects to the Switch got rejected

That is on the list because it applies to a already rejected suggestion

Scratch_Cat_Coder8 wrote:

The 2nd reason to why blocking users to be a feature is a bit silly. The “bury problems” is understandable but the “other users can still be harassed” is silly. The other users can block the cyber bully, meaning that the bully can’t continue to harass other users cuz of the block button cuz other users can block the bully until the bully can’t bully no more.

AliMASTER430258 wrote:

Za-Chary wrote:

AliMASTER430258 wrote:

-snip with safety scissors-

It's unclear where you got this link; this particular link is not in TOLORS. Here is the link explaining why there will be no list of accepted suggestions: https://scratch.mit.edu/discuss/post/4426090/

I got it from here:

Za-Chary wrote:

Contact Us wrote:

Hey there!

Thank you for reaching out! In the next week we’ll be releasing a blog post that describes the process a bit, but I’m happy to share some details now.
I’m the Design Director at Scratch, and our designers began working on the high contrast blocks last year. The process for the blocks began with them checking each original block color combination against the WCAG AA guidelines. Very few blocks met the contrast ratio so they began exploring alternative combinations that kept the same hue as the original blocks, but lightened the background and used black text — giving a higher contrast ratio and consistent look.

We launched the High Contrast blocks in Scratch Lab where ~800 users tested it and provided feedback. Many users with self-reported visual impairments or disabilities preferred the new high-contrast blocks, but many users without those impairments found the blocks to be less aesthetically pleasing. Most users asked for an option to toggle between the modes, which wasn’t functionality we had at the time. So, our engineers and designers worked to create the drop-down settings menu that allows users to choose whether or not to use the high contrast mode.

As for the colors in the nav bar and elements on the Scratch site itself, we explored a similar approach of lightening our original blue and using black text. However, that visual change felt off-brand and was quite jarring as a change. So, we decided to keep white text and use an existing brand color (the purple) which would allow us to meet the contrast guidelines and keep a common Scratch color. We actually use a purple editor in the Scratch Lab environment, so this was not a huge shift.

We’ve seen a few users ask to make this part optional as well, but unfortunately we need to ensure that the site is usable for as many people as possible (including use in schools) and that means we need a consistent design. We can certainly explore personalization features in the future, but for now, we want to make sure we have a site that is inclusive for folks with visual impairments, and we will be considering additional color modes in the future for the blocks — so stay tuned.

Thank you for asking about our process. The three links in the forum post (included below) are probably most help to point for more information about contrast standards in general.

Sincerely,
[Redacted by @Za-Chary]

https://kids.kiddle.co/Accessibility#:%7E:text=Accessibility%20is%20equal%20access%20for%2Ca%20person%20without%20a%20disability
https://www.w3.org/WAI/standards-guidelines/wcag/
https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines

Bobmr2024 wrote:

NO NOT PURPLE!!! BLUE IS GOOD!!!

ThisIsTemp1 wrote:

Bobmr2024 wrote:

NO NOT PURPLE!!! BLUE IS GOOD!!!

Not for people with visual impairments. Please be considerate about your fellow Scratchers that may have these conditions. You can read this essay for more info.

AlejandrixKing245 wrote:

ThisIsTemp1 wrote:

Bobmr2024 wrote:

NO NOT PURPLE!!! BLUE IS GOOD!!!

Not for people with visual impairments. Please be considerate about your fellow Scratchers that may have these conditions. You can read this essay for more info.

hmm, i sincerely think blue color on scratch its nostalgic just because i joined in 2022/8/4 idk what hour i joined in bruh anyways, purple its perfect for people with visual impairments, for veteran scratchers from 2012-2013-2014-2015-2016-2017 say to the blue color “nostalgic”, but with purple “not nostalgic”, since scratch 3.1 came (i refer to the 2nd version of scratch 3.0 website) made the blue color be purple, many scratchers leaved by theirs being teens or by the purple color change

AlejandrixKing245 wrote:

ThisIsTemp1 wrote:

Bobmr2024 wrote:

NO NOT PURPLE!!! BLUE IS GOOD!!!

Not for people with visual impairments. Please be considerate about your fellow Scratchers that may have these conditions. You can read this essay for more info.

hmm, i sincerely think blue color on scratch its nostalgic just because i joined in 2022/8/4 idk what hour i joined in bruh anyways, purple its perfect for people with visual impairments, for veteran scratchers from 2012-2013-2014-2015-2016-2017 say to the blue color “nostalgic”, but with purple “not nostalgic”, since scratch 3.1 came (i refer to the 2nd version of scratch 3.0 website) made the blue color be purple, many scratchers leaved by theirs being teens or by the purple color change

 [color=0099BB] 

Bobmr2024 wrote:

Za-Chary wrote:

Contact Us wrote:

Hey there!

Thank you for reaching out! In the next week we’ll be releasing a blog post that describes the process a bit, but I’m happy to share some details now.
I’m the Design Director at Scratch, and our designers began working on the high contrast blocks last year. The process for the blocks began with them checking each original block color combination against the WCAG AA guidelines. Very few blocks met the contrast ratio so they began exploring alternative combinations that kept the same hue as the original blocks, but lightened the background and used black text — giving a higher contrast ratio and consistent look.

We launched the High Contrast blocks in Scratch Lab where ~800 users tested it and provided feedback. Many users with self-reported visual impairments or disabilities preferred the new high-contrast blocks, but many users without those impairments found the blocks to be less aesthetically pleasing. Most users asked for an option to toggle between the modes, which wasn’t functionality we had at the time. So, our engineers and designers worked to create the drop-down settings menu that allows users to choose whether or not to use the high contrast mode.

As for the colors in the nav bar and elements on the Scratch site itself, we explored a similar approach of lightening our original blue and using black text. However, that visual change felt off-brand and was quite jarring as a change. So, we decided to keep white text and use an existing brand color (the purple) which would allow us to meet the contrast guidelines and keep a common Scratch color. We actually use a purple editor in the Scratch Lab environment, so this was not a huge shift.

We’ve seen a few users ask to make this part optional as well, but unfortunately we need to ensure that the site is usable for as many people as possible (including use in schools) and that means we need a consistent design. We can certainly explore personalization features in the future, but for now, we want to make sure we have a site that is inclusive for folks with visual impairments, and we will be considering additional color modes in the future for the blocks — so stay tuned.

Thank you for asking about our process. The three links in the forum post (included below) are probably most help to point for more information about contrast standards in general.

Sincerely,
[Redacted by @Za-Chary]

https://kids.kiddle.co/Accessibility#:%7E:text=Accessibility%20is%20equal%20access%20for%2Ca%20person%20without%20a%20disability
https://www.w3.org/WAI/standards-guidelines/wcag/
https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines

NO NOT PURPLE!!! BLUE IS GOOD!!!

Bobmr2024 wrote:

NO NOT PURPLE!!! BLUE IS GOOD!!!

8to16 wrote:

guys stop using tolors as a chatroom, this is for discussing rejected suggestions

PaperMarioFan2022 wrote:

What is even happening right now? Isn't this for discussing rejected suggestions and adding them only?

PaperMarioFan2022 wrote:

8to16 wrote:

guys stop using tolors as a chatroom, this is for discussing rejected suggestions

Ahem.

PaperMarioFan2022 wrote:

What is even happening right now? Isn't this for discussing rejected suggestions and adding them only?

PaperMarioFan2022 wrote:

(#9029)

8to16 wrote:

guys stop using tolors as a chatroom, this is for discussing rejected suggestions

Ahem.

PaperMarioFan2022 wrote:

What is even happening right now? Isn't this for discussing rejected suggestions and adding them only?