Professional Documents
Culture Documents
Mike Park
e-Accessibility Services
Mada, Qatar Assistive Technology Center
Office: +974 4459 4063
E-mail: mpark@mada.org.qa
Page | 1
Table of Contents
Page | 2
Website Accessibility / Usability Best Practices
Checklist
Introduction
References:
1. Some of the items in this checklist may directly quote references from the
W3C WCAG 2.0 Guidelines; http://www.w3.org/TR/WCAG/
2. Some of the ideas for usability were referenced from the BBC website;
My Web My Way; http://www.bbc.co.uk/accessibility/
Page | 3
Accessibility Standards and Guidelines
Usability Priority 1
Usability Priority 2
Usability Priority 3
Page | 4
Accessibility Tools and Methods
Usability Testing
Conducting usability tests with a screen reader and keyboard will ensure the
following;
Web content and functional components are in a logical and priority
reading order
Non-text elements are properly labeled with text equivalent
The content or application is keyboard accessible
The website will be usable to all Assistive Technology (AT) users
When conducting AT usability tests, use the free Screen Reader; NVDA
Website: http://www.nvda-project.org/
Page | 5
Accessibility Resources
Page | 6
Qatar Website Accessibility / Usability Best Practices Checklist
Use CSS and DIV element for Website layout and design.
WCAG 2.0 (A)
Reduce the number of colours and keep the website design simple
Usability Priority 1
Keep the website design and layout consistent. WCAG 2.0 (A)
Page | 7
2.0 - Colours and Contrast
Web content colour combinations must also be tested for people with
colour blindness. Use the Color Contrast Analyzer 2.2 to
achieve 4.5:1 or better contrast; use Show contrast result for colour
blindness; Normal, Protanopia, Deuteranopia, Tritanopia
Usability Priority 1
Use the Color Contrast Analyzer 2.2, from The Paciello Group.
Used for measuring colour contrast between foreground and background
content. The software checks for WCAG 2.0 colour contrast compliancy
level AA and AAA. Usability Priority 1
Reference heading; Accessibility Tools and Methods
Colour alone should not be used as the only visual means of conveying
information, indicating an action, prompting a response, or distinguishing a
visual element. WCAG 2.0 (A)
Create simple, usable, visual layout of all web content and use a
consistent style of presentation between pages.
WCAG 2.0 (AA and AAA), Usability Priority 1
o Align: left align all content to the left side of the web page. Also left
align table headers and headings in page sections, etc
Page | 8
4.0 - Multi-Media Content
Page | 9
o If a Flash application is not accessible, provide an alternative text
equivalent with detailed descriptions or create a clearly labeled link
to the HTML web version
o The Flash application should be fully operable with a keyboard
o Like web pages, the Flash functions and scenes must operate and
behave in predictable ways, as an example; avoid using auto
refresh or re-directs
o Avoid creating mouse only functionality like; sliders and drag and
drop
o All non text elements and content must have text equivalents;
(text labels)
o All operable controls must be labeled appropriately to reflect
functionality. Example; Label the play button as Play, not Play
button
o Arrange all elements and content so it may be read in a logical
tab / reading order sequence
o Provide text alternative for meaningful audio content (Captions)
o If possible, avoid playing audio after the Flash loads, otherwise a
Pause Audio button must be available at the top of the reading
order within the application so AT users using keyboard can stop
the audio
o Accessible volume control must also be available for A/V content
o Provide synchronized captions for all video content
o Usability: Test the Flash application with a keyboard and Screen
Reader to make sure it is usable. This will ensure usability of most
Assistive Technology (AT) devices
o WCAG 2.0 guidelines apply to Flash content and elements.
Example; Colour Contrast minimum contrast (AA)
o Also refer to WCAG 2.0 guideline references for Flash developers
o Flash can be made accessible, follow the link to learn how:
http://www.adobe.com/accessibility/products/flash/
Page | 10
WCAG 2.0 (A) Meaningful Sequence
Content and elements are read in a logical, intuitive order; determined by
code order.
Examples: Logical reading order in Form Fields, Content and Menus
WCAG 2.0 (A) Provide a text equivalent for every non-text element on
your web pages which include: images, embedded objects (e.g. Flash),
audio, video, etc
Use the ABBR and ACRONYM elements to denote and expand any
abbreviations and acronyms that are present. Example: <acronym
title="World Wide Web">WWW</acronym> WCAG 2.0 (AAA)
Page | 11
Only use list elements for actual lists, not formatting effects
WCAG 2.0 (A)
o Use the list element on actual lists; it serves a functional purpose
in Screen Reader usability
o Use list elements appropriately for; Short Phrases and Words
o Use ordered list for Numbered lists
o Use unordered lists for Bullets
o Avoid substituting the Paragraph element with the List element
o Avoid using ONLY numbers, dashes and image bullets without
using the actual list element mark-up
Page Titled: All web pages have unique titles that describe topic or
purpose. Page title should reflect navigation level WCAG 2.0 (A)
Examples:
a) Mada QATC, home
b) Mada QATC, About, Staff
If Paragraphs are used, use the <p> tag paragraph element and avoid
repeatedly using and substituting it with the break element <br>.
Divide large blocks of text into manageable, short paragraphs <p>.
WCAG 2.0 (A)
If possible, Lines of text should not be longer than 70 characters; this also
includes spaces in-between words. Usability Priority 2
Timing Adjustable: For each time limit that is set by the content, the user
should have the ability to; Turn Off, Adjust or Extend the time. There are
exceptions on online time dependent functions such as; Online Auctions
WCAG 2.0 (A)
Page | 12
Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating
information;
o There is a clear mechanism to pause, stop or hide the content
o Auto updating information: control the frequency of the update
o There is an exception if it is part of an activity where it is essential.
WCAG 2.0 (A)
Provide a text alternative for content rendered using the object element.
The body of the object element can be used to provide a complete text
alternative for the object or may contain additional non-text content with
text alternatives.
WCAG 2.0 (A) When using complex images; charts, flow charts and
diagrams, use LONG description attribute in the image source tag
linked to a text only equivalent webpage.
o Sample code;
<IMG SRC="graph1.gif" LONGDESC="graph1.htm" ALT="Mada Expense Graph">
Create a webpage; graph1.htm describing in detail the
equivalent visual chart. If necessary, in addition to the
description, also create an accessible data table that reflects
the visual chart data
WCAG 2.0 (A) If an image is used for only decoration and has no
function or meaning, do one of the following so AT may skip over it;
a) The image should be embedded in the CSS code and not in HTML
b) In HTML; include a blank quote in the ALT text attribute of the
image tag. <img src=file.gif Alt= title=put title here>
When using animated gifs, appropriately describe the image in the Alt
text. Slow down image frame transitions, the time in between each frame
should be set to a minimum of 3 seconds. Usability Priority 1
Page | 14
When using Image Maps, provide Alt text description for every hotspot
area and the image itself. If possible, provide alternate text links below the
image map. WCAG 2.0 (A)
Organize web pages so users may read / view web pages without
associated style sheets. Usability Priority 1
Use CSS and DIV elements for styling and the layout structure of the
website while avoid using tables. WCAG 2.0 (AA)
Create all website navigation menus with List, Div elements and CSS
styling. Usability Priority 1
All Text, font styles, HTML mark-up and attributes should be controlled
with CSS. WCAG 2.0 (AA)
b. Font Size Adjuster User has the ability to change the font size of
the website. Create a tool to adjust font size starting at CSS 90% to
200% for English website, CSS 130% to 240% for Arabic website
WCAG 2.0 (AAA), Usability Priority 2
Page | 16
o Provide accessible NOFRAMES content. WCAG 2.0 (A)
9.0 - Tables
If this table is used for layout only, do not use structural markup to
achieve formatting effects. WCAG 2.0 (A)
Keep tables simple while trying to utilize all rows and columns. Avoid
leaving too many cell spaces blank; use the dash - character in place of
empty data cells. Usability Priority 1
If this is a data table (not used for layout only), use the Caption element
as the title of the table. WCAG 2.0 (A)
Complex Tables: If multi headers are used with complex row and column
spans; Use Table; ID, Axis and Scope attributes. WCAG 2.0 (A)
10.0 - Text
English Text
o Use open typeface; San-Serif, recommended fonts are Verdana or
Arial. If possible, avoid using Serif style typeface.
o Minimum Font size, CSS 100%, equivalent to 12 points
o Fonts must be able to scale to 200% without clipping or run off
Arabic Text
o Use Arabic Naskh Type, equivalent web font;
Comic Sans MS, Cursive, Arial or Tahoma as second choices
o Minimum Font size, CSS 140%, equivalent to 16 points
o Font must be able to scale to 240% without clipping or run off
o Use the Right to Left attribute for Arabic text; code: dir=rtl
Page | 17
When using CSS fonts, always use scalable relative sizing (%)
11. 0 - Headings
Make sure header elements are not used only for bold text formatting
WCAG 2.0 (A)
Page | 18
12.0 - Links and Labeling
Create link phrases that make sense when read out of context.
Example: avoid using phrases like; Click Here, "More", Read More
and http://www.mada.org.qa, use simple concise descriptive link phrases
that describe link destination. WCAG 2.0 (A)
When using Images as links; the Alt text must be used at all times. Do
not describe the image itself, describe the link destination. Also avoid
repeating the link phrase from an image ALT and adjacent text link
phrase. Usability Priority 1
The reading (Tab) order of all links in the website should be consistent
and logical. WCAG 2.0 (A)
Page | 19
o The file name itself must be descriptive for filing and retrieval
purposes. Name the file the same as the link phrase with the proper
file extension
o Avoid linking directly to an image without properly describing it in
the link phrase. If possible, as a best practice, avoid linking directly
to images. Instead, place the image on a webpage and describe it
in the ALT attribute.
Example; link phrase for images Mada logo (JPG image)
Separate adjacent links with more than just white space, use
characters like |. Example: | About | Services | Links |
Usability Priority 1
Text links should have sufficient space around it for the user to be
able to accurately select the link, especially when several links appear
together. There should be a minimum of four pixel padding around a link;
or equivalent. Usability Priority 1
If there are logical groups of links, make sure they are clearly
identified. As an example, create a page section heading and use the list
element to list underlined descriptive link phrases. Usability Priority 2
Multiple Ways: More than one way is available to locate a web page
within a set of web pages. Example: Create a site map page with nested
hierarchal unordered list link navigation. WCAG 2.0 (AA)
Page | 20
Avoid creating combo box Jump menus without instruction or
notification of such a behavior. WCAG 2.0 (A)
Create a simple, consistent and fully visible Main Menu and Sub
Menu system for the entire website. The Tab order must be consistent
and flow logically from level 1 menus to level 2 and 3 sub-menus.
WCAG 2.0 (A)
Main Menus; if Mouse over, reveal hidden Sub Menus are used,
also provide a fully visible text menu WCAG 2.0 (A)
o Make hidden sub menus accessible by keyboard in a logical Tab /
Focus order sequence
o When using mouse over to reveal hidden sub-menus; make sure
the menu interface area around the links have sufficient space /
Page | 21
padding (2 character space)
Page | 23
Example Code:
CSS:
.req {font-size: 150%}
HTML:
<p> Required fields are marked with an asterisk
(<abbr class="req" title="required"> * </abbr>).</p>
<form action="http://www.test.com" method="post">
<label for="firstname"><abbr class="req" title="required">*</abbr> First name:</label>
<input type="text" name="firstname" id="firstname" />
Focus Order: Make sure all objects and elements that are dependant on
the TAB key are in a Logical reading order Sequence. WCAG 2.0 (A)
Thoroughly test all web programs and functions for usability with a
keyboard and screen reader. Usability Priority 1
Avoid using Java script event handlers that require only the use of a
mouse. Example: Avoid using event handlers like onMouseOver
exclusively. WCAG 2.0 (A)
Keyboard: Make sure that all elements that have their own interface are
operable with a keyboard. WCAG 2.0 (A)
Page | 24
Include keyboard shortcuts to important links so keyboard users will
be able to easily navigate around the website. Caution must be exercised
in assigning keys as the key assignment can conflict with existing keys
used in; Browsers, Windows and Assistive Technology (AT). Use the
accesskey attribute and use keys 0 to 9
Usability Priority 2
Make sure your web pages validate to current W3C coding practices.
Properly define the DOCTYPE element and use the appropriate HTML
markups. Mark-up content with the most current, good structural
standards compliant code (W3C). WCAG 2.0 (A)
On Input: Changing the setting of any user interface component does not
automatically cause a change of context unless the user has been advised
of the behavior before using the component. WCAG 2.0 (A)
Page | 25
No Keyboard Trap: Ensure that keyboard users do not become trapped
in a subset of the content that can only be exited using a mouse or
pointing device. WCAG 2.0 (A)
Error Prevention (Legal, Financial, Data): For web pages that cause
legal commitments or financial transactions for the user to occur, that
modify or delete user-controllable data in data storage systems, or that
submit user test responses, at least one of the following is true:
Reversible: Submissions are reversible.
Checked: Data entered by the user is checked for input errors and the
user is provided an opportunity to correct them.
Confirmed: A mechanism is available for reviewing, confirming, and
correcting information before finalizing the submission.
WCAG 2.0 (AA)
Page | 26
Appendix A - WCAG 2.0 Guidelines
Note: These are active links to the W3C WAI WCAG 2.0 guidelines
Principle 1: Perceivable
1.1 Text Alternatives: Provide text alternatives for any non-text content so
that it can be changed into other forms people need, such as large print,
braille, speech, symbols or simpler language.
1.3 Adaptable: Create content that can be presented in different ways (for
example simpler layout) without losing information or structure.
1.4 Distinguishable: Make it easier for users to see and hear content
including separating foreground from background.
Principle 2: Operable
2.2 Enough Time: Provide users enough time to read and use content.
2.4 Navigable: Provide ways to help users navigate, find content, and
determine where they are.
Principle 3: Understandable
3.2 Predictable: Make Web pages appear and operate in predictable ways.
Principle 4: Robust
4.1 Compatible: Maximize compatibility with current and future user agents,
including assistive technologies.
Page | 27