Paul, 
 
I stripped out my menu CSS code, so that the page only loads the styles
from the original core4.css (this is what the guys here said to do, and
apparently that's OOTB code)
 
I still have the same problem with not being able to trigger the menu
flyouts with the keyboard.
 
Has anyone had success with a 2010 menu that does work perfectly with
the keyboard? (SP2007's table based menu allowed you to press the right
arrow to open a flyout too)
 
 
It also doesn't appear to shift the flyout upwards when the flyout is
taller than the browser window (I haven't tried ideas from Dan and Paul
Noone yet... except :focus - tried that all over the place and it did
improve it, but not solve it)
 
 
any more ideas?
 
 

Kathleen Smith
Web Designer

Department of Innovation, Industry, Science and Research.

Industry House Level 4
10 Binara Street, Canberra City ACT 2601
GPO Box 9839, Canberra ACT 2601
Ph: 61-2-6213 6573
Email: [email protected]
Internet: http://www.innovation.gov.au
<blocked::http://www.innovation.gov.au/> 
ABN 74 599 608 295
P Please consider the environment before printing this e-mail

 

 

________________________________

From: [email protected] [mailto:[email protected]] On
Behalf Of Paul Noone
Sent: Monday, 20 June 2011 1:53 PM
To: ozMOSS
Subject: RE: SP2010 Main Navigation problems -
KeyboardaccessibilityandFlyouts [SEC=UNCLASSIFIED]



Apologies. OOTB = Out-Of-The-Box

 

The OOTB site templates will include CSS files that include all the
necessary styles. It's possible you've inadvertently overwritten one of
the style rules.

 

Are you using custom master pages? Publishing site layouts?

 

My suggestion would be to apply one of the default master pages to your
top-level site (don't push down changes!) and see if it works as
expected. If it does then you have a problem with your CSS, or are
perhaps missing a core JS file. NB: please do this in a stage or dev
environment.

 

Regards,

Paul

 

--

Online Developer/SharePoint Administrator,
ICT Infrastructure Team
CEO Sydney

 

From: [email protected] [mailto:[email protected]] On
Behalf Of Smith, Kathleen
Sent: Monday, 20 June 2011 1:34 PM
To: ozMOSS
Subject: RE: SP2010 Main Navigation problems - Keyboard
accessibilityandFlyouts [SEC=UNCLASSIFIED]

 

Paul, 

 

I have fully customised the CSS myself, to work with the LI and UL
layout of the menu. I don't know what an OOTB is....

 

(You'll have to forgive me as I'm primarily a graphic/web designer and
by no means a .NET developer. I just try to get things looking right via
CSS)

 

 

 

Kathleen Smith
Web Designer

Department of Innovation, Industry, Science and Research.

Industry House Level 4
10 Binara Street, Canberra City ACT 2601
GPO Box 9839, Canberra ACT 2601
Ph: 61-2-6213 6573
Email: [email protected]
Internet: http://www.innovation.gov.au
<blocked::http://www.innovation.gov.au/> 
ABN 74 599 608 295
P Please consider the environment before printing this e-mail

 

 

 

________________________________

From: [email protected] [mailto:[email protected]] On
Behalf Of Paul Noone
Sent: Monday, 20 June 2011 1:29 PM
To: ozMOSS
Subject: RE: SP2010 Main Navigation problems - Keyboard
accessibilityandFlyouts [SEC=UNCLASSIFIED]

Hi Kathleen,

 

I think Paul is just stressing that you need to apply the appropriate
style sheet.

 

Have you customised the nav CSS or is this an OOTB site?

 

Regards,

Paul

 

--

Online Developer/SharePoint Administrator,
ICT Infrastructure Team
CEO Sydney

 

From: [email protected] [mailto:[email protected]] On
Behalf Of Smith, Kathleen
Sent: Monday, 20 June 2011 1:26 PM
To: ozMOSS
Subject: RE: SP2010 Main Navigation problems - Keyboard accessibility
andFlyouts [SEC=UNCLASSIFIED]

 

Paul

 

Just to clarify, my menu is set up with UL and LI stuff - that's the
only way it works in UseSimpleRendering-true mode. (Naturally the CSS
for the 2007 menu wouldn't work unless UseSimpleRendering was set to
false.)

 

 

 

Kathleen Smith
Web Designer

Department of Innovation, Industry, Science and Research.

Industry House Level 4
10 Binara Street, Canberra City ACT 2601
GPO Box 9839, Canberra ACT 2601
Ph: 61-2-6213 6573
Email: [email protected]
Internet: http://www.innovation.gov.au
<blocked::http://www.innovation.gov.au/> 
ABN 74 599 608 295
P Please consider the environment before printing this e-mail

 

 

 

________________________________

From: [email protected] [mailto:[email protected]] On
Behalf Of Paul Turner
Sent: Monday, 20 June 2011 1:16 PM
To: ozMOSS
Subject: RE: SP2010 Main Navigation problems - Keyboard accessibility
andFlyouts [SEC=UNCLASSIFIED]

2010 natively doesn't use tables for menus any more, it is DIV/SPAN UL,
LI stuff that should be easy to apply CSS to.  But any 2007 CSS won't
work in 2010 because of this too, you need to review it for 2010 and fix
it as required.

 

http://blog.drisgill.com/2009/11/sharepoint-2010-w3c-xhtml-compliance.ht
ml

 

 

Regards

 

Paul Turner

Practice Lead - SharePoint

SMS Management & Technology


M 0412 748 168

[email protected] <mailto:[email protected]>  
www.smsmt.com <http://www.smsmt.com/>  

About SMS: Innovation House, Technology Park, Mawson Lakes Boulevard,
Mawson Lakes SA 5095
SMS Management & Technology (SMS) [ASX:SMX] is Australia's largest
publicly listed Management Services company. We solve complex problems
and transform business through Consulting, Technology and Systems
Integration

P please consider the environment before printing this email

 

________________________________

From: [email protected] [[email protected]] On Behalf Of
Smith, Kathleen [[email protected]]
Sent: Monday, 20 June 2011 9:38 AM
To: [email protected]
Subject: SP2010 Main Navigation problems - Keyboard accessibility and
Flyouts [SEC=UNCLASSIFIED]

All, 

 

In SP2010, I have been working on the new CSS menu system that is
enabled when UseSimpleRendering is set to true.

My team have found two main problems with this menu system, and I can't
seem to find any solutions. If we can't find solutions to these problems
we will be forced to switch UseSimpleRendering back to false, and rely
on the old table system instead. This would be a shame because it means
taking a step backwards which defeats the purpose of using 2010's new
menu system. (Both of these issues were not a problem in SP2007).

 

The two problems are;

 

1) The main navigation menu cannot be accessed using a keyboard. In our
situation, this is a deal breaker. When pressing the TAB key, if you
watch the status bar at the bottom of the window, you can see that the
URL is changing and it is working through the menu system, but there's
no visual way of knowing that this is happening on the menu bar. In
SP2007 this wasn't a problem.

 

2) Menu flyouts do not centre themselves vertically on the screen. For
example, if you roll over the bottom link on the navigation menu and it
has a corresponding flyout, and if this flyout contains a long-ish set
of links, the flyout will extend itself over the bottom of the screen,
making it impossible for the user to access those links. In SP2007, the
flyouts automatically re-positioned themselves to move up the screen in
a situation like this, making all links accessible. I read a post by
Brian (thanks Brian!) that suggested not having so many links in the
flyout to begin with, but we're not in a position to get the client to
do this. Their site didn't have these issues in the 2007 version, so
therefore we shouldn't have to make major changes the structure of the
site just to suit this problem.

 

 

I'm hoping somebody in this group has a solution, or at least some ideas
to work with

 

 

Cheers for now

 

Kathleen

 

 

 

************************************************************************
*
The information contained in this e-mail, and any attachments to it,
is intended for the use of the addressee and is confidential.  If you
are not the intended recipient you must not use, disclose, read,
forward, copy or retain any of the information.  If you received this
e-mail in error, please delete it and notify the sender by return
e-mail or telephone.

The Commonwealth does not warrant that any attachments are free
from viruses or any other defects.  You assume all liability for any
loss, damage or other consequences which may arise from opening
or using the attachments.

The security of emails transmitted in an unencrypted environment
cannot be guaranteed. By forwarding or replying to this email, you
acknowledge and accept these risks.
************************************************************************
*

 

________________________________

NOTICE - This communication is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking any action in reliance on, this communication by persons or
entities other than the intended recipient is prohibited. If you are not
the intended recipient of this communication please delete and destroy
all copies and telephone SMS Management & Technology on 1300 842 767
immediately. Any views expressed in this Communication are those of the
individual sender, except where the sender specifically states them to
be the views of SMS Management & Technology. Except as required by law,
SMS Management & Technology does not represent, warrant and/or guarantee
that the integrity of this communication has been maintained nor that
the communication is free from errors, virus, interception or
interference.

************************************************************************
*
The information contained in this e-mail, and any attachments to it,
is intended for the use of the addressee and is confidential.  If you
are not the intended recipient you must not use, disclose, read,
forward, copy or retain any of the information.  If you received this
e-mail in error, please delete it and notify the sender by return
e-mail or telephone.

The Commonwealth does not warrant that any attachments are free
from viruses or any other defects.  You assume all liability for any
loss, damage or other consequences which may arise from opening
or using the attachments.

The security of emails transmitted in an unencrypted environment
cannot be guaranteed. By forwarding or replying to this email, you
acknowledge and accept these risks.
************************************************************************
*

************************************************************************
*
The information contained in this e-mail, and any attachments to it,
is intended for the use of the addressee and is confidential.  If you
are not the intended recipient you must not use, disclose, read,
forward, copy or retain any of the information.  If you received this
e-mail in error, please delete it and notify the sender by return
e-mail or telephone.

The Commonwealth does not warrant that any attachments are free
from viruses or any other defects.  You assume all liability for any
loss, damage or other consequences which may arise from opening
or using the attachments.

The security of emails transmitted in an unencrypted environment
cannot be guaranteed. By forwarding or replying to this email, you
acknowledge and accept these risks.
************************************************************************
*


*************************************************************************
The information contained in this e-mail, and any attachments to it,
is intended for the use of the addressee and is confidential.  If you
are not the intended recipient you must not use, disclose, read,
forward, copy or retain any of the information.  If you received this
e-mail in error, please delete it and notify the sender by return
e-mail or telephone.

The Commonwealth does not warrant that any attachments are free
from viruses or any other defects.  You assume all liability for any
loss, damage or other consequences which may arise from opening
or using the attachments.

The security of emails transmitted in an unencrypted environment
cannot be guaranteed. By forwarding or replying to this email, you
acknowledge and accept these risks.
*************************************************************************

_______________________________________________
ozmoss mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

Reply via email to