Accessibility statement / GraphAtlas

We want anyone who needs to read a regulation, check a figure or write to us to be able to do it on this site. That includes people who use a keyboard, a screen reader, voice control, a phone, large type or a high contrast setting.

We aim to meet level AA of the Web Content Accessibility Guidelines (WCAG) 2.2, which is the benchmark in EN 301 549. No law requires this of a company like ours. Our customers are bound by it, and the people who validate our software ask for it.

Where we stand

We believe the site meets WCAG 2.2 level AA. No outside specialist has audited it yet, so until one has, read this as our own assessment. The limits of what we have checked are set out under what we have not checked.

What we have built in

Structure. Each page has one main heading, headings that go down one level at a time, a link that skips to the content, and labelled regions for the header, navigation, main content and footer. The page language is set to British English.
Keyboard. Everything you can do with a pointer you can do with a keyboard. Focus is always visible, and the first stop on every page is the link that skips to the content. Menus open with Enter or Space, close with Escape, and give focus back to the button that opened them. Search opens with Control and K, Command and K, or the slash key. The arrow keys move through the results, Enter opens the one that is chosen, and Escape closes the dialog and gives focus back.
Links. A link says where it goes. Some links show the same words, as the buttons that open each of the calculators do. The name that a screen reader gives each of them carries the rest, so the list of the links of a page does not read as one word said again and again. The words that you see come first in that name, so you can say them to voice control and be understood. Each heading that you can link to has a link of its own, named for the heading.
Colour and contrast. The site has one set of colours. It does not change with the dark setting of your system, so there is no second set that was checked less than the first. A test holds every pair of text and ground in the style sheet to a contrast ratio of at least 4.5 to 1, and large text and the edges of controls to at least 3 to 1. The colophon’s table of colours lists each pair with its ratio. A colour never carries a meaning without a word beside it.
Targets. Buttons, fields and links that stand alone are at least 24 by 24 pixels, which the checker that we run on every page tests.
Reflow and size. Pages reflow to the width of a small phone, 320 CSS pixels, without losing content. Wide tables and code scroll inside their own box, which a keyboard can reach. On a phone, a table with long cells is shown as one card for each row, with the name of the column on every cell, and a table with short cells keeps its columns and sets its figures against the right edge. If you raise the default size of text in your browser to 150% or 200%, the layout changes to that of a narrower window, since its breakpoints follow the size of text. Nothing is cut off or runs out of its box. A table that has no room for its columns at those sizes scrolls sideways in its own box, and a row of choices stands one choice under another. A phone 320 pixels wide with text at 200% has the room of a window 160 pixels wide at the usual size. It is covered as well as a phone 390 pixels wide, and no page scrolls sideways in either.
Text spacing. If you override line height, paragraph spacing, letter spacing and word spacing to the limits WCAG names, nothing is cut off or overlaps. Two parts of the page do not follow your letter spacing exactly, so that this holds. The labels inside the charts keep the width that their chart was laid out for. The large type, which is the headlines and the figures of the calculators, is set a size smaller by the share that your spacing takes, which a script on the page works out by measuring a hidden word. Without the script the large type keeps its size. The text around the charts follows your spacing, and a few layouts give way to it, as four choices that stand two by two and not in a row.
Motion. Nothing on the site moves for as long as a page is open. A drawing at the top of a page draws its lines once, in about a second and a half, when the page opens. Other animation is short. All of it stops if your system asks for reduced motion.
Transparency. The bar of the header and the strip of sections on the page of a product, which are the two parts that stay in view as you scroll, have solid backgrounds. Nothing on the site blurs what is behind it, so there is nothing for a setting of less transparency to change.
High contrast. In forced colours mode, borders, controls and focus rings stay visible, including on controls that are drawn as a block of colour. So do the words, on the light theme of the system and on the dark one. A choice that you have made is marked with a frame in the colour of selection and not with a fill. The words of a chart and the bars of a receipt are the colour of text, and a drop-down list has the arrow that your browser draws.
Pictures and drawings. The portraits are there for the look of the page and carry nothing that the text beside them does not say, so their text alternative is empty and a screen reader goes past them. Each drawing has a title and a description that say what it shows. On a phone, the numbered list under a drawing only repeats the words that are in the drawing on a larger screen, so a screen reader is not read it twice. The slips that show a receipt carry the receipt in text, and the bars on them, which are only for the eye, are hidden from a screen reader.
Charts. Each chart in a calculator has a written description of what it shows, and the figures behind it are in a table or in the text beside it.
Formulas. Formulas are set as MathML, so a screen reader can read them, and the text around each one says what it means in words.
Forms. Every field has a visible label. When a form has errors, a summary at the top names each one and links to its field, and focus moves to the summary.
Copy buttons. A block of code, a receipt and the reference of a message that you sent each have a Copy button. The button says what it copies, and a screen reader is told when the copy is done. Where the browser cannot copy, no button is drawn, and the text can be selected.

What we check, and how

Before each release we run axe-core, an automated checker, over every page of the site. It runs in a window of a desktop and in one of a phone, with the rules of WCAG 2.0 to 2.2 at level AA and its own rules of good practice. We fix what it finds.

It does not find everything, so we run a second set of scripts over every page. They use the keyboard alone, windows 320, 390 and 1280 pixels wide, a default text size of 150% and of 200%, the text spacing that WCAG names, reduced motion, and forced colours. One of them walks the width of the window from 320 to 1100 pixels in steps of four, since a layout that changes at one width can fail by a few pixels just above it. The scripts report:

what is cut off, including a word that a line has cut in two;
what runs out of its box;
what is squeezed into a column of a few letters;
what has no visible focus ring;
what a keyboard cannot reach;
whether anything moves for as long as the page is open;
whether the two bars are solid;
whether two links of a page that have one name, as a screen reader is given it, go to one place.

One more script reads the pixels of the screen and not the style sheets, which can say that words are the colour of text while the screen shows them black on black. In forced colours, on the light theme of the system and on the dark one, it holds every line of words on every page to 4.5 to 1 against what is behind it. It checks that the words show letters and not a bar, and that the arrow of each drop-down list is whole.

We also look at the pages ourselves, in all three engines.

Calculators get one more check. We operate each of them from the keyboard, then confirm the receipt it shows still matches after every change you can make to its inputs.

What we have not checked

We have not had the site tested by people who use screen readers or voice control every day. Our own tests with a keyboard and a checker are not a substitute, and we plan to commission a full audit before the site launches.
We have tested in the engines of Chrome, Firefox and Safari, which are Chromium, Gecko and WebKit, at their current versions, and on emulated phone windows with touch. The checks of text size run in Firefox only. It is the one engine in which a script can set the default size of text as a reader sets it. The other checks run in Chromium. We have not tested on a physical phone or in an older browser, and we make no promise for them.
We have read the site in forced colours in Chromium, which can be made to look as it does with the light theme of the system and with the dark one. We have not run it in Windows with a contrast theme, or in Firefox or Safari with their own settings for high contrast, where the colours are the ones that the theme names. We expect the same, since the frames and the words use only the colours of the system, but we have not seen it.
The documents we publish with the site, the proofs, are plain text files in a standard solver format. They are written for programs, and we do not describe them further for people.

Tell us about a barrier

If something on this site stops you reading or doing what you came to do, write to contact@graphatlas.com with Accessibility in the subject. Say which page, what you were trying to do, and what you use to browse. We reply within five working days, and we either fix the problem or tell you when we will.

If you are not happy with our reply, you can contact the Equality Advisory and Support Service at equalityadvisoryservice.com.

Changes to this statement

Each entry gives the date, what was checked, what the check found, and that it was fixed.

