my question is ...

how do you handle frunt end (css included) when you are blind?
Obviously you can code the colors in to your stylesheet, but how do you ensure your widths and heights don't over lap and all those other stuff that makes your web pages unreadable?
how do you deel with it?

I am freelancing

Programming is different.  Programming is reliable if you're any good and can network.  There's more demand than good programmers.  But you'll need a portfolio and all that.  Our attempt at it could have succeeded but fell apart due to interpersonal issues and overhead of trying to run a multi-person company without all being roommates.  Also because two of us (me being one of them) wanted to stop.

because here's the problem.  You know all those horror stories about the dev team who worked 80 hours to meet the deadline while being talked to by the entire technically inept company who thinks it's just flipping switches?  Those are entirely true.  Except that there's no one between you and the client to act as a buffer unless you're big enough to have a dedicated sales person or whatever, so you're the programmer *and* have to fend them off long enough to program.  They'll have no problem changing the requirements because surely x is a small change.  And if they're unsatisfied they'll just not pay you.  Plus you have no benefits or anything except that if you get enough money you can technically take as much vacation as you want.  As a side job with a sighted partner and in the kind of situation where you can be really choosy about your clients maybe it's better, but speaking from experience it's not for the faint of heart unless you can get the company to be big enough that you can have the luxury of the supporting teams and things that normal companies have to insulate the programmers from the clients.  I don't mean this in a "people suck" way but the problem is that unlike sound or art or whatever, there's no understanding on the part of the client as to what's going on.  You're just this weird black box where requirements come in and software comes out with some weird arbitrary timeline plus you keep asking nonsensical questions that seem stupid over and over and every time they change something that they think is small you say no or move the deadline out.  I wouldn't like being on the other end of that dynamic either, but there's no way to avoid it.  So now you've got your 40 hours or more of coding plus your however much of promptly dealing with clients, and probably you need to run multiple contracts in parallel to keep the lights on or whatever so that the pipeline never runs dry.

So yeah blindness is an issue.  And maybe someone is going to be like "but it's great, what do you mean".  It's possible my experience with it was just particularly bad.  But blindness isn't the primary reason I'd avoid it.

You're misunderstanding.  I'm not being disparaging as such.  If you hire Omer for sound, say, there's going to be a lot of back and forth.  But it's back and forth that's easily explained.  "I need x because y" or "it will take z additional time because these steps".  Which is fine.  When it's the client asking it's about "please justify why I gave you the money".  When it's the other side asking it's about "I need to refine what's going on".  All good.  Everyone involved understands who is in what role.  The client knows they don't know.  This is all the same mostly.  It's fine on the Ethiccal level and the is someone being stupid level.

But the exchange with programming is something like (slightly modified true story).  Client: we need to track every user action going through the system and turn them into billing data now because person X got back from vacation and noticed this critical oversight.  Programmer: sorry, you didn't tell us that and we have to start the project over, give us an additional month.  Client: Why?  Programmer: insert a bunch of stuff about design patterns and databases that might as well be Latin.

Any exchange between the average Joe and an expert in some field is somewhat like this.  I'm sure that if we looked we could find other fields with the same problem.  But Omer probably never tells clients that sorry, we can't make this change without me literally deleting all my work, or anything like that.  And when they do say something they can probably demo why it doesn't work or whatever else.  if you tell someone that the problem is that you rent a recording studio or something and it's not available till Tuesday, that's a good explanation in the sense that it's easy to communicate.

But programming is like hiring Gandalf.  He'll say something about how the stars are bright tonight and you shouldn't go via Moria and the moon is auspicious, so give him until next month and your problems will be solved.  But you're paying upwards of $50/hour for that minimum, you only find out if you got Gandalf when the software is done, and every time you ask a question on the way through you get some other answer, maybe about how mars is aligned with Venus so we need an extra week, or Pluto's orbit wobbled so sorry the server was down for your critical demo with investors, or whatever.  I'm not doing freelancing anymore but high level programming stuff is such that I literally can't explain my job to anyone who isn't also a programmer other than basically saying "I make software" and maybe mentioning a few of the clients I'm allowed to admit to.

