Accessible by design, improved with feedback
Deaf-first
Visual clarity and reading comfort come first.
Keyboard-aware
Core navigation and key interactions are designed for keyboard use.
Ongoing work
We keep improving instead of treating accessibility as finished.
Accessibility at SignDeaf
SignDeaf is built as a Deaf-first, visual-first learning platform. We aim to make the site clear, readable, keyboard-friendly, calmer in motion, and easier to use with modern browser and assistive-technology tools.
Our approach
Accessibility is product quality, not a side note.
We want SignDeaf to feel calm, legible, and respectful to read. That means strong hierarchy, room to breathe, visible focus, dependable keyboard behavior, and layouts that keep information clear instead of cluttered.
Deaf-first and visual-first
We design for clear sightlines, strong hierarchy, calm reading rhythms, and layouts that make sense quickly without audio dependence.
Readable before decorative
We aim for strong color contrast, roomy spacing, visible section breaks, and text that is easier to scan on both desktop and mobile.
Keyboard and assistive tech aware
Interactive elements should be reachable without a mouse, and important updates should be exposed to assistive technologies where practical.
Continuous improvement
Accessibility is an ongoing product standard, not a one-time badge. We keep reviewing, refining, and correcting barriers as the site grows.
Current features
Accessibility features available today.
These are examples of accessibility work currently built into the live site. They reflect the code and interactions in use today rather than aspirational promises.
Skip link and semantic structure
A skip link is available near the top of the site so keyboard users can jump straight to the main content. We also aim to use clear headings, landmarks, and section structure.
Visible focus states
Links, buttons, and interactive elements use visible focus styling so keyboard users can track where they are without guessing.
Keyboard-friendly navigation
Core navigation, search interactions, overlays, and major calls to action are built to work with keyboard input as well as pointer input.
Reduced-motion aware experiences
Animated reveals and decorative motion are designed to calm down or switch off when reduced-motion preferences are active or supported-page controls request it.
Responsive and zoom-friendly layouts
Pages are designed to reflow across smaller screens and remain readable when users zoom in or use larger default text settings.
Dictionary status announcements
The sign dictionary includes live status messaging for important updates such as loading and refreshed results so assistive technologies receive clearer feedback.
Reading support
Try the reading controls on this page.
Larger text, higher contrast, and reduced motion can be toggled below on supported pages. Your choices are stored locally in this browser on this device so you do not need to keep reapplying them.
Reading preferences
Use the controls below to adjust this page for comfort and clarity.
Larger text
Supported pages include a browser-stored larger-text mode to improve readability without forcing everyone into the same default size.
Higher contrast
Supported pages can switch to a stronger contrast presentation for users who prefer a cleaner, sharper reading environment.
Reduce motion
Motion can be reduced through supported-page controls and through operating-system reduced-motion preferences where available.
User choice matters
We encourage browser zoom, device accessibility settings, reader modes, and assistive technology. The site should work with those choices, not fight them.
Standards and review
We aim high, but we do not overclaim.
Accessibility statements should be honest. Our goal is practical, durable improvement guided by WCAG 2.2 Level AA, while being transparent that formal full conformance has not yet been declared.
Current target
We are working toward WCAG 2.2 Level AA across the public website and member experience where reasonably applicable. We do not currently claim formal full-site conformance.
How we review
Accessibility checks are part of our ongoing product updates, including manual keyboard review, focus visibility review, motion review, and content readability review on major page launches.
Compatibility approach
We aim to support current major browsers and modern device accessibility settings. Performance can still vary depending on browser, extensions, embedded providers, and assistive technology combinations.
Accessibility is not a legal paragraph we post once. It is the standard we keep applying to design, copy, motion, and interaction.
Known limitations
Areas we are still improving.
Transparency matters. If something is not finished yet, we would rather say so clearly and keep fixing it than pretend the work is complete.
Some pages are stronger than others
Newer flagship pages generally have the most polished accessibility work. Older or recently published areas may still be catching up to the same level of consistency.
Third-party interfaces can vary
Checkout, payment providers, embedded media, and some external services may expose interfaces or controls outside our direct codebase. We still want to hear about issues in those flows.
Reading controls are still expanding
Browser-stored accessibility controls are available on supported pages, including the homepage and this accessibility page, but not yet on every page of the site.
Media support is still improving
We continue improving captions, transcripts, and equivalent text support where media or archive material needs stronger accessibility coverage.
Improve keyboard and form flows
We keep refining focus order, labels, instructions, and interaction feedback across new templates and member journeys.
Extend user preference controls
We are expanding larger-text, higher-contrast, and reduced-motion controls beyond supported pages so more of the site responds to personal reading preferences.
Strengthen media accessibility
We continue reviewing how video, learning assets, and supporting content are captioned, described, or otherwise presented in a clearer way.
Feedback and support
Tell us when something gets in your way.
If a page, form, video, checkout step, or interaction is difficult to use, we want to know. Helpful reports include the page URL, device, browser, assistive technology if relevant, and a short description of the barrier.
support@signdeaf.com
Use email if you need help completing a task or want to report an accessibility problem directly.
Open the contact form
Use the contact page if you prefer a web form for feedback, support, or follow-up questions.
FAQ
Fast answers.
These are the questions people are most likely to ask about accessibility on SignDeaf.
Does SignDeaf claim full WCAG conformance?
Not at this time. We are working toward WCAG 2.2 Level AA, but we do not currently make a formal full-site conformance claim.
Can I use SignDeaf without a mouse?
That is the goal for core navigation and key interactions. If any page traps focus, hides focus, or blocks keyboard use, please report it so we can fix it quickly.
Are accessibility preferences saved?
On supported pages, reading preferences such as larger text, higher contrast, and reduced motion are stored locally in your browser on that device so they can be reused later.
What should I do if I hit an accessibility barrier?
Please contact us through the contact page or email support@signdeaf.com with the page URL, device, browser, and the barrier you experienced. We take those reports seriously.
Does this page cover third-party tools too?
It explains our approach, but some third-party services such as checkout, payments, or embedded providers use their own interfaces and may behave differently from the rest of the site.
Keep learning with confidence
Need help now, or ready to keep exploring?
If you hit a barrier, contact us and we will do our best to help. If everything feels good, you can jump straight back into learning.