Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Without JavaScript, you can not do the following:
- Store administration
- - Show links -
- View orders
- Submit search form - simple solution: add 'Search' submit button between tags
- Create order
- Search for a customer - simple solution: use Drupal's collapsible fieldset
- Create a customer - simple solution: use Drupal's collapsible fieldset
- Settings overview pages
- Click on the grey boxes - simple solution: make the 'section-title' a hyperlink
I haven't gone through the front-end interfaces yet.
In Drupal, the user should be able to do everything without relying JavaScript.
Comments
Comment #1
Rowanw CreditAttribution: Rowanw commentedCorrection...
add 'Search' submit button between tags
Should read...
add 'Search' submit button between
<noscript>
tagsComment #2
Xano+1
Relying on Javascript is bad and in practically all cases not necessary. Javascript is an extra feature, not a tool.
Comment #3
rszrama CreditAttribution: rszrama commentedUnfortunately for non-JS users (and I understand the benefits and design goals), it was seen as a tool when developing Ubercart to achieve a single page checkout. We knew it was a departure from the general Drupal design, though I'm not making any value judgments about the decision here. The reason was pragmatic, and it's served Ubercart well so far.
I'm all for greater accessibility, though. It's just going to require more than a few quick fixes to remove "JS as a tool" in UC.
Comment #4
XanoSeeing how big UC is it would be unrealistic so expect this issue being fixed within one or two months, but I think it's best to keep it in mind and remember it the next time these parts of the module are being redesigned - hopefully before a version 2 final release.
Comment #5
rszrama CreditAttribution: rszrama commentedAgreed, though we'll need to look past the 2.0 release for a fix... we're porting 1.0 as quick as we can so we don't get stuck in update limbo. : D
Comment #6
Rowanw CreditAttribution: Rowanw commentedWell there's no point fixing a couple of JS problems and leaving more in there, postponing so it can be fixed properly later on.
Comment #7
mgiffordBeing able to have a shopping cart that degrades nicely without javascript is important. Gotta be able to win every customer in this economy after all.
However, many screen readers work just fine with javascript. Would be good to know what evaluation the Ubercart team has done on accessibility of this great tool.
Comment #8
intuited CreditAttribution: intuited commentedCould somebody please clarify if this affects the front-end at all? Requiring admin users to have JS enabled is not a big deal but expecting that all end users will is pretty serious.
Comment #9
TR CreditAttribution: TR commentedRe-opening this as a feature request and moving to the D7 queue. The dependence on JavaScript will not be removed in the Drupal 6 version of Ubercart.
Comment #10
Island Usurper CreditAttribution: Island Usurper commentedI think the OP forgot to mention one of the biggest ones: checkout. That one's the most obvious to me because more people see that page than any of the admin interface.
Fortunately, that's starting to change with #305496: Checkout panes, order panes, and line items overhaul. The shipping quotes and payment details use the #ajax directive, so, in theory, they shouldn't need JavaScript to be enabled. I haven't actually tested this yet, so feedback would be welcome.
Changing the list of states when the country is changed will probably be done in a separate issue, so pretend you're in the same country as the site's store when you're testing.
Comment #11
longwaveMarking fixed for 7.x as most things have been converted over, separate bugs should be raised where problems still exist.