Of course it was, (in jest --- somewhat)...
A year ago I wouldn't design a site that could not be viewed on 640x480 display, and I would only use JS for non-critical elements of the site.
JS is useful, and 90%+ of browsers can handle it now, (most users at significantly higher than 640x480).
Unlike others who insist on 100% accessibility, I shoot for 90%. There is no such thing as "100% accessible", no matter how hard you try -- the day after you finish coding, a new device, protocol, "standard" or other element of web design will fall into fashion, and some of those people will not be able to [see/hear/use/access] the site you "finished" yesterday.
Yes, you can stay up coding 18 hours a day, attempting to please all of the people all of the time -- but you are rowing against the tide.
I would rather have 90% usability -- with rich features, ease of use, simplified coding and processes and anything else I can gain for those 90% -- the competition is welcome to cater to the 10% who are non-standard.
BTW - I have immediate family members with severe disability, so the politically correct "everything needs to pass ADA" crowd get no mileage from me. My brother is a hemi-plegic (paralyzed over 50% of his body -- inside and out), and has been for 20 years. When he first became disabled he wanted me to install grab-bars up and down the walls of the entire house. My logic said: If I give him these "crutches" to lean on, he will not fit in with every day life since there are no grab bars in most places.