Robeano posted this in our internal queue a couple days before Workbench Access was on drupal.org
It's clear we have outstanding UI issues with My Sections. Changes to My Sections have been made. It isn't clear to me that hiding non-accessible sections makes sense. It's a bit hard to read (see attachment my-sections-hiding-section.png). In this example, the user has access to all Exhibits section, all Libraries sections, and only Gift Shop Staff subsection of Gift Shop. You can see that it's a bit cumbersome. It makes it look like Gift Shop Staff is under Library. Screenshot: http://drupal.org/files/my-sections-hiding-sections.png
| Comment | File | Size | Author |
|---|---|---|---|
| my-sections-hiding-sections.png | 691.05 KB | stevector |
Comments
Comment #1
agentrickardI need a UX guru to input here. This is a very difficult problem. We can either shows the parents (which you can't use), or need a new display concept.
Comment #2
tgunter commentedSimple solution would be to show the parents but mark them clearly as inaccessible or otherwise different from those the user has access to. Maybe make the parents gray and italic, or bold those the user can access. Or both.
Edit: As this is a visual cue, some extra effort would have to be made to have a hidden descriptor of some sort if you want it properly accessible by screen readers. Perhaps preface each with a span containing something like "Parent:" and then hide it from sighted users with absolute positioning.
Comment #3
agentrickardYes. I think this is the proper solution. Something that shows the hierarchy that is relevant.
The whole module could use some AX review as well.
Comment #4
mechler commentedAlternatively, it could display a full site path/breadcrumbs to the sections listed.
While a site is relatively small, displaying the hierarchy with css clearly labeling which sections access is granted to is an option, but that breaks down when the hierarchy becomes very large (universities come to mind). I also wonder if this means that editors/contributors with permissions in a lot of sections are going to find themselves looking at a confusing table here, too.
Like you said above, it's a tough problem and one that probably needs a lot of input and QA. It's worth stepping back to ask ourselves why someone might want to see this section, too. Maybe that can guide how this display is built?
Comment #5
agentrickardI like that idea of stepping back. It may be that people don't need to see this page at all.