My commitment: I want TrayEdit to be usable for everyone. I aim to meet WCAG 2.2 AA where practical. I improve pages as I publish new guides and as readers report barriers.

Scope: This statement covers all pages at trayedit.com, including guides, plans, resources, reviews, and policy pages.

Standards I follow

• Web Content Accessibility Guidelines (WCAG) 2.2, target level AA
• Use of semantic HTML: headings, lists, landmarks, labels, and alt text
• Readable typography and strong color contrast

Measures I take

• Accessible navigation with clear headings and breadcrumbs
• Keyboard access to menus, forms, and dialogs; visible focus styles
• Descriptive link text and consistent button labels
• Alt text for meaningful images and captions for diagrams
• Form labels, instructions, and inline error messages
• Respect for reduced motion preferences; no flashing effects
• Templates sized for 100% print scale with check squares

How I test

I check new pages with keyboard-only navigation and screen reader spot checks. I also run automated audits for contrast and landmarks. Then I fix what I find.

• Manual checks: tabbing, heading order, labels, and focus
• Automated checks: contrast, alt text presence, and landmarks
• Reader feedback: I review and act on every report

Compatibility

TrayEdit works with current versions of Chrome, Safari, Firefox, Edge, and mobile browsers. However, some very old browsers may not render all features perfectly.

Known limitations & alternatives

• Legacy PDFs: A few older files may lack full tags. I add on-page summaries and will re-export tagged versions on request.
• Third‑party embeds: Some iframes (e.g., videos) use external code. I add titles and captions when possible.

If you hit a barrier, I’ll provide the information in another format (plain text, tagged PDF, or email).

Report a problem

Please contact me with the page URL, what you expected, and what happened. I try to respond within two business days and fix issues as quickly as I can.