Accessibility statement

The commitment

Margalit coaches people who lead. Some of them use a screen reader. Some enlarge type to twice its size. Some cannot use a mouse, and some get sick from motion on a screen. A website that shuts any of them out is a website doing the opposite of its job.

So accessibility is treated here as part of the build, not a patch applied afterwards. If any part of this site stops you getting what you came for, that is treated as a defect and fixed, and in the meantime the same information will be given to you another way.

The standard being worked to

This site is built to meet the Web Content Accessibility Guidelines, WCAG 2.2, at Level AA. Those guidelines are published by the World Wide Web Consortium and are the benchmark used by United States federal guidance and by state and international law.

Level AA is the level most organizations aim at. It covers contrast, keyboard access, clear structure, form labeling, resizable text, and control over movement. This site is currently assessed as substantially conformant with WCAG 2.2 Level AA, with the exceptions listed under known limitations below.

That assessment comes from an internal review by Citrus Studios using automated testing plus manual keyboard and screen reader checks. It is not a formal third party audit. An independent audit is recommended once the site is live and the real content is in place.

What has been done

These are the concrete measures in this build, not a wish list.

• Headings that describe the structure. Every page has exactly one h1, and the headings below it descend in order without skipping a level for the sake of appearance. A screen reader user can pull up a list of headings and understand the page from it.
• A skip to content link. The first thing a keyboard user reaches on any page is a link that jumps past the header and the menu, straight to the main content.
• Full keyboard operation. Every link, button, form field, menu, accordion and search control works from the keyboard alone. Nothing needs a mouse and nothing traps focus.
• Visible focus outlines. Whatever the keyboard is on has a thick outline around it, in a color that stands out against the page. Focus styling is never switched off anywhere in the stylesheet.
• Color contrast of at least 4.5 to 1 for body text. The palette was checked against the WCAG contrast ratios before the design was signed off, and large headings clear 3 to 1 or better. Color is never the only way information is conveyed.
• Form fields with real labels. Every field has a visible label tied to it in the markup. Placeholder text is never used in place of a label, so the label does not vanish the moment you start typing.
• Alt text on images that carry information. Photographs that add something get a description. Images that are pure decoration, and the decorative parts of the logo, are hidden from screen readers so they do not add noise.
• Control over the hero video. The looping cinemagraph on the home page has a visible pause button, and the site respects the reduced motion setting in your operating system. Switch that on and the loop does not play at all.
• A sticky button that gets out of the way. The floating booking button docks and disappears as you reach the footer, so it never sits on top of the footer links, the contact details or any text underneath it.
• Layout that reflows. Pages work down to a 320 pixel wide screen and at 200 percent zoom without content being cut off or needing sideways scrolling.
• Link text that stands on its own. Links say where they go, so a list of links read out of context still makes sense. There is no bare "click here" or "read more".
• Language set in the markup. Each page declares English, so a screen reader uses the right pronunciation.

Known limitations, told straight

No site is perfectly accessible, and a statement that claims otherwise is not worth reading. Here is what falls short right now.

• The scheduling tool. Booking runs on a third party tool embedded in the contact page. Its markup, its colours and its keyboard behavior are set by the vendor and cannot be corrected from here. If the booking embed does not work for you, email or phone instead and the call will be put in the calendar by hand. That option is always open and it is not a lesser service.
• Podcast players. The As Seen In page embeds players from Spotify, Apple and Acast. Their controls and their labeling are outside Margalit's control. Every episode is also listed as a plain link to the source, so you can reach it in whichever player you already use.
• Podcast transcripts. The episodes are hosted by the show, not by Margalit, and not every one has a transcript. Where a show publishes one it will be linked from the As Seen In page.
• The email signup form. Newsletter and download forms are handled by a third party email platform. The fields on this site are labeled correctly, but the confirmation pages and the emails themselves are generated by that platform.
• PDF downloads. The Question Vault and the peer group self audit are PDFs. They are readable, but they have not yet been tagged for screen reader structure. Ask and the content will be sent as plain text or as an accessible web page instead.
• Photography and video. New images are given alt text as they are added. Any future video with speech in it will need captions and a transcript before it goes up.

How to report a problem

If something here blocks you, please say so. A short message beats a perfect one, and you will not be asked to justify why you need it.

• Email: margalit@margalitmethod.com
• Phone: (818) 693-4557
• Or use the contact form, whichever suits you.

What helps, if you have it: the address of the page, what you were trying to do, what happened instead, and the browser and assistive technology you were using. If you do not have those details, write anyway.

You will get a reply within three business days, with either a fix, a date for the fix, or another way to get what you needed in the meantime.

If the answer does not resolve it, say so and it will be looked at again. Formal complaints can also be taken to the Civil Rights Division of the United States Department of Justice, which enforces the Americans with Disabilities Act.

When this statement was last reviewed

It should be reviewed after every significant change to the site, a new page, a new embedded tool, a design change, a new form, or a batch of new images, and at least once a year even if nothing changes. An accessibility statement that no longer describes the site is worse than none, because it tells people something untrue about whether they can use it.