Accessibility
Statement
Accessibility Statement
Nathan Chaim is committed to ensuring digital accessibility for all users, including people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards.
Legal Basis
This website strives to conform to the Israeli Equal Rights for Persons with Disabilities Law (5758-1998) and the Israeli Accessibility Regulations (5773-2013), based on Israeli Standard IS 5568, which adopts WCAG 2.1 Level AA as its technical specification.
Conformance Status
Partially conformant — This website partially conforms to WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not yet fully conform to the accessibility standard due to technological limitations or the scale of the work required, as detailed in Section 3.
Technical Specifications
This website is built using HTML5, CSS3, and vanilla JavaScript. Accessibility relies on compatibility between the following technologies: HTML, WAI-ARIA, CSS, JavaScript, and assistive technologies (screen readers, keyboard-only navigation, switch access).
Scope of This Statement
This statement covers the whole site at https://natanchaim.org — the homepage, how it works (איך זה עובד), pricing (מחירים), FAQ (שאלות נפוצות), guides (מדריכים), portfolio (תיק עבודות) and its individual project pages, contact (בוא נדבר) including the lead form, the privacy policy, and this statement. It does not cover the private admin area, which is not public.
הצהרת נגישות
נתן חיים מחויב להנגיש את האתר לכלל המשתמשים, לרבות אנשים עם מוגבלות, בהתאם לחוק שוויון זכויות לאנשים עם מוגבלות, תשנ"ח-1998, ותקנות הנגישות לשירות, תשע"ג-2013, בהתאם לתקן ישראלי IS 5568 המבוסס על WCAG 2.1 רמה AA.
האתר עומד בחלקו בדרישות התקן. עמידה חלקית משמעה שחלק מהתכנים אינם עומדים במלוא דרישות תקן הנגישות בשל מגבלות טכנולוגיות או עומס בלתי מידתי, כמפורט בסעיף 3.
Implemented Accessibility Features
✅ Fully Implemented
-
Keyboard NavigationAll interactive elements — navigation links, buttons, modals, category tabs, and footer links — are fully operable using keyboard only (Tab, Shift+Tab, Enter, Space, Escape). Focus order follows logical reading order.
-
Visible Focus IndicatorsAll focusable elements display a clearly visible focus ring on keyboard focus (yellow-green outline, 2px, minimum 3:1 contrast ratio against adjacent colors). Focus indicators meet WCAG 2.4.7 and 2.4.11.
-
Skip to Main Content LinkTwo skip links are present at the top of every page — one in English ("Skip to main content") and one in Hebrew ("דלג לתוכן הראשי"). They become visible on keyboard focus and allow users to bypass repetitive navigation blocks (WCAG 2.4.1).
-
Alt Text on All ImagesEvery meaningful image — including all AI visualization renders, website screenshots, the profile photo, and the logo — has a descriptive alt attribute. Decorative images use alt="" so screen readers ignore them (WCAG 1.1.1).
-
Color Contrast — TextPrimary text (#EDECEB on #07080F) achieves a contrast ratio of 19.4:1, far exceeding the WCAG AA minimum of 4.5:1. Secondary/muted text achieves a minimum of 3.1:1. Interactive element contrast meets 3:1 for non-text (WCAG 1.4.3, 1.4.11).
-
Heading HierarchyThe page uses a correct and sequential heading hierarchy (H1 → H2 → H3) without skipping levels. The main page title is H1 (NATAN), section titles are H2, and subsections are H3. This enables screen reader users to navigate by headings (WCAG 1.3.1, 2.4.6).
-
ARIA Labels on Interactive ElementsAll buttons, links, and form controls that rely on visual context have aria-label or aria-labelledby attributes. Icons-only buttons (WhatsApp, LinkedIn, Email, Close modal) have descriptive accessible names. Modals use role="dialog", aria-modal="true", and aria-labelledby (WCAG 4.1.2).
-
Language DeclarationThe primary page language is declared as lang="en" on the HTML element. Hebrew sections within the page use lang="he" and dir="rtl" to ensure correct pronunciation by screen readers (WCAG 3.1.1, 3.1.2).
-
Semantic HTML StructureThe page uses semantic HTML5 landmarks: <nav>, <main>, <section>, <footer>, <article>. All lists use <ul>/<li> elements. Sections have aria-labelledby attributes linking to their headings (WCAG 1.3.1).
-
Responsive DesignThe website adapts to all viewport sizes from 320px to 2560px+ without horizontal scrolling or loss of content. Text can be resized up to 200% without loss of functionality. Viewport is not locked (WCAG 1.4.4, 1.4.10).
-
Modal Focus ManagementWhen a modal opens, focus is moved to the modal container. The Escape key closes all modals. Clicking outside the modal closes it. Focus is managed so keyboard users cannot interact with background content while a modal is open (WCAG 2.1.2).
-
Page TitleEvery page has a meaningful, descriptive <title> element that identifies both the specific page and the site. The accessibility document page has its own distinct title (WCAG 2.4.2).
-
No Color-Only InformationNo information is conveyed through color alone. Status indicators (conformant/not conformant) use both color and text labels. Interactive state changes include shape/text changes in addition to color (WCAG 1.4.1).
-
No Keyboard TrapUsers can always navigate away from any component using only the keyboard. The Tab key moves focus through all interactive elements in order. No component traps keyboard focus permanently (WCAG 2.1.2).
-
Consistent NavigationNavigation links appear in the same location and order on every page. The logo always links to the homepage. The same links appear in the same relative order throughout the site (WCAG 3.2.3, 3.2.4).
-
Touch Target SizeAll interactive elements meet the minimum touch target size of 44×44px as required by WCAG 2.5.5 and iOS/Android accessibility guidelines. Icon buttons in the navigation are at minimum 44px in both dimensions (WCAG 2.5.5).
-
Accessible Video LinkThe video content is presented as a clickable thumbnail linking to YouTube rather than an auto-playing embedded video. Users have full control over playback. The link is clearly labeled "Watch on YouTube" (WCAG 2.2.2).
Elements Not Yet Fully Accessible
-
Video Captions (WCAG 1.2.2, 1.2.4)Issue: The AI-produced video "להיות עצמך" on YouTube does not include captions or subtitles. Barrier: Deaf and hard-of-hearing users cannot access the audio content. Reason: The video is externally hosted on YouTube; captions require post-production effort and Hebrew transcription. Plan: Hebrew captions will be added to the YouTube video within 6 months of this statement.
-
Audio Description — Background Video (WCAG 1.2.5)Issue: The background video displayed on the portfolio page does not have an audio description. Mitigating factor: The background video is purely decorative and conveys no informational content — all meaningful content is available as text and images. The video does not supplement or replace any textual information. Classification: Decorative media — disproportionate burden to add audio description for a non-informational animation.
Beyond the item above, the site meets WCAG 2.1 Level AA. Text can be enlarged to 200% using the browser's built-in zoom without loss of content or functionality (WCAG 1.4.4); the interface honours the operating system's "reduce motion" and high-contrast preferences; and all interactive elements, including the before/after comparison slider, are fully operable by keyboard (WCAG 2.1.1).
Accessibility Coordinator
If you encounter any accessibility barrier on this website, or if you have feedback on how we can improve, please contact us using any of the following methods:
When submitting an accessibility complaint, please include: the URL of the page where you experienced the barrier, the assistive technology and browser you are using, and a description of the issue.
Enforcement
If you are not satisfied with our response, you may submit a complaint to the Israeli Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice: gov.il/nechut-online
Adjusting the Site to Your Needs
This site is built to work with the accessibility tools already on your device and in your browser, rather than a separate on-page widget. Overlay widgets address only a small share of accessibility requirements and are not a substitute for a site that is accessible by design.
Ways to adapt the display
- Enlarge text: Use your browser zoom (Ctrl / ⌘ and +). The site remains fully usable up to 200% and beyond.
- Reduce motion: Turn on "Reduce motion" in your operating system. The site detects it and disables animations automatically.
- Higher contrast: The base design already exceeds the required contrast (primary text 19.4:1), and the site respects your system's high-contrast / dark-mode settings.
- Keyboard & screen reader: Every interactive element — navigation, buttons, forms, and the before/after comparison slider — is fully operable by keyboard and announced to screen readers.
This Accessibility Statement is reachable from the footer of every page via the "Accessibility statement" link.
Recommendations for Future Improvements
-
Hebrew Captions on YouTube VideoTranscribe and upload Hebrew (and English) captions to the YouTube video "להיות עצמך" using YouTube's caption editor. Priority: High. Target: within 6 months.
-
Regular Accessibility AuditCommission an independent accessibility audit using automated tools (axe-core, WAVE) combined with manual testing using NVDA + Chrome and VoiceOver + Safari. Recommended frequency: annually, or after significant site changes. Priority: Medium.
-
Live Accessibility Status PageCreate an automatically updated accessibility status page that runs axe-core on each deployment and publishes results. This demonstrates ongoing commitment and keeps the accessibility statement accurate. Priority: Low.
Accessibility QA Testing Checklist
Use this checklist when performing accessibility testing on this website. Test using the combinations: NVDA + Chrome (Windows), JAWS + Edge (Windows), VoiceOver + Safari (macOS/iOS).
WCAG 2.1 AA — Full Requirements Table
All 50 success criteria at Level A and AA under WCAG 2.1, with conformance status for this website. Criteria introduced in WCAG 2.1 (not in WCAG 2.0) are marked 2.1 New.
| Criterion | Name | Level | Description | Status |
|---|---|---|---|---|
| Principle 1 — Perceivable | ||||
| 1.1.1 | Non-text Content | A | All non-text content has a text alternative (alt text, labels, captions). | Conforms |
| 1.2.1 | Audio-only & Video-only | A | Prerecorded audio-only and silent video provide text alternatives. | N/A |
| 1.2.2 | Captions (Prerecorded) | A | Captions are provided for prerecorded audio content in synchronized media. | Fails |
| 1.2.3 | Audio Description / Alt (Prerecorded) | A | Audio description or full text alternative for prerecorded video. | Partial |
| 1.2.4 | Captions (Live) | AA | Captions provided for all live audio content in synchronized media. | N/A |
| 1.2.5 | Audio Description (Prerecorded) | AA | Audio description provided for all prerecorded video content. | Fails |
| 1.3.1 | Info and Relationships | A | Information, structure, and relationships conveyed through presentation can be programmatically determined. | Conforms |
| 1.3.2 | Meaningful Sequence | A | Content reading sequence can be programmatically determined where order affects meaning. | Conforms |
| 1.3.3 | Sensory Characteristics | A | Instructions do not rely solely on sensory characteristics (shape, size, visual location, etc.). | Conforms |
| 1.3.4 | Orientation | AA 2.1 | Content does not restrict view or operation to a single display orientation. | Conforms |
| 1.3.5 | Identify Input Purpose | AA 2.1 | The purpose of each input field can be programmatically determined. | N/A |
| 1.4.1 | Use of Color | A | Color is not the only visual means of conveying information. | Conforms |
| 1.4.2 | Audio Control | A | A mechanism to pause, stop, or control volume for any audio that plays automatically. | N/A |
| 1.4.3 | Contrast (Minimum) | AA | Text and images of text have a contrast ratio of at least 4.5:1 (3:1 for large text). | Conforms |
| 1.4.4 | Resize Text | AA | Text can be resized without assistive technology up to 200% without loss of content or functionality. | Conforms |
| 1.4.5 | Images of Text | AA | Images of text are only used for decoration or where essential (e.g., logos). | Conforms |
| 1.4.10 | Reflow | AA 2.1 | Content can be presented without horizontal scrolling at 320px viewport width. | Conforms |
| 1.4.11 | Non-text Contrast | AA 2.1 | UI components and graphical objects have a contrast ratio of at least 3:1. | Conforms |
| 1.4.12 | Text Spacing | AA 2.1 | No loss of content when letter-spacing, word-spacing, line-height, and paragraph spacing are modified. | Conforms |
| 1.4.13 | Content on Hover or Focus | AA 2.1 | Content that appears on hover or focus is dismissible, hoverable, and persistent. | Partial |
| Principle 2 — Operable | ||||
| 2.1.1 | Keyboard | A | All functionality is operable through a keyboard interface without specific timing. | Partial |
| 2.1.2 | No Keyboard Trap | A | Keyboard focus can always be moved away from any component. | Conforms |
| 2.1.4 | Character Key Shortcuts | A 2.1 | Single character key shortcuts can be turned off, remapped, or deactivated on focus. | N/A |
| 2.2.1 | Timing Adjustable | A | Time limits can be turned off, adjusted, or extended by the user. | N/A |
| 2.2.2 | Pause, Stop, Hide | A | Moving, blinking, or scrolling content can be paused, stopped, or hidden. | Partial |
| 2.3.1 | Three Flashes or Below Threshold | A | Content does not flash more than three times per second. | Conforms |
| 2.4.1 | Bypass Blocks | A | A mechanism to bypass repeated navigation blocks (skip link). | Conforms |
| 2.4.2 | Page Titled | A | Pages have titles that describe their topic or purpose. | Conforms |
| 2.4.3 | Focus Order | A | Focus order preserves meaning and operability. | Conforms |
| 2.4.4 | Link Purpose (In Context) | A | The purpose of each link can be determined from the link text or context. | Conforms |
| 2.4.5 | Multiple Ways | AA | More than one way to locate a page within a set of pages. | N/A |
| 2.4.6 | Headings and Labels | AA | Headings and labels describe topic or purpose. | Conforms |
| 2.4.7 | Focus Visible | AA | Any keyboard operable UI has a visible focus indicator. | Conforms |
| 2.5.1 | Pointer Gestures | A 2.1 | All multipoint or path-based gestures have a single-pointer alternative. | Conforms |
| 2.5.2 | Pointer Cancellation | A 2.1 | Functions that activate on single pointer can be cancelled or reversed. | Conforms |
| 2.5.3 | Label in Name | A 2.1 | Accessible name of UI components with visible text contains the visible text. | Conforms |
| 2.5.4 | Motion Actuation | A 2.1 | Functionality using device motion can be operated without motion and motion response can be disabled. | N/A |
| Principle 3 — Understandable | ||||
| 3.1.1 | Language of Page | A | Default human language of the page can be programmatically determined. | Conforms |
| 3.1.2 | Language of Parts | AA | Language of each passage or phrase can be programmatically determined. | Conforms |
| 3.2.1 | On Focus | A | Receiving focus does not automatically change context. | Conforms |
| 3.2.2 | On Input | A | Changing a setting does not automatically cause a context change unless user is advised. | Conforms |
| 3.2.3 | Consistent Navigation | AA | Navigation mechanisms repeated on multiple pages appear in the same relative order. | Conforms |
| 3.2.4 | Consistent Identification | AA | Components with the same functionality are identified consistently. | Conforms |
| 3.3.1 | Error Identification | A | Input errors are identified and described to the user in text. | Conforms |
| 3.3.2 | Labels or Instructions | A | Labels or instructions are provided when content requires user input. | Conforms |
| 3.3.3 | Error Suggestion | AA | If an input error is detected, suggestions for correction are provided. | Conforms |
| 3.3.4 | Error Prevention (Legal/Financial) | AA | For legal, financial, or data-entry submissions: submissions are reversible, checked, or confirmed. | N/A |
| Principle 4 — Robust | ||||
| 4.1.1 | Parsing | A | Content implemented in markup languages has complete start/end tags, no duplicate attributes, and unique IDs. | Conforms |
| 4.1.2 | Name, Role, Value | A | UI components have name, role, and value programmatically available and change notifications sent to assistive technologies. | Conforms |
| 4.1.3 | Status Messages | AA 2.1 | Status messages can be programmatically determined through role or properties and are not required to receive focus. | Conforms |