1. Commitment
Our Commitment
WebEaze Web Design ("WebEaze," "we," "our," or "us") is committed to providing an accessible and inclusive digital experience for all users, including individuals with disabilities. We believe the internet should be usable by everyone, and we apply accessibility principles to every website we design and deliver.
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as published by the World Wide Web Consortium (W3C). These guidelines address accessibility for users with visual, auditory, motor, cognitive, and neurological disabilities.
Accessibility is not a checkbox we apply at the end of a project. It is integrated into how we structure HTML, choose color palettes, write content, and test every site before it goes live.
2. What We Do
Accessibility Measures
The following practices are applied to every website WebEaze designs and manages:
Structure and Semantics
- Semantic HTML5 elements (
<nav>, <main>, <header>, <footer>, <article>, <section>) used throughout to define page regions
- Heading hierarchy maintained in logical order (h1 → h2 → h3) so screen readers can navigate by heading
- WAI-ARIA roles and attributes (
aria-label, aria-describedby, aria-expanded, aria-current) applied to interactive widgets where native HTML semantics are insufficient
- Landmark regions present on all pages so assistive technology users can jump directly to navigation, main content, or footer
Color and Visual Design
- Text color contrast tested to WCAG 2.1 Success Criterion 1.4.3: minimum 4.5:1 for normal text, 3:1 for large text (18pt or 14pt bold)
- UI component contrast tested to WCAG 2.1 SC 1.4.11: minimum 3:1 for buttons, form borders, and focus indicators against adjacent backgrounds
- Information is never conveyed by color alone; icons, labels, or text patterns are used alongside color
Keyboard and Focus
- All interactive elements (links, buttons, form fields, dropdowns) are reachable and operable using Tab, Shift+Tab, Enter, and Space
- Visible focus indicators applied via
:focus-visible CSS; no element has outline: none without an accessible alternative
- Modal dialogs and overlays trap focus within themselves and return focus to the triggering element when dismissed
Images and Media
- All meaningful images include descriptive
alt text per WCAG 2.1 SC 1.1.1; decorative images use empty alt="" to be skipped by screen readers
- Icon-only buttons include
aria-label text so their purpose is announced by screen readers
Forms
- Every form input has a programmatically associated
<label> or aria-label
- Required fields are identified both visually and via
aria-required="true"
- Inline error messages reference the affected field with
aria-describedby so screen readers announce the error in context
Responsive Design and Motion
- Layouts tested down to 320px viewport width with no horizontal scrolling, per WCAG 2.1 SC 1.4.10 (Reflow)
- Browser zoom tested up to 400% without loss of content or functionality
- A
@media (prefers-reduced-motion: reduce) block is included in every site's CSS to disable animations and transitions for users with vestibular sensitivity
- Body text is set at a minimum of 16px; line-height is 1.6 or greater for readability
3. Testing
How We Test
Every WebEaze site undergoes accessibility testing before and after launch. Our testing approach combines automated scanning with manual review.
Automated Tools
Manual Testing
- Keyboard-only navigation: every page navigated without a mouse, confirming tab order, focus visibility, and interactive element operability
- Screen reader testing with VoiceOver on macOS and Safari, verifying that headings, landmarks, images, forms, and interactive controls are correctly announced
- Mobile accessibility testing on iOS with VoiceOver enabled
- Cross-browser testing on current versions of Chrome, Firefox, Safari, and Edge
Target score: We aim for a Google Lighthouse Accessibility score of 90 or above on all delivered pages. Issues identified during testing are resolved before launch.
4. Third-Party Content
Third-Party Content
Our website and client sites may incorporate functionality from third-party providers, including scheduling tools, embedded media, analytics platforms, and CRM forms. We evaluate vendors for their accessibility practices and prefer those committed to WCAG conformance. However, we cannot fully guarantee the accessibility of third-party content.
Where third-party tools present accessibility barriers, WebEaze will make reasonable efforts to provide alternative methods for completing essential tasks. If you encounter a barrier from embedded third-party content, please contact us and we will work to assist you directly.
5. Known Limitations
Known Limitations
Despite our efforts, certain limitations may exist. The following are known and being actively addressed:
- Third-party form embeds: Embedded forms from HubSpot and similar platforms may not fully conform to WCAG 2.1 Level AA. We are working with vendors and, where necessary, providing alternative contact methods.
- Legacy pages: Pages developed prior to our current accessibility standards may contain gaps. These are remediated on a prioritized schedule, beginning with highest-traffic pages.
- Client-provided content: Images, PDFs, and documents provided by clients may not always meet accessibility guidelines. We provide written guidance and offer to remediate content as part of our ongoing plans.
- Video and audio: Some video content may lack captions or audio descriptions. All new multimedia produced by WebEaze includes appropriate text alternatives.
Ongoing assessment: Accessibility issues are triaged by user impact and technical feasibility. This statement is reviewed bi-monthly and updated when significant changes are made or new issues are resolved.
6. Technical Standards
Technical Specifications
WebEaze websites are built on the following technologies and standards for accessibility conformance:
- HTML5 with semantic landmark elements and valid markup (W3C validated)
- CSS3 with
prefers-reduced-motion support and fluid, responsive layouts
- JavaScript applied with progressive enhancement; core content and functionality do not require JavaScript to be accessible
- WAI-ARIA (Web Accessibility Initiative: Accessible Rich Internet Applications) roles, states, and properties for dynamic widgets
Our sites are designed to be compatible with the following assistive technologies:
- Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS and iOS), TalkBack (Android)
- Screen magnification software (tested up to 400% zoom)
- Speech recognition software (Dragon NaturallySpeaking and browser built-in controls)
- Keyboard-only navigation
- Switch access and alternative pointing devices (via proper keyboard focus management)
7. Report an Issue
Report an Accessibility Issue
We welcome feedback on accessibility. If you encounter a barrier or have a suggestion, please let us know. We respond to accessibility reports within 5 business days and aim to resolve verified issues within 30 days where technically feasible.
To help us investigate quickly, please include:
- The URL of the page where you encountered the issue
- A description of what happened and what you expected to happen
- The browser, operating system, and device you were using
- Any assistive technology in use (name and version if known)
Prefer to reach us directly? Email support@webeaze.io or call (347) 377-2408.
Submit a Report
8. Alternative Formats
Alternative Formats
Upon request, WebEaze will provide information in alternative accessible formats, including accessible versions of invoices, contracts, and service agreements. Send requests to support@webeaze.io and we will fulfill them within a reasonable timeframe.
If you require assistance completing any transaction or accessing any information on our website due to a disability, please contact us and we will provide reasonable accommodations.
9. Review and Approval
Review and Approval
This Accessibility Statement has been reviewed and approved by WebEaze Web Design management. Our accessibility program includes:
- Bi-monthly review of this statement, or more frequently when significant changes are made
- Accessibility checks integrated into our site build and launch checklist
- Monitoring of WCAG updates and evolving legal requirements (including ADA Title III guidance)
- Staff awareness of accessibility principles and best practices
Statement last reviewed: