Accessibility Statement

ArcAnswer, a product of Birchwood Group LLC

At a glance: ArcAnswer is committed to being usable by everyone, including people who rely on assistive technologies. We design with accessibility in mind, aim to align with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, test our work, and welcome your feedback so we can keep improving.

Introduction

Birchwood Group LLC ("Birchwood Group," "we," "us," or "our") builds ArcAnswer, a premium, AI-powered Chrome extension that audits web pages for AI search readiness and produces one-click, copy-ready fixes for engines such as ChatGPT, Claude, Gemini, and Perplexity. We believe that great software should work for everyone, regardless of ability, device, or the assistive technology someone depends on.

This Accessibility Statement describes our commitment to inclusive design, the standards we work toward, the accessibility features built into ArcAnswer and our website, how we test, the limitations we are aware of, and how you can reach us if something does not work for you. Accessibility is not a one-time checkbox for us; it is an ongoing practice woven into how we design, build, and improve the product.

Table of Contents

1. Executive Summary
2. Purpose
3. Scope
4. Definitions
5. Our Accessibility Commitment
6. Inclusive Design Principles
7. WCAG Alignment
8. Keyboard Navigation
9. Screen Reader Support
10. Color Contrast and Visual Design
11. Text Scaling and Zoom
12. Responsive Design
13. Accessibility Testing
14. Known Limitations
15. Ongoing Improvements
16. User Responsibilities
17. Company Responsibilities
18. Feedback Process
19. Examples
20. Frequently Asked Questions
21. Accessibility Contact
22. Future Improvements
23. Conclusion

Executive Summary

ArcAnswer aims to conform to WCAG 2.1 Level AA, the widely recognized international standard for digital accessibility. In practice, this means we design the extension and website to be operable by keyboard, understandable to screen readers, readable at high zoom levels, and legible for people with low vision or color-vision differences.

We are transparent about the fact that accessibility is a continuous journey. Some areas may fall short of our goals at times, and when they do, we want to hear about it and fix it.

Purpose

The purpose of this statement is to communicate our accessibility commitments clearly, to document the standards and practices we follow, and to give people who encounter barriers a straightforward way to reach us. It also reflects our belief that accessible design produces a better product for everyone, not only for people with disabilities.

Scope

This statement applies to:

• The ArcAnswer browser extension, including its popup interface and generated reports.
• The ArcAnswer marketing website operated by Birchwood Group LLC.
• Documentation and support materials we publish.

It does not cover third-party websites you audit with ArcAnswer, which are controlled by others, or third-party services with their own accessibility practices.

Definitions

Our Accessibility Commitment

We commit to making ArcAnswer usable by the widest possible range of people. Concretely, this means:

• Treating accessibility as a requirement, not an afterthought.
• Targeting WCAG 2.1 Level AA across the extension and website.
• Testing with real assistive technologies, not only automated tools.
• Listening to feedback and prioritizing fixes for barriers people report.
• Improving continuously as standards, browsers, and assistive technologies evolve.

Note: Accessibility benefits everyone. Clear structure, good contrast, and keyboard support make software easier and more pleasant to use for all users, including people in bright sunlight, on small screens, or working hands-free.

Inclusive Design Principles

Our design process is guided by principles drawn from established inclusive-design practice.

1. Perceivable. Information and controls are presented in ways people can perceive, including through text alternatives and sufficient contrast.
2. Operable. Every function can be operated with a keyboard and does not require precise timing or fine motor control.
3. Understandable. Interfaces behave predictably, use plain language, and explain errors clearly.
4. Robust. Content works reliably across browsers and with current assistive technologies.
5. Equitable. We avoid designs that exclude, and we seek solutions that serve the broadest range of people.
6. Flexible. We support different ways of interacting, such as keyboard, mouse, touch, and voice, where feasible.

WCAG Alignment

ArcAnswer targets conformance with WCAG 2.1 Level AA. The table below summarizes how our work maps to the four WCAG principles.

