Accessibility statement

1Our commitment#

We intend FrankieGPT to be usable by everyone, including people who use a screen reader, a screen magnifier, high contrast settings, a keyboard instead of a mouse, a switch, head tracking, or voice control, and people with low vision, color blindness, dyslexia, tremor, limited dexterity, hearing loss, or memory difficulty.

We treat an accessibility problem as a defect. It goes in the same queue as a broken button, not in a wish list.

2The tools built into every page#

Look for the round accessibility button in the lower left corner of any page. It opens a panel of adjustments that take effect immediately and are remembered on that device. Nothing is sent to us; the choices live in your own browser.

• Ready made profiles for low vision, dyslexia, motor difficulty, cognitive ease, seizure safety, and screen reader use, so one tap sets several things at once.
• Bigger text, in steps, without breaking the layout.
• More space between lines, letters, and words.
• A dyslexia friendly typeface, or a clean sans serif, whichever reads better for you.
• Left aligned text, which is easier for many readers than justified blocks.
• High contrast, inverted, and dark modes, plus reduced saturation and grayscale.
• Highlighted links and headings, so structure is visible at a glance.
• A stronger focus ring, so you can always see where you are when using a keyboard.
• Bigger click and tap targets, for hands that do not land precisely.
• Animation off, which also happens automatically if your device asks for reduced motion.
• A larger cursor, a reading mask that dims everything but the line you are on, and a reading guide bar.
• A page structure view, listing the headings and landmarks so you can jump straight to a part of a long page.
• Reset all, which puts everything back the way it was.

Behind the panel, the same module repairs common markup problems on each page as it loads: missing image descriptions, buttons without names, form fields without labels, links that only say "here," and duplicate or missing landmarks. The panel reports how many repairs it applied on the page you are looking at.

3Keyboard and screen readers#

• Every control can be reached and operated with a keyboard alone. Tab moves forward, Shift and Tab move back, Enter or Space activates.
• A "skip to main content" link is the first thing in the tab order on every page, so you do not have to walk through the header each time.
• Press Alt and 0 together to open or close the accessibility panel from anywhere. Escape closes it and returns focus to where you were.
• Pages use real headings in order, real landmarks, and real buttons and links, which is what a screen reader relies on.
• Status messages, such as a saved setting or a failed send, are announced rather than only shown.
• The assistant screen is a single simple layout on purpose. There is no drag and drop anywhere, and nothing requires a hover to reveal it.

4Frankie reads things aloud#

For many people the most useful accommodation is not a setting, it is a voice. Frankie will read any answer aloud, and he will read this page, the Terms of Service, or the Privacy Policy to you if you ask. He also listens, so a whole conversation can happen without reading or typing anything at all. He speaks English and Russian.

5The standard we work to#

We work toward conformance with the Web Content Accessibility Guidelines version 2.1, level AA. That is the standard courts and agencies apply under the Americans with Disabilities Act, and it is the basis of Section 508 of the Rehabilitation Act and of EN 301 549 outside the United States.

We test with a keyboard, with the screen reader built into the operating system, at 200 percent zoom, at narrow widths, and with contrast measured rather than judged by eye. Color is never the only way information is conveyed, and text contrast is checked against the 4.5 to 1 ratio the standard requires.

This statement is a description of our current work, not a claim of perfect conformance. Nobody should promise that, and we would rather be believed.

6What is not finished yet#

• The accessibility panel follows the assistant language: its labels appear in Russian when the assistant is set to Russian, and in English otherwise. The read aloud tool speaks in the language of the page.
• Some content comes back from an artificial intelligence model, so its exact wording and structure vary from one answer to the next. We control the container and the reading order, not every sentence inside it.
• A page that another company serves, such as a search result you follow, is outside our control entirely.
• Live spoken conversation depends on your browser's microphone support, which differs between devices. Where it does not work, the app falls back to a record and send button, and typing always works.

If something here matters to you and is holding you back, tell us. That is how it gets prioritized.

7Documents in another format#

We will provide the Terms of Service, the Privacy Policy, this statement, or any other document we publish in large print, as plain text, or in another format you can use, at no charge and without asking why. Write to hello@frankiegpt.com.

8Tell us what is not working#

If any part of FrankieGPT is difficult or impossible to use with your assistive technology, write to hello@frankiegpt.com. Tell us the page, what you were trying to do, and what device, browser, and assistive technology you use, if you know. If you do not know, describe it in your own words and we will work it out.

We answer within 5 business days, and we will tell you either that it is fixed or when it will be. If you would rather write on paper: DotNet Holdings LLC, 1401 21st St Ste R, Sacramento, CA 95811.