While internally targeted Web pages may still have to comply with some aspects of the Web policy, they are specifically exempted from the Site Review process. Web Services is more than happy to review the site anyway if you have concerns about presentation, ADA compliance or other issues. Please review the Web Policy to determine the best approach.
Also, note that this is exempted specifically because it is password protected. If you have a site targeted internally but it is publicly available. Even though the audience is strictly internal, because anyone can see the site, it must be submitted for a Site Review.
Section IV.A.1.b. of the Web Policy specifies: "All official Web materials developed after July 1, 2003 must comply with Section 508 accessibility standards of the federal government. All official Web materials developed after October 1, 2005 must also comply with state statute KRS 61.980-61.988, the Governor’s ADA Taskforce for Postsecondary Institutions Guidelines for the Accessibility of Electronically Delivered Instruction and Services, and the Americans with Disabilities Act. All UK Web materials must comply with any additional legal or regulatory mandates with regard to accessibility in force at the time of the creation of those Web materials in accordance with University standards and guidelines provided by the Office of Public Relations. In situations of apparent conflict between or among these regulations, the Office of Public Relations will provide determination of appropriate action for the University. These accessibility standards supersede all other obligations including University requirements and code validation."
NOTE: This language was changed by the Web Advisory Committee this summer to include more of the governing regulations and also allow for interpretation of those regulations by the Office of Public Relations.
The bottom line here is that you should take all reasonable efforts to make your sites accessible to people with disabilities. If your images do not have alt attributes, you're not even trying. That said, most accessibility can be best dealt with by using current standards and modern design which already consider the issue.
The following is taken for the Site Point Tech Times Newsletter (http://www.sitepoint.com/newsletter/viewissue.php?id=3&issue=117)
Here's an HTML list. Dead simple, right?
<ul>
<li>List item</li>
<li>List item</li>
</ul>
List item
List item
Sometimes, your list items contain entire paragraphs of text, and you want to give each item a little breathing room. In the old days of presentational markup, you might cheat this by adding a line break after all but your last list item:
<ul>
<li>List item<br></li>
<li>List item</li>
</ul>
Nowadays, any good designer should run screaming from this practice. Instead, you can apply a margin to your list items with a little CSS:
<style type="text/css">
/* This should go in an external CSS file */
ul.para li {
margin-top: 1em;
margin-bottom: 1em;
}
</style>
<ul class="para">
<li>List item</li>
<li>List item</li>
</ul>
This will work just fine, but it turns out HTML provides its own semantically correct solution. If your list items contain paragraphs of text, why not just mark them up as such?
<ul>
<li><p>List item</p></li>
<li><p>List item</p></li>
</ul>
List item
List item
List items are among a select few HTML tags that can contain either inline tags or block tags. Other tags that can do this include <div>, <td>, <th>, <ins>, <del> and <dd>.
The definition of a guru might be when you can be referred to by your first name on a subject and everyone knows who you are. Eric Meyer, CSS guru, has developed a simple way to deal with a common IE bug involving child selectors. (If you don't know what that means, don't worry, you can skip this part until you get caught up on your CSS.)
Here's an example:
Eric’s simple solution gives us an antidote by turning the universal selector on itself, like this:
#nav * * {margin:0}
For the full details see http://www.sitepoint.com/blogs/2005/06/20/erics-universal-child-selector/
The new version is now out. Look for a full review at next month's Web Pubs meeting.
The main thing to remember here is that with non-HTML documents the user tends to think of them as separate files and not part of the Web. Consequently, your Web site should reflect this. Save opening new windows for these documents and keep all your Web pages in the same window.
Standards compliance from Microsoft? Maybe.
Two rules - Most PDF documents should not be PDF's and Some documents truly should be PDF's
Google is now going to start considering how long a domain has been registered as part of its search algorithm. This probably means nothing to most of us. However, it should help reduce the effects of phishing scams and spoofs (roughly 40% of users will click on the first link provided by a search engine).
Here are a couple of links that I found recently that may/may not be helpful:
TRAINING UPDATE: Web@UK - Wednesday, Oct. 5, 1:30-4 p.m., B108a William T. Young Library
Register:
http://www.uky.edu/
HR/HRD/Training/
ClassReg.html
South on October 17, 2 p.m., TBD
North on October 18,
2 p.m.,
TBD