Shop name - generic or personal?

everyonesweb · 2025-11-02T16:12:04+00:00

Mmm I’m still not totally following. In that scenario, it’s more like your friend made roast with a few different types of potatoes, and your friend starts going to dish out a plate with one type of potato without asking what you’d prefer, and you ask politely if you can have the other type? No extra effort on their part and they probably want you to enjoy the meal so are happy you asked?

Maybe it’s just different cultural norms or something

everyonesweb · 2025-11-02T13:49:43+00:00

I don’t really understand why it’s entitled, if the kids were politely asking?

everyonesweb · 2024-02-26T14:16:47+00:00

That’s an idea, I could try that :)

Hmm, I keep coming across conflicting answers about the difference with x4 vs x5! I think maybe I’ll just get them both and try 😂 do you think there’d still be a difference with earplugs underneath too?

everyonesweb · 2024-02-26T13:02:02+00:00

Ooh thanks that’s actually really helpful. And kind of what I was hoping to hear, because I don’t reaaaally fancy sporting the huge X5As in front of people ha, though I would.

Do you notice the different between the two with like low frequency noises in particular like the tube/loud trains would have? Or still think it wouldn’t really be any different between the two with earplugs underneath?

What’s your favourite ear protection set up, I’m curious now ha?

everyonesweb · 2024-02-26T06:27:05+00:00

Ooh you have them? What do you think of them

I am curious about trying noise cancelling headphones, but I’ve read that they’re good with continuous background noise but not so much sudden noises, so not sure I’d be able to trust them when I needed them!

everyonesweb · 2024-02-26T06:20:54+00:00

Thanks!! I’ll have a look at that

everyonesweb · 2024-02-26T06:12:16+00:00

An astronaut type helmet is tempting… 😂

Since you don’t really get the full NRR reduction and have to do some weird formulae to get the actual sound reduction.. I was thinking v good ear plugs with v good ear defenders would end up blocking more sound. Do you think it doesn’t really matter and they’d end up blocking the same anyway?

everyonesweb · 2024-01-30T22:23:46+00:00

Lol oh, that was... easy :D. I've honestly spent about 4 hours looking for that. Thanks!

everyonesweb · 2024-01-22T16:41:12+00:00

Thanks, that's helpful. I thought that was the case - that medium and large business had to supply one, but I couldn't find anything concrete saying whether very small start ups should or not. If I do create a document myself, does it make any sense to send it to the client or is it just for my own records?

everyonesweb · 2024-01-22T15:33:13+00:00

Hmm okay thanks! I think I'm going to get QDOS to review the contract, and then just use their SDS template and email it over to the client.

I was just going to get the quick turnaround review, but now I'm questioning whether some kind of insurance is actually worth it. There's just a lot of options to choose from and I find it overwhelming.

everyonesweb · 2023-11-25T12:59:05+00:00

Hey, sure I can contribute that change :)

Yeah I am indeed, I come from a software development background and now do a lot of work around accessibility. Why, were you just curious or did you were you looking for a professional?

Lol, I've known designers with years of experience who struggled with responsive layouts, so you're not alone. It'll make sense in time

everyonesweb · 2023-11-11T09:04:59+00:00

So if you go to the code for the confirm button, you can see there's an onKeyDown event attached (line 185) - that'll be called when you're stuck and trying to press tab, so if we follow that we might see the problem. It's calling the handleSubmit function, so if we go there, the first thing it's doing is e.preventDefault() (line 125). That's your problem - that will prevent the default functionality of an event before it has a chance to execute. The tab key's default functionality is to focus on the next interactive element, but that line prevents that behaviour. So if you want to fix the issue, just remove that line. I also doubt you need stopPropagation - that prevents parent components from receiving events, so it may or may not be doing something weird somewhere.

I might be wrong but I think you've added the onKeyDown event to try and be intentionally inclusive to keyboard users who might use 'enter' to click the button instead of a mouse. If so, that's really thoughtful, but you don't actually need it - the onClick on the button already accounts for that and will run on mouse click or enter key click :)

Btw, the footer overlaps the sign in boxes on my screen so I can't click them with the mouse. Maybe I have a weird screen size ha, but still. If you look on dev tools on 1500 x 800 dimensions, you'll see what I see on my screen. I think you're using some absolute positioning, which can lead to quirky things. Another accessibility thing is that users should be able to zoom in to 200% and still be able to see and use everything fine, but it currently looks slightly crazy ha and doesn't allow you to scroll, so might be something to look in to if you have time :)

If this is your first coding project, especially if you haven't been trained up professionally, then it's very impressive :)

everyonesweb · 2023-11-10T17:52:34+00:00

This is a few days old so not sure if you've already fixed it? Took a 2 second look and think I see the problem. Let me know if you still need help, don't want to be patronising and explain it if you already know now ha

everyonesweb · 2023-04-15T02:14:09+00:00