While Level AA is our target, we adopt Level AAA techniques where they are practical and beneficial. Conformance can vary across features and over time as we ship updates, which is why we test continuously and welcome reports of any gaps.

Keyboard Navigation

Many people navigate without a mouse, whether by choice or necessity. ArcAnswer is designed to be operable using a keyboard alone.

• Interactive elements, such as buttons, tabs, and links, are reachable in a logical order using the Tab key.
• The currently focused element is shown with a visible focus indicator, so you always know where you are.
• Actions can be triggered with standard keys, such as Enter and Space.
• We avoid keyboard traps that would prevent you from moving away from a component.

Best practice: If you rely on the keyboard, you can move through the extension and website using Tab and Shift+Tab, and activate controls with Enter or Space. If you find a place where focus behaves unexpectedly, please tell us.

Screen Reader Support

We design ArcAnswer to communicate clearly with screen readers such as NVDA, JAWS, VoiceOver, and TalkBack.

• We use semantic structure, including proper headings and landmarks, so screen reader users can navigate efficiently.
• Interactive controls have descriptive labels, so their purpose is announced clearly. For example, our repeated "Add to Chrome" calls-to-action carry distinct labels that identify their context.
• Non-text content, such as icons and product visuals, includes appropriate text alternatives or is marked as decorative when it carries no additional meaning.
• Status changes and important messages are conveyed in ways assistive technologies can announce.

Note: Screen readers interpret content differently across versions and browsers. We test with common combinations, and we appreciate reports about any specific setup where something is unclear.

Color Contrast and Visual Design

Legibility matters for everyone, and especially for people with low vision or color-vision differences.

• Text and essential interface elements are designed to meet or exceed WCAG AA contrast ratios.
• We do not rely on color alone to convey meaning; we pair color with text, icons, or patterns.
• Our interface uses generous spacing, clear typography, and a consistent visual hierarchy to reduce cognitive load.

Example: In our pricing and call-to-action areas, we use a deeper shade of our brand color behind white text specifically so the contrast meets accessibility thresholds, rather than choosing a lighter tone that would look brighter but read poorly.

Text Scaling and Zoom

People often enlarge text or zoom the page to read comfortably.

• Content is designed to remain usable when text is enlarged or the page is zoomed, without loss of essential content or functionality.
• Layouts reflow rather than forcing horizontal scrolling at higher zoom levels wherever possible.
• We avoid fixing text at sizes that cannot be adjusted.

Best practice: Use your browser's zoom (often Ctrl and Plus, or Command and Plus) or your operating system's text-size settings to enlarge content to a comfortable level.

Responsive Design

ArcAnswer's website and interfaces are built to adapt to different screen sizes and orientations, from large desktop monitors to tablets and mobile devices. Responsive design supports accessibility by ensuring content remains readable, controls remain reachable, and layouts remain coherent regardless of the device or the amount of zoom applied. This benefits people using magnification, small screens, or non-standard viewports.

Accessibility Testing

We combine multiple testing methods because no single method catches everything.

Automated tools are helpful but limited; they typically catch only a portion of potential issues. That is why manual and assistive-technology testing are central to our process.

Known Limitations

In the spirit of transparency, we acknowledge that accessibility is never fully finished, and some limitations may exist at any given time.

• Some newly shipped features may not yet be fully tested with every assistive technology.
• Product visuals that reconstruct the extension interface are provided with descriptive alternatives, but complex visualizations can still be challenging to convey fully in text.
• Third-party components or services we rely on may have their own accessibility characteristics outside our direct control.
• Browser and assistive-technology combinations vary, and behavior can differ across setups.

Where we identify a limitation, we prioritize a fix and, when helpful, offer an alternative way to accomplish the task.

Warning: If a limitation prevents you from completing something important, please contact us. We will work with you to find a solution and to fix the underlying issue.

Ongoing Improvements

Accessibility is a continuous commitment. We:

