Skip to main content
Get your Wikispaces Classroom now:
the easiest way to manage your class.
Pages and Files
Accessibility - math department website
Accessibility - Philosophy Department
Accessibility - Tammy Tran
Accessibility Assignment SEE
Accessibility Submission, Andrew Palma
Accessibility Submission, Ghassan Abu-Ghaida
Accessibility Submission, Ian King
Accessibility Submission, Janahan Sivaraman
Accessibility Submission, Kevin Van
Accessibility, Jennifer Gorski
Accessibility, Mark Stewart
Accessibility, Matt Orlove
Aida's Home Page
Aida's Login Page
Add "All Pages"
Accessibility - Tammy Tran
ACCESSIBILITY of the UMD Bursar Web Site
Tammy Tran (UID: 111917440)
(this webpage does not contain any non-text content)
(this webpage does not contain any time-based media)
Information is presented in a simple structure by using table markups to organize the content. Because this page is very simple, the HTML is not too complex. Unfortunately, table cells are not labeled with supporting id and header attributes. White space characters are used improperly in the source code to format tables and labels. Furthermore, CSS is not used to portray textual content in a uniform aesthetic throughout the site. For example, heading tags are not used to orderly portray headers, and there is no universal pattern/standard for how headers, links, and regular text are displayed. As a result, interpretation of page content is very reliant on visual sensory. In general, though the content of this page is presented in a simple structure, the HTML semantics used to create this page is not very organized and therefore not completely adaptable.
The one distinguishable feature about this page is that all text is of large enough font to be highly visible and readable. Unfortunately, the use of color, sizing, and contrast makes the text very indistinguishable between headers, links, and text. There is no aesthetic cohesion between similar page content; especially in the top banner. Each header is displayed in a different manner (i.e. some are underlined, each is highlighted in a different color – creating very poor contrast between the text and its background) and it is unclear what is a link versus a header. Due to the in-cohesiveness of the page’s content, this page is not quite distinguishable.
This page has no features that allow the users to navigate using any keyboard controls; navigation is soled dependent on “pointing-device-specific event handlers”.
(this webpage does not contain any time sensitive content)
(this webpage does not contain anything that flashes)
The main reason why this webpage is only
navigable is due to the visual indistinctiveness of links. As mentioned earlier under “Distinguishable”, the in-cohesion of the content display makes it very hard to navigate between links and headers. Fortunately, wherever contents are distinguishable, headers and links are clearly labeled to describe its purpose.
All text on this webpage is readable and understandable. There are no uses of abbreviations and the ability to fully comprehend the content of this page merely requires mediocre reading abilities. Furthermore, the simplicity of this webpage does not require any advance mechanisms to assist with the readability and the ability to understand its content.
Due to the inconsistent presentation of navigational links and identification headers, this webpage is only partially predictable. It is very evident in the bottom half of this page which content is a header versus a link (i.e. headers are identified using all-caps, red labels, whereas all links are in blue font). Unfortunately, as mentioned above, the top banner of the page does not identify its headers and links in a consistent manner; therefore, the webpage does not completely appear and operate in a predictable manner.
(this webpage does not contain any input fields)
According to the WCAG 2.0 compatibility guidelines, this webpage appears to be fully compatible with alternative assistive technologies. The webpage’s HTML is complete in reference to its use of start and end tags, id attributes are well labeled and property attributes are well formatted. The simplicity of webpage makes it more compatible with current and future user agents.
Overall, the UMD Bursar webpage only
the WCAG 2.0 guidelines for accessibility. Though the design of this webpage is kept very simple (possibly for readability and compatibility purposes), as a result, the webpage is not very adaptable or navigable for all of its users. The UMD Bursar is used by most UMD students, despite race or disability, to acquire financial information and/or perform various financial services with the university through this interface. Due to the vast use and need of this webpage by the wide range of students at UMD, the accessibility of the UMD Bursar webpage is a crucial element, not to be overlooked.
help on how to format text
Turn off "Getting Started"