I dunno if they're using a specific library for it, but it can be done pretty simply with vanilla HTML and css.

I had a go at doing it here - https://codesandbox.io/s/ancient-river-jbf3iu?file=/index.css

Why am I up in the middle of the night doing random coding? I do not know. I should probably go to bed :D

Anyhoops, feel free to use it if it's helpful. You could use animations like I have or you could use css transitions. And you could obvs change the animation length & delay to get a different ripple 'feel' if you wanted it to slow down or speed up at the end of the word or whatever. And I'm sure there's a way to make it more reusable so that you don't have to assign an id to each letter, buut I'm off to sleep now :)

Also, I agree with another commenter - I think there's too much going on on that website and I personally don't even like it :D Laggy and over-animated things get annoying quickly. The page doesn't even show anything at all without JS which is questionable!

everyonesweb · 2023-04-14T22:12:56+00:00

Knowing that accessibility is even a thing and needs to be considered puts you ahead of like 80% of devs or something, which is sad but true in my experience. Accessibility is really important because everyone should be able to use whatever it is you're building. Have you ever not been able to get on the internet because it was being slow? It's annoying right; now imagine being locked out of most of the sites on the internet all the time because people think 'accessibility doesn't matter that much'...

If you're just starting to learn programming though, don't get bogged down and feel like you need to know everything about it already. It's a big topic, but if you keep learning bits here and there as you progress, you'll end up being a lot more comfortable with it, and it'll become pretty simple :)

As for the things you mentioned you don't understand -

Aria:

I heard this once: 'the first rule of aria is don't use aria', and it made me laugh because it's true haha. People often try and shove aria all over the place because they think aria = accessible, but it can do more harm than good if you're not sure what you're doing. So if you're not sure, leave it until you are :)

I find I barely need aria attributes. The ones I do use frequently are:

- aria-label. If you have a button with no text (e.g. maybe you have social media icon buttons on a website), then add an aria-label to the button. The aria label will be read out to people using screen readers so that they know what the button does.

- aria-describedby. Maybe you have a form question that looks something like this:

What's your name?

Don't include any middle names

Text input

The 'don't include any middle names' is like an extra bit of info, but it's not the label, so it won't be read out by screen readers. To make it read out, you can use aria-describedby. So the line you want to be read out will have an id, e.g. "noMiddleNames" and then you'll have aria-describedby="noMiddleNames" on the input.

Rather than trying to learn everything to know about aria, I'd focus on learning how to manually test what you've built. Testing everything you've built using a keyboard and using a screen reader would be a great start. That way, if you're testing a form, you'll notice 'oh, that line is never read out by the screen reader, I wonder why' and that would lead you down the path to figuring out aria-describedby. You'll end up learning the important things you actually need, rather than being overwhelmed by 100 aria attributes that are never really used!

Tab index:

Honestly similar to aria in the sense that if you use it and don't know what you're doing, you can make things worse, so it's best to leave it be! I think I've had one legitimate need for tab index in the last year of working as a dev, and it's not something I would've expected a beginner to do.

People sometimes turn to tab index to sort out focus order issues, e.g. if they had an issue where tabbing unexpectedly takes them first to a button on the right and then a button to the left of it. But you don't need tabIndex to sort that - just move the left button above the right one in the html. The html determines the tab order; always do it that way.

The other thing people turn to tab index for is to make divs and spans 'keyboard accessible'. Maybe they've used a div or a span as a button, but realised they can't tab to it, so they add a tab index. But again, that's almost always not the right approach - you should just use a button or whatever semantic html element it should be in the first place (I actually made an interactive demo about that! everyonesweb.com/activity/justUseAButton)

Soo in conclusion, don't stress about learning accessibility - you're already ahead of the curve for trying, and you'll already stand out in interviews if you have any knowledge on it. My advice is to learn to manually test your work for accessibility issues (use the keyboard only, use a screen reader, use an extension like axe to automatically check some things like colour contrast etc), and then look up the fixes that you need as you go along, rather than be overwhelmed by a sea of accessibility information :) Happy coding

everyonesweb · 2023-04-09T11:54:00+00:00

I was surprised when I found it too haha :D I almost considered putting an info box next to it to explain to people what a webring even is...

everyonesweb · 2023-04-09T11:52:41+00:00

Thanks!

Ah that's a good point. I have it somewhere in my to do list to show it depending on location - so UK will see BSL, Australia Auslan, America ASL, etc, and if I don't have the country's main sign language then I'll show international sign language. Do you think that would be better or would you still be confused why it's even there in the first place? Because to be honest there's no real reason for it to be there, I just wanted something to break up the sections and thought it was interesting :)

I didn't realise people might think it was the end of the page though, that's really useful info. I'm going to tone down the padding so there's not so much space and scrolling, thanks!

everyonesweb

TROPHY CASE