brukbrahet for funksjonshemmede

Internett for funksjonshemmede

Hele orginaldokumentet kan leses her:  W3C Working Draft, 8 July 2004

Artikkelen beskriver:

• Scenarier som illustrerer funksjonshemmedes bruk av et tilrettelagt internett. Scenariene illustrerer samtidig generelle krav til webtilgjengelighet for personer med fysiske, visuelle, hørsel, kognitive og nevrologiske funksjonshemminger
• Noen typer hjelpeteknologier og tilpassingsstrategier.

SCENARIER SOM ILLUSTRERER FUNKSJONSHEMMEDES BRUK AV ET TILRETTELAGT INTERNETT

De følgende eksemplene viser personer med ulike funksjonshemminger som benytter ulike teknologier og tilpassingsstrategier for å få tilgang til www:

• Online shopper with color blindness (user control of style sheets)
• Reporter with repetitive stress injury (keyboard equivalents for mouse-driven commands; access-key)
• Online student who is deaf (captioned audio portions of multimedia files)
• Accountant with blindness (appropriate markup of tables, abbreviations, and acronyms; synchronization of visual, speech, and braille display)
• Classroom student with dyslexia (use of supplemental graphics; freezing animated graphics; multiple search options)
• Retiree with aging-related conditions, managing personal finances (magnification; stopping scrolling text; avoiding pop-up windows)
• Clerk with cognitive disability at an online grocery service (clear and simple language; consistent design; consistent navigation options; supplemental audio)
• Teenager with deaf-blindness, seeking entertainment (user control of style sheets; accessible multimedia; device-independent access; labeled frames; appropriate table markup)

NOEN TYPER HJELPETEKNOLOGIER OG TILPASSINGS STRATEGIER

• Alternative keyboards or switches
  (scenario -- "reporter ")
• Braille and refreshable braille
  (scenarios -- "accountant" and "teenager ")
  Braille is a system using six to eight raised dots in various patterns to represent letters and numbers that can be read by the fingertips
• Screen magnifiers
  (scenarios -- "teenager" and "retiree ")
  Screen magnification is software used primarily by individuals with low vision that magnifies a portion of the screen for easier viewing.
• Sound notification
  Sound notification is an alternative feature of some Web-based applications that allows deaf or hard of hearing users to receive visual notification that a warning or error sound has been emitted by the computer.
• Screen readers
  (scenarios -- "accountant" and "teenager ")
  Software used by individuals who are blind or who have dyslexia that interprets what is displayed on a screen and directs it either to speech synthesis for audio output, or to refreshable braille for tactile output..
• Speech recognition
  Speech (or voice) recognition is used by people with some physical disabilities or temporary injuries to hands and forearms as an input method in some voice browsers. Applications that have full keyboard support can be used with speech recognition.
• Scanning software
  Scanning software is adaptive software used by individuals with some physical or cognitive disabilities that highlights or announces selection choices (e.g., menu items, links, phrases) one at a time.
• Speech synthesis (speech output)
  (scenario -- "accountant ")
  Speech synthesis or speech output can be generated by screen readers or voice browsers, and involves production of digitized speech from text.
• Tabbing through structural elements
  (scenario -- "accountant ")
  Some accessibility solutions are adaptive strategies rather than specific assistive technologies such as software or hardware. For instance, for people who cannot use a mouse, one strategy for rapidly scanning through links, headers, list items, or other structural items on a Web page is to use the tab key to go through the items in sequence.
• Text browsers
  Text browsers such as Lynx are an alternative to graphical user interface browsers. They can be used with screen readers for people who are blind.
• Voice browsers
  Voice browsers are systems which allow voice-driven navigation, some with both voice-input and voice-output, and some allowing telephone-based Web access.
• Controlling color
  scenario --online shopper
  • WCAG 1.0 Checkpoint 2.1 (Priority 1) Ensure that all information conveyed with color is also available without color, for example from context or markup. Example of conveying information conveyed with and without color.
  • WCAG 1.0 Checkpoint 2.2 (Priority 2/Priority 3) Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. Example of contrasting foreground and background color combinations.
• Controlling presentation with style sheets
  (scenarios -- "online shopper" and "retiree ")
  • WCAG 1.0 Checkpoint 3.3 (Priority 2) Use style sheets to control layout and presentation. Example of using style sheets to control layout and presentation  and another example of  using style sheets for layout and presentation.
  • WCAG 1.0 Checkpoint 3.4 (Priority 2) Use relative rather than absolute units in markup language attribute values and style sheet property values.
• User override of author style sheets
  (scenarios -- "online shopper" and "teenager ")
  • UAAG 1.0 Checkpoint 4.3 (Priority 1) Allow the user to configure the foreground color of all text, with an option to override author-specified, and user agent default, foreground colors. Allow the user to select from among the range of system colors.
  • UAAG 1.0 Checkpoint 4.4 (Priority 1) Allow the user to configure the background color of all text, with an option to override author-specified and user agent default background colors. Allow the user to select from among the range of system colors.
