Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Are JavaScriptless forms accessible?

+2
−1

I consider to make my website's contact form totally javascriptless (only HTML-PHP-CSS --- no JavaScript at all).

  • No modals or alerts
  • No prevent default
  • No AJAX/AJAX/XHR/JHR
  • No form disappearance and replacement with a success message in the same page (rather, a user would be redirected to a success page)

Accessibilitywise, are JavaScriptless forms standard?

If a JavaScriptless form cannot reflect current W3C accessibility standards (in any plausible interpretation of an accessibility expert) than I should stay with JavaScript.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (1 comment)

1 answer

+3
−0

As indicated by your source using (or not) JS is mostly independent of accessibility since the latter is obtained mainly through HTML and CSS.

As a side note, while not using JavaScript is an option, you must also consider the performance and UX implications of this:

  • client-side validations provide instant feedback and spare the server for extra calls
  • using AJAX (or wrappers provided by modern UI frameworks) calls provide a better user experience because almost only a tiny bit of information is exchanged with the web server and application feedback is better

Depending on the web application traffic and users expectations, these might be more than simple "convenience" features.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »