There's an old saying about "knowing just enough to get you into trouble", and right now I'm really on the edge of walking away from negotiations on a new contract just because the client's in-house IT guy is basically talking out his arse, but the owner just keeps agreeing with his BS no matter how I word or disprove his claims.... DESPITE the actions of said director of IT being the joker that landed them in court, and why I'm even being talked to in order to correct their problems in the first place.
This has been an increasing problem in recent years when freelancing as an accessibility advocate. These websites with their endless inaccessible "JavaScript for nothing" and garbage frameworks that tell users to go plow themselves repeatedly end up with fines and lawsuits -- but when you explain why and how to fix it, more often than not the people who created it refuse to listen to a single word of it.
I mean, it's part of why I'm so anti-framework, but when you're looking at thousands of dollars a DAY in fines, get recommended to someone who knows how to fix your problems, and then they dare to tell you what's wrong and how to fix it, MAYBE, JUST MAYBE you might want to huffing listen?!?
I get the feeling it's a bit like what Patton was talking about during WWII when it came to military planning and interacting with civilian governments:
In view of the prevalent opinion in America that soldiers are -- of all persons -- the least capable of discussing military matters and that their years of special training is nil compared to the innate military knowledge of lawyers, doctors, and preachers. I am probably guilty of a great heresy in daring to discuss tanks from the viewpoint of a tank officer.
-- General George S. Patton Jr.
It honestly feels like I'm guilty of heresy in daring to talk about accessibility from the viewpoint of a freelancer specializing in the subject.
I'm going to give it a go again tomorrow, but if there's a repeat of this willful ignorance and outright denial of the facts I'm probably just walking away from this one. Again it's almost like dealing with cultists, homeopaths, and other pseudo-science quacks. A confirmation bias deeply rooted in cognitive dissonance.
The CG part being the core of it, "But lots of people use bootstrap and react and don't have these problems" -- YES THEY DO!!! The difference is those sites are not in industries where it is a legal or contractual requirement for the project.
Like the bank account access this contract is for fixing.
Anyhow, does anyone out there have any advice for dealing with this, or want to relate similar stories? It might just be enough to hear I'm not alone in dealing with this level of stupid.
... 'cause if I do stick with it I'm probably going to increase my quote just for the aggravation of dealing with this level of stupid. I might just go full Wolf on them.
Get it straight buster - I'm not here to say please, I'm here to tell you what to do and if self-preservation is an instinct you possess you'd better 'ing do it and do it quick. I'm here to help - if my help's not appreciated then lotsa luck, gentlemen.
-- Vincent Wolf, Pulp Fiction
I'm just trying to avoid what I went through this time last year, where I went from "Hero who fixed it" to "Witness for the prosecution".
-- UPDATE --
PROBLEM SOLVED; when it comes to the clown that was in my way? He got the "Mr. McMahon" treatment.

Apparently I was not the only consultant they were talking to butting heads with this clown. When you have five bidders and they're all telling you the same thing...
You're doing A with framework B and that landed you in court.
I advise you to use C, possibly couple it with D so you can fix the problem you have.
If they don't want to listen, let them find another consultant. Save your nerves and keep choosing who you want to work with. Not every client is worth every dollar.
Hmm I don't clearly understand where WCAG actually breaks with bootstrap. It's just a responsive layout framework with a class composition approach and some basic functionality.
It should have nothing to do with it, i don't like it that much either but I found out that a big portion of the people just don't know enough to actually build a responsive homepage.
That's it about the technology. I think your reasoning is not conclusive but taste. Bootstrap and WCAG are not mutually exclusive. But stupid applications of any approach can lead to failed results.
To your concrete problem, I agree with Milica she puts it very reasonable.
You are the expert you were hired to give them advice, if they want to push another agenda, you either don't have enough evidence or they are ignorant.
I would rather push on the principles of how WCAG works and not against a specific technology, but if you really can't stand it -> her approach seams to be the most professional to me.
I've definitely been in the presence of absolute geniuses who knew my area of expertise way better than me before ;) I can relate to that feeling. I don't have any one particular person or situation in mind, but I'll share my answer:
One answer: Never let them know you think they are wrong, but try to find a way to educate them, or learn (more like re-learn) the lessons you already know in a way that they can also witness and experience.
I see this one all the time in graphic design circles, where designers sit around telling stories about the dumbest, most demanding clients and laugh at how little they knew about stuff, but to me that's a failure in communication. There's a gap there, and I think at least 50% of the responsibility for bridging that gap is from you, the actual trusted expert.
Ever since I realized that in my own client relationships I haven't had any of those 'nightmare clients', and I don't think it's because they went away, I think over time you (can) learn how to bring them up to speed, and share your understanding with them to help them see the same things from your perspective. But that's not instantaneous, and it isn't always effortless. Sometimes it's easy to explain something (like here's why 'above the fold' is a concept that doesn't apply to web design) and sometimes you almost have to establish a base vocabulary for the concepts you're talking about and teach them how to think and speak about something before you can explain what you know about it.
In the end, I believe most 'nightmare clients' can become slightly smarter, slightly better, and hopefully learn to trust your judgement more. The more you teach them and guide them, the more they will listen to what you have to say when it's time to give personal opinions on things.
I agree with Milica who put it very succintly. Even as a consultant, a culture fit is very important. Most people assume that this is reserved for employees only. As a consultant, if you've been brought on board as an "expert" in a field, then they would do well to take your advice. Disagreements are normal, but if you're this unhappy about it, walk away. No shame.
Having said that, there are times in the past where I've disagreed with the client but still went ahead and did what they asked for. In those scenarios, it's about covering your own ass first. I'd make my disagreement with their final decision in a written format to ensure a paper trail to the saga. At the end of the day, it's their product, their company and their team. It's up to them how to run the show. I was there to help in any way I could. If all they wanted was a pair of hands, that's all they get. If the client actually wants a brain to go with it, I'd be happy to oblige, but I'm not killing myself over it. Obviously I never renewed their contract.
Well, there are different kinds of people out there. Usually, and if possible, I try to be polite and diplomatic. Ideally, I try to change the subject to something more pleasant, or I walk away, talk to someone else.
A: You know, anything not using React in today's world is not worth it. Not using it is outright stupid. I have developed websites for three whole years and I know what I am talking about. Me: You know, you might be right about that.The best course of action imho is to not collide with them, because that just results in a big discussion without end, which is very taxing on your nerves and will exhaust you quickly. Use an argument-stopper, like just agreeing with them unconditionally. Chill, be cool, let them talk BS, let them make experiences and hopefully grow up one day. That's not your job to fix, though.
In your case, your job is to fix a website. My advice would be to stay focused. Don't let their arguments bother you. Create an issue overview and tell them how it has to be fixed from a legal point of view, which results in certain technical decisions. However, don't give them any choices - you are the expert. Either they agree and you land the job, or you walk away from this madness. Your health is more important and you can easily get another job with more pleasant people, which is a boost to your motivation. Motivation is important, because no one can just work like a machine.