13 November 2026. The customers are no longer shown by a drawn mark, and the people who are quoted are no longer shown by a portrait, so the sentence of this statement about the marks was removed. The checks were run again on the front page, the customers page and the case studies, and found no fault in what replaced them.
10 November 2026. A script now opens every page in five windows, from 1440 pixels wide to 320, and looks for the button that books a demo, in the bar or, where the bar has no room, at the foot of the menu. It found the button out of the window on a phone 320 pixels wide on all 45 pages, and on 12 pages of a phone 390 pixels wide, so that a reader had to know to scroll the menu to reach it. The foot of the menu stays at the bottom of the window now and the rows above it scroll, and the script finds none. Reports of a barrier go to contact@graphatlas.com now, with Accessibility in the subject, which is the one address that the site has.
8 November 2026. The site was redesigned: a white sheet on a blue field, one typeface, and drawings in thin lines. Every check above was run again on every page and in every state of the calculators and the forms. The checks found words that a line had cut in two at some widths of window, and a few boxes that ran past their room by 2 to 5 pixels in a band of widths. We fixed each, and the checks find none now. A table with short cells now keeps its columns on a phone, with its figures against the right edge. Code, receipts and references have a Copy button.
8 November 2026, earlier. A script now reads the colour of every button, at rest and with the pointer on it, against what it stands on. It found buttons whose words were gone under the pointer on every page, and buttons that were the colour of the band behind them. Each button takes its colours from the ground it is on now. The script finds none.
8 November 2026, earlier. A script now puts the keyboard on two controls of each kind on every page and measures the outline that shows where it is. The outline was too faint on the deep colours, on cards of night, on blocks of code, and on the red border of a calculator field. Each ground now sets the colours that stand on it, and the script finds no outline under 3 to 1 and no words under 4.5 to 1.
8 November 2026, earlier. A script now reads the pixels of the screen in forced colours. It found a chosen option drawn as a black bar, words of charts that were too faint on the dark theme, and a drop-down list with no arrow. We fixed each, and the script finds none.
8 November 2026, earlier. A check now reads the links of every page by the names that a screen reader is given, and holds that two links with one name go to one place. It found 21 names that went to two places or more, on 16 of the 42 pages. The link to a heading was called “Link to this section” 78 times. Every link now says where it goes, and the check finds nothing.
6 November 2026. The design was made a little less modern and a little more coloured, and every check was run again. They found five faults in the new pages. A mark under a quotation was wider than a phone with text at 200%. A block of code made a page scroll sideways by a pixel. The version of a package on the colophon was wider than its cell. Three labels over the grid of correlations on the page of FRTB-SA ran into each other. A field label on the contact page was paper-coloured on white and could not be read. We fixed each.
5 November 2026. The design was made plainer, and every check was run again. The checker found one fault: the small label that marks a change of a rule was under 3 to 1 once its red was made quieter. A phone 320 pixels wide with text at 200% showed two more, a site name and an arrow that ran past their room. We fixed all three. Several things that moved are gone, and nothing on the site moves for as long as a page is open.
4 November 2026. The site was redesigned and this statement was written again. The checker found a search button and a demo link with no name on a phone, a list of changes under the wrong level of heading, faint text, links under 24 pixels tall, and buttons that disappeared in forced colours. We fixed each. The limit that this statement had named for a phone 320 pixels wide with text at 200% is gone, since nothing runs out of its box there now. The button that opens the menu no longer promises the arrow keys, since what it opens is a panel of links.
3 November 2026. On a phone 390 pixels wide with text at 200%, the line under the footer that gives the registration of the company ran out of the page on every page. It wraps now.
2 November 2026. The header and the strip of sections were a little see-through, with what is behind them blurred, whatever the system asked for. Both are solid now when the system asks for less transparency.
1 November 2026. The checks of text size, text spacing, motion, forced colours and the keyboard now run over every page and inside the calculators. They found options of the WLTP calculator with no focus ring, figures that ran together in the ledger, labels of charts that ran past their chart, and large figures that broke across two lines when the letters were spaced. We fixed each.
29 October 2026. First version.