Class+Pages+for+the+University+of+Maryland,+Computer+Science

[]

Principle 1: Perceivable - Information and user interface components must be presentable to users in ways they can perceive.
All information are text based hyperlinks. There is no non-text content, time based media. It's structure is very adaptable - a straight forward list, sorted reverse chronologically by semester, and then by increasing course number. However, the majority of the page consists of blue hyperlinks. Since most of this page is blue text, there is very little black text to contrast the link color with. Since the color primarily conveys to the user what text is a link and there is no current alternative, it is not very distinguishable. [] shows how blue links may appear to someone with varying degrees of color blindness.
 * Partial Implementation**

Principle 2: Operable - User interface components and navigation must be operable.
Without any special software, all links on the page can be selected with tab, and reverse selected with shift-tab. Browser extensions exist that allow an even more keyboard-centric experience, such as [|Gleebox]. The page is static, so users have as much time as they need to navigate the page. There are no flashes. The page is properly titled, and a cookie crumb nav bar shows you what page you're on in relation to the home page. Easily distinguishable titles break up the sections by semester and year.
 * Complete**

Principle 3: Understandable - Information and the operation of user interface must be understandable.
The majority of the text are either technical terms related to computer science, or the names of the professors/lecturers, proper nouns. The page behaves as expected and only responds when the user initiates an interaction. There are no user inputs which require correction.
 * Complete**

Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
The page is a straightforward HTML list, using the unordered list tag  and  for individual class webpages. Headers are categorized appropriately, with titling the page, and titling subsections. All tags are unique in there purpose (for example, no headers are used in list items).
 * Complete**