
At Exygy we believe that Accessibility should be Inclusive. Period. While we don’t always get it right the first time, we are committed to designing all of our products to be accessible to everyone.
It's central to our mission to ensure that the products and services we build are truly human-centered and reach as many people as possible. This is especially true for those that have been traditionally marginalized or underserved by technology. Is it therefore vital that we design for accessibility and inclusiveness from the outset.
We have brought this ideology of empathy into our entire design and development process by focusing on research, testing, and feedback from ALL our users. While we adhere to Section 508, 504, and WCAG accessibility guidelines, we are always seeking ways to further our commitment to accessibility and inclusivity.
We developed this framework to clearly communicate our commitment to accessibility and hold ourselves accountable. We hope that it helps educate, inspire, and aid in creating equal access to digital services for all.
Good question. Simply put - accessibility is ensuring our products can be used by as many people as possible.
Accessibility can mean different things to different folks so it’s helpful to clarify some terms as a starting point.
At least 1 in 5 people in the world are living with a disability. 1 Committing to web accessibility means ensuring that people with a range of disabilities can use your digital product. The disabilities that relate to digital accessibility include four types of users: 2
We are all required by law to make our design accessible to a certain degree.
What is required, however, is not nearly sufficient. We can do much better than the bare minimum! By sharing these ways to increase accessibility and inclusion we hope to bring others together around this common mission of making design accessible and to hold ourselves accountable as agents of equity.
Designing for accessibility takes commitment. To effect change and to break from the dominant narrative of non-accessible products, we must commit ourselves to create in a way that is human-centric for every one among us. The following commitments serve as starting places for our community here at Exygy.
Our core commitment to accessibility is an earnest intention to serve those underserved communities. Here are some things to keep in mind when deciding to focus on accessibility. Setting realistic expectations and creating alignment upfront can make a long-term commitment to accessibility more feasible. We are all in this for the long haul.
In a fast-paced world, our clients move quickly and often require us to make a rapid turnaround. Accessibility concerns can be neglected or deprioritized in the hurry to build things. Additionally, it takes time for team members to become familiar with a shared language and deliver accessible user experiences consistently across multiple platforms built on a wide range of technologies. Communicating that accessibility is a non-negotiable from the start can help develop an accurate timeline and budget.
The landscape regarding accessibility is still changing and adapting to meet the diverse needs of its intended audience. A commitment to accessibility doesn’t end once a project has been released but must continue to evolve as new avenues to reach people present themselves. Stay up to date with the conversation with these resources.
https://accessibility.civicactions.com/
https://accessibilitycluster.com/
https://www.w3.org/WAI/about/projects/wai-tools/
https://accessibe.com/
We are all required by law to make our designs accessible to a certain degree. What is required, however, is not nearly sufficient when it comes to providing equal access. To provide truly accessible content, an organization needs to commit to doing more than what is required. At Exygy, we are continuing to learn how we can go beyond what is required to be more inclusive. We hope you join us as we continue to learn how to better serve PwD.
We constantly throw around the term alignment at Exygy. In this instance, it is important to align on what success looks like so that everyone is working towards the same collective vision. Working out a standardized success metric can motivate, guide, and inspire teams as they design accessible platforms. Key metrics could include - time spent, money spent, team members engaged, usability, overall user experience, disabled people engaged, and total user engagement.
We firmly believe that we cannot be committed to accessibility without belonging to a community that reflects those beliefs. When we work collaboratively with relevant stakeholders and accountability partners we can produce the most inspired and holistic work. As most of us are able-bodied, it is important to include those we wish to serve throughout the entire design process.
Involving People with Disabilities (PwD) is crucial to catching key pain points in an accessible user experience. Their lived experience and first hand-feedback are necessary for catching the minutia that most users/designers may not catch. By involving them in the design research process they can give feedback on whether the intended result of a feature is accomplished.
It is important to note that there is a variety of experiences within the PwD and making sure that you include the appropriate people is vital. For example, if you are testing an auditory feature you should gather feedback from people with various types of auditory disabilities such as someone who is deaf or partially deaf. It just makes sense.
Teams focusing on accessibility benefit from a group-wide allegiance about goals for accessibility and how to be proactive in their pursuit of it. Ways to create a team that is centered around accessibility include - providing training about language/experience regarding accessibility, having communication channels to communicate with accessibility experts, and avenues to interact and develop relationships with PwD. Building community isn't always quick and easy. Be patient and persistent and if you need some encouragement we are always available at hello@exygy.com
It is invaluable to have the perspectives of people with disabilities talk regarding accessible products and services. They are the absolute best people to clearly articulate what would make their user experience better. Most of us probably don’t consider how our use of technology is contingent on the privilege of being able-bodied. There is so much to be learned about others’ experiences should we just ask.
It is everyone's responsibility to create an atmosphere of safety and inclusivity regarding accessibility and PwD. Nobody likes to be left out, yet often our digital tools are inherently difficult or impossible to use for PwD. We should always seek to use the most appropriate and current language when we are describing or discussing with people whose lived experiences are different from ours. When we do this, we honor their entire person.
Finally, there must be zero tolerance for any team member who has discriminatory, ableist, or derogatory viewpoints aimed at PwD. The inclusive design begins with a worldview that values everyone's experience as equal.
There is a worldwide community that is rallying to create a more equitable digital world for everyone. By joining the movement you can learn more, be inspired, and be held accountable by other organizations and individuals seeking the same thing. Try joining these communities with us!
https://accessibility.civicactions.com/playbook/community#:~:text=/accessibility%20subreddit
https://www.tpgi.com/anybody-can-be-an-a11y-slacker/
https://www.drupal.org/community/contributor-guide/reference-information/talk/tools/slack
Also, we would love to connect with you at Hello@exygy.com
Designing for accessibility should be present from the beginning to the end of a project. In the ongoing conversation at the intersection of Design and Accessibility here are some important starting places.
Bring in an accessibility expert along the way to help point out any missing links or perspectives in the design process. They are experts after all.
Try working with organizations that recruit people with disabilities to test your products using screen readers and assistive technology that they use every day.
Write out user stories to help empower product managers to ensure that accessibility guidelines are included in the acceptance criteria.
For low vision users, proper typographic contrast is important, both size and color. Foreground colors should stand out from background colors. We use tools to calculate the contrast ratio of your foreground and background colors. The contrast ratio should at least be 1:4.5 for normal text and 3:1 for large text.
Keyboard access. All website interactions should be accessed with a keyboard because it is the backbone upon which assistive technology on computers works.
Text Hierarchy. This is important because screen readers can also use headings and section titles to scan your page content like a document outline.
Accessible Forms. Forms are the primary source of transactions and user-submitted content so it’s critical that these elements are readable by screen readers and associated with their instructions and notifications of any potential errors. As a general rule, it is best to avoid PDFs completely. Google and screen readers cannot look into PDFs which makes them useless for many users with a disability.
Most screen readers include many shortcut keys to skip around a page. For example, a screen reader can read every heading on a page, or every link, making it easier to find the right content on the page. Don’t take shortcuts in design and make sure you work in accessibility shortcuts.
When posting photos anywhere, it is of vital importance to make sure that those images have relevant Alt text. The best example of this principle is the compelling and poetic language that NASA used to describe the images from the James Webbs telescope. Quality Alt Text goes beyond boosting SEO and provides real support for those who need it.
Engineers can set up automated testing tools to run in the background to catch easily identifiable accessibility issues.
Before releasing features, team members can perform a manual accessibility test using browser tools and keyboard commands.
As we engage with our community partners, it’s clear that we can expand the reach of our work and nest our accessibility efforts within a larger umbrella of inclusiveness. Inclusive design aims at serving cultural, social, and intersectional needs. 4
“Inclusive design is a design methodology that enables and draws on the full range of human diversity.” 5
Some of the solutions that fall under this category include designing for those with limited internet access, using inclusive and anti-racist language, and creating simple and intuitive interfaces for those with limited technological experience.
Designing for accessibility is just the first step in authoring a more inclusive future. Inclusive design may start with PwD but it aspires to fully embrace all how we can look towards design that proactively responds to all the barriers of engagement. Let's build a more equitable future together.