I think an issue with web development is that frequently customers dictate too much to the developer. Of course, the customer ought to detail their business model and the website designer shouldn't intrude with the blueprint unless it's necessary to do so.
Even so, on technical issues that have an effect on categories like usability, the customer has to accede to the designer's experience. All too often this isn't the case, and that can block the actual success of the site. For example, an aesthetic specification from the client might cause a problem with website security, and the web designer has to identify this to the client, and hopefully the customer will acknowledge this and endeavour to work on an amended design.
It is a difficult balancing act, as no web designer needs to upset a client; however I think it's the obligation of a website developer to guard a client from issues they're rather likely not conscious of, and to ensure their web site has every likelihood of success when it goes live. Thus my recommendation is to talk to an online developer - listen to them, and collaborate with the design team. A great web developer is there to help you and utilise their experience to stop what you are promoting from stepping into future problems.