How we’re building more inclusive and accessible components at GitHub

We’ve made improvements to the way users of assistive technology can interact with and navigate lists of issues and pull requests and tables across GitHub.com.

Eric Bailey
4 min readbeginner
--
View Original

Overview

GitHub emphasizes its commitment to diversity and inclusivity by enhancing the accessibility of its components. The article outlines the improvements made to lists of issues, pull requests, and tables, highlighting the importance of user participation, especially from those who use assistive technologies.

What You'll Learn

1

How to improve accessibility in software components

2

Why direct participation from assistive technology users is crucial

3

How to implement consistent navigation for assistive technologies

4

When to utilize Primer components for tables

Key Questions Answered

What improvements are being made to GitHub's lists of issues and pull requests?
GitHub is enhancing its lists of issues and pull requests by adding dedicated subheadings for navigation, keyboard shortcut support for screen readers, and improved focus management. These updates aim to make navigation more efficient for users of assistive technologies.
Why is user participation important in accessibility efforts?
User participation, especially from those who rely on assistive technologies, is vital as it ensures that the design and development processes are informed by real-world experiences. This involvement helps GitHub to create genuinely inclusive experiences that go beyond mere compliance.
What is the significance of using Primer components for tables?
Using Primer components for tables provides consistency and predictability in navigation and interaction. This approach replaces bespoke implementations with a standardized solution, enhancing the overall user experience and aiding assistive technology users.
What philosophy guides GitHub's approach to accessibility?
GitHub's approach to accessibility is influenced by the 'Progress Over Perfection' philosophy, which emphasizes iterative improvements based on user feedback. This mindset acknowledges that accessibility is an ongoing process that must evolve to meet users' needs.

Key Statistics & Figures

Number of bespoke tables replaced with Primer components
75
This statistic highlights the scale of GitHub's efforts to standardize and improve accessibility across its platform.

Technologies & Tools

Frontend
Primer
Used for creating consistent and accessible table components across GitHub.

Key Actionable Insights

1
Incorporate user feedback from assistive technology users during the design process.
This practice ensures that the components you develop are genuinely accessible and meet the needs of all users, particularly those with disabilities.
2
Utilize dedicated subheadings and keyboard shortcuts to enhance navigation in your applications.
These features significantly improve the user experience for individuals using assistive technologies, making your application more inclusive.
3
Adopt a consistent design system like Primer for your tables.
This helps streamline the user experience across your application, making it easier for users to navigate and interact with complex data.
4
Embrace the philosophy of 'Progress Over Perfection' in your accessibility initiatives.
This approach allows for continuous improvement and adaptation based on user needs, ensuring that your solutions remain relevant and effective.

Common Pitfalls

1
Neglecting to involve users of assistive technologies in the design process.
This can lead to products that do not meet the needs of all users, resulting in a lack of true inclusivity and potentially alienating a significant portion of the user base.

Related Concepts

Accessibility Best Practices
User-centered Design
Inclusive Design Principles