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, and a chip that holds a choice names it, such as “Status: Done”. 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. Recalculate says why it cannot be pressed yet on the page, “Recalculate in 1 min”, not only in a tooltip a keyboard never reaches. A greyed row in a menu writes its reason under its words.
• Not by colour alone. Blockline writes every level as a word: OK, Watch, At risk, Blocked. Sumline names every warning. Logline’s yellow and red marks carry their figure.
• Tap targets. A figure that opens something, such as an hours figure in Logline’s timesheet or a cell in Blockline’s team matrix, is a target of at least 24 by 24 pixels, as WCAG 2.2 asks.
• Blockline’s dependency map. Every box on the map is a link that names its level and date: Tab moves from box to box 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 for a 1920 and a 1440 pixel screen and a 390 pixel phone, and looked at on all three. 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 too wide for a phone scrolls sideways there, in a frame a keyboard can reach and a screen reader names; on a larger screen it fits. A row of pills over a screenshot is a group of radio buttons named for what it picks, moved with the arrow keys. A guide or a docs page names its place in a trail above its title.

Not there yet

• Wide figure grids on a phone. The tables of figures, Sumline’s roll-up tables, Logline’s timesheet and Blockline’s team matrix, are wider than the screen and scroll sideways in their own box, as does Logline’s list of saved reports. Every other table folds into a card per row on a phone, and a folded table does not carry its name there.
• 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, or the choice it names, carries it instead.
• A greyed chip. A chip that does not apply is greyed and says why on hover; a keyboard that cannot reach a greyed control does not hear that reason. The same holds for a greyed button other than Recalculate.
• Logline’s marks. In the timesheet, the yellow mark on a figure under what is expected and the red mark on a figure over its estimate say what they mean only when you point at them; a keyboard or a screen reader gets the figure alone, such as “-3h” or “130%”.
• 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, against WCAG 2.1 A and AA on a desktop screen; the WCAG 2.2 rules, such as target size, are held by tests in the code. Each surface is walked with the keyboard and looked at on the three screens. These websites are not checked by axe yet, and a pass with a screen reader is not yet part of every release. There is no VPAT yet. This page is checked against the apps every month and with each release, and says when it last was: 26 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.