Accessibility

The choices that make this journal readable, the one known limit, and how to report a barrier.

A reference page that cannot be read is worse than no page at all, because a reader has already spent effort arriving at it. These are the decisions that follow from that, written down so they can be tested rather than taken on trust.

Structure

Every page is semantic HTML. One H1, headings in descending order beneath it, and real landmark regions. A list is a list element and a comparison is a table element, never a run of dashes or an arrangement of columns faked with spacing. The first thing a keyboard reaches on any page is a skip link to the main content. Articles, field pages and policy pages read without scripting at all; only the search box needs it, and the search page says as much.

Keyboard and focus

Controls are all operable from the keyboard, and the tab order follows the visual order. The search box is built as an ARIA combobox: the arrow keys move through the suggestions, Enter opens the highlighted one, Escape closes the list and returns focus to the input, and the result count is announced as suggestions appear. The focus outline is visible on every focusable element and is deliberately heavier than any hairline rule in the design, so it can never be mistaken for a border.

Text, contrast and color

Body text is set large, on a generous line height, with the measure held to a comfortable width so the eye finds the next line without hunting. Nothing breaks when text is scaled to twice its size in a browser. Contrast has been checked against WCAG AA for body text, meta text and every interface element; the burgundy accent is used at a value that clears the threshold as text, and color is never the only signal that something is a link.

The site ships in a light theme only, and that is a design decision rather than an omission. The whole design is derived from print — bone paper, hairline rules, photographs graded warm for that background — and an inverted palette would fight the grade instead of helping anybody read.

Motion

There is very little movement here, and what exists is subordinate to the reader's own setting. When an operating system asks for reduced motion, transitions and smooth scrolling stop. Nothing on the site moves, flashes, autoplays or scrolls on its own, and no page carries a carousel, a video or an animated advertisement.

Photographs

Alt text on a photograph says what the picture shows, not what the article argues, so a reader using a screen reader takes away the same impression a sighted reader takes from a glance. Image dimensions are declared in advance, so text does not jump while a photograph loads. No image on the site has words printed inside it, which means nothing readable is trapped in a picture.

The known limit

Comparison tables can be wider than a phone screen, and where that happens the table scrolls sideways inside its own container while the rest of the page stays put. Tables are used only where a comparison genuinely needs rows against columns, and the surrounding prose carries whatever point the comparison supports, so a reader who passes the table by loses the arrangement and nothing else.

Reporting a barrier

Write to contact@justicepartnersgroup.com naming the page, describing what happened, saying what was expected instead, and listing the assistive technology, browser and settings in use. A barrier is treated as a defect in the same class as an incorrect citation, not as a feature request, and it is fixed in the same way an error in an article is fixed. See corrections for that process and contact for everything else the address handles.