Public and signed-in routes are checked at phone width for readable text, tap targets, and no horizontal overflow.
Accessibility
UYB should feel clear before it asks for anything hard.
Private writing only works when people can read the screen, move through the app, understand the status, and come back without feeling lost.
Accessibility receipt
Accessibility receipt.
Use this receipt to see what UYB checks automatically, what still needs a human pass, and how to report a barrier without sharing private writing.
The app keeps skip navigation, focus states, labels, and main landmarks in the verification path.
Reduced-motion mode should calm transitions, animations, and scroll behavior.
Real phone review, larger text, assistive tech, writing rooms, and reveal moments still need human checks.
44px tap targetskeyboard focusreduced motionsafe barrier reports
The accessibility receipt is launch evidence, not a promise that every need is solved. Report the screen, device, browser, assistive setup, and blocked step without sending journal answers, drafts, reveal text, invite links, or private names.
Access need
Choose what is getting in the way.
Start with the thing that feels hardest right now. You can read the full accessibility notes later.
Larger textWords need more room
Check wrapping, spacing, and whether the next action still stays visible when text is bigger.
Check larger textScreen readerStatus needs plain wordsReview how UYB names pages, receipts, buttons, and status without relying on color alone.
Review status wordsKeyboardI need to move without a mouseUse skip navigation, focus states, and barrier reporting without needing tiny pointer control.
See keyboard checksGlass contrastSoft surfaces need to stay readableCheck that glass panels, chips, and calm backgrounds still keep enough contrast.
Check contrastReport a barrierTell us what blocked youSend the page, device, browser, assistive setup, and blocked step without private writing.
Report safelyone access needplain status wordskeyboard pathcontrast stays visibleno private writing
This access router stores nothing and changes no settings. It only points to public accessibility notes and safe feedback without journal answers, drafts, reveal text, invite links, private names, emails, or crisis details.
Accessibility is part of trust.
UYB is built for private, emotional writing. That means the interface has to be clear, calm, readable, and usable for kids, teens, parents, partners, and adults with different needs.
Do not send private journal answers when reporting an accessibility issue. Share the page, device, browser, and what got in the way instead.
What we check
- No horizontal scroll on common phone widths.
- Readable contrast on glass surfaces and soft backgrounds.
- Tap targets that work with thumbs, not tiny desktop habits.
- Skip navigation and focus states for keyboard users.
- Reduced motion support for people who prefer calmer screens.
- Labels, helper copy, and status messages that make sense with assistive technology.
Assistive review
Assistive review receipt.
Use this receipt before launch changes ship. It keeps larger text, screen-reader style review, keyboard movement, and glass contrast visible as product work, not hidden QA notes.
Text can grow without covering the next action.
- Hero copy and receipt cards wrap without sideways scroll.
- Buttons keep readable labels and 44px tap targets.
- Writing boxes and save receipts stay close enough to understand.
Status should make sense without seeing the layout.
- Pages keep one main landmark and labeled navigation.
- Receipts use headings, labels, and status text instead of color alone.
- Controls have names that explain the action, not only the icon.
A user can move, skip, focus, and report a barrier.
- The first Tab reaches Skip to main content.
- Focus remains visible on links, buttons, and form controls.
- Barrier reporting can be reached without a mouse.
Premium surfaces still have to be readable.
- Soft panels keep enough contrast for normal and large text.
- Reduced motion keeps the page calm without hiding state.
- Status chips are backed by words, not color alone.
larger text reviewscreen reader pathkeyboard routeglass contrastno private writing
The assistive review receipt stores no user data. Barrier reports should name the screen, device, browser, assistive setup, and blocked step without journal answers, drafts, reveal text, invite links, emails, private names, or crisis details.
Mobile first by default.
Core flows are checked on small screens for readable text, clear tap targets, no horizontal scroll, and no covered first-viewport content.
Keyboard access matters.
The global shell includes skip navigation, visible focus states, and page structure that should work without a mouse.
Motion should respect the person.
The app supports reduced motion preferences so movement can calm down when someone asks their device for that.
Writing tools should stay understandable.
Forms, autosave status, and helper text should explain what is happening without hiding the box where someone writes.
Verification
What is checked automatically and what still needs a human pass.
Automated checks catch repeatable mobile and keyboard problems. Manual review still matters because UYB is used during emotional moments, on real phones, with real attention limits.
Checked before public smoke passes.
- Public mobile routes render at phone width with no horizontal scroll.
- Each checked public route keeps one clear H1 readable in the first phone viewport.
- First-viewport headings, copy, and primary actions are checked for obstruction by trays, headers, and overlays.
- Readable contrast samples are checked against 4.5:1 for normal text and 3:1 for large text.
- The first keyboard Tab reaches Skip to main content.
- The focused skip link shows a visible focus signal.
- Skip to main content activates into the main content anchor.
- Key public buttons, menus, links, and form controls meet the 44px mobile tap target floor.
- Reduced motion mode forces calmer transition, animation, and scroll behavior.
- Footer links keep privacy, terms, safety, accessibility, and notifications reachable.
- Copy checks keep distracting dash punctuation out of app and library source.
Still reviewed by a person before broad launch.
- Read touched screens on a real phone with larger text enabled.
- Check writing rooms, reveals, profile, updates, and invite flows after signing in.
- Confirm glass surfaces keep enough contrast in bright and dim environments.
- Verify reduced motion feels calm instead of broken.
Barrier reports
How to report a barrier safely.
A useful report names the blocked step without exposing private writing. That helps UYB fix the app without turning support into another place where private feelings leak.
Share the page or flow name, such as Profile, Private Write, a journal invite, or the reveal screen.
Share the phone, tablet, computer, browser, and whether assistive technology or larger text was on.
Tell us what you could not read, tap, hear, focus, understand, save, or return to.
Do not paste journal answers, draft text, reveal text, invite links, email addresses, or private names.
Tell us what gets in the way.
Share the device, browser, page, and what happened. Keep private journal text out of the report.