• Providing full keyboard support
  (scenario -- "reporter ")
  • ATAG 1.0 Checkpoint 7.1 (Priority 1/Priority 2 /Priority 3) Use all applicable operating system and accessibility standards and conventions . Also in Techniques for ATAG 1.0, see techniques for Checkpoint 7.1.
• Using access keys for shortcuts
  (scenario -- "reporter ")
  • WCAG 1.0 Checkpoint 9.5 (Priority 3) Provide keyboard shortcuts to important links [including those in client-side image maps], form controls, and groups of form controls. Example of access key.
  • UAAG 1.0 Checkpoint 9.3 (Priority 2) Provide information to the user about current author-specified input configurations [e.g. keyboard bindings specified in HTML documents with the access key attribute].
• Making multimedia accessible
  (scenarios -- "online student" and "teenager ")
  • WCAG 1.0 Checkpoint 1.1 (Priority 1) Provide a text equivalent for every non-text element (e.g. via "alt", "longdesc", or in element content). This includes: ...sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
    • Example of a text equivalent for sounds
    • Example of a text equivalent for stand-alone audio files
    • Example of a text equivalent for audio tracks of video
    • Example of a text equivalent for video
  • WCAG 1.0 Checkpoint 1.3 (Priority 1) Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
    • Example of auditory description of visual track of a multimedia presentation, and continued example of auditory description.
  • WCAG 1.0 Checkpoint 1.4 (Priority 1) For any time-based multimedia presentation (e.g. a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.
    • Example of synchronized equivalent alternatives, and continued example of synchronized alternatives.
• Using column and row headers in tables
  (scenarios -- "accountant" and "teenager ")
  • WCAG 1.0 Checkpoint 5.1 (Priority 1) For data tables, identify row and column headers. For example, in HTML, use TD to identify data cells and TH to identify headers.
    • Example of identifying row and column headers, and continued example of identified row and column headers.
• Expanding abbreviations and acronyms
  (scenario -- "accountant ")
  • WCAG 1.0 Checkpoint 4.2 (Priority 3) Specify the expansion of each abbreviation or acronym in a document where it first occurs. For example, in HTML, use the "title" attribute of the ABBR and ACRONYM elements. Providing the expansion in the main body of the document also helps document usability.
    • Example of expanded abbreviations and acronymns.
• Synchronizing screen display with audio and braille rendering of information
  (scenario -- "accountant")
  • WCAG 1.0 Checkpoint 1.4 (Priority 1) For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.
    • Example of synchronizing equivalent alternatives with a presentation.
  • UAAG 1.0 Checkpoint 4.5 (Priority 1) Allow the user to slow the presentation rate of audio, video and animations that are not recognized as style. For a visual track, provide at least one setting between 40% and 60% of the original speed. For a prerecorded audio track including audio-only presentations, provide at least one setting between 75% - 80% of the original speed. When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks. Below 80%, the user agent is not required to render the audio track.
• Supplement text with graphic or auditory presentations
  (scenarios -- "online student" and "teenager ")
  • WCAG 1.0 Checkpoint 14.2 (Priority 3) Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.
    • Example of supplementing text with graphic and auditory presentations.
• Allow user to freeze moving context and scrolling text
  (scenarios -- "online student" and "retiree ")
  • WCAG 1.0 Checkpoint 7.3 (Priority 2) Until user agents allow users to freeze moving content, avoid movement in pages.
• Avoid auto-refreshing pages
  (scenario -- "retiree ")
  •  WCAG 1.0 Checkpoint 7.4 (Priority 2) Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.
    • Example of auto-refreshing page.
• Avoid causing "pop-up" windows
  (scenario -- "retiree ")
  • WCAG 1.0 Checkpoint 10.1 (Priority 2) Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user
    • Example of appropriate notification for a "pop-up" window.
• Use clear and consistent navigation mechanisms
  (scenario -- "clerk ")
  • WCAG 1.0 Checkpoint 13.4 (Priority 2) Use navigation mechanisms in a consistent manner.
    • Example of using consistent navigation mechanisms.
• Use clear and simple language
  (scenario -- "clerk")
  •  WCAG 1.0 Checkpoint 14.1 (Priority 1) Use the clearest and simplest language appropriate for a site's content.
  • Example of a clear and simple language
• Use a consistent style of presentation across pages
  (scenario -- "clerk ")
  • WCAG 1.0 Checkpoint 14.3 (Priority 3) Create a style of presentation that is consistent across pages.
    • Example of consistent presentation across pages.
• Enable device independence
  (scenario -- "teenager ")
  • WCAG 1.0 Checkpoint 9.2 (Priority 2) Ensure that any element that has its own interface can be operated in a device-independent manner.
    • Example of element that has its own interface and can be operated in a device-independent manner.
• Label frames
  (scenario -- "teenager ")
  • WCAG 1.0 Checkpoint 12.1 (Priority 1) Title each frame to facilitate frame identification and navigation.
    • Example of titled frames.