Accessibility
Accessibility Statement
What is the accessibility standard for this site?
MartinZialcita.com targets WCAG 2.2 Level AA conformance. The site is built on semantic HTML with keyboard navigation, visible focus states, 4.5:1 body-text contrast, and reduced-motion support. Known limitations are documented on this page. If you encounter a barrier, the contact page at /contact/ is the fastest route to a response. Accessibility barriers are treated as defects, not enhancement requests.
59-word direct answer
Accessibility commitment
MartinZialcita.com is committed to being accessible to all users, including people who use screen readers, keyboard-only navigation, voice control, or other assistive technologies. Accessibility is designed in from the start, not retrofitted.
The target standard is Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. This is not a declaration of full conformance (some areas have known limitations, documented below), but it is the standard the site is designed and tested against.
Accessibility measures in place
The following measures have been implemented across the site.
Semantic HTML landmarks
Pages use correct landmark elements (
<header>,<main>,<nav>,<footer>, and<aside>) so screen reader users can jump directly to the section they need.Keyboard navigation
All interactive elements (navigation, links, buttons, and form fields) are reachable and operable with a keyboard. Tab order follows visual reading order.
Visible focus indicators
Focus states are visible on all interactive elements, with sufficient contrast to be seen without relying on color alone.
4.5:1 body-text contrast
Body text meets a minimum 4.5:1 contrast ratio against its background. Large text and UI components meet the 3:1 ratio required for their size.
Reduced-motion support
Animations and transitions respect the prefers-reduced-motion media query. Users who have requested reduced motion in their operating system see a non-animated version of any page that includes animation.
Descriptive link text
Links describe their destination rather than using generic text like “click here” or “read more.”
Alternative text for images
Informative images carry descriptive alt text. Decorative images carry an empty alt attribute so they are ignored by screen readers.
Form labels and error messages
Form inputs are associated with visible labels. Error messages identify the field in error and describe what correction is needed.
Captions and transcripts for media
Video content includes accurate closed captions. Audio content is accompanied by a transcript. Caption and transcript files are linked near the media element.
Correct heading hierarchy
Each page has one H1. H2s introduce major sections. H3s introduce subsections within an H2. Heading levels are not skipped.
ARIA used only where semantic HTML is insufficient
ARIA roles, states, and properties are applied only where native HTML semantics do not provide the accessibility information needed. ARIA is not used redundantly or decoratively.
Known limitations
The following limitations are acknowledged. Each is tracked as a defect and is scheduled for remediation.
Known accessibility limitations
| Area | Limitation | Status |
|---|---|---|
| Third-party embed scripts | Embeds from external platforms (e.g., scheduling tools or video hosts) may not fully meet WCAG 2.2 AA. These are outside direct control. | Evaluating alternatives; alternatives linked where possible. |
| Complex data tables | Some research tables may lack sufficient column and row header markup for complex nested layouts. | Targeted for markup improvement on next review. |
| PDF documents | PDFs linked from this site may not be fully tagged for accessibility. The relevant content is also available as HTML. | Ongoing; all new PDFs will be tagged. |
If you find a barrier not listed here, please report it. Unlisted barriers are also taken seriously.
How the site is tested
Accessibility testing uses a combination of automated tools and manual checks. Automated tools (including Axe and Lighthouse) catch common markup errors. Manual keyboard testing and screen reader testing (NVDA on Windows, VoiceOver on macOS and iOS) are used for interactive elements and page structure.
Automated tools do not catch all issues. Manual review is the final authority on whether an element is accessible in practice.
Reporting a barrier
Accessibility barriers are treated as defects. If you encounter a page, element, or feature that prevents you from accessing content or completing a task, please report it through the contact page at /contact/.
Include the URL of the page, a description of the barrier, and, if you are comfortable sharing it, what assistive technology you are using. A response will be provided within 5 business days. If the barrier is urgent, say so in your message.
This statement was last reviewed on 2026-07-31. The WCAG 2.2 reference document is published by the W3C at https://www.w3.org/TR/WCAG22/.