The first example you show is probably ok (it is hard to tell with a static image as we can't test contrast easily).
The second example is almost certainly not in accordance with WCAG.
The third example is probably not ok either, but yet again hard to tell "at a glance".
There is a guideline that inputs and controls should have a contrast ratio of ...
Here is a previous post about it with some more points of consideration - Is it a "Natural language" form a good practice?
Can be very hard to deal with the lot of culture and languages.
Harder to design help and error message
It's hard to represent optional inputs, because it leads to empty sentences
Can be hard to parse fast by the user
Not good ...
Natural language forms are much suited in short queries. Like i would like to book a ticket to "Choose Destination" on "Choose Date". These are much intuitive and direct. You can check out Luke's post on mad-libs form to learn more. But when it comes to long forms, it can increase the load on the user.
Standard forms are lot easier when ...
As far as I understood, user may have many records and for many records scenario, tabular structure is very useful (your second option).
At first, you will have empty table of records and in above toolbar there will button to create a new Project service. On the button click, you can open a pop up(I assume Project Service Table is not opening in pop up ...
Is the pencil icon necessary?
Is it necessary to repeat the title items?
I would propose to highlight the text area on hover or click and edit it on a second click.
When the text edition is on, show at the right the save and cancel icons.
For me Auto-save works. This is my scenario and my reasons for implementing it.
Our app has long form with lots of data input, some of that free text comments.
We have more than 100 users with different quality of connection
We have lots of validation rules that depend on multiple fields
When the form is complete and valid it goes to next step ...