Web accessibility means ensuring that people with a range of sight, hearing, movement, and cognitive abilities can use SmartSimple. SmartSimple strives to meet Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA or higher.
Who: System administrators
When to Use Accessibility Principles
Use accessibility principles when:
- Preparing to configure a SmartSimple system and you need to understand what accessibility requirements apply.
- Reviewing existing system configuration or content to identify potential accessibility gaps.
- Responding to user or auditor inquiries about accessibility compliance.
- Your organization must comply with specific accessibility legislation, such as WCAG, ADA, AODA, or EAA.
Assistive Technologies
Assistive technologies are tools or devices that help individuals overcome or manage disabilities. Common examples include eye tracking devices, switches, sip and puff devices, refreshable braille keyboards, screen readers, and screen magnifiers.
Screen Readers
Screen readers are among the most used assistive technologies. The most widely used screen readers are:
- Job Access with Speech (JAWS) — Used with Chrome.
- NonVisual Desktop Access (NVDA) — Used with Microsoft Windows.
- Apple VoiceOver — Used with Mac.
Screen readers on mobile devices use a gesture-based interface. Desktop screen readers use a keyboard-based interface. SmartSimple's primary accessibility testing is performed using the JAWS screen reader on desktop computers.
Guidelines and Legislation
Accessibility guidelines and legislation continue to evolve and vary by jurisdiction. The following are key standards and regulations that may apply to your organization.
WCAG
The Web Content Accessibility Guidelines (WCAG) are international standards published by the World Wide Web Consortium (W3C). They provide testable success criteria organized around four principles:
- Perceivable — Can users perceive the interface and the information presented?
- Operable — Can users navigate and operate the system?
- Understandable — Is the information comprehensible and the system usable?
- Robust — Can a range of assistive technologies be used with the system?
WAI-ARIA
Web Accessibility Initiative – Accessible Rich Internet Applications (WAI-ARIA) is a set of developer standards designed to improve the accessibility of web pages with dynamic content and specific UI components.
Section 508 (USA)
Section 508 of the U.S. Rehabilitation Act requires federal agencies to provide information in an accessible format.
ADA (USA)
The Americans with Disabilities Act (ADA) requires organizations in the United States to provide accessible information and prohibits disability-based discrimination.
California AB 434 (USA)
California state agencies and entities must display signed certification of compliance with WCAG 2.0 or higher.
European Accessibility Act (EAA)
EU member states must comply with WCAG 2.1 Level AA standards.
EU Web Accessibility Directive
Public sector organizations across the EU must comply with WCAG standards. The European standard for technology accessibility in the public sector is EN 301 549.
Equality Act 2010 (UK)
The UK Equality Act 2010 requires public sector organizations to ensure their websites are accessible.
Accessible Canada Act
The Accessible Canada Act (Bill C-81) applies to the federal government and federally regulated private sector.
AODA (Ontario, Canada)
The Accessibility for Ontarians with Disabilities Act (AODA) requires adherence to WCAG guidelines.
DDA (Australia)
The Disability Discrimination Act (DDA) 1992 prohibits disability-based discrimination and requires websites to comply with WCAG 2.0.
Testing for Accessibility
SmartSimple undergoes regular accessibility testing by internal teams and, on request, by third-party testers. Primary testing uses the JAWS screen reader on desktop computers.
Automated Testing Tools
The following tools are available for automated accessibility testing:
- Wave Toolbar — A free browser extension that highlights potential issues directly on a page.
- Accessibility Insights for Web — A free browser extension that identifies potential issues inline at the page level.
- Google Lighthouse — A free tool that conducts an accessibility audit at the page level.
- Siteimprove — A free browser extension with an overview of accessibility issues at the page level.
- AXE DevTools — A free browser extension with a premium tier for Chrome DevTools.
Additional tools for validators and contrast checking:
- W3C Markup Validator — Validates HTML and XHTML markup.
- W3C CSS Validator — Validates CSS markup.
- Accessible Colors — Checks contrast ratio of text against background.
- WebAIM Contrast Checker — Checks contrast ratio between foreground and background.
- a11y Contrast Checker — Checks contrast of content on a web page.
Beyond Automated Testing
Automated tools may produce false positives and may not identify usability errors. It is recommended to:
- Establish a user testing group. A group of five individuals is commonly recommended.
- Conduct usability testing.
- Consider a third-party audit.
SmartSimple Design, Development, and Testing Methodology
SmartSimple builds accessibility into its design, development, and testing processes at every stage.
Design — SmartSimple's design methodology applies an inclusive framework aligned with WCAG and the Perceivable, Operable, Understandable, and Robust (POUR) principles. The design process begins with empathetic research and analysis, addresses users with a range of abilities, and incorporates feedback throughout implementation.
Development — The development methodology mirrors the design approach, including accessible code practices aligned with WCAG and W3C standards. Internal code reviews and automated tools such as SonarQube are used for continuous code inspection.
Testing — The accessibility testing methodology aligns with WCAG standards and Section 508 baseline testing. External auditors and automated testing tools are also used as part of the quality assurance process.
Resources
For more information about accessibility, see: