MyJackfruit

Help
Browse topics · Finishing

Finishing

← Finishing

How do I check that my app works for people who use a screen reader or large text?

Short answer

Your AI is told to build to a known accessibility standard; try it yourself with VoiceOver (Command-F5) on a Mac and with the page zoomed.

Deeper

Accessibility means that people can use your app also when they cannot see the screen well, cannot use a mouse, or need larger text. A screen reader is a program that reads the screen aloud, or shows it on a braille display, for people who are blind or see poorly.

What your AI does. A written accessibility rule says every app must meet WCAG 2.1 AA. WCAG, the Web Content Accessibility Guidelines, is an international standard whose documents explain how to make web content more accessible to people with disabilities, made by a group of the W3C, the body that sets web standards (https://www.w3.org/WAI/standards-guidelines/wcag/, read 13 November 2026); AA is the level the rule names. Agent.Tester, the agent that tests what others built, reads the rule and checks for it; Agent.Coder, the agent that writes your app's code, is named in it for checking colours by hand. An agent is your AI following one written procedure, its standing instructions, for one kind of work.

The rule asks, among other things:
that every button, link and box can be reached and used with the Tab key and Enter or Space, without a mouse;
that every picture has a text saying what it shows;
that every box to fill in has a label, and an error message is tied to its box;
that a real button is used for a button, and so on, so a screen reader can say what each thing is;
that text stands out from its background: at least 4.5 to 1 for normal text and 3 to 1 for big type (18 pixels and larger, or 14 pixels and larger in bold).

Agent.Tester, the agent that tests what others built, checks every part for an automatic accessibility test that passes, real buttons, picture texts, labels and error messages. Each file of browser tests that opens the whole app also includes a full-page check with axe-core, a free tool that finds many such faults by itself. The rule says the tool cannot check every colour, so the builder checks those by hand. Automatic checks find many faults, not all.

Try it yourself.
With a screen reader: a Mac has VoiceOver built in, and Apple says to turn it on or off: Press Command-F5. (https://support.apple.com/guide/voiceover/turn-voiceover-on-or-off-vo2682/mac, read 13 November 2026). Open your app and move through it with the Tab key: each button and box should be read out by what it does, and you should reach and use everything without the mouse. In Safari, Tab may skip links and buttons; press Option-Tab to reach them (Apple, https://support.apple.com/guide/safari/keyboard-and-other-shortcuts-cpsh003/mac, read 13 November 2026). On a Windows computer, Narrator is built in; Microsoft says to start it with Win+Ctrl+Enter (https://support.microsoft.com/en-us/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1, read 13 November 2026). A try like this is not a full accessibility check.
With large text: in Chrome, Google says to press ⌘ and + on a Mac, or Ctrl and + on Windows, to make everything on a page larger, and ⌘ and - or Ctrl and - to make it smaller (https://support.google.com/chrome/answer/96810?co=GENIE.Platform%3DDesktop, read 13 November 2026). Make the page large and check that nothing is cut off or covers something else.
Best of all, ask someone who uses a screen reader every day to try it.

Tell your AI what you found, as with any fault; the answer How do I tell my AI about a fault so it can fix it? shows how. Whether a law asks your app to meet such a standard depends on where and for whom you offer it: ask a professional, as this help gives no legal advice. How GilbApp itself works with a screen reader is in Can I use it with a screen reader?

Must my app work for people with a screen reader? As said above, whether a law asks it depends on where and for whom you offer your app, and this help cannot tell you. What it can say: your AI is told to build every app to WCAG 2.1 AA anyway, and the checks above show how far it gets. If you know of a law your app must keep, tell Kai-Zen, the planning agent, so your plan holds it as a Constraint, a limit the plan must keep, such as a budget, a date or a law; the answer How do I write a Constraint in my plan? shows how. If you are not sure, ask someone who knows the law where you and your users are.

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Rule_Code_accessibility (RuleA11yWcagAa: All components and apps must meet WCAG 2.1 AA; RuleA11yTools: axe-core; RuleA11ySemanticHtml; RuleA11yKeyboard: "reach and operate every button, link, and input using the Tab key and Enter/Space"; RuleA11yAltText; RuleA11yFormLabel; RuleA11yErrorAssoc; RuleA11yE2eTest: full-page check in every end-to-end test; RuleA11yTesterChecks; RuleA11yContrast: 4.5:1 normal text, 3:1 large text, it cannot check colours defined in CSS variables or computed at runtime), Agent.Tester (Standards: reads Rule_Code_accessibility), Agent.Coder. W3C, WCAG 2 Overview (https://www.w3.org/WAI/standards-guidelines/wcag/, read 13 November 2026). Apple, Turn VoiceOver on or off on Mac (https://support.apple.com/guide/voiceover/turn-voiceover-on-or-off-vo2682/mac, read 13 November 2026). Google, Change text, image and video sizes (zoom), Computer (https://support.google.com/chrome/answer/96810?co=GENIE.Platform%3DDesktop, read 13 November 2026). Apple, Safari keyboard shortcuts (https://support.apple.com/guide/safari/keyboard-and-other-shortcuts-cpsh003/mac, read 13 November 2026). Microsoft, Complete guide to Narrator (https://support.microsoft.com/en-us/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1, read 13 November 2026). Live help pages, sentences shared: Can I use it with a screen reader? (screen reader gloss). Rule_Code_accessibility (RuleA11yWcagAa). Live help pages, sentences shared: Do I have to follow rules such as GDPR or app store rules from the start? (a rule your app must keep can be written as a Constraint; ask someone who knows the law where you and your users are); How do I write a Constraint in my plan?

Checked against GilbApp d529620.