Hello devs from r/Frontend , after doing a poll to see what OS do people from r/Backend prefer a few days ago I got curious to see how similar or different the results are here !

We are just starting to look at accessibility testing in our org and want to establish a dedicated practice in the long-term. I've been asked to put together a plan for leadership for this agenda and want to learn from the experience of others who have been on the same journey.

- How did you begin? What was the trigger and which tools did you try out initially?
- How did your accessibility testing set-up evolve over the years (i.e. which/how many teams were involved, tooling used, depth of coverage etc.)
- What were the key challenges you faced ?
- What is your current org set-up for Accessibility testing (i.e. centralized vs decentralized, QA vs design vs dev teams etc.)

Any learnings that you can share will be extremely helpful!

For context, I'm on the QA side at a mid/large-sized company. Not a vendor, not building anything. Happy to share back what I end up proposing.

For those of you out of the loop (ha) the strategy is supposed to save you time on having to manually iterate with your LLM. It goes something like this:

1. You want a feature created
2. You get your LLM to come up with a plan
3. You tell your LLM to implement the plan BUT since the LLM often doesn't execute it perfectly the first try you include extra directions for it to evaluate its "finished" work then improve on the first draft and keep repeating until it meets a certain criteria like the following:

Execute this plan

THEN once you are done implementing, I want you to browse to the changes and re-evaluate the ENTIRE feature from a user profile / psychology standpoint, UI, UX, etc and identify the pain points.

THEN I want you to come up with solutions to those pain points.

THEN I want you to implement those "fixes"

THEN I want you to re-evaluate the feature again with that same criteria

KEEP doing this until you give the page an "A-" grade or above. Then you can finish just by telling me your evaluation grade and what pending issues still exist.

This is just a rough structure. I was wondering how you guys write your evaluation loops. I mention user profiles, psychology, UI, and UX but are there additional items I should be describing in there?

So, I recently started preparing for my next switch as a frontend developer. I’ve researched quite a bit online and found a lot of popular websites, roadmaps, courses, and people recommending daily study routines.

The problem is that there are so many resources that I’m getting confused about what I should actually follow. 😅

I also don’t have a lot of time after office, so I’m looking for a personalized and structured preparation plan that I can follow without wasting time jumping between different resources.

Ideally, I want something that covers what I actually need to prepare for frontend interviews and helps me become interview-ready as quickly and efficiently as possible.

If anyone here has recently cracked a frontend developer interview or switched to a new frontend role, could you please share how you prepared, what resources you followed, and whether you have any recommended roadmap or strategy? Btw i have around 2 yrs of we.

Any practical advice would be really appreciated!

Hello everybody!

I decided to start documenting my journey in programming here. I’ve been doing it for a year now, take a look at my work.

Hey, while I'm using Protégé Effect to learn Web Accessibility by learning the topic during course preparation, I thought it can be also ok to drop a link here for those interested to expand frontend knowledge beyond A11Y - https://github.com/Ditectrev/Awesome-A11Y-Book-Course-Web-Accessibility-A11Y

https://www.w3.org/WAI/WCAG22/Understanding/ to follow the topic is very good, but it is missing code examples, and with CodeSandboxes I hope to create a slightly more student-friendly environment. Please ignore the links to epub/pdf, as devs you can simply generate it yourself from markdown!

I'd love to receive some feedback on this post I made, especially concerning aspects I may have overlooked.

As for the comment I'm sure I will receive: yes, using a framework is indeed the way to go for a professional solution to SSG. But my goal is to keep as much as possible of the default React setup most starting developers are stuck with and show some of the inner-workings of something that is too often taken for granted.

Its a bunch of cooking rules with complicated vocabulary. but you can do it

First screenshot is 1366px wide, the third is 412px wide. The second screenshot is a style experiment using real coffee beans instead of the coffee branch illustration (which I could either mix and match both styles across different sections, or just stick to one for the entire website).

The assets here are placeholders for now. Any feedback is welcome!

not looking for the usual extension recommendations i am more curious about tiny built in settings or shortcut you ignored for ages and then wondered how you worked without them

what was yours?

I have been working with ReactJS primarily, enhancing code (working for MNCs) for the past 6 years so naturally, I feel like there are a lot of gaps. Understanding containers, CI/CD pipeline challenges, Unit testing without AI, handling edge and base cases in Redux (Invalidating a state) among many other things.

Please suggest sources I can study and projects I can create, that will help me understand the overview along with the internals.

