Inner Pages

You are ready to populate the site, expanding its content beyond the landing page. The guidelines below are meant to support you.

All the accessibility principles described on this site, POUR, do not apply only to the masthead and the footer.

Web Content Accessibility Guidelines:
The P.O.U.R. principles

Organized into four guiding principles — Perceivable, Operable, Understandable, and Robust (POUR) — and referenced throughout this site, they provide the basis to address web accessibility.

鈥楶鈥� is for Perceivable

Providing alternative ways to access your web content is essential to compensate for missing or weaker senses. This also implies that your website supports the use of assistive technology (such as screen readers, magnifying tools, etc.).

  • See specific references on the Masthead page (colour contrast, visual presentation, etc.) and under Homepage聽(text alternatives, video, carousel, tables, lists).

鈥極鈥� is for Operable

Not everyone experiences a website the same way. Users with disabilities may use assistive technology such as screen readers, Braille terminals, screen magnification software, etc.

  • See specific references on the Masthead page (keyboard accessible, navigable) and under Homepage (programmatic elements, seizures, enough time).

鈥楿鈥� is for Understandable

This web accessibility principle refers to ensuring that both the content and the features of a website can be understood and make sense. Content that uses complex language and a lot of acronyms may be difficult to understand for persons with some forms of disabilities, as well as for users who are non-native speakers.

  • See specific references on the Masthead page (input assistance, readable), under Footer (designing with HTML), and under Homepage (predictable, page hierarchy).

鈥楻鈥� is for Robust

Digital content must be robust enough to be interpreted by a wide variety of user agents: various browsers and assistive technologies. In other words, if you choose custom content, ideally a standard version should be provided in an established standard format (such as HTML and XML) to ensure that web content is properly interpreted via agents.

  • See specific references under Homepage (documents and PDFs, compatibility).