Accessibility statement

What this statement covers

This statement covers the website seora.one with its public pages and the application behind it: ordering, sign-in, account, “My audits”, the audit view with report and action plan, the pages opened through a share link, the AI assistant, and the team console – in German, English, Spanish, Italian and French.

It does not refer to the accessibility check in every analysis or the add-on “Accessibility in depth”: both check the website you have analysed – not seora.one itself. What they include is described under Add-ons on the pricing page.

Voluntary – and the yardstick

This statement is voluntary. With it we disclose what we tested, what works and what does not. The yardstick is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

Conformance status

seora.one is partially conformant with WCAG 2.2 at level AA: in the test of 9 October 2026 the tested requirements were met – with the exceptions listed under “Known limitations”; what has been added since is named under “How and when it was tested”.

How and when it was tested

Tested on 9 October 2026 by the provider itself – a self-assessment, not a report by an independent body.

Automatically with axe-core 4.13.0 and its rules for WCAG 2.0, 2.1 and 2.2 (levels A and AA) in a Chromium browser – the same rule check that seora.one applies to audited websites. Experience shows that automated checks find only part of the barriers.

Additionally measured by script in the browser: keyboard operation and order, visible focus (image comparison with and without focus), skip link, menus and dialogs (Esc, return of focus), headings, page regions, page titles, language attributes, form labels and error messages, reflow at 320 pixels width, 200% zoom, increased text spacing, target sizes of 24 pixels, contrast of text, icons and field borders on the rendered pixels – over the moving background in three positions of its motion and at four window widths from 390 to 1920 pixels –, the behaviour with “Reduce motion” and with motion paused, the duration of the notices and the tagging of exported PDF files.

Scope: 34 pages and views – public pages, ordering, sign-in, account, “My audits”, one audit with report, action plan and action tracker, and the team console – each on desktop (1280 pixels) and phone (390 pixels), in the platform's dark design and in one light team design; plus 12 open states such as menus, dialogs and select lists. Borders and example texts of input fields additionally in all 27 team designs on a test page. The German version was tested, the English one in spot checks, the Spanish one on this page only; the Italian and French versions have not been tested yet.

After the interface was rebuilt on uniform components, the automated rule check with axe-core 4.13.0 ran once more on 16 October 2026: on 205 pages and views in 380 page loads on desktop and phone – including the free check, signing in with Google, the cookie notice with the “Statistics” switch and the AEO chapter – and on the page with all components in the platform and in all 27 team designs. In the interface it found no violation (two target areas that were too small were fixed along the way); in the documents it found insufficient contrast, listed under “Known limitations”. The script measurements from the third paragraph were not repeated.

Not tested: use with a screen reader (such as NVDA, JAWS or VoiceOver), with voice input or a screen magnifier, browsers other than Chromium and real mobile devices. No report in a language other than German was available for testing. Only traced in the program code and not measured in the browser: the duration of sessions and the analysis video.

Since the test of 9 October 2026, parts have been added or rebuilt. They are covered at most by the automated rule check and by self-tests on the program code, but have not been re-checked with the script measurements:

• the whole interface after it was rebuilt on uniform components (buttons, fields, menus, dialogs, tables, navigation)
• the free check before buying: page with the start field, progress with live updates, result and the form for the result email
• signing in and registering with Google
• signing in with LinkedIn and connecting LinkedIn under Account → Sign-in & security
• the “Statistics” switch in the cookie notice and in the cookie settings
• the step “Connect Google” in the audit details with the choice of the Analytics property
• the report chapter on Google answer boxes (AEO)
• the guided details after payment with their step bar
• the selection of further markets in the order form
• the new view of the pages behind a share link
• the button and the window of the AI assistant
• the smaller report PDF with page numbers added afterwards
• the custom player of the analysis video (control bar, subtitle and speed menus, keyboard shortcuts) including slides with entrance animations and scrolling
• the website icons (favicons) in the “My analyses” and Monitoring lists
• the annual pack with automatic follow-up audits and the choice between a single audit and the pack when ordering
• the cards of the add-ons when ordering (Accessibility in depth, analysis video & PowerPoint)
• the improvements made after the test: focus ring in the field for the website address, announcement of the notices at the bottom right, name and description of the option cards, and the AI assistant button and the language notice no longer covering fields

What works

• Keyboard: on the tested pages the controls can be reached with the Tab key in the order of the page. Every focused element shows a visible focus ring – including the field for the website address – and is scrolled into view so that the sticky header does not cover it. On the home page and on the page of the free check the cursor is placed in the field for the website address on load – intentionally, only on devices with a mouse or trackpad and only once the cookie notice has been answered; otherwise no page moves focus into a field by itself on load.
• Menus and dialogs close with Esc and return focus to their trigger; modal dialogs keep focus while they are open.
• A “Skip to content” link is at the start of the public pages, the sign-in pages, the application and the team console; a notice about another language version of the page only comes after it.
• On the first visit the cookie notice comes first in keyboard order and covers no content: the page keeps its space free.
• Every tested page has exactly one main heading and no skipped heading levels; navigation regions are named, the page language is set, and the entries of the language menu carry their own language.
• Forms: every field has a label. Error messages appear as text at the form, are announced to assistive technology and are linked to the field.
• Text reaches the required contrast of 4.5:1; borders of input fields and switches and icons reach 3:1 – measured on the rendered pixels, also over the coloured light patches of the background in several positions of their motion.
• The pages can be enlarged to 200% and read at 320 pixels width without the whole page scrolling sideways. Bars with tabs and filters wrap, and text is not cut off – not even with increased text spacing. Only data tables scroll sideways; their region can be reached by keyboard and has a name.
• With the system setting “Reduce motion”, whatever moves by itself stops: the drifting patches of light in the background, blinking characters and fade-ins. Loading indicators keep running. The button “Pause motion” at the foot of every page does the same.
• Notices at the bottom right close by themselves after 7 seconds; under “Adjust the display” this can be switched off – they then stay until you close them. Their text is also placed in an area that assistive technology announces – error messages with priority.
• The overall score in the report has a text alternative. A report is marked up in its own language even when the interface uses another one, and its labels follow the language of the report. Exported PDF files carry a title of their own and the language of the report and are tagged with structure, table headers and bookmarks; figures there carry a caption, screenshots an alternative text.
• The analysis video has subtitles in German, English, Spanish, Italian and French, switchable in the player and available as files to download (checked in the program code).

Adjust the display

You set two things yourself here. Both apply at once, on every page, and are kept after reloading.

“Pause motion” is also at the foot of every page. If your device already asks for less motion (“Reduce motion”), the same things are already stopped.

A cookie on this device remembers your choice (sa_a11y, one year). It is only created when you use one of the switches, holds nothing but these two settings and is removed again once both are off.

The choice applies to this address. If your team works under an address of its own, set both there at the foot of the page.

Known limitations

What did not pass the test – each with the consequence for those affected and, where there is one, a workaround.

• In reports whose language differs from the language of the audited website, search terms and quotations are not marked up separately. This concerns translated reports and reports ordered in another language: search terms, verbatim quotations from the website and answers from AI systems stay in the language of the website but carry no language attribute of their own in the report. A screen reader reads them with the pronunciation of the report's language. Workaround: Read the report in the language of the audited website – there language and markup match. Checked in the program code only.
• The analysis video has subtitles but no audio description. What is only visible on the slides and does not occur in the narration is not conveyed to anyone who cannot see the slides. Workaround: The report contains the content of the video as text. Checked in the program code only.
• In the board view of the action tracker, entries can only be moved to another column with a mouse. With the keyboard you can reach and open every entry there (Enter or space bar). Dragging it to another column – that is, changing its status – only works with a mouse in this view. Workaround: The list view of the tracker is equivalent: it shows the same entries, and you change the status there with a select field, also with the keyboard. An entry you open in the board with the keyboard appears directly in this list. Checked in the program code only.
• Whether the report PDF is still fully tagged after the page numbers have been added is open. The page numbers are put into the finished file in a second step. Whether structure, language and bookmarks survive this unchanged can only be measured on an exported file – this measurement has not been made yet. Workaround: The report in the browser contains the same content with headings, table headers and language. Checked in the program code only.
• In the report PDF, the slides and invoices, some small labels do not reach a contrast of 4.5:1. This concerns the chapter numbers in the report's table of contents and the footer of the slides – both in the colours of the brand profile – and the column headers of the table on invoices and credit notes. People with low vision read these details less easily. Workaround: These details only add to what stands next to them in full: chapters and slides carry their title, the invoice lines their description and amounts. The report in the browser shows the same content in the contrasts of the interface.

Report a barrier

Have you come across a barrier – including one that is not listed here? Write to hilfe@seora.one or use the form under Help & contact. The address of the page, what you wanted to do and what you work with (browser, assistive technology) are helpful.

Your message goes to the support of seora.one. We look at every report – it helps us find and remove barriers.

Date of this statement

This statement was last changed on 22 October 2026. It is based on the test of 9 October 2026; no complete new test has taken place since – on 16 October 2026 only the automated rule check ran once more. What has been added since the test is listed under “How and when it was tested”.