Performance & Accessibility for Energy and Solar

Performance & accessibility for energy and solar is the work of making savings calculators, quote forms, project galleries and local service pages load quickly on ordinary phones and work for every customer, including people who use screen readers, keyboard navigation, magnification or voice control. In this industry the website is often the first place a homeowner meets a savings claim, and the calculator that produces that claim is frequently the slowest and least accessible thing on the site. Fixing it is partly an engineering job and partly a compliance job, because the numbers a calculator shows are representations the business is responsible for.

This guide is for marketing leads, founders and in-house web teams at residential solar installers, battery and storage sellers, heat pump and efficiency contractors, community solar programs and energy retailers. It leads with the rules and sign-offs that shape the work, because in solar the order matters: a calculator that is fast and accessible but shows unsubstantiated savings is still a problem, and a compliant calculator that many visitors cannot finish is a wasted asset. After the rules come the practical response: what to fix, in what order, how projects run, what drives cost, how to brief a supplier and how to prove the work paid off.

The positions here are practical, not legal. Where a section touches regulation, it says so, and it points you toward counsel for the final word on your own claims and your own states.

The rules that sit behind every solar savings number

Solar is a high-ticket consumer purchase sold largely on a promise about the future: lower bills, a payback period, protection from rate increases. That promise is exactly the kind of claim consumer protection law cares about. Before anyone touches load times or focus order, it helps to know which rules the site's content has to respect and who inside the business owns each one.

The Federal Trade Commission has acted against companies that made unsubstantiated solar savings claims, and its general position on advertising applies fully to the web: objective claims need a reasonable basis before they are made, not after a customer complains. A calculator output that says a homeowner will save a specific amount over twenty years is an objective claim. So is a banner that says a system will eliminate an electric bill. The substantiation has to exist first, and it has to match the assumptions the calculator actually uses.

Several states have solar-specific consumer protection statutes on top of general deceptive practices law. They vary, but they commonly deal with what must be disclosed in a sale, how financing and lease terms are presented, and cooling-off or cancellation rights. A site that serves several states may need state-aware disclosures near the calculator result and the quote form, not one generic footnote.

Federal tax credit representations must be accurate. Federal incentives for residential solar changed under legislation passed in 2025, and incentive rules can change again, so any page, calculator default or explainer that applies a credit needs checking against current law whenever the rules move. A calculator that still subtracts an incentive a homeowner can no longer claim is both a compliance problem and a trust problem, and it is one of the most common reasons a savings tool needs an urgent update.

Why accessibility is a sales problem for solar sites

The constraint that shapes everything in this industry is simple to state: calculators need labeled inputs and results that screen readers can announce, or some customers cannot use them at all. A homeowner who is blind, who navigates by keyboard because of a tremor, or who zooms the page to twice or four times its normal size for low vision is still a homeowner with a roof and an electric bill. If the calculator's inputs are unlabeled sliders, its result appears silently in a canvas chart, and its "Get my estimate" button is a styled div that cannot receive focus, that customer is out of the funnel before the sales conversation starts.

Solar buyers are homeowners of every age, including many older people. Age brings more people who use magnification, larger system text, or who simply struggle with low-contrast gray text and small tap targets. Nothing about that requires a special mode. It requires the ordinary success criteria of WCAG 2.2 at level AA applied carefully to the handful of templates that matter most.

What WCAG 2.2 adds that matters for calculators and quote forms

WCAG 2.2 is the current version of the guidelines, and several of its newer AA criteria land directly on solar funnels. Target Size (Minimum) asks for pointer targets of at least 24 by 24 CSS pixels or enough spacing around smaller ones, which matters for the plus and minus steppers many calculators use for bill amounts. Dragging Movements asks that anything done by dragging can also be done with a single pointer, which matters for bill sliders and for roof-drawing tools on satellite maps. Redundant Entry asks that information a user has already entered in the same process is either filled in again automatically or available to select, which matters when a multi-step quote form asks for the address twice. Accessible Authentication matters for customer portals where homeowners log in to track installation or monitor production. Focus Not Obscured matters when a sticky "Book a consultation" bar covers the field a keyboard user has just moved into.

Older criteria still carry most of the weight. Every input needs a programmatic label, not just placeholder text that disappears. Errors need to be identified in text and tied to the field. Results that update without a page reload need to be exposed as status messages so assistive technology announces them. Text needs a contrast ratio of at least 4.5 to 1 against its background for normal-sized text, and savings charts need text equivalents because a color-coded bar chart alone tells a screen reader user nothing.

No single tool or plugin settles this. An overlay widget alone does not make a site conformant, and no honest supplier will promise that a site is "ADA compliant" or safe from legal claims. What a good audit and remediation do is reduce real barriers, document conformance against WCAG 2.2 for the templates tested, and give your team a process to keep it that way. Audit timing depends mostly on how many distinct templates are in scope and how complex the calculator is.

The performance problem specific to energy and solar

Solar sites share a recognizable shape. There is a homepage with a large hero video of panels on a roof, a savings calculator, a project gallery of installed systems, dozens or hundreds of local service-area pages, financing explainers, and a quote form. Each of those has a typical performance failure.

The calculator built as a heavy app

Where it usually goes wrong: a savings calculator built as a heavy app that shows nothing until everything has loaded. The typical pattern is a single-page application bundle that also loads a mapping library, a charting library, an address autocomplete script and a financing widget before it paints a single input. On a mid-range phone over a cellular connection the visitor looks at a spinner or a blank panel for long enough to leave. Largest Contentful Paint is late because the main content is rendered by JavaScript, and Interaction to Next Paint suffers because the main thread is busy parsing and executing script when the visitor first taps.

The fix is structural rather than cosmetic. Render the first step of the calculator as plain HTML on the server, so the address or bill input is visible and usable immediately. Load the map only when the visitor reaches the step that needs it, and offer a text path for people who cannot or do not want to use a map. Draw the result chart after the numeric result is already on screen as text. This progressive approach helps speed and accessibility at the same time, because the text-first result is also the one a screen reader announces.

Project galleries that weigh more than the rest of the site

Installed-system photography sells, and drone shots of arrays are genuinely persuasive. They are also often uploaded straight from the camera at full resolution. Lighter project galleries come from generating responsive image sizes, serving modern formats such as AVIF or WebP with fallbacks, lazy loading everything below the first screen, declaring width and height so the layout does not shift as images arrive, and paginating or filtering a gallery by region or system type rather than loading every project on one page.

Hero video and rendering

Site visualization and rendering, such as a 3D view of panels placed on a customer's roof or an animated explainer of how net metering works, are strong deliverables in this industry. They need a still poster image that loads first, controls that are keyboard operable, a way to pause anything that moves for more than five seconds, and captions for any narration. If you are commissioning that kind of content, the teams producing it should hand over files already sized for the web rather than leaving compression to the end.

Local pages and third-party scripts

A strong local presence matters in solar because installers are licensed and scheduled by territory. Service-area pages multiply, and each one tends to carry the same chat widget, review carousel, call-tracking script and tag manager container. Individually each script seems small. Together they can delay interaction on every page. An audit should list every third-party script, what it is for, who owns it and whether it can load after the first interaction.

What to fix first: a priority order for solar sites

Most solar sites cannot fix everything at once, and they should not try. The order below follows where revenue and risk concentrate. It assumes the savings claims themselves have already been reviewed, because making an unsubstantiated number faster and easier to reach is not progress.

The quote form deserves more attention than it usually gets. Two details cause most failures. The first is required fields that are marked only with a red asterisk and no text explanation, which is covered in depth in how to get marking required fields right. The second is phone and ZIP code inputs with rigid masks that reject pasted values or confuse screen readers as characters are inserted; input masks and formatting, done properly explains the safer patterns.

Making a savings calculator fast, accessible and defensible

The calculator is where performance, accessibility and compliance meet, so it deserves its own design pass. A good solar calculator does three jobs: it gives the visitor a credible estimate, it qualifies the lead for the sales team, and it documents exactly what assumptions produced the number.

Inputs

Most calculators ask for an address, a monthly electric bill, and sometimes roof orientation, shading or utility. Each input needs a visible label and an accessible name that match. A bill slider should always have a paired text field so people can type a figure rather than drag. Utility selection works better as a searchable list with a proper combobox pattern than as a custom dropdown built from divs. Where the tool asks about shading, a short text description of each option beats an icon-only choice.

Results

Put the key result in text first: an estimated range, the assumptions used, and the date the assumptions were last reviewed. Expose the result container as a live region or status message so its content is announced when it changes. Then add the chart as a visual supplement with its own text summary. Showing a range rather than a single precise figure is often easier to substantiate, and it reads as more honest to a skeptical buyer.

Assumptions and disclosures

Put the assumptions next to the result, not behind a modal that traps focus. Typical assumptions include utility rate, assumed annual rate change, system size, production estimate source, degradation and any incentive applied. If the calculator applies a tax credit or local rebate, name it and state that eligibility depends on the homeowner's situation. When incentive rules change, this is the section that must be updated first, and the calculator logic with it.

Qualification without friction

Lead forms that qualify are one of the deliverables that work in this industry, and they can be accessible too. Ask qualifying questions (homeownership, roof age, approximate bill) as simple radio groups with a fieldset and legend, one topic per step, with a visible progress indicator that is also available as text. Avoid time limits on steps; if a session must expire, warn the visitor and let them extend it.

A worked example: measuring calculator completion before and after

The following is an illustrative example with round numbers chosen for clarity, not results from a real client. It shows how a solar marketing lead might measure the effect of calculator work.

Suppose the calculator page receives 6,000 visits in a month. Of those, 2,400 visitors enter a bill amount, which is 400 in every 1,000 visits. Of the 2,400 who start, 720 reach the result step, which is 300 in every 1,000 starters. Of the 720 who see a result, 144 submit the quote form, which is 200 in every 1,000 result viewers. End to end, that is 144 quote requests from 6,000 visits, or 24 in every 1,000.

The audit finds three problems: the first step does not appear until the full bundle loads, the bill slider has no text input and cannot be operated with a keyboard, and the result is not announced. After remediation, suppose the monthly traffic is the same. If starts rise to 3,000 (500 in every 1,000 visits) because the first step appears immediately, and completion among starters rises to 1,050 (350 in every 1,000) because the slider and result now work for everyone, and form submission stays at 200 in every 1,000 result viewers, then quote requests become 210. That is 66 more requests per month from the same traffic, or 35 in every 1,000 visits end to end.

The point of the example is the method, not the numbers. Instrument each step, record a baseline for a full cycle before changing anything, make the changes, and compare over a comparable period. Solar demand is seasonal, so compare like with like: the same weeks year on year if you have the data, or run the old and new versions side by side if you do not. The person who signs off the work should be a marketing lead who sees how many visitors finish the calculator, because that single number captures speed, usability and trust at once.

Seasonality, incentive changes and when to schedule the work

Performance and accessibility reviews in solar are best scheduled before busy seasons and whenever incentive changes require calculator updates. Demand tends to rise when homeowners feel bill pressure and when installation weather is good, and it can spike sharply before an incentive deadline. The worst time to discover that the calculator falls over on phones is the week traffic doubles.

Plan for three triggers. The first is a scheduled pre-season review, a few weeks before your historically busiest period, covering Core Web Vitals on the key templates and a focused accessibility pass on the calculator and quote form. The second is an incentive or tariff change: when federal, state or utility programs change, the calculator's assumptions, the explainer pages and any banner claims all need review together, and the regression test should cover accessibility as well as the arithmetic. The third is any redesign or new vendor script, such as a new chat tool or financing widget, which should not ship without a performance budget check and a keyboard and screen reader test.

Incentive changes are also when content teams write new explainer pages quickly. Those pages need proper heading structure, real table markup for comparisons, and plain-language summaries. Coordinating with whoever owns content strategy for energy and solar means the accessibility requirements are in the template before the copy is written, not retrofitted after launch.

How a performance and accessibility project runs

A solar project usually runs in five stages. The length of each depends on the number of templates, the complexity of the calculator and how quickly the compliance review can turn around wording changes, so the stages below describe sequence rather than a fixed schedule. More detail on how the work is scoped and checked is on how the work runs, what it costs and how we check it.

1. Scoping. Agree which templates are in scope, typically the calculator, the quote form, a representative local page, the gallery, the financing explainer and the homepage. List the third-party scripts and name the owner of each claim that appears on those pages.
2. Baseline. Collect field data for Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift where enough real-user data exists, and lab data on throttled mobile profiles for the rest. Record calculator funnel numbers for the baseline period.
3. Audit. Test the in-scope templates against WCAG 2.2 AA with automated tools, manual keyboard testing, and screen reader testing on at least one desktop and one mobile combination. Profile the calculator's script cost and the gallery's image weight.
4. Remediation. Fix issues in priority order, starting with anything that blocks a task entirely. Changes to the calculator's wording or assumptions go through the claim approver before release.
5. Verification. Retest the fixed templates, compare funnel and Core Web Vitals data against the baseline over a comparable period, and hand over a short maintenance checklist.

