[wp-testers] Re: Default actions for top-level admin menu items

[DD32]

Ok so:
  * <div class='wp-submenu-head'>..title..</div> is seemingly non-needed, I  
removed it and it doesnt seem to affect anything.. Probably a use for it  
somewhere. Confuses screen readers since it duplicates the menu title  
(Which is a link just above it)
  * No title attribute on links makes it hard to determine menu action,  
Suggestion: ...title="Links: Add New">Add New</a
  * JS disabled = interface unuseable - I dont see a problem at all without  
JS.. I've done it many times, Aside from not being able to access the  
menu's without clicking into a different page (What do you expect?), there  
doesnt appear to be much of a backstep there, barely any problem  at all..  
can you enlighten me?
  * with CSS disabled, the Turbo/Help/Screen options appear between the  
menu and the content.. Who uses without CSS these days? What screen reader  
is not smart enough to determine menu and main content? Is there anything  
which can be done to help direct screen readers as to what is a menu, and  
what is content?
  * I'm no accessability whiz, or UI designer, I suck at both, I'm just  
trying to understand the issues you're outlining :)

On Mon, 17 Nov 2008 23:18:36 +1100, Elpie <Lynne.Pope at gmail.com> wrote:

> Some of those links are just not clickable with JavaScript off
> unfortunately.
>
> On 2.6.3 the backend is still fully functional without js, and
> although the backend is loaded with three repeats of the Google Gears
> message at the top, its still navigable with CSS off. The Google Gears
> messages are a nuisance, but all links to actions are meaningful and
> not likely to cause confusion.
>
> In 2.7, apart from loss of functionality, the dashboard screen
> reads ...
> "Add new post, add new page, comments" right below the "welcome
> username, turbo, logout". Then it gets really confusing..
> "Dashboard - dashboard - dashboard- askismet stats-posts-posts-add new-
> edit-tags-categories-media-media-add new-edit" etc etc.
> Every top-level menu title is repeated and none of the links have
> titles (which make all the "edit", "add new" and other repeated
> phrases difficult to interpret).
>
> Between corporate clients who have JavaScript disabled at the firewall
> and disabled folk using assistive technologies, either I (or someone)
> will have to write a new admin theme that completely changes the
> current output or these folk will have to stay with 2.6.3 until
> changes are made in the future.
>
> The old UI was not great and had its problems, granted, but the new UI
> is really problematic. I personally love the fact that its now quicker
> to add new posts and am pleased that the threaded comments and backend
> admin of comments is available, but such heavy reliance on Ajax
> combined with loss of accessibility is a real problem.
>
> On Nov 16, 12:39 am, DD32 <wordpr... at dd32.id.au> wrote:
>> On Sat, 15 Nov 2008 22:23:29 +1100, Elpie <Lynne.P... at gmail.com> wrote:
>> > Looks like I have to write a new admin theme anyway as the default is
>> > really convoluted for users where JavaScript is turned off. (Have to
>> > click on a top-level link, which opens a new post/page screen, just to
>> > get the other options to be seen).
>>
>> Well, That was a problem under the old design too, But a <10 line  
>> plugin  
>> should be able to override the CSS and force them all open 100% of the  
>> time if need be.
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>