Judging Criteria

• All non-text contents, such as icons, photos, pictures, images, banners and maps that are presented to users have a text alternative that provides a meaningful description.

• If Flash/Animated content is provided, accessible version Flash/Animated content or a skip function shall be provided.

• All functions on a webpage are operable through a keyboard interface; the operation shall not enforce a time limit for individual keystrokes.

• If any audio on a webpage plays automatically for more than 3 seconds, either a function is available to pause or stop the audio, or a function is available to control audio volume independently for that specific audio.

• If there is a popup window, a close button shall be included to allow closing the popup window through keyboard interfaces.

• If there is a link, either the link text alone or the text preceding the link is clear and meaningful in order to help users navigate.

• To help users understand what information is contained in the webpage and how information is organised, use clear and appropriate headings and labels to describe a topic or purpose.

• Use heading mark-up (h1..h6) to identify headings in the content. Heading mark-up allows assistive technologies to present the heading status of text to users.

• Navigational mechanisms that are repeated on multiple webpages within a set of webpages occur in the corresponding relative order each time they are repeated, unless a change is initiated by the user.

• If webpage content needs to be read in a certain order to make sense, webpage shall be written/coded in a way which indicates this order
• Webpage, especially web form, shall be coded in a logical manner when read by assistive technologies.

• If an input error is automatically detected, the error shall be identified and described to users.
• Labels or instructions are provided when prompting user input.

• Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

• Provide an accessibility statement with contact point for website users to contact the website owners when they encounter accessibility problems.

1. Provide meaningful text alternatives for images (Corresponding Techniques PDF1 for WCAG 2.0)
2. Ensure correct tab and reading order
   (Corresponding Techniques PDF3 for WCAG 2.0)
3. Use table elements for table markup
   (Corresponding Techniques PDF6 for WCAG 2.0)
4. Set the default language in the document catalog (Corresponding Techniques PDF16 for WCAG 2.0)
5. Specify the document title
   (Corresponding Techniques PDF18 for WCAG 2.0)

• For any component that is able to trigger an event, it will not change the context (for example jumping to a new window) immediately when the component receives focus.

• A mechanism is available to bypass blocks of content that are repeated on multiple webpages.

• Provide more than one way to access a webpage such as using a search function, site map, standard navigation, etc.

• If there is any moving information that starts automatically and lasts more than five seconds, there shall be a mechanism for users to pause, stop or hide it.

1. time limit can be turned off; or
2. time limit can be extended by a simple action

• Visual presentation of text and images of text has a contrast ratio of at least 4.5:1. Logo or brand name is exempted.

• For content coded with mark-up languages, elements shall have complete start and end tags, correct nested coding.

• Transcript, captions or sign language are provided for 30% of pre-recorded videos and audio content published in the most recent 2 years, except when the media is a media alternative for text and is clearly labelled as such.

• To ensure that the information and relationships of content conveyed in form of a table is perceivable to all.

Provide error prevention for transactions
(Corresponding success criterion in WCAG 2.0 – 3.3.4 [Level AA])

• For transaction involved legal or financial commitments, error prevention mechanism shall be included through at least one of the following–
  1. Reversible: submissions are reversible.
  2. Checked: input data are checked for errors and users are allowed to correct them.
  3. Confirmed: a mechanism is available for reviewing, confirming, and correcting information before finalising the submission.