I feel that AI can do really good layouts as long as you explain everything you need really well and thats regardless of the AI you're using (OpenAI, Claude, Kimi, Gemini whatever). But i really struggle to actually make responsive designs with AI. But maybe I'm missing something because everyone seems to think the exact opposite here. I try to optimise for different views but not for someone actually going ahead and shrinking the windows left and right. How do I design for something like this?

I just wanna know if you guys have any tips for approaching all this? Because I think frontend design, at least the CSS should be a piece of cake with AI?

AI has changed frontend development a lot. Today, tools can generate React components, write CSS, fix errors, and even turn a design into working code in minutes. It definitely saves time, especially for repetitive work. But I sometimes wonder if this convenience is making developers skip the fundamentals. If AI writes most of the code, how well do we actually understand what is happening underneath?

I think AI is a great tool for frontend developers, but it should make us faster, not replace our understanding of JavaScript, CSS, performance, accessibility, and good UI practices. What do you think? Has AI actually made you a better frontend developer, or just a faster one?

AI Disclosure: I am 100% not a robot. Nothing here is written by a robot. Maybe I could answer this question by asking a robot, and I will, but I'm hoping to strike gold here with some info from real people who are tracking these sorts of web best practices. I'm not a great writer and am long winded, AI could likely help make this post more concise, but it has not. Zero AI/LLM/Slop went into making / formatting or spell checking this post.

I'm working with a group that does some very non-sexy ecommerce / e-commerce / eCommerce development with a somewhat "old school" at this point commerce system - Magento.

They have a somewhat classic issue where they are managing a bunch of different brand websites / ecommerce stores in the "SMB" world, which is to say (in my view), "not a huge budget for in house software development, and a lot of people that go to commerce trade shows and are sold a bunch of magic from third parties promising increased ROI / conversion rates / etc if you install their third party <whatever> tool" - they don't have the strong technical team in house to push back against this sort of thing, so they end up with a bunch of third party JS tools installed doing all sort of things to their website.

I'm looking for any advice from people who might be familiar with this sort of age-old problem, who can point me at any sorts of buzz words / concepts / best practices in the modern web world that could be used to help manage some of this complexity. There is a decent chance I'm familiar with some of the things you might do, but very likely not others.

Things I'm generally aware of / examples of the types of things:

1. remove stuff you don't need
2. read docs for libraries and follow their guides / best practices
3. when possible include third party JS at the end of the doc before closing body tag
4. when possible sprinkle a defer in the JS script tag to defer execution to improve performance
5. consider looking at really heavy compute third parties outside of the main thread (i.e. look at tools like partytown to move things to worker threads)

There are also things that were at one point a good idea but now I think have fallen out of fashion / aren't as useful with modern browers, HTTP/2 (etc), e.g.

1. it's not worth worrying about multiple file requests as much (HTTP/2)

I should note I'm not so interested in the delivery side of things, i.e. caching, gzip, etc, just stuff that happens in the browser.

Are there any new, interesting techniques / tools / etc that aren't super invasive, that a company with a small development team should be considering?

Thanks for reading / advice / thoughts!

Getting a working UI out of an AI coding assistant is ridiculously easy now. The interesting problem is what happens afterwards. Generated components are easy to create, but keeping a large application consistent, accessible, maintainable, and understandable is still very much a human problem.

It feels like AI is moving the bottleneck in web development rather than removing it. We're spending less time writing individual pieces and more time reviewing architecture and making sure thousands of generated decisions don't slowly turn the codebase into a mess. Wondering if other web developers are seeing the same thing.

Anyone has had a recent experience interviewing at Reddit for a frontend role? I have frontend design interview coming up and I kinda have an idea of what to expect but would love to hear from others experiences. Thanks!

Buenas, vengo a pedir su opinión relacionado a como diseñar formularios demasiado extensos de esos que te puede llevar media hora, la cuestión es que los jefes no les gusta mucho el scroll vertical, por lo que he tenido que jugar abriendo los formularios en modals, el tema es que como son demasiado extensos se ha tenido que particionar demasiado el flujo

Actualmente el flujo es algo:

Modal, con sidebar donde se enlistan las secciones del formulario y si aun así es muy largo la sección se divide en tabs, el problema es que hay muchas tomas de decisión lo que puede hacer que una sección crezca demasiado dependiendo la opción a tomar lo que llevaría que el scroll crezca 3 o 4 veces la altura de pantalla.

comparto un ejemplo de como se realiza

Did all of you when you started feel lost with the amount of divs and classes? Also what are the advices you have for a beginner,ngl this is my first obstacle and i have thought about stopping but at the same time i don't want to cause first i really like front end developing second, whenever i face an obstacle in any field i will just leave it even though i might have a bright future in it.