Skip to main content
. 2016 Jun 9;18(6):e157. doi: 10.2196/jmir.5442

Table 2.

Barriers and facilitation measures categorized by the ‘perceivable’ foundational principle of Web accessibility.

Barrier Facilitation measure
Unable to locate information [34] Provide intuitive navigation and ensure information filters and search functions work properlya.
Nonperceivable icons [34] Avoid complicated language and ensure menu options and links are easy to understanda.
Too small font [30] Increase font sizeb.
Difficulty reading small font and with eye strain [42] Use small but legible font and refrain from using graphics in websites with shallow information hierarchies that do not feature navigational listsb [39].
Use large navigation buttonsa [32].
Use a minimal number of colors that differentiates information and contrasts wella [31].
Use a simple design with pages that are pleasing to the eye and easy to reada [31].
Use graphics that are purposeful to the websitea [31].
Prominently present hyperlinks: ensure clear labeling and highly visible positioningb [37].
Make hyperlinks' text as explicit as possibleb [37].
List hyperlinks for a given topic together in a single columnb [37].
Font size, buttons, and links should be sufficiently large to ensure usabilitya [42].
Use attention grabbing and not boring designb [40].
Guideline 1.1: Provide text alternatives for any nontext content so that it can be changed into other forms people need, such as large print, braille, speech, symbols, or simpler languagec [23].
Guideline 1.2: Provide alternatives for time-based mediac [23].
Guideline 1.3: Create content that can be presented in different ways (eg, simpler layout) without losing information or structurec [23].
Guideline 1.4: Make it easier for users to see and hear content including separating foreground from backgroundc [23].
Guideline 5: Ensure that the user can control the behavior of viewports (ie, screen) and user interface controls, including those that may be manipulated by the author (eg, through scripts—list of computer commands)c [44].
Guideline 3: Support the creation of accessible contentc [43].
Guideline 2: Generate standard markup (ie, document annotations)c [43].
Guideline 1: Support accessible authoring practicesc [43].
Guideline 7: Ensure that the authoring tool is accessible to authors with disabilitiesc [43].
Guideline 2: Ensure that users have access to all content, notably conditional content that may have been provided to meet the requirements of the Web Content Accessibility Guidelines 1.0c [44].
Guideline 3: Ensure that the user may turn off rendering of content (eg, audio, video, scripts) that may reduce accessibility by obscuring other content or disorienting the userc [44].
Guideline 4: Ensure that the user can select preferred styles (eg, colors, size of rendered text, and synthesized speech characteristics) from choices offered by the user agent. Allow the user to override author-specified and user agent default stylesc [44].
Guideline 11: Allow users to configure the user agent so that frequently performed tasks are made convenient and allow users to save their preferencesc [44].

aFacilitation measure derived from expert opinion of researcher(s) conducting a study.

bFacilitation measure derived from empirical evidence.

cFacilitation measure derived from working group of experts.