Designing and Developing for Accessibility
Designing and Developing for Accessibility
Designers and developers need to work together to ensure the sites they’re working on are accessible to those with disabilities.
To adhere to accessibility guidelines, web developers and designers can do the following:
Use headings appropriately to convey hierarchy.
Use <h1> through <h6> tags for page headings, and be sure to use them in the proper order (e.g., <h1> precedes <h2>). Use CSS to style heading tags:
<h1>The Future of Northeastern Retirement Benefits</h1>
Style text with CSS rather than use images.
Do not create graphics that look like text. Use text and style it with CSS instead:
<h2 class="introBlurb">Northeastern University opens its doors to all who work hard and dream big.</h2>
Ensure the site is readable with stylesheets disabled.
If you disable CSS, the site must be readable and logical. It may be less visually appealing, but the site should not be confusing or lose information.
Use skip navigation links.
“Skip nav” links allow users to jump to the content and skip the repetitive navigation links. You can display the skip nav link at the top of a page or use CSS to hide it until the link is active.
Do not use display: none; to hide the skip nav link, or else it will also be hidden from screen reader users. Instead, use a negative value for margin-left to “hide” the link until it has focus.
<p if="skipNav"><a href="mainContent">Skip to Main Content</a></p>
Use device-independent code.
Label form elements.
Visually impaired people may need a screen reader to associate a form’s input elements and labels. If the input elements aren’t labeled appropriately, the user may complete the wrong field or be unable to access the form.
<label id="name"> Name (first and last name):</label> <input type="text" id="name" value="name" size="20" />
Caption all video and audio.
Video and audio files should have synchronized captions. Videos without audio should have an accompanying audio track to describe the video for the blind or vision impaired.
Don’t rely on color to convey meaning.
Color-blind users may have trouble with a website if color is used to convey important information. Avoid instances like “Click the green button to proceed” and instead opt for using color for aesthetics and providing contrast only.
Ensure appropriate color contrast.
Use tools such as contrast analyzers to measure the contrast among graphics, fonts, and backgrounds on your page. Users can change the site’s contrast to suit their needs if you used plain text instead of images of text.
Mark up data tables correctly.
Tables are reserved for tabular data, not page layouts. Designate row and column headers with <th>. Use the <thead>, <tbody> and <tfooter> tags. Use the scope or id/header attribute to associate data with the appropriate header(s).
Use descriptive text for links.
Screen reading software scans a page for links and provides the list to the user. Numerous “click here” links are useless when separated from their context. It’s better to use descriptive text such as “Explore our academic programs.”
Identify links to PDFs, Word documents, Excel spreadsheets, etc.
This is important for screen reader users, but it’s also useful for sighted viewers who may not want to open another software program. Include the document designation in the link so that it will be read by screen readers:
<a href="documents/uc_mission.pdf" >Northeastern Mission Statement (pdf)</a>
Open off-site links in the same browser window.
Modern browsers offer tabbed browsing, so a user has control over whether to open a link in a new tab or new window. By forcing an off-site link to open in a new browser window, you are taking away that control from the user. Additionally, some older versions of screen reading software do not notify users when they open a new browser window. Users won’t know what has happened until they try to use the “Back” button and find they can’t go back.
Don’t use frames. If you must use them, correctly markup frames and iframes.
Frames are not inaccessible to modern screen readers, but they do introduce accessibility issues. Add title attributes to all <frame> and <iframe> tags. If you must use frames, provide equivalent content (or a link to it) within the <noframe> tags. Similarly, when you’re using iframes, provide equivalent content (or a link to it) within the <iframe> tags. This allows a user to access the content directly if his/her browser doesn’t support frames or iframes.
Give a user sufficient time to respond to timed content.
When a timed response is required, alert users and give them sufficient time to respond. People with mobility issues may have difficulty with limited time constraints.
Don’t create flickering pages or multimedia.
To prevent seizures among optically sensitive users, don’t create any pages or multimedia that flicker between 2 to 55 times per second.
Validate HTML and CSS.
IT accessibility begins with clean, valid code, so be sure to check your code with code validators.
Check for IT accessibility compliance.
Use accessibility checking tools to verify that your webpage is accessible.