WordPress websites must be developed in accordance to ODU’s Information Technology Accessibility Standard which follows WCAG 2.2 standards. ADA compliance is not a WordPress function, it is a web site designers responsibility to comply with the requirements using the tools available within the application.
The purpose of this standard is to ensure that information technology at Old Dominion University is compliant with the standards and requirements set forth in Section 504 of the Rehabilitation Act of 1973, the Americans with Disabilities Act of 1990, and the subsequent amendment to the Rehabilitation Act, Section 508 of the Rehabilitation Act.
Site designers should frequently consult and comply with all aspects of the information outlining requirements for the visual representation and application operation and response within their sites. Links to the ODU Accessibility Standard, Federal Accessibility Standard, and W3C’s Accessibility Initiative are included on this page for reference. In general the following items should be considered when implementing websites and applications.
Software Applications and Operating Systems
When software is designed to run on a system that has a keyboard, product functions will be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.
Applications will not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards.
Applications will not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.
A well-defined on-screen indication of the current focus will be provided that moves among interactive interface elements as the input focus changes. The focus will be programmatically exposed so that assistive technology can track focus and focus changes.
Sufficient information about a user interface element, including the identity, operation, and state of the element, will be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text.
When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images will be consistent throughout an application’s performance.
Textual information will be provided through operating system functions for displaying text. The minimum information that will be made available is text content, text input caret location, and text attributes.
When animation is displayed, the information will be displayable in at least one non-animated presentation mode at the option of the user.
Color-coding will not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels will be provided.
Software will not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 72 Hz and lower than 55 Hz.
When electronic forms are used, the form will allow people using assistive technology to access the information, field elements, and f
Web-based Intranet and Internet Information and Applications
A web site will ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. WAI WCAG checkpoint 2.2.
The opening of new browser windows should only be done if the user is notified that a new window will open and there may be a possibility of functional difficulties.
Use style sheets to control layout whenever possible
Do not use tables for layout unless the table makes sense when linearized.
Font sizes should be percentage based instead of fixed.
A method will be provided that permits users to skip repetitive navigation links. (See: WATG for details.)
Content headers will use the Heading Element (H1 through H6) hierarchy, although style sheets may be used to modify the size and other characteristics of that text.
This Standard applies to all Web sites supported by the University, except downloadable documents (e.g. Word document, PowerPoint presentation, PDFs, etc.) although accessible and equivalent versions of the content must be available.
HTML frames are forbidden when in the visual template.
Title frames with text that facilitates frame identification and navigation.
Procedures, Guidelines & Other Related Information
W3C’s Web Accessibility Initiative
Office of Educational Accessibility