Accessibility Statement & Controls
Volunteer Oakville is committed to digital inclusion, ensuring that community opportunities and resources are accessible to everyone.
Try Accessibility Preferences Now
Adjust reading, contrast, and navigation preferences below. Changes take effect instantly and persist across all pages on this device without requiring an account.
Accessibility & Typography
Customize reading comfort, text scaling, visual contrast, and keyboard navigation controls for this device.
Scale interface and reading text proportionally across the entire site.
Switch site typography to Lexend to improve character recognition and reading comfort.
Increase line height, letter spacing, and word spacing to reduce visual crowding.
Sharpen text and border contrast, remove background blur, and underline all links.
Display high-visibility amber and indigo outlines around the active keyboard-focused element.
Minimize UI animations, smooth scrolling, and decorative transitions.
Live Typography & Contrast Preview
Volunteering with Volunteer Oakville connects you directly with neighborhood groups, environmental initiatives, and youth education programs. Our community benefits when everyone can participate fully.
This sample paragraph immediately reflects your chosen font family, letter and word spacing, text scale, and link styling preferences.
Built Into Every Page
Beyond user-configurable toggles, our platform incorporates accessible engineering patterns across all templates.
Skip to Main Content
Keyboard visitors can jump straight to primary content (#main-content), bypassing repeating navigation banners.
Focus Indicators & Padding
High-contrast 2px/4px focus rings remain visible at all times, with root scroll-padding preventing fixed headers from obscuring active elements.
Semantic Landmarks
Every page uses single main landmarks, labelled navigation bars, and hierarchical heading trees for screen readers.
Forced-Colours Mode
Windows High Contrast and OS forced-colours modes are supported with native system-colour borders, outlines, and switch states.
Form Error Association
Submission validation errors are declared in role=alert error summaries, connected via aria-describedby directly to fields.
Autofill & AT Identification
All contact and personal fields specify standardized autocomplete tokens (email, tel, name, address) for automated input assistance.
WCAG 2.2 AA Conformance Matrix
Exhaustive criteria audit across all 56 WCAG 2.2 Level A and AA success criteria, organized by principle.
1. Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
| Criterion | Level | Status | Implementation Details |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Partial | Core UI icons, illustrations, and logos provide accessible text alternatives. Third-party community uploads (event flyers, user photos) may lack descriptive alt text. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Not Applicable | Platform does not host native prerecorded audio-only or video-only media. |
| 1.2.2 Captions (Prerecorded) | A | Not Applicable | Embedded video content from third parties is hosted on external platforms (e.g. YouTube) with native captioning. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | No prerecorded video media hosted directly on platform. |
| 1.2.4 Captions (Live) | AA | Not Applicable | Platform does not broadcast live synchronized media streams. |
| 1.2.5 Audio Description (Prerecorded) | AA | Not Applicable | No prerecorded video media hosted directly on platform. |
| 1.3.1 Info and Relationships | A | Meets | Semantic HTML5 landmarks (<header>, <nav>, <main>, <section>, <footer>), strict heading hierarchies (H1-H6), and accessible table headers (<th scope="...">) ensure relationships are programmatically determinable. |
| 1.3.2 Meaningful Sequence | A | Meets | DOM reading sequence mirrors visual layout flow and preserves narrative logic across responsive breakpoints. |
| 1.3.3 Sensory Characteristics | A | Meets | Instructions and feedback never rely exclusively on shape, color, size, visual orientation, or sound. |
| 1.3.4 Orientation | AA | Meets | Views operate seamlessly in both portrait and landscape display orientations without content locking. |
| 1.3.5 Identify Input Purpose | AA | Meets | Contact, authentication, and profile inputs declare standard HTML5 autocomplete tokens (email, tel, name, street-address, postal-code). |
| 1.4.1 Use of Color | A | Meets | Color is never used as the sole method of conveying information; alerts, badges, and active navigation states use icons, text, and underlines. |
| 1.4.2 Audio Control | A | Meets | Platform plays no unsolicited audio or automatic sound effects. |
| 1.4.3 Contrast (Minimum) | AA | Meets | Body text achieves at least 4.5:1 contrast against backgrounds; large text and headings achieve at least 3:1 in both light and dark themes. |
| 1.4.4 Resize Text | AA | Meets | Text scales up to 200% via browser zoom or the in-app reading controls without truncation or loss of functionality. |
| 1.4.5 Images of Text | AA | Meets | Real text rendered in CSS is used throughout rather than rasterized images of text, except for organization logotypes. |
| 1.4.10 Reflow | AA | Meets | Layout reflows down to 320 CSS pixels without requiring horizontal scrolling or loss of information. |
| 1.4.11 Non-text Contrast | AA | Partial | Focus indicators, form boundaries, and UI components meet 3:1 contrast; Leaflet map marker pins and selected tertiary badges are undergoing contrast tuning. |
| 1.4.12 Text Spacing | AA | Meets | Content accommodates custom line height (1.5x), paragraph spacing (2x), letter spacing (0.12em), and word spacing (0.16em) with zero clipping. |
| 1.4.13 Content on Hover or Focus | AA | Partial | Dropdowns and custom tooltips are hoverable, persistent, and dismissible via Escape. Interactive Leaflet map pin popups are being enhanced for full keyboard dismissibility. |
2. Operable
User interface components and navigation must be operable.
| Criterion | Level | Status | Implementation Details |
|---|---|---|---|
| 2.1.1 Keyboard Navigation | A | Meets | All functional features, modals, filter drawers, and interactive forms are operable via keyboard alone. |
| 2.1.2 No Keyboard Trap | A | Meets | Modal dialogs trap focus while open and release focus upon closure or pressing Escape, without trapping the user. |
| 2.1.4 Character Key Shortcuts | A | Meets | Single-character shortcut keys are not active unless an input or textarea has focus, avoiding accidental voice/switch activation. |
| 2.2.1 Timing Adjustable | A | Meets | User sessions provide advance warning notifications prior to timeout with the ability to extend the session. |
| 2.2.2 Pause, Stop, Hide | A | Meets | Any moving or animating content respects prefers-reduced-motion and provides pause/stop mechanisms. |
| 2.3.1 Three Flashes or Below Threshold | A | Meets | No content flashes more than three times in any one-second period. |
| 2.4.1 Bypass Blocks | A | Meets | A visible-on-focus skip link bypasses navigation and brings users directly to main content. |
| 2.4.2 Page Titled | A | Meets | Every page delivers a unique, descriptive <title> tag reflecting current section and active context. |
| 2.4.3 Focus Order | A | Meets | Keyboard focus moves sequentially in a logical and predictable order matching the visual interface. |
| 2.4.4 Link Purpose (In Context) | A | Meets | Links provide descriptive text or aria-labels disambiguating generic actions (e.g. 'View details for Tree Planting'). |
| 2.4.5 Multiple Ways | AA | Meets | Multiple mechanisms are available to locate opportunities and content: global navigation, search filters, sitemaps, and directory listings. |
| 2.4.6 Headings and Labels | AA | Meets | Headings and form labels clearly describe the topic or purpose of sections and interactive fields. |
| 2.4.7 Focus Visible | AA | Meets | Standardized high-contrast 2px offset + 4px focus rings communicate keyboard focus on all interactive elements. |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Meets | Scroll-padding-top ensures in-page anchors and focused controls are never hidden behind the fixed site header. |
| 2.5.1 Pointer Gestures | A | Meets | All multi-point or path-based gestures can be completed with a single pointer tap or click. |
| 2.5.2 Pointer Cancellation | A | Meets | Functions execute on up-event (click), allowing users to abort actions by dragging the pointer away before releasing. |
| 2.5.3 Label in Name | A | Meets | For all controls with visual labels, the programmatic accessible name contains the visible text string. |
| 2.5.4 Motion Actuation | A | Meets | No functionality is triggered by shaking, tilting, or physically moving the device. |
| 2.5.7 Dragging Movements | AA | Meets | All actions achievable by dragging or gesturing can also be completed with simple button taps or key presses. |
| 2.5.8 Target Size (Minimum) | AA | Partial | Primary buttons and touch targets meet 24x24px targets; select inline breadcrumbs and dense table action icons are being expanded. |
3. Understandable
Information and the operation of the user interface must be understandable.
| Criterion | Level | Status | Implementation Details |
|---|---|---|---|
| 3.1.1 Language of Page | A | Meets | The default human language of each page is declared via the html lang attribute ('en' or 'fr'). |
| 3.1.2 Language of Parts | AA | Meets | Multilingual sections and phrases specify appropriate lang attributes when switching between French and English. |
| 3.2.1 On Focus | A | Meets | Receiving keyboard focus never initiates unexpected context changes or form submissions. |
| 3.2.2 On Input | A | Meets | Changing the setting of any form control does not automatically trigger context changes unless the user has been forewarned. |
| 3.2.3 Consistent Navigation | AA | Meets | Navigation mechanisms repeat in identical relative orders across all platform templates. |
| 3.2.4 Consistent Identification | AA | Meets | Components with identical functionality are consistently named and styled across the site. |
| 3.2.6 Consistent Help | A | Meets | Help and contact options appear consistently in identical relative orders across header navigation and footer. |
| 3.3.1 Error Identification | A | Meets | Form validation errors are identified in text, highlighted in red, and linked with aria-describedby error blocks. |
| 3.3.2 Labels or Instructions | A | Meets | Inputs provide clear visual labels and instructional placeholder/help text. |
| 3.3.3 Error Suggestion | AA | Meets | When an input error is detected, suggestions for correction are provided in plain text unless doing so jeopardizes security. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Meets | Actions causing data loss, account cancellation, or application withdrawal require explicit confirmation dialogs. |
| 3.3.7 Redundant Entry | A | Meets | Information previously entered in multi-step workflows is auto-populated or available for reselection. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Partial | Password managers and FIDO2/WebAuthn passkeys are supported; reCAPTCHA v2 fallback remains under active replacement. |
4. Robust
Content must be robust enough that it can be reliably interpreted by a wide variety of user agents, including assistive technologies.
| Criterion | Level | Status | Implementation Details |
|---|---|---|---|
| 4.1.1 Parsing | A | Meets | HTML markup uses valid opening and closing tags, unique IDs, and well-formed attributes conforming to HTML5 standards. |
| 4.1.2 Name, Role, Value | A | Meets | Custom controls (switches, drawers, tabs, modals) expose standard ARIA roles, states, and accessible names. |
| 4.1.3 Status Messages | AA | Meets | Dynamic DOM updates (e.g. search filter updates, toast notices) are announced via role=status / role=alert and aria-live regions. |
How We Test & Verify
Automated testing catches approximately 30-40% of digital accessibility barriers. We combine multiple automated rule engines with mandatory manual audits.
Automated CI Testing Lanes
- Axe-core (Playwright & pa11y-ci): Automated scanning across 15+ public and authenticated views on every pull request.
- IBM Equal Access Accessibility Checker: DAP rule analysis validating ARIA landmarks and screen reader announcements.
- Playwright E2E Regression Gates: Verification of forced-colours high contrast, focus visibility, and HTMX DOM swaps.
- Static Architecture Guards: Pre-commit checks enforcing heading level continuity and button labeling.
Manual Verification Passes
- Full Keyboard Navigation: Verifying tab sequence, visible focus rings, escape key dismissal, and focus trapping.
- Screen Reader Audits: Manual validation with NVDA, VoiceOver, and Orca across core volunteering workflows.
- 400% Zoom / Reflow Audits: Inspection at 320 CSS pixels to ensure responsive reflow without clipped content.
- Windows High Contrast: Validation across dark and light OS system palettes.
Known Limitations & Alternatives
We believe in being transparent about current accessibility gaps while active remediation is underway.
Interactive Leaflet Maps
Dynamic interactive map tiles on directory and event views can be difficult to navigate via screen readers. Text-based listings and search filters provide full equivalents for every mapped item.
User-Uploaded Community Documents & Images
Third-party community organizations may upload PDF flyers or event graphics lacking alternative text descriptions. We prompt organization managers for descriptions and provide manual remediation on request.
CAPTCHA Verification Challenges
Automated bot protection during registration may present visual challenges. Audio alternatives and passkey-based registration are provided to mitigate cognitive hurdles.
Formal Accessibility Statement
Volunteer Platform is partially conformant with WCAG 2.2 Level AA guidelines. Partially conformant means that some parts of the content do not yet fully conform to the accessibility standard.
Statement Reviewed: 2026-11-18 (Version 2.2.0)
Feedback & Remediation: We welcome feedback on the accessibility of this site. If you encounter an accessibility barrier or need content in an alternative format, please contact our accessibility coordinator:
- Online Form: Contact & Feedback Form
- Email: info@volunteeroakville.ca
- Response Commitment: We aim to respond to accessibility inquiries within 2 business days and implement fixes promptly.
Frequently Asked Questions
Do my accessibility preferences carry over to other devices?
Preferences are stored in your device's localStorage so that you do not need to log in to enjoy customized reading comfort. Because they are device-specific, you can configure different settings on your phone, tablet, or desktop computer.
What is the difference between High Contrast mode and Dark Mode?
Dark Mode adjusts the site color palette for low-light environments. High Contrast mode enforces strict WCAG AAA contrast ratios, outlines all cards and interactive controls, eliminates background transparencies, and underlines all links.
Why does the site use the Lexend font for dyslexia support?
Lexend is an open-source variable font specifically designed to reduce visual stress and improve reading speed and comprehension for individuals with dyslexia and other reading difficulties.
Help Us Build a More Accessible Community
If you experience any difficulty accessing content or have ideas for improving accessibility, we want to hear from you.