Skip to content

من النهر إلى البحر
#FreePalestine

Accessibility Statement

This is the official accessibility statement for Adeeology.my. Any comments or feedback is welcome, and can be forwarded to hello@adeeology.my, or by using the contact form below. You can also view this website’s accessibility features in action to have a better idea of how accessibility and also usability is applied in the website.

Access keys

Most browsers support jumping to specific links by typing keys defined on the website. In Windows, you can press the ALT key together with an access key; with Macintosh, you can press Control together with an access key. All pages on this website define the following access keys:

Access key 1 – Home page
Access key 2 – Skip directly to content link
Access key 3 – Sitemap
Access key 4 – Search
Access key 8 – About page
Access key 9 – Contact information
Access key 0 – Accessibility statement

Different browsers on a PC or a Mac have different ways of implementing access keys. In Firefox it’s ALT+SHIFT+key. For example, the combo ALT+SHIFT+1 would take you to the home page.

For Internet Explorer 10 or higher: Use Alt + [accesskey] (Windows/Linux), or Control + [Accesskey] (Mac).

For Firefox: Use Alt + Shift + [accesskey] (Windows/Linux) or Control + [Accesskey] (Mac).
For Chrome: Use Alt + [accesskey] (Windows/Linux), or Control + Option + [Accesskey] (Mac).
For Safari: Use Alt + [accesskey] (Windows/Linux), or Control + Option + [Accesskey] (Mac).

Source: Using browser access keys.

Standards compliance

  • All pages on this website comply ‘in spirit’ with the major accessibility guidelines as outlined in the Bobby Guidelines, the W3C Web Content Accessibility Guidelines and Section 508 Guidelines. Compliance in full cannot be guaranteed, as most guidelines are vague and cannot be tested automatically. These guidelines were reviewed and I believe all my pages are in compliance.
  • All pages(*) of this website validate as XHTML 1.0 Strict. This is not a judgement call; a program can determine with 100% accuracy whether a page is valid XHTML.
*
I’ve coded my website entirely by hand. They’re bound to be some errors, but most pages are already validated. Maybe I should’ve re-phrased it as, “All pages (not yet validated) of this website (may not) validate as XHTML… “

Navigation aids

  • Skip link are provided to directly access the main content (access key 2).
  • All pages include a search box (access key 4).

Links

  • Many links have title attributes which describe the link in greater detail, unless the text of the link already fully describes the target (such as the headline of an article).
  • Links are written to make sense out of context.
  • Links are colour-coded (in most cases), to have sufficient contrast.
  • Download links are clearly indicated with ” “, for visual browsers, and given a descriptive alt attribute (alt=”download link”) for textual browsers.
  • Except for the top-level section links (Home, About, Contact etc.), all links leading to the current (same) page are ‘deactivated’(**).
  • Links leading to the same page (home page link to home page) are clearly indicated(**) for users of textual browsers and/or browsers with no CSS support.
**
Is more a usability issue than an accessibility issue. But then again, the two are often intertwined and overlap. Anyway, links leading to the same page (home page link on home page, or for an easy example, this link – accessibility statement, which is on the the page itself) can confuse a user into thinking it is a different page. My ‘fix’ is a patchjob, admittedly, but it’s better than nothing. Note: This only affect the top-level links. (Home, About, Contact etc.)

Images

All Most content images used in this website include descriptive alt attributes. Purely decorative graphics include null alt attribute (alt=””) attribute.

Visual design

  • This website uses CSS for visual layout.
  • This website uses relative font sizing, compatible with the user-specified ‘text size’ option in visual browsers.
  • If your browser or browsing device does not support stylesheets at all, the content of each page is still readable.I might invest time in a different theme.
  • Access to this website is technically possible using any visual browser on any platform. Renditions, however may differ slightly from each browser and platform. Many damning cross-browser (in)compatibilities were addressed to (and will continue to be) in the design of this website. Textual browsers’ access is not possible at the moment.

Others

Form

  • Input fields, when selected (such as the search box, or comment) is highlighted when in focus.
  • A hand cursor is indicative (in a visual browser) of a label.

Acronyms

  • Full wording of acronyms are always explained, in both visual and textual browsers.
  • An acronym’s full wording is visible for most browsers.
  • Hovering the cursor over an acronym in most major visual browsers will reveal the full wording of the acronym as a tooltip.
  • Clicking on an acronym will reveal its full wording. To close the full wording, just click on another area.
  • Full wording of acronyms will be printed in full when a page is printed. A separate print CSS will be added.
  • The <acronym> tag in HTML is used to define an acronym, and to spell out another word. It is used to give useful information to browsers, translation systems, and search-engines. This tag is not supported in HTML 5 though, and is now replaced with the <abbr> tag.
Note:
Not all instances of an acronym is explained in full. The first instance is always explained. The subsequent instances may not all be explained, especially if more than one instance can be found in a single sentence or in a same paragraph.

Scripting

  • Scripting can be disabled (by choice or necessity) with no ill-effects.
  • The <noscript> tag is placed to describe the script’s functions.

Contact Form