Accessibilité
Accessibility is a foundational principle of the GNWT Design System. Every resident of the Northwest Territories should be able to access and use government services online — regardless of ability, device, or location.
Building accessible services is an expression of the GNWT’s commitment to equity, inclusion, and good service design.
Accessibility Principles
- Inclusive by design
Accessibility begins at the start of a project — during research, design, development, and testing — not as a final review step. - Usable by everyone
Accessible design benefits all users. Strong colour contrast, clear structure, and consistent interaction patterns make digital services easier to use for everyone, including those with slower internet connections, limited English proficiency, or mobile-only access. - Perceivable, operable, understandable, robust (POUR)
All GNWT components follow the four WCAG 2.2 principles to ensure that content can be perceived, operated, understood, and maintained across assistive technologies and future platforms. - Continuous improvement
Accessibility is never “done.” Regular audits, feedback, and updates keep the GNWT Design System and services aligned with changing standards, technologies, and user needs.
GNWT Accessibility Standards
The GNWT Design System follows the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as a minimum requirement.
These standards include but are not limited to:
- Keyboard navigation — All interactive elements must be fully usable without a mouse.
- Contrast and legibility — Text and interface elements must meet or exceed a 4.5:1 contrast ratio.
- Meaningful structure — Use semantic HTML with proper headings, lists, and landmarks for assistive technology.
- Visible focus indicators — Focus states must always be visible and clearly distinct.
- Descriptive alternatives — Images, links, and controls must include meaningful text alternatives.
- Responsive and adaptable layouts — Content must remain functional and readable on all screen sizes and orientations.
Accessibility testing is part of the GNWT Design System’s ongoing maintenance cycle.
All components are tested across browsers, devices, and assistive technologies before being added to the system.
Roles and Responsibilities
Accessibility is a shared responsibility across teams and vendors.
- Designers ensure that layouts, colour palettes, and visual elements meet accessibility standards and maintain adequate contrast and spacing.
- Developers implement semantic HTML, ARIA attributes, and accessible keyboard interactions.
- Content editors write in plain language, use descriptive link text, and include alternative text for all images.
- Quality assurance teams test for accessibility issues using both automated tools and manual testing with assistive technology.
- Vendor partners must follow GNWT’s accessibility and design system requirements when creating or maintaining services.
Reference: Accessible Canada Act (ACA) and WCAG 2.2 Overview.
Accessibility and the GNWT Design System
The GNWT Design System embeds accessibility into every component by default.
When you use a GNWT component, you automatically inherit built-in accessibility features such as:
- Proper semantic structure
- ARIA roles and labels
- Keyboard navigation support
- Visible focus indicators
However, accessibility can be lost if components are modified incorrectly. Always:
- Follow documented usage guidelines
- Avoid removing or overriding built-in accessibility attributes
- Test customized components in real user environments
Testing and Continuous Improvement
Accessibility testing should occur throughout the design and development process.
Use a combination of automated, manual, and user-based testing to identify and fix barriers early.
- Automated testing: Use tools such as Axe DevTools, Lighthouse, or WAVE.
- Manual testing: Test pages using only the keyboard and with screen readers such as NVDA, VoiceOver, or TalkBack.
- User testing: Include residents with diverse abilities and devices to ensure real-world usability.
Report accessibility issues or improvement ideas through the Design System feedback form so that learnings can be shared across departments.
Additional guidance: W3C Accessibility Testing Resources.
Key Takeaways
- Accessibility is a shared, ongoing responsibility.
- All GNWT services must meet WCAG 2.2 Level AA as a baseline.
- Accessibility improves usability for everyone.
- The GNWT Design System ensures accessible design is the default, not the exception.
- Testing early and often ensures services remain inclusive, effective, and trustworthy.