Improved

The claim and source libraries are fully keyboard-navigable

Both libraries' trees now follow the standard tree keyboard model: arrow up and down move through the rows you can see, right opens a closed branch and then steps into it, left closes an open one and then climbs to its parent, and Enter opens what you have landed on. The whole tree is a single tab stop, so tabbing past it no longer means pressing Tab once per row. Branch rows carry a disclosure arrow that shows whether they are open.

Publishing explains itself before you commit to it

The publish confirmation now says what publishing an argument actually does — the version becomes public and read-only, and anything you change afterwards goes into the next version you publish — instead of asking you to confirm an action it did not describe.

Fixed

A bad link is answered as a missing page, not a broken server

A link can carry anything in the part that names a claim, an argument, a review or a task, and until now a value that could never name one was answered as a server error — the kind of failure an app is entitled to retry, except that this one could never succeed. Those requests now get the same answer as a link to something that simply is not there, everywhere across the API rather than on the one place it was first noticed. Where a request could never have gone wrong on the server, nothing internal is reported back either.

Links that point at something real, and links that point at something that has been deleted or was never yours to see, behave exactly as before: an address that cannot exist is deliberately indistinguishable from one you are not allowed to know about.

Your saved-arguments toggle answers the same whether or not you are signed in

The bookmark control on a public page could get a different answer to the same question depending on whether you had signed in. It no longer can.

The arguments list always comes back a page at a time

Asking the arguments API for a page size it cannot honour — zero, a negative number, or more than 500 — is now answered as a bad request rather than quietly handing back the entire catalogue in one response. An ordinary request with no page size specified returns the first page as it always should have, and paging past it works unchanged.

Text fields, tooltips and dialogs look the way they were meant to

Clicking into a text field now shows a focus ring, so it is clear where typing will go — previously a focused field looked identical to an unfocused one. Tooltips of more than a word or two are laid out as a readable bubble instead of a tall column one word wide, and a tooltip on a control in an argument's sidebar is shown in full rather than cut off at the edge of its section. Dialogs no longer draw two empty grey scrollbar margins around their contents, and the sidebar on an argument no longer carries a scrollbar along its foot that leads nowhere. A sidebar section you have moved to with the keyboard is now outlined all the way round rather than along its straight edges only.

Telling us a curated argument gets its source wrong

The curated-argument section used to send you to GitHub to open an issue or a pull request. It now links to support, in the same tab, so reporting one no longer means having an account somewhere else or leaving the argument you are looking at.

Review steps announce their titles as headings again

The line naming what a step is about — the premise being judged, the notice that you skipped some — was styled as a heading but was not one, so a screen reader moving by headings passed straight over it. Since the review deliberately keeps its dialog title out of view, that left those steps with no heading at all.

The review wizard's keyboard shortcuts work from the first keypress

Opening a review put the keyboard on its close button, so the very first Enter — the shortcut the wizard itself tells you to use — closed the review instead of moving you on. It now opens on the line naming the step you are on, and Enter advances as described. A screen reader is also told which step you are on when the review opens, rather than only which dialog it is.

Long claim and premise titles no longer run off the edge on a phone

An argument whose premise or claim titles are long enough to fill more than a line pushed the whole column wider than a narrow screen, so part of every card sat off the right edge and the page scrolled sideways to reach it. Titles now give way to the width they have: a premise title clips to its one line, and a claim title wraps.