Skip to end of metadata
Go to start of metadata
Accessibility is important to us
The issue of accessibility is a subject that's close to our hearts. We want to make it a priority to remove any barriers or restrictions so Linchpin works for you - the way you want it to.
In February of 2021, we participated in a workshop on accessibility development with our developers, UI designers and product owners. We wanted to gain insight into what we had done right, and what still lies ahead. The workshop confirmed what we had already suspected - we have a long way to go.
Currently we are working on improvements in navigating through Linchpin with keyboard and/or screen reader. The goal of this first step is to allow a user of keyboard navigation and/or a screen reader to reach all contents within Linchpin easily. Improvements will be available with regular Feature-Releases of Linchpin, so you might want to keep an eye on the release notes of those.
Is Linchpin accessible?
Unfortunately at this point, no. We're currently taking a look at all our to-do's, both large and small and we haven't conducted a BITV test with Linchpin yet.
Contact us if you'd like to be kept up-to-date on this topic specifically.
Will Linchpin become accessible?
Whether Linchpin can be 100% accessible in the future is unclear at this point. The basis for Linchpin Data Center is Confluence, and almost every Linchpin system is extended by apps from other providers. These are issues that we, as the provider of just Linchpin, have very little influence over.
In a social intranet, content is, ideally, created by a large number of employees. As a product vendor, we can only influence the accessibility of the content to a limited extent.
Issues like whether videos have captions for the hearing impaired, if images have alt text, or if the heading hierarchy makes sense - this is where the content creators come in. This is something you can take on internally by training your colleagues to be aware of these issues when creating your content.
Differing levels of accessibility in one intranet
After many discussions with customers about their requirements and priorities, we drew up a rough plan that we can use to take on all the areas of Linchpin that still need work.
This is the most important level because it affects everyone. Whether you need a strong contrast, navigate with a keyboard or use a screen reader - all content should be accessible and consumable. This is the basic level that all other levels need to be based on. This is our focus.
Likes, comments and writing microblogs
A social intranet thrives on the engagement of the people within an organization and not just passive consumption. One of the reasons Linchpin is so well-liked is because it offers so many possibilities. Some things should be relatively easy to implement in terms of accessibility - others will be more complex. This is something we're evaluating on a closer level.
Writing news articles and creating events
Another important aspect of a social intranet is content creation by as many users as possible. Writing news, creating events and designing pages deal with more complex editors and forms. This creates more of a challenge when dealing with accessibility issues.
In many cases, Confluence's own editor comes into play for things like page creation and news. That means we have limited influence in what we can do to improve these things. We rely on Confluence and what it offers out-of-the box, heavily.
We're currently not planning to tackle the accessibility issue from the system administration side. Unfortunately, the effort vs. gain ratio doesn't warrant this according to our customers, because they don't have a need for an improvement on that end.
Should you have any questions, or would like to be kept up-to-date please use the contact form to get in touch with us. We will be able to give you the latest Linchpin status updates on a quarterly basis.
This page was last edited on 01/27/2022.