Skip to main content

Home/ H810 2013/ Group items tagged objectives

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Kev Harland

Document object model (DOM) and screen readers - 0 views

www.bbc.co.uk/..._MobileSandG_v7_production.pdf

H810 accessibility html dom content Guidelines

shared by Kev Harland on 10 Nov 13 - No Cached
    • Kev Harland
      Kev Harland on 10 Nov 13
       
      Alternatives MUST NOT include information about the type of object (Editorial & Development) When using standard controls for links, buttons, images etc. information about its type is assigned elsewhere and should not be repeated in the alternative. This information is generally provided by default for platform objects, controls, or elements and will be announced by speech output software. For example never use the text 'Add button' as an alternative, only 'Add'. Adding additional roles means the role is announced twice to users of speech output software. An exception to this may be when a role or state cannot be added in such as way. For example, in the case of an HTML page tabs that gracefully degrade it may be useful to add the word "Selected" to the link.
    • Kev Harland
      Kev Harland on 10 Nov 13
       
      Do not use the Title attribute unless on a form input as these are not widely supported on mobile
    • Kev Harland
      Kev Harland on 10 Nov 13
       
      Speech output software renders content in the order in which it appears in the document object model (DOM). Place content in the DOM in the correct order either through source code or inserting nodes in the DOM
Kev Harland

The Difference between Web Site Usability and Accessibility | Usability Geek - 0 views

usabilitygeek.com/te-usability-and-accessibility

usability accessibility H810

shared by Kev Harland on 16 Nov 13 - No Cached
  • Kev Harland on 16 Nov 13
     
    I come across articles and recommendations that tend to confuse usability with accessibility. The objective of this post is to establish the link between the two terms while outlining their differences. In order to do so, it is important to first understand what is web site usability and web site accessibility.
Kev Harland

Infosemantics.com.au | How to Use Blooms Taxonomy Learning Objectives to Design Drag an... - 0 views

www.infosemantics.com.au/...esign-e-learning-interactivity

design interactions H810 Guidelines blooms taxonomy objectives

shared by Kev Harland on 01 Dec 13 - No Cached
  • Kev Harland on 01 Dec 13
     
    Learning outcomes and Accessibility? How do e-Learning designers re-think ID in light of accessibility requirements
Kev Harland

HTML Global title Attribute - 0 views

www.w3schools.com/...att_global_title.asp

xerte html H810

shared by Kev Harland on 10 Nov 13 - No Cached
  • The title attribute specifies extra information about an element. The information is most often shown as a tooltip text when the mouse moves over the element.
  • Kev Harland on 10 Nov 13
     
    This attribute seems to be required by Xerte if embedding images where the embed functionality is not available from the "optional properties" menu. (Why use this instead of "Alt"? - When screen reading a Xerte object the the Alt tag seems to get ignored but "title" tag gets read aloud)
1 - 4 of 4
Showing 20▼ items per page