Our Website Accessibility Commitment
ConcreteSwift is committed to making its concrete estimating tools and educational content useful to a broad audience. The site includes project calculators for slabs and patios, footings and piers, walls, columns and beams, together with concrete bag estimates, ready-mix cost estimates, unit conversion tools, articles, comparison guides, tables, formulas, diagrams and policy pages. We recognize that people interact with those resources in different ways, and that a feature that works well with a mouse or on a large monitor may create a barrier for someone using only a keyboard, a screen reader, browser zoom, a mobile device or another assistive technology.
Our goal is to design and maintain content so that important information does not depend only on color, pointer movement, hover effects, tiny text or a single visual format. Where practical, interactive controls use native HTML elements, headings follow a logical structure, tables are placed in horizontally scrollable wrappers on smaller screens, and responsive layouts reflow instead of forcing users to zoom out.
Accessibility Standard We Aim to Follow
Our accessibility work is guided primarily by the Web Content Accessibility Guidelines (WCAG) 2.2 published by the World Wide Web Consortium (W3C). WCAG organizes accessibility around four principles: content should be perceivable, operable, understandable and robust. We aim for Level AA where reasonably achievable across our own templates, calculators and editorial content.
WCAG is a technical accessibility standard, not a guarantee that every individual will experience a website in exactly the same way. Real accessibility also depends on browsers, operating systems, assistive technology, user settings, content quality and third-party services. For that reason, we treat conformance work and direct user feedback as complementary rather than interchangeable.
Accessibility is strongest when technical standards are paired with practical testing and a clear way for users to report barriers.
Accessibility Measures We Use
Keyboard Access
Interactive controls are intended to be reachable and usable without requiring a mouse, with visible focus where practical.
Readable Text
We use responsive type sizing, strong foreground/background contrast and layouts that support zoom and smaller screens.
Semantic Structure
Headings, buttons, lists, labels, links and tables are structured to make page relationships easier to understand.
Responsive Tables
Wide conversion and cost tables are placed inside scrollable wrappers so mobile users can access every column.
Additional Practices
- We try to provide descriptive page titles, headings and link text so users can understand context before activating a link.
- We avoid relying on color alone to communicate essential calculator results, validation states or instructions.
- Calculator fields are intended to have visible text labels and understandable input instructions.
- Validation messages are written in text rather than being represented only by a border color.
- Decorative visual elements are kept separate from essential content where practical, while important information is also described in text.
- Layouts are designed to reflow for tablets and phones, with overflow protection for long unit labels, values and figure notes.
- FAQ controls use buttons and update their expanded/collapsed state for assistive technology.
Accessibility Support Across Common Website Features
ConcreteSwift’s main calculator currently supports Slab & Patio, Footing & Pier, Wall, and Column & Beam workflows. The site also presents cubic-yard and cubic-foot results, approximate bag quantities, optional ready-mix material cost and a downloadable result PDF. We treat those calculator inputs, controls, results and supporting explanations as core accessibility priorities.
Where a downloadable result is offered, the information shown on the web page remains the primary accessible source. If a generated PDF is difficult to use with your assistive technology, you can use the on-page result or contact us for help understanding the same estimate in another format.
| Website Feature | Accessibility Approach | What Users Can Expect | Potential Limitation |
|---|---|---|---|
| Calculators | Visible labels, standard inputs, text results and validation messages | Keyboard entry and readable result text | Some browser/device combinations may announce dynamic results differently |
| Conversion Tables | HTML tables inside horizontal scroll wrappers | All columns remain reachable on narrow screens | Very wide tables may require horizontal scrolling |
| FAQ Accordions | Button controls with expanded/collapsed state | Keyboard activation and structured answer content | Older assistive technologies may handle dynamic state differently |
| Figures & Diagrams | Supporting text explains the main concept | Critical guidance should not depend only on the image | Some complex visual relationships may be easier to understand visually |
| External Links | Descriptive link text where practical | Users can identify the destination or source | We do not control accessibility of third-party websites |
| Mobile Layout | Responsive grids, wrapping text and scalable cards | Content should reflow without desktop-only assumptions | Browser text-enlargement settings can affect some dense visual layouts |
Browsers, Devices and Assistive Technology
ConcreteSwift is designed for current mainstream browsers and responsive use on desktop, tablet and mobile devices. Our pages are intended to remain usable with common browser zoom, keyboard navigation and platform accessibility settings. Because assistive technologies interpret web content through combinations of browser engines, operating systems and accessibility APIs, behavior can vary across environments.
We do not maintain an exhaustive certification matrix for every browser, screen reader, magnifier, switch device, speech-input tool or operating-system version. If a ConcreteSwift page behaves unexpectedly in your setup, please tell us what page or calculator you were using, what you were trying to do, and—if you are comfortable sharing it—the browser, device or assistive technology involved. That information can help us reproduce and prioritize the barrier.
Known and Potential Accessibility Limitations
We continue to improve the site and cannot guarantee that every page, archived page, embedded service or external resource is free of accessibility barriers. The following areas may require additional attention depending on the page and technology being used.
Complex Visual Figures
Some diagrams use spatial relationships to explain measurements, layers or conversions. We aim to provide equivalent explanatory text, but the visual presentation may still offer context that is difficult to reproduce perfectly in plain text.
Third-Party Content
External websites, embedded tools, analytics, advertising technology or services provided by third parties may not follow the same accessibility practices as our own templates.
Older or Legacy Pages
Pages created under an older template may not yet include every accessibility enhancement used on newer pages. We may prioritize remediation based on usage, severity and user reports.
Alternative Access
If a barrier prevents you from accessing important information, contact us and describe the content you need. We will try to provide the information in an accessible alternative format or explain it another way.
Third-Party Websites, Services and External Sources
Our articles may link to manufacturers, standards organizations, government agencies, professional associations, technical publications and other external resources. Some pages may also rely on third-party infrastructure or services. We cannot control the accessibility, privacy practices, content structure or ongoing availability of websites that we do not operate.
When we choose authoritative external sources, we try to use descriptive link text and clearly identify the destination. If an external source creates an accessibility barrier, you may contact us for help locating the essential information in another form, but we cannot guarantee that we can reproduce copyrighted or proprietary third-party material.
How to Report an Accessibility Problem
ConcreteSwift welcomes accessibility feedback. If you have difficulty using a calculator, selecting a project type, entering dimensions, reading a result, downloading a result PDF, reading a table, understanding a figure, navigating by keyboard, accessing content with a screen reader, or completing another task on the site, please use our Contact Us page.
To help us investigate, please include as much of the following information as you reasonably can:
- The URL or title of the page where you encountered the barrier.
- A short description of what you were trying to do.
- What happened and what you expected to happen.
- The device and browser you were using, if known.
- The assistive technology involved, if relevant and if you are comfortable sharing it.
- The format or alternative access you need if you are requesting an accommodation.
We cannot promise that every issue can be fixed immediately, but specific reports are valuable inputs to our accessibility work.
Requesting Information in Another Format
If an accessibility barrier prevents you from obtaining information from ConcreteSwift, contact us and tell us what information you need. Depending on the content, we may be able to provide a plain-text explanation, restate calculator instructions, summarize a table, explain a diagram, or provide another reasonable alternative.
For ConcreteSwift calculators, it helps to include the project type, the values you were trying to enter, and the result you need—for example cubic feet, cubic yards, bag quantity or a ready-mix material-cost estimate. For a table or article, identify the heading or topic. This allows us to focus on the requested information rather than requiring you to troubleshoot the technical barrier yourself.
How We Review Accessibility
Accessibility review can include both automated and manual checks. Automated tools can identify certain issues—such as missing labels, some contrast failures, duplicate IDs or structural problems—but they cannot determine whether every label is meaningful, whether keyboard order is logical, whether a diagram has an adequate text explanation, or whether a calculator workflow makes sense to a person using assistive technology.
For that reason, our process may include source-code review, responsive testing, keyboard navigation checks, focus-state review, semantic heading checks, table structure review, content editing and investigation of user reports. We also try to improve shared components so that one fix can benefit multiple calculators and guides rather than patching individual pages only.
Accessibility Is Part of Ongoing Site Maintenance
New ConcreteSwift calculators, conversions and guides can introduce new interactions or data presentations. As templates evolve, we may update older content to use improved accessibility patterns. We also monitor issues such as overflowing hero text, cramped mobile figures, very long unit labels and wide data tables because these can become practical barriers even when they are not obvious on a large desktop screen.
Accessibility in Editorial and Calculator Content
Clear writing is part of accessibility at ConcreteSwift. We aim to use descriptive headings, explain formulas in words, define units, avoid unexplained abbreviations where practical, and provide examples that help users understand how a result was produced. A calculator should not be a “black box” when the underlying formula can be explained clearly.
For conversion pages, we typically provide the conversion factor, formula, examples and a reference table. For ConcreteSwift project calculators, we explain assumptions such as ordering allowance, bag yield, concrete thickness and user-entered ready-mix pricing. Our main concrete calculator also presents cubic feet, cubic yards, approximate bag quantities and optional material cost, with project-specific workflows for slabs and patios, footings and piers, walls, columns and beams. When an estimate depends on product-specific information, we encourage users to check the manufacturer label rather than presenting one universal number as exact.
You can learn more about how we create and maintain content through our Editorial Policy, Disclaimer, Terms of Use and Privacy Policy.
Accessibility Standards and Legal Context
Accessibility laws and obligations vary by organization type, jurisdiction and use case. In the United States, the U.S. Department of Justice publishes guidance about web accessibility and the Americans with Disabilities Act (ADA). Federal agencies and certain federal digital content are also subject to Section 508 requirements. These frameworks do not necessarily apply to every private website in the same way.
This Accessibility Statement describes ConcreteSwift’s website practices and goals. It is not legal advice, a certification, or a representation that the site satisfies every accessibility law, regulation or technical standard that could apply in every jurisdiction. If you need legal guidance about accessibility obligations, consult a qualified professional.
Related Website Policies and Resources
Accessibility at ConcreteSwift intersects with content quality, privacy, disclaimers and user support. You may also want to review our Privacy Policy, Terms of Use, Editorial Policy, Disclaimer and Contact Us page.
If you are here because you could not use a specific tool, start with the ConcreteSwift Concrete Calculator, or browse related resources such as the Concrete Slab Calculator, Concrete Bags to Cubic Feet converter and other concrete conversion guides. If one version of a tool is inaccessible to you, tell us what calculation you need and we will try to help provide the information another way.
Accessibility References
We use recognized accessibility resources to guide our approach. The external references below are provided for transparency and further reading.
- W3C — Web Content Accessibility Guidelines (WCAG) 2.2
- W3C Web Accessibility Initiative — WCAG Overview
- W3C WAI — Developing an Accessibility Statement
- U.S. Department of Justice — Guidance on Web Accessibility and the ADA
- Section508.gov — Guide to Accessible Web Design & Development