Legal
Accessibility
MacStartup aims to keep this website usable with a keyboard, a screen reader, and a small screen. This page describes that approach. It is not a formal conformance certificate.
Version date: October 15, 2026.
Accessibility goals
The site is a content and contact website: service explanations, guides, and a request form. The practical goal is that those tasks can be completed without a mouse, without relying on color alone, and without horizontal scrolling at common phone widths. Pages use semantic regions—header, navigation, main, and footer—and one top-level heading per page.
MacStartup has not commissioned a formal WCAG audit and does not claim WCAG certification or a conformance level.
Keyboard navigation
Links, buttons, form fields, and the FAQ disclosures are reachable in tab order. A “Skip to main content” link is the first focusable control. Focus is shown with a visible outline. The mobile menu is a button that setsaria-expanded and opens a list of the same destinations as the desktop navigation. Escape closes that menu and returns focus to the button. The menu is not a hover-only control.
FAQ answers use native details and summary elements, which are operable from a keyboard without a custom script.
Responsive design
Layouts use flexible grids that collapse on narrow screens. Controls in the header and form are sized for touch. The mobile navigation replaces the desktop link row below the desktop breakpoint. Text wraps inside the content width instead of forcing a sideways scroll.
Readable typography
Body text uses the Manrope typeface when Google Fonts is available, and a system sans-serif otherwise. Body copy is set with a comfortable line height. Headings are larger than body text and follow a single H1, then H2 and H3 where a page needs subsections. The stylesheet reduces motion when the operating system asks for it.
Color and contrast
Primary text is dark on a light background. Links are distinguishable from surrounding text. The design does not use color as the only way to tell a control’s state: focus has an outline, and the mobile button has an expanded state. A full contrast audit of every secondary and footer color has not been published, so this page does not claim that every muted label meets a particular ratio.
Forms
The contact form has a visible label for every field, including optional fields. Required fields use the browser’s built-in checks for empty values and email format, so the form works with JavaScript disabled. Errors from those checks are the browser’s own messages, next to the field.
If the server rejects the submission, the site redirects to a separate error page instead of returning a field-by-field summary. That is a known limitation: the PHP handler does not store the form or redisplay it. The error page explains the kinds of problems that stop a request and links back to the form.
The form does not ask for passwords or payment details. A hidden anti-spam field is not part of the visible task.
Images
Photographs that convey a topic include a text alternative. Decorative marks in the logo are hidden from assistive technology because the brand name is already in the link. The website uses photographs to illustrate digital organization topics and example workspaces. These images do not represent a visitor’s actual files or an application developed by MacStartup.
Feedback
If you cannot use a page or the form, send a note through the contact form or to[email protected]. Describe the barrier, the page address, and the browser or assistive technology you used. If the form itself is the barrier, use the email address.
You can also email [email protected].
Known limitations
- No formal WCAG certification is claimed.
- Server-side form failures use a general error page rather than inline field errors.
- Font files are loaded from Google. If that request fails, the fallback font is used.
- Some secondary text and footer text is intentionally muted. It has not been certified against a contrast standard.
- macOS setting names in the guides can differ by version. The articles say so, but they are still written descriptions rather than an interactive tutorial.