Well you could do a lot more to tidy up that source code and make the page more accessible. For example, putting that list of navigation links into an unordered list and removing decorative images (such as deilogo.jpg and maroonline.jpg) from the HTML source and applying them as backgrounds to other elements using CSS. Using more descriptive alt text for the images that are content, because you actually have the same alt text four times for a group of different images and it's not very helpful, "GlenEchoPark", also note that there are three words there, but it's written as one.
For your nav links I would suggest something like this:
Users of graphical browsers won't see it, but screen readers will dutifully read it out.
Note that I've also disposed of those <br> elements, you can use CSS to create new lines of links if you want, but a better alternative would be to apply a width to the parent <ul> and apply display:inline to all of the <li>'s. The <li>'s will then sort themselves out into multiple lines.
You could also use the <ul> to display your logo. Just put some left padding on the <ul> then set the logo as a background image, and the maroon line could be replaced with a bottom border on the <ul>.
I briefly mentioned it earlier, but I'll say it again, you never include any spaces in your alt text for the images. By not using spaces you're effectively shutting out blind users and search engines, because it won't make any sense when read out as a single word.
Every fight is a food fight when you’re a cannibal.
I'd like to just pipe up and question the motives of what you're doing.
Skip links are fine, but why hide them? If, sorry, when they receive focus, how does anyone know what to do with that focus? the link is hidden. This presents a usability problem. In terms of accessibility, if your content is marked up with headers then most assistive user agents will navigate a document by the headers making the skip link redundant. The point is to deliver content from the initial load of a page and skipping the navigation and any other stuff in the process. Headers above the content resolve this.
There are many arguments for the pros and cons of skip links. Personally, I don't feel they're needed if the site is structured well. If you feel inclined to offer a skip link facility then show it. Sometimes, CSS part loads, some have this turned off and some devices offer narrow view so visible skip links offer a means of getting straight to the content without scrolling, something which is awkward on some PDA's and SmartPhones.
Providing links that allow the user to skip directly to content, bypassing the navigation, enhances the accessibility of your web site. This is recommended for blind or visually impaired users, people who use screen readers, and also for text-browsers, mobile phones and PDAs (Personal Digital Assistants).
These links are common on most US, UK, Irish, and other government websites, as well as many universities and private organizations.
From the accessibility and usability point of view, it is recommended that you make such links visible. Why?
In his article titled "Providing Skip Links", Frank Gayne of frontend.com explains:
"Skip links would be useful for people who cannot easily use a mouse. Many of these people depend on tabbing in order to make progress through an interface and might appreciate a skip links feature to lighten the amount of work they have to do. If there is no visible focus to let these people know they have hit a link, then this useful feature is lost to them."
How can you build such links? Immediately after the logo of your web site, insert the skip link: "Skip to main content". Does the link have to go after the logo? Many web sites have the "Skip to main content" links before the logo of the page, but a logo is the precursor of a web page. It lets the user know what website he/she is on.
For example, if a Screen Reader user clicks an internal link on your page, your logo's alternate text attribute tells the user that he/she has not yet left your website. If the "Skip to main content" link is before this logo, then the user does not know immediately which website he/she is on.
In many occasions, web site developers or their clients do not wish to have the "Skip to main content" link visible, with the excuse that it does not fit in their design. In this case they might use a technique wrapping the accessibility text or links in an HTML div setting it to display: none or visibility: hidden.
The problem with this technique is that it does not always work as expected. Some screen readers do not speak material that is marked display: none or visibility hidden, and others depend on how the style is specified. To solve this problem, you could make them invisible with the technique of using transparent graphics.