| Manila ICT/WDAR | SECTION 508 | WCAG 1.0 |
| MS 1 – 1 – Provide an Access Instruction page for visitors explaining the accessibility features of the web site. Put an e-mail hyperlink for visitors to communicate web page accessibility problems. | None | None |
| MS 1 – 2 – Avoid using words such as "This" or "Click Here" in creating links. Use descriptive hyperlinks to support text browsers. |
None | Priority 2 – 13.1 – Clearly identify the target of each link. |
| MS 1 – 3 – Attach ALT<alt> (alternative) text to graphic images so that assistive computer technology such as screen readers can reach the content. | (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | Priority 1 – 1.1 – Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video. |
| MS 1 – 4 – Provide a "D" hyperlink to a page providing descriptive text of photographs that contribute meaningful content to the page. | None | None |
| MS 1 – 5 – Provide text transcriptions or descriptions for all audio and video clips. | (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Priority 1 – 1.3 – Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
Priority 1 – 1.4 – For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. |
| MS 1 – 6 – Provide alternative mechanisms for online forms such as e-mail or voice/TTY phone numbers since forms are not supported by all browsers. | (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.* | None |
| MS 1 – 7 – Avoid access barriers like: PDF files with no equivalent HTML or ASCII files, non-linear page formats, frame formats and content that requires user to download software to access it. | (i) Frames shall be titled with text that facilitates frame identification and navigation.*
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.* |
Priority 2 – 12.2 – Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. |
| MS 2 – 1 – For ALT texts: 2 – 1.1 – Decorative images must contain null ALT text or ALT="". 2 – 1.2 – Anchor elements within the Image Maps must contain ALT texts. 2 – 1.3 – Alternate texts that require more than 80 characters must instead be changed to "D" hyperlink. |
None | Priority 1 – 1.2 – Provide redundant text links for each active region of a server-side image map. |
| MS 2 – 2 – Provide a Site Map with a link appearing on every page. | None | Priority 2 – 13.3 – Provide information about the general layout of a site (e.g., a site map or table of contents). |
| MS 2 – 3 – All pages must provide a link back to the home page. | None | Priority 2 – 13.4 – Use navigation mechanisms in a consistent manner.
Priority 3 – 13.5 – Provide navigation bars to highlight and give access to the navigation mechanism. |
| MS 2 – 4 – Use Access keys in creating shortcuts to important links and form controls. |
None | Priority 3 – 9.5 – Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. |
| MS 2 – 5 – Provide a "Skip to Content" link in every page. | (o) A method shall be provided that permits users to skip repetitive navigation links. | Priority 3 – 13.6 – Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. |
| MS 2 – 6 – Make the language that you use in your web site easy to understand. | None | Priority 1 – 14.1 – Use the clearest and simplest language appropriate for a site’s content. |
| MS 2 – 7 – Do not use blinking, rolling or scrolling markup tags on your web pages. |
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Priority 1 – 7.1 – Until user agents allow users to control flickering, avoid causing the screen to flicker.
Priority 2 – 7.2 – Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). |
| MS 2 – 8 – Provide a LABEL text and ALT text on the input elements of your forms. | (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | Priority 2 – 10.2 – Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.
Priority 2 – 12.4 – Associate labels explicitly with their controls. Priority 3 – 10.4 – Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. |
| MS 2 – 9 – Avoid using the FONT SIZE markup in your web pages or change the size to relative units. | None | Priority 2 – 3.4 – Use relative rather than absolute units in markup language attribute values and style sheet property values. |
| MS 2 – 10 – Provide a Search form within your site. | None | Priorities 3 – 13.7 – If search functions are provided, enable different types of searches for different skill levels and preferences.* |
| MS 2 – 11 – Layout must be navigable even if the page style is turned off. | (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Priority 1 – 6.1 – Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. |
| MS 2 – 12 – Website content must appear clearly even when colors are turned off. | (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Priority 1 – 2.1- Ensure that all information conveyed with color is also available without color, for example from context or markup. |
| MS 2-13 Provide descriptive titles for every page. | None | Priority 2 – 13.1 – Clearly identify the target of each link. |
| MS 2-14 Page style must be consistent all throughout the website. | None | Priority 3 – 14 – 3 – Create a style of presentation that is consistent across pages. |
| MS 2-15 Provide enough contrast between foreground and background color combinations. | None | Priority 2 – 2.2 – Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text]. |
| MS 2-16 Avoid background sounds or music that may distract the user’s focus on the content. | None | None |
Notes:
MS – Maturity Stage
* – Not exactly the same or has a different definition
Section 508 data were taken from the Access-board.gov official website.
Web Content Accessibility Guidelines Checkpoint 1.0 data were taken from the W3C Official Website.
Analysis of Comparison
- Manila ICT/PWAG Design Accessibility Recommendations only has a total of 23 checkpoints.
- WCAG 1.0 has a total of 65 checkpoints distributed in three Priorities. Priority 1 has 16 checkpoints. Priority 2 has 30 checkpoints and Priority 3 has 20. However, only 24 of those checkpoints have an equivalent Manila ICT/WDAR checkpoint or 37% compatibility rate.
- Section 508 has a total of 16 checkpoints. However, only ten of those checkpoints have an equivalent Manila ICT/PWAG checkpoint.
- Non-conforming checkpoints/recommendations are as follows:
a. Manila ICT/PWAG recommends "D" link while Section 508 and WCAG opted to use "longdesc".
b. Manila ICT/PWAG does NOT recommend the use of frames while WCAG and Section 508 do but with limitations.
c. Manila ICT/PWAG recommends a Search form while WCAG allows it but with modifications.
Share this:
