Warning
this is a page is in draft and has not yet been edited or approved
Accessibility at Progress
Progress is committed to making the Infra 360 Design System (I3DS) accessible for all users. Accessibility is not only a fundamental aspect of good design but also an opportunity to build products that are usable by people of all abilities. Incorporating accessibility from the start of every design and development project ensures a more inclusive experience for everyone.
Approximately 16% of the world’s population has a disability, according to the World Health Organization, and many more experience temporary or situational disabilities. Designing with accessibility in mind benefits everyone by creating products that are easier to use and understand.
Why Accessibility Matters
Accessible design allows users with disabilities to perceive, navigate, and interact with digital products. When accessibility is integrated early in the design process, it becomes a seamless part of the product, reducing the need for costly rework and improving usability for all.
Accessible products consider various disabilities, including:
- Visual: Accommodates people with visual impairments, such as blindness or color blindness.
- Hearing: Supports users who are Deaf or hard of hearing with alternatives for audio content.
- Mobility: Assists those with physical impairments, such as limited use of hands, by supporting keyboard navigation and other input options.
- Cognitive: Provides clarity and simplicity for those with memory or processing challenges.
Types of Disabilities:
- Permanent: Disabilities that do not change over time (e.g., someone who is blind).
- Temporary: Conditions that are resolved over time (e.g., a broken arm).
- Situational: Conditions dependent on the environment (e.g., using a device in bright sunlight).
Accessibility Standards
Progress aims to meet or exceed the Web Content Accessibility Guidelines (WCAG) 2.1 AA standards. Following these guidelines ensures that all components are perceivable, operable, understandable, and robust, making them usable by a wide range of people with disabilities.
Key Standards Include:
- WCAG 2.1 AA Compliance: Ensures accessible web content.
- Section 508 Compliance: Aligns with U.S. legal standards for accessibility.
Principles of Accessible Design
-
Make Interactions Consistent
Accessibility requires consistency across platforms and devices. The same solutions should solve the same problems, regardless of screen size, device, or assistive technology. Using I3DS components creates a cohesive experience that feels familiar to all users. -
Provide Text Alternatives
Text is essential for accessibility. Whether visual (text on-screen), auditory (text-to-speech), or tactile (braille), good labeling, alt text, and transcripts ensure that assistive technologies can interpret content effectively. -
Use Accessible Colors
Color should never be the sole method for conveying meaning. I3DS components adhere to contrast standards (4.5:1 for normal text and 3:1 for large text) to ensure content is perceivable for those with color vision deficiencies or low vision. -
Give People Control
Designs should adapt to user needs. Components are responsive and adjustable, with options for dark mode, reduced motion, and enhanced contrast to accommodate personal preferences and settings. -
Use Semantic HTML
Semantic HTML gives structure and meaning to web elements, enabling assistive technologies to interpret and navigate content accurately. Elements such as headings, sections, and navigation areas are used instead of generic tags to improve accessibility. -
Be Inclusive
Accessibility is for everyone, and inclusive design reflects diverse races, ethnicities, genders, and backgrounds. I3DS considers intersectional accessibility, supporting users with multiple disabilities or those from marginalized communities. -
Keep It Simple
Respect users' time by creating clear, straightforward interfaces that help them accomplish tasks without frustration or confusion. An accessible experience is an uncomplicated one.
Accessible Development with I3DS
I3DS provides accessible components that follow best practices for inclusive design. Each component is built with appropriate ARIA roles, semantic HTML, and accessible markup as a foundation for building usable applications. By default, I3DS components include:
- Accessible Forms: Proper use of
<fieldset>and<legend>tags, clear labeling, and intuitive form controls. - Keyboard Navigation: Components are designed to support keyboard interactions, enabling users with mobility challenges to navigate without a mouse.
- Color and Contrast Compliance: Adherence to WCAG color contrast requirements for readability and accessibility.
- Text Alternatives for Images and Icons: Text descriptions for non-text elements, ensuring content is available to screen readers.
Testing for Accessibility
To maintain high standards for accessibility, it’s crucial to test components and applications with a wide range of users and devices. We recommend the following:
- Manual and Automated Testing: Combine automated tools with manual tests to capture real-world accessibility insights.
- Diverse User Testing: Include users with varying disabilities, devices, and technical expertise.
- Continuous Feedback Loops: Regularly update and refine components based on user feedback, testing results, and evolving standards.
By following these principles and using I3DS components, Progress is committed to building accessible digital experiences that enable everyone to interact with, understand, and navigate our products seamlessly.