• Review accessibility as part of our design and release process.
• Re-test key flows after significant updates.
• Track and prioritize accessibility issues reported by users.
• Keep pace with evolving standards, such as newer versions of WCAG.
• Educate our team so accessibility is considered from the start.

User Responsibilities

While the responsibility for accessibility rests primarily with us, you can help us help you:

• Keep your browser, operating system, and assistive technology reasonably up to date, since compatibility improves over time.
• Tell us the specific browser, assistive technology, and steps involved when you report an issue, so we can reproduce and fix it quickly.
• Let us know which alternative formats or accommodations would help you most.

Company Responsibilities

Birchwood Group LLC commits to:

• Design and build with accessibility as a core requirement.
• Target WCAG 2.1 Level AA and improve toward it continuously.
• Test with real assistive technologies, not just automated tools.
• Respond to accessibility feedback promptly and respectfully.
• Provide alternative ways to accomplish tasks when a barrier exists.

Feedback Process

Your feedback is one of the most valuable inputs to our accessibility work. If you encounter a barrier or have a suggestion, here is how the process works.

1. Reach out. Email us at accessibility@bwg.llc with a description of the issue.
2. Include details. Tell us the page or feature, your browser and assistive technology, and what happened versus what you expected.
3. We acknowledge. We aim to acknowledge accessibility reports promptly.
4. We investigate and respond. We work to reproduce the issue, propose a solution or workaround, and keep you informed.
5. We follow up. We track the fix and let you know when it ships.

Note: If you need help completing a task while we work on a fix, ask us. We would rather help you directly than leave you stuck.

Examples

Example 1 — Keyboard-only navigation. A user who cannot use a mouse tabs through the extension's tabs and buttons, sees a clear focus outline at every step, and activates the scan with the Enter key.

Example 2 — Screen reader labels. A screen reader user hears distinct labels for each "Add to Chrome" button, so they understand which plan each one refers to, rather than hearing the same phrase repeated with no context.

Example 3 — Reporting a barrier. A user finds that a particular control is hard to reach with their screen reader. They email accessibility@bwg.llc with their setup and steps. We reproduce the issue, ship a fix, and confirm it with them.

Frequently Asked Questions

Which accessibility standard does ArcAnswer follow? We target WCAG 2.1 Level AA across the extension and website.

Can I use ArcAnswer with a keyboard only? Yes. Interactive elements are reachable and operable by keyboard, with a visible focus indicator.

Does ArcAnswer work with screen readers? Yes. We use semantic structure and descriptive labels, and we test with common screen readers.

What if I find an accessibility problem? Email accessibility@bwg.llc with details, and we will investigate, respond, and work toward a fix.

Is your accessibility work ever finished? No. Accessibility is an ongoing commitment that we revisit with every significant update.

Do you support text scaling and zoom? Yes. Content is designed to remain usable when enlarged or zoomed.

Accessibility Contact

• Accessibility feedback: accessibility@bwg.llc
• General support: support@bwg.llc
• Company: Birchwood Group LLC, State of Florida, United States
• Websites: https://arcanswer.com and https://bwg.llc

We welcome your questions, suggestions, and reports, and we treat them as a priority.

Effective Date, Version, and Last Updated

• Effective Date: July 19, 2026
• Version: 2.0
• Last Updated: July 19, 2026

Future Improvements

Looking ahead, we intend to keep raising our accessibility bar. Planned directions include expanding assistive-technology test coverage, refining descriptive alternatives for complex product visuals, incorporating newer WCAG success criteria as they mature, and continuing to educate our team so accessibility is designed in from the first sketch. We will update this statement as our practices and capabilities evolve.

Conclusion

Accessibility is a measure of respect: it says that everyone deserves to use the tools that help them do their best work. We are proud of the accessibility built into ArcAnswer, honest about the fact that there is always more to do, and grateful to the users who help us improve by sharing their experiences. If ArcAnswer ever does not work for you, tell us, and we will make it right. Thank you for helping us build software that includes everyone.