Accessibility Statement

GPT LLM ORAGLE Ltd. Liability Co. is committed to making GPTpost usable by everyone, including people who use screen readers, keyboard-only navigation, magnification, speech input, or reduced-motion settings.

This statement says what we target, what we have actually done, and where we currently fall short. An accessibility statement that lists no gaps is not credible, so ours lists them.

Report a barrier to support@oraglegpt.org with "Accessibility" in the subject line.

1. Conformance target

"Partially conformant" means the Service conforms to most of the standard but not to all of it. We say so rather than claiming full conformance.

2. What we have done on these legal and public pages

Every page under oraglegpt.org/legal/ is built to be read by anyone, on any device, without JavaScript:

• Server-rendered HTML. The content is in the initial response. It does not depend on script execution, so screen readers, text browsers, and automated checkers all receive the full text.
• Skip link. A "Skip to main content" link is the first focusable element on every page.
• Landmarks. Each page uses <header>, <nav>, <main>, and <footer> landmarks, with accessible names on the navigation regions.
• Heading structure. Exactly one <h1> per page, with <h2> and <h3> in order and no skipped levels, so heading navigation works.
• Contrast. Body text and interface text meet or exceed the 4.5:1 ratio required at Level AA, in both the light and dark colour schemes.
• Respects your system theme through prefers-color-scheme, and respects prefers-reduced-motion.
• Visible focus. Every interactive element has a clear, high-contrast focus indicator that is never removed.
• Responsive and reflowable. Content reflows to a single column at 320 CSS pixels without horizontal scrolling, and remains usable at 200 percent zoom.
• Tables have proper header cells and captions, and scroll horizontally inside their own container so the page itself never scrolls sideways.
• No colour-only meaning. Where colour conveys status, text or a symbol conveys it too.
• No time limits, no motion traps, no autoplay on these pages.
• Text resizing works to at least 200 percent without loss of content, since layout uses relative units.

3. What we have done in the application

• Keyboard operation for the primary flows: composing, scheduling, approving, and publishing.
• Form fields have programmatically associated labels, and errors are announced rather than shown only in colour.
• Dialogs trap focus while open and return focus to the trigger when closed.
• Media uploads support alternative text, and we prompt for it rather than letting it be silently omitted.
• The interface is usable at 200 percent zoom.

4. Assistive technology we test with

Testing combines automated checks in the release verification gate with manual keyboard and screen-reader passes on the primary flows.

5. Known limitations

We are honest about these because a user is better served by knowing a barrier exists than by discovering it mid-task.

6. Preparation of this statement

• This statement was prepared on 2026-08-04.
• It is based on a self-assessment carried out by the Company, combining automated testing with manual keyboard and screen-reader review.
• It has not been reviewed by an independent third-party auditor. We say so rather than implying external validation we do not have.
• It is reviewed whenever the interface changes materially, and at least once a year.

7. Feedback and how we respond

If you cannot use part of GPTpost, tell us. We treat accessibility reports as defects, not as feature requests.

Email support@oraglegpt.org with "Accessibility" in the subject line, and include:

• the page or screen where the problem occurs;
• what you were trying to do;
• your operating system, browser, and assistive technology, if you know them.

What you can expect:

If you need information from a page in an alternative format, ask us and we will supply it.

8. Enforcement and escalation

If you are not satisfied with our response, escalate to legal@oraglegpt.org.

Depending on where you live, you may also be able to complain to a national enforcement body responsible for the European Accessibility Act, to an equality or disability rights body, or to the relevant authority under Section 508 or the Americans with Disabilities Act. You do not have to exhaust our process first.

9. Contact

GPT LLM ORAGLE Ltd. Liability Co.
30 N Gould St, Ste N
Sheridan, WY 82801
United States