Accessibility Statement

1. Our Commitment

SnapUtils is committed to ensuring digital accessibility for people with disabilities. We continuously work to improve the usability of our Site and tools for all visitors, regardless of ability or the technology they use to access the internet.

We believe that accessibility is not a checkbox — it is an ongoing commitment. We are actively working toward compliance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and relevant legal standards including the Americans with Disabilities Act (ADA).

2. Conformance Status

Partially Conformant

SnapUtils is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not fully conform to the accessibility standard. We are actively addressing known gaps.

We assess our accessibility against the following standards:

• WCAG 2.1 Level A — Largely conformant
• WCAG 2.1 Level AA — Partially conformant
• Section 508 (U.S. federal standard) — Partially conformant

3. Accessibility Features

We have implemented the following accessibility features across the Site:

Visual Design

• Color contrast: Our dark theme uses text colors designed to meet or exceed WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text). Our primary text (#e8e8ec) on background (#0a0a0b) exceeds 15:1 contrast.
• Color independence: Information is not conveyed by color alone — we use icons, labels, and text alongside color coding.
• Text resizing: All text can be resized up to 200% without loss of content or functionality.
• No time limits: No tool imposes time limits on user actions.
• No flashing content: The Site contains no content that flashes more than three times per second.

Navigation & Structure

• Semantic HTML: We use semantic HTML5 elements (<nav>, <main>, <footer>, <section>, <h1>–<h6>) to provide meaningful document structure across all pages.
• Keyboard navigation: All interactive elements are reachable and operable via keyboard. Focus order follows a logical reading order.
• Skip navigation: A visible skip-to-main-content link is present at the top of every page, allowing keyboard and screen reader users to bypass navigation and jump directly to the main content.
• Page titles: Each page has a unique, descriptive <title> element.
• Language attribute: The HTML lang="en" attribute is set correctly on all pages.
• Landmark regions: All pages use <main id="main-content">, <nav>, and <footer> landmarks for clear document structure. The navigation includes a hamburger menu with full aria-expanded, aria-controls, and keyboard support (Enter/Space to toggle, Escape to close).
• Heading hierarchy: All pages follow a logical heading structure (h1 → h2 → h3) with no skipped levels.

Interactive Tools

• Form labels: All form inputs (text areas, text inputs, range sliders, number inputs, color pickers, select dropdowns) have programmatically associated labels via <label for> or aria-label attributes.
• Live regions: All tool output areas (JSON formatter output, code formatter output, regex match results, text diff view, word count stats, plagiarism results, mortgage/interest calculations, QR code output) use aria-live="polite" to announce results to screen reader users automatically when content changes.
• Error identification: Input errors are identified in text and described to users.
• Buttons and controls: All interactive controls have accessible names via visible text content, title attributes, or aria-label. Toggle buttons use aria-pressed to communicate on/off state.
• Focus visibility: Keyboard focus indicators are visible on all interactive elements. We use a custom 2px green outline (outline: 2px solid #00e599; outline-offset: 2px) on interactive elements — no focus is suppressed without a visible replacement.

Screen Reader Support

• ARIA attributes are used throughout to convey dynamic state changes (expanded/collapsed menus, active tab selection, toggle states).
• All tool output regions are wrapped in aria-live="polite" regions so results are announced automatically when the tool produces output.
• Document landmark structure (<main>, <nav>, <footer>) enables screen reader users to navigate by region.

4. Known Limitations

Despite our best efforts, some areas of accessibility are not yet fully achieved. Known limitations include:

• Complex visual output: The regex tester's inline match highlighting and the text diff side-by-side colored view are conveyed visually. While results are announced via aria-live regions, the detailed character-level or line-level diff formatting may not convey full meaning to screen reader users in all modes.
• Charts and visual output: Charts in the Mortgage and Interest Calculators convey data visually. Summary tables are provided alongside charts as an accessible alternative, but chart data itself is not yet fully represented with text descriptions.
• Keyboard shortcut documentation: Tool-specific keyboard shortcuts (e.g., Ctrl+Enter to format, Ctrl+S to copy) are functional but not all are discoverable via standard accessibility patterns such as an on-screen shortcut reference.
• Mobile touch targets: Some controls on very small screens may not meet the 44×44px minimum touch target recommendation (WCAG 2.5.5) on all devices.
• Third-party advertisements: Google AdSense advertisements are served by a third party and may not meet the same accessibility standards as the rest of the site. See section 5 for details.

We are actively working to address these issues. If you encounter a barrier not listed here, please contact us.

5. Third-Party Content

The Site displays advertisements served by Google AdSense. These advertisements are provided by third parties and may not meet the same accessibility standards as the rest of the Site. We do not control the accessibility of third-party ad content.

If third-party advertising content creates a significant accessibility barrier, please contact us and we will work with our advertising partners to address it.

6. ADA Compliance

We are committed to complying with the Americans with Disabilities Act (ADA) and other applicable accessibility laws. Our ongoing efforts include:

• Regular accessibility audits using automated tools (axe, Lighthouse) and manual testing.
• Screen reader testing on both desktop and mobile platforms.
• Keyboard-only navigation testing.
• Responsive design testing across device types and sizes.
• Following the Inclusive Design Principles in all new feature development.

If you are unable to access any part of the Site due to a disability, please contact us and we will make every reasonable effort to provide the information or service to you in an alternative format or through an alternative means.

7. Feedback & Contact

We welcome feedback on the accessibility of SnapUtils. If you experience any barriers, have suggestions for improvement, or need assistance accessing any part of the Site:

Email: snaputils@polsia.app
Subject line: "Accessibility Feedback"

Please provide:

• The URL of the page where you experienced the issue
• A description of the accessibility barrier
• The assistive technology you were using (screen reader, switch access, etc.)
• Your operating system and browser version

We will acknowledge your message within 2 business days and aim to resolve issues within 30 days where reasonably practicable.

8. Formal Complaints

If you are not satisfied with our response, you may contact the relevant enforcement authority in your jurisdiction:

• United States: U.S. Department of Justice Civil Rights Division — ada.gov
• European Union: Your national equality body or disability rights authority.
• United Kingdom: Equality and Human Rights Commission — equalityhumanrights.com