Where possible, include people with disabilities in testing the calculator and form, because automated tools catch only part of the problem. A practical guide to testing accessibility with real users covers how to recruit and run those sessions without a large budget.

What drives the cost of this work for solar companies

Performance & accessibility work starts at $1,200.00 per audit with us. That is a starting price, and the final number depends on scope. The pricing page puts every rate next to what the US market typically charges, and a quote turns the range into one number for your volume.

The factors that move the cost for a solar site are predictable:

• Calculator complexity. A single-step bill-based estimate is far simpler to audit and fix than a multi-step tool with satellite roof drawing, financing comparisons and utility-specific tariffs.
• Number of distinct templates. Two hundred service-area pages built from one template count as one template for audit purposes; five differently built landing page systems count as five.
• Third-party dependencies. Financing widgets, chat tools and scheduling embeds that you do not control may need vendor escalation or replacement rather than a code fix.
• Platform constraints. A calculator built in a page builder with limited control over markup can be harder to fix than one in custom code.
• Compliance review cycles. If calculator wording must be approved by counsel, each round of changes adds coordination time.
• Remediation versus audit. An audit finds and documents issues; fixing them is separate work, priced by the size of the fix list.

For a broader view of what moves these budgets, see how much accessibility remediation costs. When you are ready to price your own site, the pricing page lists the rates and a quote gives you a single figure for your scope.

How to brief a supplier for solar performance and accessibility work

A good brief saves a week of discovery calls. For solar, it should put the compliance context on the table at the start, because a supplier who does not know which words are approved will either stall or change things they should not.

When comparing suppliers, look for evidence of manual testing with assistive technology, not just automated scan reports, and ask how they handle calculator logic they did not write. How to choose a web accessibility agency has a fuller list of questions. If you want to see how a supplier works before committing, you can send a couple of your own files for a trial review.

Measuring results after launch

Results in this industry should be measured in three layers: technical health, task completion and sales quality.

Technical health

Track the Core Web Vitals on the calculator, quote form and a representative local page. Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024, and it is the metric most likely to expose a heavy calculator, because it measures how quickly the page responds to every tap and keystroke, not only the first. Google's published "good" thresholds are a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less, assessed so that at least three in every four real page loads meet the threshold. Check both field data, which reflects real visitors, and lab data on throttled mobile profiles, which lets you test changes before they ship.

Task completion

The single most useful number is calculator completion: how many visitors who start the calculator reach a result. Pair it with form submission rate after a result, and with error rate per field if your analytics can capture validation failures. A rise in errors on one field after a change usually points to a labeling, masking or validation problem.

Sales quality

Faster and more accessible funnels should not produce worse leads. Ask sales whether the share of qualified consultations holds steady. If the calculator shows ranges and clear assumptions, fewer prospects should arrive with expectations the proposal cannot meet, which also lowers the risk that a disappointed customer complains about the savings they were shown.

Keeping it fixed

Accessibility and performance regress quietly. A new chat script, a redesigned slider or an updated gallery plugin can undo months of work. Build checks into your release process: automated accessibility tests in the build, a performance budget for the calculator bundle, and a manual keyboard and screen reader check before any calculator change ships. Teams that release often should make these checks part of the definition of done for every sprint. If broader conversion work is planned, keep it coordinated with the conversion team so A/B tests do not ship inaccessible variants.

Related

Other work for energy and solar

• Motion Graphics & Animation for Energy and solar
• 3D Design & Development for Energy and solar
• Web Design & Development for Energy and solar
• SEO Services for Energy and solar

Performance & accessibility in other sectors

• Performance & Accessibility for Fitness and wellness
• Performance & Accessibility for Regulated retail and cannabis
• Performance & Accessibility for E-commerce and DTC brands
• Performance & Accessibility for Furniture and home goods

More on performance & accessibility

• How the work runs, what it costs and how we check it
• How to Get Marking Required Fields Right
• Input Masks and Formatting, Done Properly

Trying us out

The quickest way to find out if we are any good for you is to send a couple of your own files and look at what comes back. It is free and there is no card involved. If the scope is already clear, ask for a fixed price instead.