Accessibility
This documentation is no longer being updated. For the most up to date information please visit our techdocs
Home > CHEFS Capabilities > Accessibility
Accessibility is important because it empowers everyone to use the forms you'll build with CHEFS. It ensures equal access and inclusion, enabling individuals to use forms on an equal footing. By making forms accessible, such as providing clear instructions and appropriate labels, we empower people to fully engage and participate. Accessibility not only benefits all users but also improves their experience and ensures compliance with accessibility standards. It fosters an inclusive environment where everyone can confidently and independently interact with CHEFS forms.
Our goal is to go above the minimum compliance requirement level AA of the Web Content Accessibility Guidelines 2.1 (WCAG 2.1).
We are committed to meeting your needs no matter how you use the service. We understand that people may have different needs for accommodation. To make sure we can be inclusive of everyone, we want to learn from you.
To tell us about accessibility issues on Submit, you can:
- Reach out to us through our CHEFS Exchange Lab - Teams Channel
- Email us at submit.digital@gov.bc.ca
- Create an issue on our public GitHub repository
We will work with you to:
- Understand issues you’ve encountered and how they impact you
- Log all bugs in our product backlog and address them with high priority.
- Resolve issues as soon as we can
We are grateful for your feedback and insights.
The form components used in CHEFS already include accessibility features. ARIA attributes make labels, tooltips, and descriptions accessible to screen readers and other tools. However, form developers still need to be mindful of accessibility principles to create truly inclusive experiences. The built-in accessibility features of CHEFS form components allow form developers to focus on other accessibility considerations.
As an example, the Vox screen reader for the Chrome browser will read this component:
as "This is the label. This is the tooltip. This is the description. Within: This is the placeholder. Edit text". Note that the user does not need to hover, etc, to “pop up” the tooltip to have it read out.