Quebec Web Accessibility Standards: SGQRI 008 Compliance Guide

Quebec's web accessibility standard: SGQRI 008 overview: - Standard from Quebec government - Based on WCAG 2.0 Level AA - Required for government websites - Recommended for all Quebec businesses - Ensures accessibility for people with disabilities Who must comply: - Quebec government websites (mandatory) - Public sector organizations - Organizations receiving government funding - Businesses wanting government contracts Who should comply: - Any business serving Quebec public - E-commerce sites - Service businesses - Educational institutions - Healthcare providers Benefits beyond compliance: - Expands market (15% of Canadians have disabilities) - Better SEO - Improved usability for everyone - Legal risk reduction - Demonstrates social responsibility

What SGQRI 008 requires: Perceivable content: - Text alternatives for images (alt text) - Captions for videos - Audio descriptions where needed - Content adaptable to different presentations - Sufficient color contrast - Resizable text Operable interface: - Keyboard navigation (no mouse required) - Sufficient time to read/use content - No content that causes seizures - Clear navigation structure - Meaningful link text Understandable content: - Readable text (appropriate language level) - Predictable navigation - Input assistance for forms - Error identification and suggestions - Language identified Robust content: - Compatible with assistive technologies - Valid HTML markup - Proper semantic structure - ARIA labels where appropriate

Issues found on most websites: Images without alt text: - Screen readers can't describe images - Alt text should be descriptive - Decorative images need empty alt ("") - Don't say "image of" (implied) Poor color contrast: - Text too light on light backgrounds - Minimum 4.5:1 ratio for normal text - 3:1 for large text - Don't rely on color alone for meaning Keyboard navigation problems: - Can't access features without mouse - No visible focus indicators - Illogical tab order - Keyboard traps Form accessibility: - Missing labels - Poor error messages - No instructions - Required fields not indicated Heading structure: - Skipping heading levels (H1 to H3) - Multiple H1s on page - Not using headings for structure - Headings not descriptive Video and audio: - No captions or transcripts - Auto-playing media - No pause controls

Practical steps to make your site accessible: Design phase: - Choose accessible color schemes - Plan clear navigation structure - Design for keyboard users - Include accessibility in wireframes - Test designs for contrast Development: - Use semantic HTML - Implement ARIA labels properly - Ensure keyboard navigation - Add alt text to all images - Create accessible forms - Use proper heading hierarchy Content creation: - Write clear, simple language - Use descriptive link text - Break up long content - Add captions to videos - Provide transcripts Testing: - Automated tools (WAVE, axe) - Manual keyboard testing - Screen reader testing - Real user testing - Regular audits For bilingual sites: - Accessibility in both languages - Language switching accessible - Consistent navigation both languages - Alt text translated

Helpful accessibility tools: Testing tools: - WAVE (browser extension) - axe DevTools - Lighthouse (in Chrome) - Color Contrast Analyzer - NVDA or JAWS (screen readers) Development resources: - WCAG 2.0 guidelines - SGQRI 008 documentation - WebAIM guides - A11Y Project - MDN accessibility docs Montreal resources: - AlterGo (accessibility consulting) - AccessibilitéWeb - Quebec government resources - Local accessibility experts Ongoing maintenance: - Regular accessibility audits - Update as content changes - Stay current with standards - Train content creators - Budget for accessibility Accessibility isn't one-time—it's ongoing.

Budgeting for accessibility: New website: - Build accessibility in from start - Adds 10-15% to development cost - Much cheaper than retrofitting - Include in initial scope Existing website remediation: - Audit: $2,000-$5,000 - Minor fixes: $5,000-$15,000 - Major overhaul: $15,000-$50,000+ - Depends on current state Ongoing costs: - Content training - Regular audits - Updates as standards evolve - Testing new features ROI considerations: - Expanded market reach - SEO benefits - Reduced legal risk - Better user experience - Government contract eligibility Most businesses find accessibility investment pays for itself.