Our Commitment
Masonic Web Design is committed to conforming to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. These guidelines, published by the World Wide Web Consortium (W3C), define how to make web content more accessible to people with disabilities — including those with visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.
We believe that accessibility is not a checkbox — it is an expression of respect for all people who visit our site and for the organizations we serve. Freemasonry teaches the inherent dignity of every person; our digital work should reflect that value.
Standards We Follow
This website targets conformance with WCAG 2.2, Level AA. We strive to meet all Level A and AA success criteria. Key standards include:
- Perceivable — Content is presented in ways users can perceive, including text alternatives for non-text content, captions for media, and sufficient color contrast.
- Operable — All functionality is available via keyboard, there are no seizure-inducing flashes, and users have adequate time to interact with content.
- Understandable — Text is readable and understandable, pages operate predictably, and forms provide clear input assistance.
- Robust — Content can be reliably interpreted by assistive technologies, including screen readers and browser extensions.
Measures Taken
We have taken the following concrete steps to improve accessibility on this website:
- Semantic HTML5 elements used throughout (landmarks, headings, lists, tables)
- Single H1 per page with logical heading hierarchy (H2, H3, etc.)
- Skip navigation link to bypass repeated header content
- All interactive elements are keyboard navigable
- Visible focus indicators on all focusable elements
- Color contrast ratios meet or exceed WCAG 2.2 AA minimums (4.5:1 for normal text)
- Descriptive alt text on all meaningful images; decorative images use empty alt text
- Form inputs have associated labels; error messages are descriptive and accessible
- ARIA attributes used where native HTML semantics are insufficient
- Prefers-reduced-motion media query honored — animations are disabled for users who prefer reduced motion
- Mobile-responsive design that supports browser zoom up to 200% without horizontal scrolling
- No content conveys meaning through color alone
- No auto-playing audio or video
- Page language declared in HTML (
lang="en")
How We Test
Our accessibility testing process combines automated tooling with manual review:
- Automated audits — We run Lighthouse, axe-core, and WAVE scans on all pages during development and prior to launch.
- Keyboard navigation testing — All interactive elements and workflows are manually tested using keyboard-only navigation (Tab, Shift+Tab, Enter, Space, Escape, Arrow keys).
- Screen reader testing — Key page flows are tested with VoiceOver (macOS/iOS) and NVDA (Windows) to verify that content is announced correctly.
- Contrast checking — All color combinations are verified against WCAG contrast requirements using tooling such as the WebAIM Contrast Checker.
- Mobile and zoom testing — Pages are tested at 320px viewport width and 200% browser zoom.
Known Limitations
While we strive for full WCAG 2.2 AA conformance, accessibility is an ongoing effort. We actively monitor for and address any issues identified through testing or user reports. If you encounter a barrier on this site, please let us know — see the section below.
Reporting Accessibility Issues
If you experience any accessibility barriers on this website, we want to hear about it. Please contact us at:
Email: dan@rosecross.sh
Please include:
- The URL of the page where you encountered the issue
- A description of the barrier you experienced
- The assistive technology or browser you were using (if applicable)
We will respond within 2 business days and work to resolve reported issues in a timely manner.
Ongoing Improvement
Accessibility is not a one-time effort. We are committed to:
- Regular accessibility audits as content and features change
- Keeping our knowledge of WCAG standards current
- Incorporating accessibility requirements into every new project
- Promptly addressing user-reported accessibility barriers
This statement was last reviewed: March 2026