So like.  You can deal with it.  But it quickly becomes a lot of your job.  Sales is an entirely different skillset.  Translating from the backend architecture to something the client understands is a skillset.  Saying no repeatedly without alienating someone takes time and energy.  Dragging all the info out of the client at the beginning without losing them is a whole thing.  because let me tell you, they don't know what you need and they will totally forget to mention some really important thing until week 3.

But no, it's not the client's fault.  It's not your fault either.  But it is prone to getting to a place where the client doesn't understand why the answers you're giving them are basically "trust us".  Saying "trust us" over and over isn't going to make anyone happy at all if they're giving you $50/hour and you're doing 40 hour weeks.  Nor is saying "no, we an't do that" to really small-seeming things like adding an additional dashboard or whatever else.  The rates are great, but the business/communication overhead, which I might add you're not paid for usually, is brutal.  Consider how many people around here struggle for years to get good enough to make a game.  The newest coder on this forum is more informed than your clients.  your clients are going to think that you code in binary or insert any other stereotype you care to think of.  Again. This. Is. Not. Wrong.  They're not being idiots.  They know they need you because they don't' know how this works.  But the dynamic is very energy-intensive anyway.

Well if you're not talking about freelancing, that's different, and yeah bad companies exist.  If you decide to build a tech team as employees and you aren't willing to trust them you should either get a different tech team or not do one.  But freelancing doesn't usually turn into that sort of relationship.

Even so, even in employee land, there's definitely a different dynamic when you know more than your manager by enough that your manager can't even tell if you're working.

Ok, let me rephrase: when I say freelancing doesn't turn into that sort of relationship I mean that it doesn't turn into the sort of relationship where you have trust with clients and can say "sorry it's going to be late because".  If you want those sorts of horror stories as described in post 10, freelancing will definitely give you one in very short order.

before I go into the rest of this let me just say that 99% of the people who freelance don't have these sorts of problems 99% of the time, but it will happen at some point and you do have to be prepared for the worst.

In normal employee land, you can be fired but being fired still gets you paid for the work you did because employers can't go "we fired you and also you're not getting this month's salary".  far as I know that's illegal.  You also have to really go all out before your employer will sue you or something.  In freelancing land, you don't have these protections.  It depends what your contract says, but usually there will be clauses and things in the client's favor to the effect of "if we get really unhappy you have to give the money back" or what have you.  It also depends on jurisdiction and some other things, but "if you don't meet the deadline we can sue you for $100000" is actually the sort of thing that can end up in your contract for example.  It'll be phrased something like you promise January 17, not having January 17 is a breach of contract, on breach of contract you owe us $100000 in damages.  I'm simplifying but the effect is the same.  Obviously when you're small you can just walk away from the really bad contracts like that of course--they can't force you to sign.

When I did this, and also from my friend doing it now, the most common thing is you end up doing a few weeks of work for free, but if you're up against someone with the money they can just sue your ass out of existence if you make them mad enough no problem.  We had one client seriously threaten that.  They don't have to win, they just have to out-money you.  In all seriousness don't work for lawyers, out-moneying you for them is free.

In normal employment land, firing is the worst bad thing that can happen to you.  in freelancing land, firing is the *best* bad thing that can happen to you.

You want to be behind an LLC and with the corporate veil in place.  If you aren't then the worst bad thing that can happen to you is you get sued for $100000 or something and the judge says "sorry, you didn't have a corporation in place, better sell your house".  I'm not kidding.  That can happen to any small business that's not using a corporation of some sort.  Fortunately at least in the U.S. they're like $300 a year and you can start one by filling out an online form in 20 minutes, but there is some overhead.  basically the more you run your LLC like a proper business the better off you are: you definitely want a business bank account, you probably want to consider paying yourself and recording what you paid yourself, and you should probably talk to a lawyer because I'm a programmer and this is really important to get right.  If you have all of this in place, then the worst that someone can do in the vast majority of cases is take all your business assets.  If you don't, then your personal property and personal finances can also be seized by lawsuits and the like and you can *literally* end up with not a penny to your name.  Fortunately this is very very easy to avoid.