Policy
Accessibility
Updated July 24, 2026
1. What this page is
This is a working note about how the notebook is built, not a badge and not a claim of perfection. Below you will find the standard we work toward, the limits we know about, and where to write when something blocks you. If a page here keeps you out, that is a defect in our work, not a shortcoming in your equipment.
2. The standard we work toward
We work toward version 2.1 of the Web Content Accessibility Guidelines, at level AA. No outside auditor has reviewed this site, and we do not claim conformance in the formal sense of that word. What we can say is that each page is checked against the level AA criteria that apply to a text site with illustrations and two forms. Where a criterion is not met, section 9 says so.
3. Structure and semantic markup
Pages are written in plain semantic HTML: one header, one main region, one footer, and real landmarks around them. Headings run in order without skipped levels, and every page carries exactly one first-level heading that matches what the page is about. Navigation is a real list of links inside a navigation landmark, so a screen reader can announce how many items it holds. With styling and scripting switched off, every page still reads from top to bottom in a sensible order.
4. Color and contrast
The palette is deliberately narrow: a cool gray page, near-black text, a brick red accent, and a slate blue secondary. Body text and headings are tested against their backgrounds for a contrast ratio of at least 4.5 to 1. Links inside body text are underlined as well as colored, so nothing depends on seeing red against gray. Error text on the contact form is announced in words, not by turning a field red.
5. Keyboard use, focus, and the skip link
Everything on the site can be reached and operated with a keyboard alone. Every page begins with a skip link that jumps past the header to the main content, and the link becomes visible as soon as it takes focus. Focus styles are never removed. Buttons, links, form fields, and the menu toggle all show a clear focus outline. Before each release the site is walked through with the Tab key alone, so focus visibility is checked by hand at this desk rather than assumed from the stylesheet. Tab order follows the visual order of the page, and the mobile menu returns focus to its toggle when it closes.
6. Motion and animation
Sections fade upward slightly as they enter the viewport, and that is the entire animation budget of this site. There is no autoplay, no carousel, no parallax, and no video. When a browser reports a preference for reduced motion, all transitions and transforms are switched off, and content simply appears in place.
7. Touch targets and spacing
Buttons, navigation links, and form controls are sized to at least forty-four by forty-four pixels. Text is set at seventeen pixels with a line height of about one and a half. The reading column stops around seven hundred pixels, so lines never run past a comfortable length. Pages reflow to a single column on narrow screens without horizontal scrolling. Zooming to two hundred percent does not clip text or hide controls, and pinch-to-zoom is never disabled.
8. Images, alternative text, and forms
Every image on the site carries an alt attribute along with width and height, so the layout does not jump while a page loads. Each illustration describes what appears in its frame in a sentence a reader can use. Form fields on the contact page and in the home page signup have visible labels placed above the field, never inside it as a placeholder that vanishes when you type. Validation messages appear next to each form and are written as sentences, so they make sense when read aloud.
9. Known limits
The illustrations that head each entry are decorative by design. Their alt text names what the frame shows, not what the place is like today. A reader using a screen reader loses nothing of substance, because no fact in an entry lives only in a picture. Two other limits are worth stating. Long entry pages have no in-page table of contents yet, and the section listings rely on order rather than on a labeled group. Both are on the list for the next revision of the styles.
10. Telling us about a problem
If any page, control, or file here blocks you, write to ledger@asmattravels.com and describe what happened. It helps to name the page, to say which browser or assistive technology was in use, and to describe what you expected instead. You may also call +1 (603) 218-4470 during posted hours and describe it out loud, which is often faster. Accessibility reports are read first and answered within three business days. If a fix will take longer, we will say so and send the information you were after in another form.
11. How this page is reviewed
This page was last reviewed on July 24, 2026, and it is checked again whenever the styles or the page layouts change. Reviews cover keyboard operation, focus visibility, heading order, contrast values, and the behavior of both forms. Findings that cannot be fixed the same week are written into section 9 rather than left unmentioned.
Contact about this policy
Write to ledger@asmattravels.com about anything on this page, including a request for content in a different format. Mail reaches us at Asmat Media LLC, 1750 Elm Street, Manchester, NH 03104, United States. The telephone is +1 (603) 218-4470, answered Monday through Thursday, 10:00 am to 2:00 pm, Eastern Time. Questions about data and requests about personal information go to notice@asmattravels.com and are covered by the Privacy Policy. The Terms of Use and the Disclaimer explain the rest of the arrangement between this desk and a reader.