Moodle Community Sites

Disabling JavaScript causes http://docs.moodle.org/ layout to fail

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Component/s: docs.moodle.org
  • Labels:
    None

Description

Disabling JavaScript causes http://docs.moodle.org/ layout to fail. The front page is filled by large empty space. This happens for example when using Firefox 3 and NoScript (http://noscript.net/). Enabling JavaScript solves the problem. Page layout, however, shouldn't depend on JavaScript.

Issue Links

Activity

Hide
Olli Savolainen added a comment - - edited

This will actually not really be resolved by the issue I linked this to. The actual issue is that javascriptless browsers, text browsers and screen readers will have to wade through that entire list before getting to content.

Adding a skip to content link will alleviate this.

But I think the only real solution is to only have the top-level links visible without javascript and have the submenus on the target pages. Hiding them with CSS and then disabling that CSS with javascript solves the issue for CSS-enabled browsers, but probably not for text browsers and screen readers.

So if we don't want the entire "site map" splashed on the disabled users' face when they enter, it (the submenus) shoud either be at the bottom of the page or made javascript-dependent altogether.

So this might not be that minor after all, and not primarily a usability issue but one of accessibility.

Show
Olli Savolainen added a comment - - edited This will actually not really be resolved by the issue I linked this to. The actual issue is that javascriptless browsers, text browsers and screen readers will have to wade through that entire list before getting to content. Adding a skip to content link will alleviate this. But I think the only real solution is to only have the top-level links visible without javascript and have the submenus on the target pages. Hiding them with CSS and then disabling that CSS with javascript solves the issue for CSS-enabled browsers, but probably not for text browsers and screen readers. So if we don't want the entire "site map" splashed on the disabled users' face when they enter, it (the submenus) shoud either be at the bottom of the page or made javascript-dependent altogether. So this might not be that minor after all, and not primarily a usability issue but one of accessibility.
Hide
Juha Kari added a comment -

Please consider solving the problem with pure CSS: http://www.grc.com/menu2/invitro.htm

GRC's Script-Free solution is a neat one. It can be enhanced with JavaScript if needed.

Show
Juha Kari added a comment - Please consider solving the problem with pure CSS: http://www.grc.com/menu2/invitro.htm GRC's Script-Free solution is a neat one. It can be enhanced with JavaScript if needed.
Hide
Olli Savolainen added a comment -

That's a start, sure. But the above issues I mentioned still apply? That is, it is problematic to push an enormous list before content on text-only or screen reader users. It seems to me that the first thing to do would be to add a skip link.

Show
Olli Savolainen added a comment - That's a start, sure. But the above issues I mentioned still apply? That is, it is problematic to push an enormous list before content on text-only or screen reader users. It seems to me that the first thing to do would be to add a skip link.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated: