Teaching People How To Enlarge Web Pages: Providing Feedback

I believe it is common knowledge that providing feedback while teaching is very important. In particular, positive reinforcement consequent to successful performance is essential for increasing the likelihood a skill will be acquired (that a behavior will occur again). As it is my intention to teach basic Web skills via the Web itself, tutorials must be designed so reinforcing feedback is provided automatically.

A common way of designing such interactivity into Web pages is to use JavaScript. I met last week with a developer who is an accessibility expert. For many years, Rich Caloggero has worked for The National Center for Accessible Media and for The MIT Adaptive Technology Information Center. We anticipate building interactive features that, for example, would indicate to people they indeed pressed the correct keys, in the appropriate sequence, to enlarge a Web page.

It is my hope to approximate on a simple level the sophisticated feedback features that Dr. Janet Twyman, who is guiding me in this project, has had built into software for teaching children to read. From the beginning, she has stressed to me the importance of detecting and reinforcing the pressing of the correct key sequence. I will post the details of this effort as the three of us develop them.

Notes: This post is the fourth in a series about Teaching Web Page (Text) Enlargement. Please post a comment with any suggestions.

Google Video Teaches How To Make Text Bigger

A new Web site, TeachParentsTech.org, was announced by Google recently. Its purpose is to teach basic computer skills to parents. See the announcement and explanation.

The site teaches exclusively via videos. Among the 50+ videos now on the site, “How to make text bigger (or smaller)”, embedded below, is included in the first group displayed on the home page. My guess is that’s because learning how to make text bigger is one of the most common skills parents (older adults for whom vision may not be ideal) request to be taught.

The video starts be reassuring the audience that the task is “super easy”. The skill is then succinctly defined. It is taught exactly how I intend to do so, in that the audience is shown how to use a two-key combination within a Web browser. There is perhaps one main difference between the video and the one I hope to produce for people with cognitive disabilities. I intend to show an image of a keyboard, focusing specifically on how to press the correct two keys, in sequence, to make a Web page (text) larger.

Notes:

Teaching People How To Enlarge Web Pages: Task Definition

Many people need to enlarge Web pages to better see information. People with cognitive disabilities often require larger text sizes to better comprehend information as well.

To develop a best practice for teaching a Web page (text) enlargement skill, I will conduct in-person teaching to groups of people with cognitive disabilities. Specifically, I intend to teach people to use a keyboard with a Web browser to enlarge Web pages. Many browsers will enlarge pages in response to the pressing of two keys: the plus key and the Control key (IBM) / Command key (Mac).

Functional Objective

Given a Web page that may contain images, but must contain text, learners will press two keys to enlarge page content.

Outcome Measure

Learners will open a novel Web page and, without instruction or prompting, enlarge its contents.

Component Skills To Be Taught

Pressing Keys

Learners will:

  • locate the correct keys (2)
  • hold-down one key for at least 3 seconds with sufficient force to be recognized by the computer
  • hold down the one key and tap the other key by pressing it with sufficient force to be recognized by the computer, and immediately releasing it

Completing Sequential Steps

Learners will:

  • follow a multi-step chain of behaviors
  • identify the start- and end points of the behavior chain
  • repeat the behavior chain

Prerequisites

Learners must be able to:

  • respond to textual-, auditory- and/or video-based instruction
  • press keys with their fingers or with equivalent assistive-technology
  • press the correct keys only
  • open a Web page with Internet Explorer

Computers must be:

  • IBM-compatible
  • attached to a monitor and a keyboard or equivalent assistive-technology
  • using Internet Explorer as the default Web browser
  • connected to the Internet

Notes:

Learning To Teach Basic Web Skills to People with Cognitive Disabilities

All people need basic skills to use the Web. A significant part of my effort to teach them to people with cognitive disabilities, via the Web itself, is to implement instructional-design techniques. This post is about my first experiment.

For people of all abilities, examples of basic Web skills are:

  • opening a Web site / using Web addresses;
  • navigating by clicking links and using the back button;
  • performing simple searches with a search engine.

Teaching such a skill includes:

For people with cognitive disabilities, an additional basic Web skill is enlarging the text/font size of a Web site. Thus to learn how best to teach such a seemingly-simple skill, I am continuing my effort to create related instructions.

Guiding me is Janet S. Twyman, Ph.D., BCBA, Associate Professor of Pediatrics at The University of Massachusetts Medical School (Shriver Center), where I work. Dr. Twyman is an expert in instructional design.

Notes: Future blog posts will provide details on each step we take in this experiment. This post is the first in a series about Teaching Web Page (Text) Enlargement. Next up: “Teaching People How To Enlarge Web Pages: Task Definition“.

20 Sites Assessed For Cognitive Web Accessibility

This post summarizes the results from my assessments of the Web sites of 20 organizations that serve people with cognitive disabilities. It is my plan to perform 100 such cognitive Web accessibility assessments. The Clear Helper site has detailed information and results.

The assessments have 10 criteria. Seven are based upon WebAIM’s latest Cognitive Web Accessibility Checklist. Three are intended to help evaluate general Web site accessibility.

The following are the assessment criteria and the percentages of the sites that met them. The included links go to pages that provide details and results for the guidelines comprising the assessment criteria.

Content Criteria

Design Criteria

Design-Related Criteria

Notes

University Web Site for People with Learning Disabilities: Starting a Redesign

Today, I visited a local university that has a campus-based program for students with learning disabilities. I am helping to make the program’s Web site more accessible to its students. I met with the program director, two representatives of university Web services, and an adjunct-faculty member responsible for managing site content. We discussed possible cognitive-accessibility features and next steps for the project.

We will focus on content first.

  • Outdated information will be pruned or updated.
  • Text will be rewritten into plain language.
  • Contextually-relevant images will be added, especially photos taken during program activities.
  • After the above tasks are accomplished for one to five pages, they will be evaluated by program students.

We will then revise the site’s design. To do so, we will determine which cognitive-accessibility features we can incorporate using the university’s content management system (CMS). Examples:

Notes:

  • Other development steps will be outlined in future posts. For example, the My Web My Way idea could be expanded such that site visitors could choose their own mixture of content types.
  • Program students will be included in every step of the site development.

My Current Cognitive Web Accessibility Projects

The following are brief descriptions of projects I have undertaken to help make the Web more accessible to people with cognitive disabilities.

Note: If you would like to help with any of these projects, please post a comment or contact me.

Helping a Nonprofit Provide PC- & Web Access to People with Intellectual Disabilties

Yesterday, I visited a nonprofit that serves several hundred people with intellectual disabilities. I met with the executive director, the director of information services, and a representative of the people being served. We discussed setting up a computer lab, providing computers to people living in their residences, and training.

Generally, the people being served do not possess computers. There is a small number who use the computers of public libraries. A poll taken by the representative indicated significant interest in acquiring and learning to use computers, with e-mail being the main purpose. The executive director expressed the need for people also to learn basic employment-related skills, such as word processing, spreadsheet use and job finding.

About computers in a lab and in residences, identified questions included the following.

  1. Should and could technical staff resources be extended to set up and maintain computers, related infrastructure, and end-user support?
  2. Which other resources should and could be provided: e.g., Internet connections, computers, software, training?
  3. How could the agency help protect people from nefarious activities such as scams and malware infestations?
  4. What assistive-technology hardware and/or software might be needed? Who would purchase and support it?

I suggested an overall approach. We brainstormed about some potential solutions.

  1. Have the three groups (executive, information technology, and the people being served) work together to develop policies. The policies would both offer and reasonably limit:
    1. hardware and software installation;
    2. maintenance and technical support;
    3. services such as broadband Internet connections, and how they could be supported financially;
    4. minimum security standards;
    5. end-user training;
  2. Start with setting up a computer lab in part to train people who want a computer in their residence.
  3. Set up central management of the computers, as schools and businesses do, to:
    1. prevent installation of rogue software;
    2. keep operating systems and applications up-to-date; and
    3. revert computers to a previously-stored state either regularly or if trouble occurs.
  4. Consider router / firewall services:
    1. requiring computers to meet minimum standards before attaching to a network or to the Internet; and
    2. providing anti-virus, anti-malware and, perhaps, Web site-restrictions.
  5. Install on computers exclusively a Web browser and software ancillary to it.
  6. Train people on the basics of Web-based applications such as Google Docs or Microsoft Office Live.
  7. Show people how to use Web-based e-mail or perhaps an e-mail product designed for people with intellectual disabilities.
  8. Develop training not only for the people being served, but also for support staff who could help them maintain newly-acquired skills. The representative of the people being served expressed ideas for related funding.
  9. Perhaps bring into the residences, after the work with the computer lab has gone well, sharable broadband connections and/or computers.
  10. Consider, instead of computers, a device such as the Apple iPad. Potential advantages are:
    1. low purchase cost, especially if it could be used in place of very-expensive assistive technology;
    2. low maintenance, in part because hardware support would be provided by the manufacturer, not by the agency’s technical staff;
    3. a simple-to-use interface that would not require learning how to use a mouse or a (external) keyboard;
    4. built-in connection to the Internet via a wireless- or cellular network.

I agreed to continue in a technical-advisory role. I also committed to work directly with people to learn about their difficulties using computers and the Web, and to help train them to overcome those problems. Such training would be passed on to support staff so long-term assistance could be provided.

I will post updates about the project as it progresses. Have advice? Want to get involved? Please post a comment or contact me.

Alzheimer’s Foundation of America: Accessibility Paradox

Alzheimer's Foundation of America home page Detailed results from my cognitive Web accessibility assessment of The Alzheimer’s Foundation of America revealed an apparent, related effort on its content.  Paradoxically, it seemed there was little on the accessibility of its design.

Content

Textual content is crafted to be readable. For instance, a lot of technical language is used but is followed by attempts at simple explanations. Also of note is that this site conforms to every aspect of readability criteria: line length and height; text spacing and size, etc..

Textual content is also designed so site visitors’ attention is focused on it. White space is used well. Distractions are avoided. Content is written in visual chunks and using lists. The home page is an exception to these successes.

Design

The site met only 25% of design criteria. Indications that little attention is paid to accessibility guidelines are 49 related errors on the home page (as reported by WebAIM’s WAVE). Alternative text for images, which is a basic sign that site designers are aware of accessibility, is generally absent. Misspellings and typographical errors make its rare use problematic.

Conclusion

It is reasonable to assume a significant portion of the site’s visitors are seniors. Those who do not have Alzheimer’s Disease may have cognitive deficits, as happens to all of us as we age. The site’s content creators apparently recognize this. In my opinion, their efforts do not make up for the site’s accessibility design failures.

Notes

Cognitive Web Accessibility Assessments: Detailed Results By Site

I published an index of detailed results, by site, of my cognitive Web accessibility assessments.

For each Web site, the detailed-results page displays:

  • the applicable guidelines the site met or did not meet;
  • the numbers of points scored by sections (Content, Design and Design-Related); and
  • the site’s assessment score and conclusion (accessible or inaccessible).

Notes: This post is part of a continuing series on Cognitive Web Accessibility Assessments. I have also published an index of aggregate results.