Accessibility

Every Lineset app is drawn inside Jira with Atlassian’s own components, so it follows Jira’s keyboard, focus and screen reader behaviour. This page says what we build on top of that, what is not there yet, and how to tell us when something does not work for you.

In the apps

• Keyboard. Every button, chip, menu and link is reached with Tab and pressed with Enter. A filter chip’s menu opens, picks and closes from the keyboard, and keeps your place while the page draws again.
• Names a screen reader says. A button is named by its words, never by its icon; a filter that is on or off says “On” or “Off” before its words. Tables carry a name, such as “Timesheet: Team week, 28 Sep – 4 Oct”. A row’s chevron says whether it opens or closes.
• Reasons in words. A button that cannot be pressed yet says why on the page, such as “Recalculate in 1 min”, not only in a tooltip a keyboard never reaches.
• Not by colour alone. Blockline writes every level as a word: OK, Watch, At risk, Blocked. Logline’s yellow and red marks say what they are when you point at them, and Sumline names every warning.
• Blockline’s dependency map. Every box on the map is a link: Tab moves along the chain and Enter opens the work item.
• Light or dark. The apps take Jira’s own colours, so they follow the theme you choose in Jira.
• Three screens. Every page is designed and checked on a 1920 and a 1440 pixel screen and a 390 pixel phone. A row of controls wraps onto the next line instead of running off the screen.

On these websites

Every page reads with JavaScript off, starts with a link that skips to its content, and gives every screenshot a text alternative. A screenshot wider than a phone scrolls sideways in a frame of its own, named for a screen reader.

Not there yet

• Small tap targets in Logline. The figures in Logline’s timesheet, each a button that lists its worklogs, are smaller than the 24 pixels WCAG 2.2 asks of a tap target.
• Wide tables on a phone. A table wider than the screen scrolls sideways in its own box rather than folding into a list.
• A chosen chip. A filter chip that is on is drawn pressed, but Jira’s button does not tell a screen reader so; the “On” before its words carries it instead.
• A greyed choice. A chip or a menu row that does not apply is greyed and says why on hover; a keyboard that cannot reach a greyed control does not hear the reason.
• Jira’s own parts. The cross that removes a chosen value from a multi-select is Atlassian’s, 16 pixels wide, and an app cannot resize it. Backspace in the field removes the value too.

What we hold ourselves to

The target is WCAG 2.2 at level AA. Every page of every app is checked with axe in the UI checks that run before each release, walked with the keyboard, and looked at on the three screens; a screen reader pass is done by hand on each surface before a release that changes it. There is no VPAT yet; this page is reviewed with each release and says when it last was: 25 October 2026.

Tell us

If something in an app or on these websites does not work with your keyboard, screen reader, zoom or phone, tell us through our support site or by email at support@lineset.dev: what you were doing, where, and with which browser and assistive technology. We answer within one business day, Monday to Friday.