Skip to main content

Home/ H810 2013/ Group items tagged links

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Kev Harland

Images / NCAM - 0 views

ncam.wgbh.org/...guideline-a-images

shared by Kev Harland on 09 Nov 13 - No Cached
  • If you absolutely must use a server-side image map, always place redundant text links adjacent to the map so someone with a screen reader, or someone who can't use a mouse, can access the links.
    • Kev Harland
      Kev Harland on 09 Nov 13
       
      NCAM Guidelines. Might also be used to justify other kind of redundant links
  • If an image is merely used to set atmosphere or provide decoration, it is not always necessary or even desirable to provide a description. In such cases it is best to give that image a null description, such as null alt, as demonstrated below. (A null description informs assistive technologies that the graphic does not need description. If no description [e.g., no alt] at all is included, assistive technologies may announce an unlabeled graphic, leading the user to wonder what is missing.)
    • Kev Harland
      Kev Harland on 10 Nov 13
       
      use for decorative images that do not contribute toward the learning outcomes
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

H2: Combining adjacent image and text links for the same resource | Techniques for WCAG... - 0 views

www.w3.org/...H2

image text links techniques accessibility Guidelines html design

shared by Kev Harland on 23 Nov 13 - No Cached
  • Kev Harland on 23 Nov 13
     
    A single illustration of the myriad of techniques a web designer must take on board in order to create accessible websites.
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
1 - 4 of 4
Showing 20▼ items per page