in #601932-259: Allow dashboard to limit available blocks there is an explanation of the experience for users who cannot use drag and drop, but who wish to administer their Dashboard:

@Everett Zufelt: Re #257: You can read the last third of #222 for context, but copying the two text messages again here, in case that's helpful. When someone first gets to the admin/dashboard page, if JS is disabled, they see this text:

To customize the dashboard page, move blocks to the dashboard regions on the Dashboard administration page, or enable JavaScript on this page to use the drag-and-drop interface.

And if JS is enabled, they see this text:

Drag and drop these blocks to the columns below. Changes are automatically saved. More options are available on the configuration page.

That is the current HEAD behavior, unchanged by this patch. I do not believe it's at all friendly to people who have JS enabled, but who cannot use a mouse, and I think that warrants an issue. Please open one, and link to it from here.

I agree that the current text for users with JS enabled, but who cannot use drag and drop UI is not sufficient to indicate that "More options ... configuration page" means a page where the same behavior can be performed without using drag and drop.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Everett Zufelt’s picture

Title: Link to Dashboard administration page requires better text » Users who cannot drag and drop require clear anchor text to find Dashboard Administration page
David_Rothstein’s picture

Issue tags: +String freeze

Adding the "string freeze" tag.

carlos8f’s picture

Priority: Major » Normal

Since this is just a text change and doesn't affect functionality, I don't believe this qualifies as "major".

"Priority levels of issues":
http://drupal.org/node/45111

Everett Zufelt’s picture

Priority: Normal » Major

Issues which have significant repercussions but do not render the whole system unusable are marked major.
...
Major priority is also used for tasks or features which consensus has agreed are important (such as improving performance or code refactoring), but which are not functional bugs.

So, if I can't admin my Dashboard, because I can't figure out where to go to do it, then I think that is pretty major.

I really wish I could help come up with a better string, I'm really bad at that. I just know that the current string will be confusing to many users, who will not understand that More options ... 'configuration page'" is where they need to go to get the alternative UI that is accessible to them.

bowersox’s picture

Something like this:

"Drag and drop these blocks to the columns below. Changes are automatically saved. More options and accessible dashboard administration are available on the configuration page."

Everett Zufelt’s picture

How about 'If you have difficulty using a drag and drop interface use the Dashboard administration page'

Why do we have to disguise this. We didn't make this accessible to all people, so say it outright and give them a clear path to the alternative.

EvanDonovan’s picture

I think that brandonojc's proposal is better simply because it is more succinct.

Instead of saying accessible, though, we could say "administrative interface without drag-and-drop". That would let people make the call on whether they needed that.

EvanDonovan’s picture

Alternatively,

Drag and drop these blocks to the columns below. Changes are automatically saved. More options are available on the configuration page, which does not use drag and drop.

EvanDonovan’s picture

Status: Active » Needs review
FileSize
1.3 KB

Went with #9 as a patch. I don't think we can use #7 because the page has two purposes - it both provides more options and is more accessible. That said, I am open to alternatives, though time is almost up for this string change.

catch’s picture

Version: 7.x-dev » 8.x-dev
Category: bug » task
Priority: Major » Normal
Status: Needs review » Reviewed & tested by the community
Issue tags: +Needs backport to D7

I'm moving this to a normal task - it's a combination of accessibility and usability enhancement, major bugs should be reserved for interfaces that are actually un-usable or inaccessible.

This breaks string freeze but I'll let webchick decide whether it's sufficient to warrant doing so, otherwise I'm RTBC-ing it and marking for backport.

catch’s picture

#10: dashboard-accessible.patch queued for re-testing.

webchick’s picture

Status: Reviewed & tested by the community » Needs review
Issue tags: +Needs accessibility review

This seems like it could use review from the accessibility team; not sure the amended text is sufficient.

And I'm leaning towards not committing this in 7.x. I see Everett's point, but the link is there for the clicking, and we have many, many other examples in D7's user interface text being obtuse, which we also aren't going to fix in D7. Not removing the tag just yet, though, so this could be discussed.

Everett Zufelt’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: -Needs accessibility review

Looks reasonable to me. Would be nice to see it backported to 7, but can understand reasoning to not do that.

mgifford’s picture

#10: dashboard-accessible.patch queued for re-testing.

webchick’s picture

Component: dashboard.module » user interface text
Issue tags: -String freeze, -Needs backport to D7

Ok, after thinking on this some, I really do think this belongs to 8.x only. That means it's Dries's patch. Sorry.

xjm’s picture

Tagging issues not yet using summary template.

catch’s picture

Status: Reviewed & tested by the community » Needs work
Issue tags: +Needs issue summary update, +Accessibility

The last submitted patch, dashboard-accessible.patch, failed testing.

oriol_e9g’s picture

Status: Needs work » Needs review
FileSize
1.13 KB

Reroll

Bojhan’s picture

lol @ which does not use drag and drop. This is a pretty ugly fix.

People have no clue that drag and drop isn't accesible, for Drupal 8 can't we figure out how to actually make this kind of interaction acccesible?

mgifford’s picture

Status: Needs review » Needs work
Issue tags: +Needs issue summary update, +Accessibility

The last submitted patch, dashboard-accessible-963598-20.patch, failed testing.

mgifford’s picture

Issue tags: +mobile, +keyboard focus

Adding tags. Having a generalized way to do this would be good. Solution could be similar to Table drag.

mgifford’s picture

Issue tags: +Needs tests

adding tags. The tests are a problem and are halting this issue.

mgifford’s picture

Status: Needs work » Closed (won't fix)

The dashboard module isn't in core any more, so...

#950956: Remove Dashboard from core