Accessibility
How this system meets WCAG 2.2 AA and the DICT web accessibility guidelines.
SIP PCMS is built to be usable by everyone who needs it, including people who navigate by keyboard, use a screen reader, or need larger text and stronger contrast.
Standards we follow
- WCAG 2.2 Level AA — the Web Content Accessibility Guidelines published by the W3C.
- DICT web accessibility guidelines — the Philippine Department of Information and Communications Technology's requirements for government systems, which build on WCAG.
What this means in the system
- Every action can be reached and performed with a keyboard alone. Nothing needs a mouse.
- The first thing Tab reaches on any page is a Skip to main content link.
- Whatever has keyboard focus is always visibly outlined.
- Forms open in a side panel. Focus moves into the panel when it opens, stays inside it while it is open, closes on Esc, and returns to the control you came from. Each form also has its own page, which works with JavaScript turned off.
- Every field has a visible label. When something is rejected, the reasons are listed at the top of the form, announced, linked to the field they belong to, and repeated under that field.
- Status is never carried by colour alone — approved, pending, overdue and rejected all carry text as well.
- Tables have captions and proper row and column headers.
- Text can be enlarged to 200% in the browser without losing content or function.
- Animation is reduced automatically if your device asks for reduced motion.
Known limitations
- Exported PDF reports are generated for print and are not tagged for screen readers. The same figures are available on screen in the equivalent report page, and as Excel exports.
- Charts on the dashboard are visual summaries. Every figure they plot is also published as text in the metric strip above them and in the underlying report.
Tell us if something blocks you
If any part of this system stops you from completing your work, report it to your system administrator. Please include the page you were on, what you were trying to do, and the assistive technology or browser you were using. Accessibility defects are treated as functional defects, not enhancements.
This statement was last reviewed on 1 August 2026.