Dani Iswara .Net

Site Help

Dani Iswara .Net blog try to ensure that this weblog is accessible to everyone. If you have any questions or suggestions regarding the accessibility of this blog, please contact me (see about author). I am continually striving to improve the experience for all of our visitors. This Site Help features:

Visually impaired users

All information on this site / weblog should be easily accessible using screen-readers. The size of text is changeable.

Users of minority browsers

This site should be accessible using any (modern and not too old) browser and mobile browser.

Navigation

Users will be able to reach all parts of the weblog by following links that are keyboard navigable. No parts of the site are “hidden” behind links that can only be displayed by mouse action.

Text sizes

All text is resizable, so if it is too small or large for easy reading, use browser setting to display it at the size you prefer. For example (on Firefox, Opera):

• ctrl + + to increase fonts size
• ctrl + - to decrease fonts size
• ctrl + 0 to change back to normal fonts size.

Links

The wording for text links will be carefully chosen so that each link is:

• Clear in telling the destination
• Unique, each text links refer to different destination
• Completed by short description nearby the text link
• Concise, short enough, meaningful, and to the point
• Easy to identify, not using words like “click here” or “link to”
• Honest, no ‘make money’ referral link without a warning!

Images

A text alternative will be provided for all images.

• Images used as links, text: will have alternative text (using alt attributes), descriptive enough, as good as text links
• Informative images: text in the content will give the information that the image contributes to the page
• Decorative / layout images: will be given empty alternative text.

Abbreviations & Acronyms

Abbreviations and acronyms are marked up as an aid to ScreenReaders and other assistive technologies. The definitions are given using the title attribute. Sorry for IE user, I will choose abbr (more semantic) instead of acronym.

Colour

Colours will be chosen to provide good contrast between text and its background, and avoid combinations that are known to cause difficulties for people with colour blindness.
Passes with “no Fail result” (all test mode) using Colour Contrast Analyser (Firefox extension).

Forms

Forms are marked up using the fieldset, label & tabindex attributes and will be accessible using tab key. Completing forms is made easy because the information user need to complete each input box will be clear and well positioned:

• Text labels will always be present, correctly positioned
• The tab order will be logical.

New windows

This weblog doesn’t use open in new window order. So users can use revert / back button — ← (browsers) or Alt + ← (keyboards) safely. If any, users will find a warning either in the link text or the sentence the link is given in. Typically new windows are used for audio and video.

Audio & video

Any information that is presented in video, audio or multimedia will have alternatives. Same information will be available to people with hearing problems.

JavaScript

No part of the website will be impossible to either reach or use because of a total reliance on JavaScript. If JavaScript is used, it won’t create moving text that cannot be stopped, controls, operated by either the mouse or the keyboard.

Access keys

Access keys are available to specific links by typing keys combination defined on the weblog:

• On Windows, users can press Alt + [an access key]
• On Macintosh, you can press Control + [an access key]
• In Opera, users presses ↑ Shift + Esc + [an access key]
• In Konqueror on GNU/Linux, the Ctrl key is pressed and released + [an access key]
• In Firefox 2.0+ users can use ↑ Shift + Alt + [an access key].

Further reading: Access keys - Wikipedia.

All pages on this weblog define the following access keys:

• Access key 1 - Home page
• Access key 2 - Skip to entry section
• Access key 3 - Skip to navigation section
• Access key 4 - Skip to subscribe option section
• Access key 5 - Set focus to search box
• Access key 6 - Skip to sidebar
• Access key 7 - Skip to footer
• Access key 0 - Site Help (this page)

Leaving Comment

All of users — no registration is needed — can leave comment(s):

• Strict XHTML (semantic markup) tags allowed:
  • <strong>strong/bold text</strong>
  • <em>emphasized text</em>
  • <del>deleted text</del>
  • <code>coded text</code>
  • <a href="http://daniiswara.net/" title="visit Dani Iswara - Indonesia Physician Weblog">Dani Iswara .Net</a> (live link)
  • <abbr title="eXtensible HyperText Markup Language">X/HTML</abbr> (abbreviations and acronyms)
  • <blockquote>
    

    …to quote long lines and paragraphs quotation
    to quote long lines and paragraphs quotation…

    </blockquote>

• All tags must be properly closed.
• Comment contains some words (eg. URLs) will be held in moderation.
• Paragraphs and line breaks are automatically converted.
• Keep relevant. Inappropriate comments may be edited, moderated, or removed.
• To have image beside your comment, get Gravatar!

Use proper (numeric-based) entities in XHTML on those comment form:

• safe name-based entities:
  • " for "
  • &lt; for <
  • &gt; for >
• some numeric-based entities:
  • &#8482; for ™
  • &#945; for α
  • &#946; for β
• more details on Markup Specific Entities in XHTML and Symbol Entities in XHTML.

Standards compliance

• All of Dani Iswara .Net web pages complies with the W3C-WAI WCAG Level 2 (AA) or better (see WCAG 2.0). Try other accessibility guidelines:
  • BITV 1.0 (Level 2) (Germany standard)
  • Section 508 (Section 508 : The Road to Accessibility - USA standard)
  • Stanca Act (Italian accessibility law)
• Validate web accessibility (machine-based) using ATRC Web Checker (Change guidelines). Actually it needs human evaluation also.
• All of these web pages are written in XHTML 1.1, served as application/xhtml+xml to compatible browsers, text/html to the other browsers (eg. Internet Explorer).
  Equations are written in MathML 2.0. If possible, figures are displayed in SVG 1.1, with a fallback to a GIF image.
• Validate X/HTML by Validome.org (W3C based) or W3C Markup Validator.
• Styling is done using CSS. Site is still accessible without CSS.
  • A separate print stylesheet is used to provide a more printer-friendly format for printing.
• Validate CSS (W3C CSS validator).
• All pages use structured semantic markup and tableless.