Accessibility Statement

TRIIVON S.R.L. wants GPTpostLLM at https://app.oraglegpt.org to be usable by as many people as possible, including people who navigate by keyboard, use a screen reader, magnify the page, or need higher contrast.

This statement says what we aim for, what actually works today, and what does not. It is deliberately specific about the gaps, because a statement that lists only successes is not useful to the person deciding whether they can do their job in this product.

1. The standard we target

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

Two words in that sentence carry weight. It is a target. We work towards it, we design against it, and we treat a failure against it as a defect worth fixing. We do not claim conformance with it. Parts of the product meet it, parts have not been assessed against it in detail, and the honest summary is partially conformant.

Where WCAG 2.2 adds criteria over 2.1, such as focus appearance, dragging movements, target size and consistent help, we treat them as part of the target rather than as optional extras.

2. No independent audit has been carried out

This is the most important disclosure on the page, so it is not buried.

• No third-party accessibility audit has been commissioned. No external specialist, agency or certification body has assessed this product.
• There is no certification. No accessibility certification, conformance badge or seal exists for this product, and any such claim would be false.
• There is no VPAT and no Accessibility Conformance Report. We have not produced one and we will not present internal testing as though it were one.
• The assessment behind this page is self-assessment: developer testing with keyboard-only navigation, browser and extension-based automated checks, and manual review of the main flows against the WCAG 2.2 AA criteria.

Self-assessment finds obvious failures and misses subtle ones. Please read section 4 with that in mind.

3. What works today

The following reflects the state of the product at the date above and is described in terms of what we have actually tested, not what the framework is supposed to provide.

Structure and semantics. Pages are built from semantic HTML: real headings in a sensible order, real lists, real tables with header cells, real buttons and real links used for their proper purposes. Form controls have associated labels, and grouped controls use fieldsets and legends. Landmark regions identify the header, navigation, main content and footer.

Keyboard navigation. The primary flows can be operated without a mouse: signing in, composing a post, attaching media, scheduling, reviewing the queue, managing connections, and the settings screens. Tab order follows the visual order. Menus and dialogs can be closed with Escape.

Skip links. A skip-to-content link is the first focusable element on each page, so keyboard and screen reader users do not have to traverse the navigation on every load.

Visible focus. Focus indicators are visible and are not removed by the stylesheet. Interactive elements show a focus style with sufficient contrast against their background, on both light and dark themes.

Colour and contrast. The palette was chosen with the 4.5:1 ratio for body text and 3:1 for large text and interface components in mind, in both themes. Colour is not the only means of conveying information: status is carried by text or an icon as well as by a colour, so a red or green state is also labelled.

Zoom and reflow. Layouts are responsive and reflow to a single column. Content remains usable at 200% browser zoom, and text can be resized without loss of content or function. No layout depends on a fixed pixel viewport.

Motion. There is no auto-playing video and no carousel that moves on its own. Where transitions exist they are brief, and prefers-reduced-motion is respected.

Images and media. Interface icons that convey meaning have accessible names, and decorative images are hidden from assistive technology. You control the alternative text for media you upload; the composer provides a field for it and we encourage you to fill it in, because the destination platform will use it.

These legal pages. Every page in the legal section, including this one, is plain HTML. No JavaScript runs on them, no cookies are set, and no third-party resource is loaded. They render and are fully readable with scripting disabled, in a text browser, or in a screen reader's document mode. Headings are ordered, tables have header rows, and links are meaningful out of context. If any part of the product is going to be reachable for you, it is these pages.

4. Known gaps

Listed honestly. These are areas where we know we may fall short of WCAG 2.2 AA.

• Complex data tables have had less accessibility testing than the core flows. Sortable columns, multi-select rows, inline editing and horizontally scrolling tables may announce poorly or be awkward to operate by keyboard.
• Modal dialogs have had less testing than the pages that open them. Focus trapping, focus return on close, and dialog labelling are implemented but are not verified across every dialog in the product.
• Not every assistive technology has been tested. Our testing has been with a limited set of screen reader and browser combinations. Behaviour with combinations we have not tried, and with voice control, switch access and braille displays, is unverified.
• Rich composer controls, including the media picker and drag-based reordering of attachments, are easier to operate with a pointer than with a keyboard. A keyboard route exists, but it is not as efficient.
• Date and time pickers used for scheduling rely on custom controls. Typing a date directly works, but the calendar grid may not announce every state as clearly as it should.
• Charts and visual summaries convey information graphically. The underlying figures are available as text or in an export, but the graphic itself is not a substitute.
• Content you publish is your responsibility. We cannot make your text, your images or your captions accessible. Alternative text you do not supply is alternative text the platform will not have.
• Error messages returned by a destination platform are shown as that platform worded them. They are announced, but their clarity is not ours to control.

We do not have a dated remediation schedule for every item above and we will not invent one. Items are fixed as they are reached in ordinary development, and reports from users move them up.

5. Our legal position, stated accurately

EU Directive (EU) 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies, and Legea nr. 232/2022 which implements it in Romania, impose binding accessibility obligations and a formal accessibility statement on public sector bodies. TRIIVON S.R.L. is a private company and is not a public sector body, so that regime does not apply to us and we are not legally bound by it.

We adopt WCAG 2.2 AA as a voluntary target because it is the right standard for a product people use for work, and we publish this statement in the spirit of that regime even though it does not compel us. This page should not be read as a declaration made under Legea 232/2022, because it is not one.

Directive (EU) 2019/882, the European Accessibility Act, is the regime that does progressively extend accessibility requirements to private sector digital services, and it has been transposed in Romania. We mention it because it is the direction of travel and because it would be misleading to cite only the public-sector regime and stop there. We are not claiming present conformity with it. WCAG 2.2 Level AA remains a target rather than an achieved and verified state, conformance is partial, the gaps in section 4 are real, and nothing on this page has been independently audited.

Where separate accessibility obligations apply to us under other law, we comply with them; nothing here is a disclaimer of a duty that does exist.

6. Reporting a barrier

If something in the product stops you doing your work, tell us. A specific report from a person who hit the problem is worth more than any audit.

Write to contact@oraglegpt.org with the subject line "Accessibility" and include:

1. What you were trying to do and where in the product.
2. What happened, and what you expected.
3. The assistive technology and version, the browser and version, and the operating system.
4. Whether there is a workaround you found.

Response targets, which are targets and not guarantees, for the reasons set out in Support:

We answer in Romanian or English. If email is itself a barrier for you, say so in whatever way you can reach us and we will work with the format that suits you.

Note that +40 753 980 299 is the company's registered telephone number published for legal identification under Legea 365/2002 art. 5 and is not a support line, as explained in Support.

7. Alternative ways to get things done

If a screen in the product is not usable for you:

• Your data is exportable as structured files. A full workspace export is available in the interface at Settings, Data Privacy, and produces a signed archive containing a manifest and your records. Working from those files may be easier than working from a chart or a complex table.
• The API can do what the interface does. Where a visual control is the obstacle, the corresponding API endpoint is not, and support can point you at the right one.
• Ask us to carry out an account or workspace administration task for you at contact@oraglegpt.org, after we have verified you are entitled to request it.

8. Keeping this statement honest

This statement is reviewed when the interface changes materially and at least once a year. The date at the top changes when it is revised. If we commission an independent audit, this page will say who carried it out and what it found, including the parts that failed.

Until then, the position is exactly as stated: WCAG 2.2 Level AA is our target, conformance is partial, nothing has been independently verified, and the gaps in section 4 are the ones we know about.

Related pages: Support for how our single support channel works, Service Status for availability, and Company Identification for who we are.