Designing Pervasive Games Oriented Towards the Elderly: A Case Study

Abstract

Elderly people is a segment of population that is quickly increasing during the last years. In the digital society where we live, it is not bearable that this segment of population remains out of the advances in information and communication technologies. In fact, such advances have the potential to improve aspects such as memory or physical condition. This is the case of computer games, and, specifically, of pervasive games. They are a new genre of games in which some of the traditional boundaries of computer games get exceeded. Therefore, in this chapter we explain the design process of a pervasive game oriented towards the elderly and some assessment activities to validate it. The game implies the elderly moving in the real world searching some targets that have to be scanned with a mobile device with the game running. When this happens, the game unlocks a memory, which is a piece of information about a past event, a person or a place. Players store the memories unlocked in an album that can be accessed at any time. Testing of the game in a real environment has started, with some interesting feedback collected.

Appendix

1.1 Accessibility Assessment

In order to validate the application, we have analyzed the accessibility aspects considered according to WCAG 2.0 “Applies to Older People”.

Perceivable Information and User Interface.

This section explains how many of the Web Content Accessibility Guidelines (WCAG) 2.0 guidelines and success criteria specifically meet the needs of older web users. Although not all the WCAG 2.0 success criteria are applied here, we use WAI recommends meeting at least all WCAG 2.0 Level A and AA success criteria.

This section is organized under the four principles of web accessibility from WCAG 2.0: perceivable, operable, understandable, and robust. Success criteria are listed thematically, to help readability. Sometimes they are drawn from different guidelines to address a particular aspect.

Text Size

Large text has been applied due to decreased vision, including text in form fields and other controls. According to WCAG 2.0 success criteria:

• Resize text (AA): Text can be resized in the application without assistive technology up to 200 per cent without loss of content or functionality. We’ve applied techniques:

  • Using relative font-sizes such as percent (C12) or ems (C14) and ensuring text containers resize (C28).

  • Avoiding the use of text in raster images.

Text Style and Text Layout

The following aspects regarding the style of the text and its visual presentation have been taken into account. Since they influence the difficulty or ease of reading for people, especially older people with vision problems.

• Visual Presentation (AAA) some of the requirements on text style, text justification, line spacing, line length, and horizontal scrolling. We’ve applied techniques:

  • Avoiding fully-aligned text (C19)

  • Using readable fonts

  • Using upper and lower case according to the spelling conventions of the text language

  • Avoiding chunks of italic text

  • Avoiding overuse of different styles on individual pages and in sites

Color and Contrast

We apply various specifications for the use of color, paying special attention to those aspects that older people find it difficult to recognize, such as contrast and others:

• Use of Color (A) Color is not the only means of transmitting information, we normally apply it together with other indicators such as signs or text to identify buttons or the various sections of the app. Applied technique:

  • G14: Ensuring that information conveyed by color differences is also available in text

• Contrast (Minimum) (AA) as required a contrast ratio of at least 4.5:1 is applied for the visual presentation of text and images

  • Using a light pastel background rather than a white background behind black text to create sufficient but not extreme contrast

  • G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text

• Contrast (Enhanced) (AAA) as required a higher contrast ratio of at least 7:1 for the visual presentation of text and images

  • G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text

  • Using a light pastel background rather than a white background behind black text to create sufficient but not extreme contrast

Multimedia

Because the hearing or vision of many older people decreases, we have applied the following requirements:

• Extended Audio Description (Prerecorded video) (AAA) Applying the technique:

  • G158: Providing an alternative for time-based media for audio-only content

• 1. Low or No Background Audio (Prerecorded) (AAA). Applying the technique:

  • 1. No Background: The audio does not contain background sounds.

Text-to-Speech (Speech Synthesis)

We do not apply speech synthesis.

CAPTCHA

Captcha systems offer reading difficulties. Older people with low vision may not be able to distinguish characters in a CAPTCHA, especially since CAPTCHAs often have low contrast and do not increase in size when users have larger text. As a measure of success:

• 1. Non-text Content (A) includes a requirement for alternative CAPTCHAs. we decided not to apply forms with CAPTCHA, as is contemplated in the technique:

  • 1. Not requiring CAPTCHAs for authorized users

Operable User Interface and Navigation

Links

As many older people need the links to be particularly clear and identifiable due to impaired vision and cognition, we apply the following requirements:

• 1. Link Purpose (In Context) (A) the purpose of a link can be determined from the link text alone, or from the link text together with its surrounding context. We apply the technique:

  • 1. G91: Providing link text that describes the purpose of a link

  • 2. Limiting the number of links per page

  • 3. Making links visually distinct

• 2. Focus Visible (AA) requires a visible keyboard focus indicator that shows what component on the web page has focus. We apply the technique:

  • 1. Highlighting a link or control when the mouse hovers over it, or when it receives keyboard focus

Navigation and Location

Many older people require particularly clear navigation due to decreased cognitive abilities. The adaptations that we have taken into the app are the following:

• 1. Page Titled (A): “web pages have titles that describe topic or purpose”. We apply the techniques:

  • 1. G128: Indicating current location within navigation bars

  • 2. Providing a link to the home page or main page

Mouse Use

It is difficult for some older people to use a mouse due to declining vision or dexterity. This section is in relation to aspects that we have already described previously. We apply the following success requirements:

• 1. Focus Visible (AA) says that focus indicators should be visible. As we said previously we use the technique:

  • 1. Highlighting a link or control when the mouse hovers over it

• 2. Resize Text (AA) says that text should be resizable up to 200 percent. We apply the technique:

  • 1. Using real text with relative font size (C12, C14) and avoiding the use of text in raster images as larger text is easy to click.

Keyboard Use and Tabbing

The content cannot be operated with a keyboard interface, as it is an app developed for a mobile phone. This precept does not apply.

Distractions

Some older people are particularly distracted by any movement and sound on web pages. So we have included controls in the audio and video elements following the success requirements:

• 1. Pause, Stop, Hide (A): “a mechanism for the user to pause, stop, or hide'’ moving or blinking content. We apply the technique:

  • 1. G4: Allowing the content to be paused and restarted from where it was paused

• 2. Audio Control (A): “a mechanism is available to pause or stop the audio”. We apply the techniques:

  • 1. G4: Allowing the content to be paused and restarted from where it was paused

  • 2. G171: Sound playing only on demand.

Understandable Language

Many older people find it particularly difficult to understand complex sentences, unusual words, and technical jargon. For this reason, the sections have been drafted as clearly as possible:

• 1. Reading Level (AAA) requires providing a version that “does not require reading ability more advanced than the lower secondary education level”. We apply the technique:

  • 1. Using the clearest and simplest language appropriate for the content

Consistent Navigation and Labeling

For people who are new to the web, and older people with some types of cognitive decline, consistent navigation and presentation is particularly important.

• 1. Consistent Navigation (AA) requires that navigation is presented in the same relative order across a website. We apply the technique:

  • 1. G61: Presenting repeated components in the same relative order each time they appear

• 2. Consistent Identification (AA) requires that components with similar functionality are identified consistently. We apply the technique:

  • 1. G197: Using labels, names, and text alternatives consistently for content that has the same functionality

Pop-Ups and New Windows

Some older people experiencing cognitive decline can be confused or distracted by pop-ups, new windows, or new tabs.

This is how we have eliminated pop-ups that open without user request. As success requirements:

• 1. On Focus (A) says “when any component receives focus, it does not initiate a change of context”

• 2. Change on Request (AAA) says “changes of context are initiated only by user request or a mechanism is available to turn off such changes”

  • 1. G107: Using “activate” rather than “focus” as a trigger for changes of context

Page Refresh and Updates

Some older people with declining vision or cognition can miss content that automatically updates or refreshes in a page.

• 1. On Focus (A) says “when any component receives focus, it does not initiate a change of context”. We apply the techniques:

  • 1. G80: Providing a submit button to initiate a change of context

  • 2. G107: Using “activate” rather than “focus” as a trigger for changes of context

• 2. On Input (A) says that changing a setting does not automatically change the context unless the user has been advised beforehand

• 3. Change on Request (AAA) says “changes of context are initiated only by user request or a mechanism is available to turn off such changes”

  • 1. G76: Providing a mechanism to request an update of the content instead of updating automatically. We apply the techniques:

  • 2. SCR19: Using an onchange event on a select element without causing a change of context

Instructions and Input Assistance

It is difficult for some older people to understand the requirements of forms and transactions. Thus, to make the application more accessible, we have developed the following elements:

• 1. Labels or Instructions (A) says “labels or instructions are provided when content requires user input” we apply the technique:

  • 1. G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input

• 2. Consistent Identification (AA) says “components that have the same functionality within a set of Web pages are identified consistently” we use the technique:

  • 1. G197: Using labels, names, and text alternatives consistently for content that has the same functionality

Error Prevention and Recovery

It is difficult for some older people to use forms and complete transactions due to declining cognitive abilities.

• 1. Error Prevention (All) (AAA) says that users can check and correct any information they submit. So that we use the technique:

  • 1. G98: Providing the ability for the user to review and correct answers before submitting

Robust Content and Reliable Interpretation

Older Equipment/Software

Some older people will use older systems that may not be as capable or fault tolerant as current versions.

• 1. Parsing (A) requires that markup is used correctly according to specification:

  • 1. G134: Validating Web pages

  • 2. G192: Fully conforming to specifications

Taking all the aforementioned into account, we understand that our application fulfills in a satisfactory way most accessibility requirements, so it is suitable for its use by elderly people.