Closed (won't fix)
Project:
Homebox - Individual user dashboards
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Feb 2011 at 15:33 UTC
Updated:
21 Feb 2023 at 18:25 UTC
Jump to comment: Most recent
Comments
Comment #1
Everett Zufelt commentedI wouldn't really say that this is an accessibility issue. All modules should work w/o JS as a basic principal of progressive enhancement. I doubt that it is much more likely that a disabled user is browsing w/o JS than any other user.
It is important to ensure that w/ or w/o JS that the UI is accessible to all users, by following WCAG 2.0
Comment #2
thekevinday commentedI guess I was thinking of section 508, where following that means running a website entirely without javascript!
Or at least, that is what I think section 508 was saying...
Comment #3
brianV commentedPatches are accepted. But whatever patch implements this will likely result in a complete new branch.
Comment #4
mgiffordI don't see this as much of an issue as 508 is being rewritten and most AT works on the DOM level.
Now my friends who are security buffs would like it to work with JS disabled.... But not sure it's an accessibility issue.
Now this is an issue - #949090: Dashboard block reordering not accessible to screen-reader (keyboard?) users
Comment #5
anybodyPlease create a new Drupal 8+ (3.0.x) issue, referencing this one, if this is
still relevant for Drupal 8+ (3.0.x).
As this issue was created for Drupal 7 which is close to EOL and won't
receive any new features here anymore (unless someone implements them or
sponsors development) I'm closing this issue for cleanup now.
If anyone works on this or has a solution, feel free to reopen! 😄
Thank you.