WVU is required to have Web pages and Web applications that are accessible for the disabled according to Section 508 of the Americans with Disabilities Act.
Common Mistakes to Avoid
Below are some common accessibility mistakes content editors make when adding content to their site. Be careful not to make these mistakes.
- Using in-line attributes to style an object: Do not use in-line attributes to style tables, Twitter widgets, etc. e.g. "frameborder", "cellspacing", etc.; these styles should be defined by your Prof. Tech using CSS.
- Using non-distinguishable links: If you have two links labeled the same, they should point the user to the same destination. Either change the link, or change the label to more specifically reference what you are linking to.
- Not using proper markup for headers: For headers, use <h2>, <h3>, <h4>, etc. tags (or select from the Block Format dropdown menu in the editor if using CleanSlate), not <strong> or <u> tags.
- Not using titles for iFrames: When you embed a YouTube video, Twitter widget, or any other element in an iFrame, you must use a title attribute.
- Insufficient link text: Do not use “Read more” or “click here” as link/button text. The text should describe what the user is clicking on e.g. “More about x, y, z.”
Using anchor tags incorrectly: When linking to a page anchor (for
example with a list of FAQs), do not use the
name="my-anchor". Use an ID instead e.g.
id="my-anchor". The ID must apply to an actual page object e.g.
<div id="my-anchor">Here is my content</div>, as opposed to an empty one e.g. <a name="my-anchor"></a>.
- Using infographics that do not have a text alternative: Do not create graphics to display complex text layouts. If you do, provide a plain text alternative below or on another page, then link to it below the graphic.