Also, The CSS menu does not work too well if used “inline” on a whole page with inline divs.
As a result, its easier layer the menu above the page, thus showing bottom in the Freeway show item pallete. As a result the menu is shown last in the accessibility preview and last to be published in the code.
It looks like this is the way the Softpress site is done.
Is that a problem for accessibility or the search engines? Ernie would you like to comment?
Well, my thoughts are that earlier placement in the semantic order
makes more sense than later… choices about navigation are probably
not best as an afterthought.
That said, there are dozens of ways to make CSS menus – that Freeway
can make one for the casual user is great, but doesn’t mean that it
can’t be improved upon.
I admit that I haven’t tried this new feature yet – I suppose I
should take a look at it.
On Sun, Jun 15, 2008 at 2:35 AM, WebWorker wrote:
Is that a problem for accessibility or the search engines? Ernie would you like to comment?
Found a reasonable example here that could be adapted and styled.
I’m planning a quite large Freeway site, And this is where Freeway can be easier to have includes for common items like a CSS menu that is common to all pages, Master page items when inline just don’t work (hence layering the CSS menu action - but then its published last!).
Your technique of using FW5 code for items places direct on an other Freeway page is very handy for keeping things together in Freeway and including as php includes elsewhere on the site.
Here’s a simple and quick FW 5 example that uses the CSS menu action (drop-down) on an inline menu with 2 inline elements below it. It works fine though I haven’t looked at it in any flavor of IE.
That just it, it works when the layout is simple, but gets fiddly with a more complex layout. With some background div images that need to line up correctly.
And looking at mine, and your example on an IE6 box, layout and menus are all messed up. I’ve got a layout of none and my menu goes way of screen to the left
CSS menus possibly seem like a good idea, but in this case maybe its just a none starter, and something more traditional is needed.