The ADA Website Deadline Is Real: What Wisconsin Villages and Districts Need to Know Before April 2028
The short version: The ADA website deadline is real. Under a federal rule finalized in April 2024, every state and local government website in the country must meet WCAG 2.1 Level AA accessibility standards. Governments serving 50,000 or more people must comply by April 26, 2027. Smaller communities and all special districts, including school, fire, sanitary, library, and water districts, have until April 26, 2028. There is no small-town exemption.
What is the new ADA website rule?
The Americans with Disabilities Act has always required government services to work for people with disabilities. For decades that mostly meant physical things like wheelchair ramps and accessible parking. In April 2024, the Department of Justice made it official for the web: government websites and mobile apps are services too, and they now have a named technical standard, WCAG 2.1 Level AA.
The DOJ originally set deadlines for 2026 and 2027, then extended both by one year in April 2026 after hearing from school districts and small communities that the timelines were not realistic. The extension moved the ADA website deadline back one year. It did not change the requirement.
When is the ADA website deadline?
- April 26, 2027 for state and local governments serving 50,000 or more people
- April 26, 2028 for everyone smaller, plus all special district governments: school, fire, sanitary, library, and water districts
Most Wisconsin villages, towns, and districts fall in that second group, so the date that matters for most of our region is April 26, 2028. That sounds far away. For reasons covered below, it is not.
What does WCAG 2.1 Level AA actually require?
Stripped of the jargon, an accessible government website means:
- The site works with a screen reader
- Everything can be used with a keyboard alone, no mouse required
- Text has enough color contrast to actually read
- Images have alt text describing what they show
- Videos have captions
- Forms have proper labels so people know what each field is for
The part that bites hardest: PDFs
Villages and districts post agendas, minutes, budgets, and permit forms as scanned PDFs. A scanned PDF is a picture of text. A screen reader gets nothing from it. Under the rule, that is a failure on every single document, and a typical municipal website has hundreds of them.
Document remediation is the biggest chunk of the work and the reason this is not a one-afternoon fix. The earlier a community starts working through its document library, the more manageable it is.
What happens if a community misses the deadline?
It is not a fine that shows up in the mail. It is a complaint filed with the DOJ, or a private lawsuit. Either way, the community ends up fixing everything anyway, on someone else’s timeline, with legal fees on top. Fixing it early is simply cheaper.
Is there an exemption for small towns?
No. A village of 400 residents is held to the same standard as Milwaukee. Only the compliance date differs. There are a few narrow exceptions in the rule, such as archived content that is no longer in use, but there is no exemption based on population.
Frequently asked questions
Who enforces the ADA website rule?
The Department of Justice; official guidance is at ADA.gov. Enforcement comes through complaints filed with the DOJ and through private lawsuits, not automatic fines.
Our website is run by an outside vendor. Does the deadline still apply to us?
Yes. The legal responsibility belongs to the government entity no matter who builds or hosts the site, so vendor contracts should name WCAG 2.1 AA explicitly.
Does the rule cover documents or just web pages?
Both. Agendas, minutes, budgets, and forms posted online must be accessible too, which is why scanned PDFs are the largest chunk of the work for most communities.
What should Wisconsin communities do now?
- Get an accessibility audit of the current website against WCAG 2.1 AA
- Fix the site itself: templates, navigation, contrast, forms, and media
- Work through the document library, converting scanned PDFs to accessible formats, starting with the documents residents actually use
- Set up a publishing process so new pages and documents go up accessible from day one
Fox Valley Web Design has been building websites for Wisconsin municipalities and small communities since 1997, and accessibility is part of every build we do. If your village, town, or district wants to know where its website stands before the 2028 deadline, request a quote and we will take a look.
Planning a WooCommerce Store in Wisconsin: Products, Payments, Shipping & Growth
Short answer: A successful eCommerce website begins with decisions about products, customers, payments, taxes, shipping, inventory, photography, fulfillment, returns, integrations, security, and ongoing ownership. Choosing a theme or payment button before those decisions are clear usually creates rework.
Use these 20 planning questions before requesting an online-store proposal. The answers will help a Wisconsin retailer, manufacturer, farm market, lodging business, or specialty producer define a realistic scope and budget.
1. What will the store sell?
List physical products, digital goods, services, bookings, subscriptions, gift cards, memberships, or donations separately. Each type can require different product fields, delivery rules, taxes, customer emails, and account behavior.
2. How many products and variations are involved?
Count the products that will be ready for launch, then note variations such as size, color, flavor, material, package quantity, or customization. A product with five sizes and ten colors may create fifty purchasable combinations, each with its own price, image, stock, weight, or identifier.
3. Who will prepare the product data?
Every product needs a consistent set of information. Define the required fields before collecting content.
- Product name and short description
- Detailed description and specifications
- Categories and attributes
- Price and sale-price rules
- SKU, barcode, or manufacturer identifier
- Weight and package dimensions
- Inventory quantity and backorder policy
- Images and image alternatives
- Shipping restrictions
- Related products and add-ons
A spreadsheet or system export can speed setup when the fields are clean and consistent. The project scope should state who imports, reviews, and corrects the data.
4. Do you have strong product photography?
Customers cannot hold an online product. Use clear, consistent images that show scale, details, packaging, variations, and the product in context. Decide whether the business will supply finished images or needs a new photo session, editing, background removal, and web-ready crops.
Fox Valley Web Design offers commercial and product photography in-house so the store, website, social media, and printed materials can share a consistent visual library.
5. Who is allowed to buy?
Define whether the store serves consumers, approved wholesale accounts, dealers, employees, members, or a mix. Business-to-business stores may need applications, role-based pricing, tax exemption, purchase orders, minimum quantities, negotiated terms, or restricted products.
6. Where will you sell?
Specify local pickup areas, states, countries, or regions. Selling beyond Wisconsin can affect shipping, taxes, privacy, accessibility, product restrictions, currencies, and customer service. International sales add customs, duties, classification, and documentation decisions.
7. Which payment methods will you accept?
Common options include cards, digital wallets, PayPal, bank transfer, purchase orders, financing, or payment at pickup. Compare processor fees, payout timing, dispute handling, fraud tools, supported countries, recurring-payment needs, and compatibility with the store platform.
The business—not the web designer—should own the merchant and payment accounts wherever possible.
8. How will sales tax be handled?
Online tax obligations depend on where and what the business sells. The store software can calculate tax based on configured rules or a connected service, but the business needs qualified tax guidance on registration, nexus, product taxability, exemptions, filing, and recordkeeping.
WooCommerce’s tax documentation explains software settings and explicitly recommends consulting an accountant or tax professional about what and when to charge.
9. How will orders be delivered?
List every method: shipping, local delivery, curbside pickup, in-store pickup, digital delivery, appointment, or freight quote. For physical products, record package sizes, weights, carrier accounts, service levels, handling time, free-shipping rules, oversized items, hazardous restrictions, and destinations.
In WooCommerce, shipping zones determine which options and rates customers see for an address. The official shipping-zone guide explains how zones and methods are matched.
10. Where does inventory live?
Decide whether the website is the master inventory system or must sync with a point-of-sale, ERP, accounting platform, warehouse, marketplace, or supplier. Document the direction and frequency of each sync and what should happen when an item sells in two channels at nearly the same time.
11. What happens after checkout?
Map the order from payment to fulfillment:
- The customer receives a clear confirmation.
- The correct team is notified.
- Payment and fraud status are reviewed.
- Inventory is adjusted.
- The order reaches the fulfillment workflow.
- Shipping or pickup information is sent.
- Tracking and status updates are communicated.
- Refunds, exchanges, and support are documented.
Test every step before launch, including failed payments and out-of-stock items.
12. What are the return, refund, and cancellation rules?
Write policies in plain language before building checkout. Cover time limits, product condition, final-sale items, custom products, return shipping, restocking fees, damaged shipments, refunds, exchanges, cancellations, and support contact information. Ask qualified legal counsel to review policies appropriate to the business and markets.
13. Does the store need customer accounts?
Guest checkout can reduce friction, while accounts can support order history, saved addresses, subscriptions, wholesale access, rewards, or repeat ordering. If accounts are required, explain why and minimize the information collected.
14. Which systems must connect?
Make a list of accounting, CRM, email marketing, ERP, POS, shipping, inventory, tax, reviews, loyalty, customer service, analytics, and marketplace systems. For each integration, confirm:
- Who provides and supports the connection?
- Which data moves in each direction?
- How often does it sync?
- What happens when the service is unavailable?
- Are API, transaction, or subscription fees involved?
15. How will customers find products?
Plan categories, filters, search, menus, related products, and landing pages around how customers shop. Internal product codes may not match customer language. Test the structure with someone who does not already know the catalog.
16. What search information should products provide?
Use unique product names and descriptions, accurate availability and price, crawlable category paths, descriptive images, and useful internal links. Google documents structured data relevant to eCommerce, including Product, Offer, Organization, LocalBusiness, Breadcrumb, Review, and Video information where appropriate.
Structured data should match the visible product page and current store data. It can improve understanding and eligibility for certain shopping displays, but it does not guarantee that a special result will appear.
17. Is the mobile checkout easy?
Test the complete purchase on actual phones. Check product selection, variations, cart changes, coupons, address entry, shipping choices, tax display, wallet payments, validation errors, order review, confirmation, and account creation.
Reduce unnecessary fields and distractions. A beautiful homepage cannot recover revenue lost to a confusing checkout.
18. What security and recovery plan is required?
An online store needs HTTPS, secure payment handling, restricted administrator access, strong authentication, software updates, monitoring, backups, restoration procedures, and a response plan. Because orders and inventory change frequently, backup frequency should reflect how much transaction data the business can afford to lose.
Review Fox Valley Web Design’s managed hosting and security services, and confirm the exact store-specific scope in writing.
19. Who will operate the store every week?
Assign owners for products, prices, inventory, promotions, orders, refunds, customer questions, updates, reports, and technical support. Decide what staff can manage and what the web partner will handle. Training should use the real workflow, not only a generic platform tour.
20. What does success look like?
Set a small group of useful measures: completed purchases, revenue, qualified wholesale applications, average order value, repeat orders, cart abandonment, fulfillment time, refund rate, customer-service issues, and margin after payment, shipping, advertising, and platform costs.
Launch with a measurement plan, then improve based on customer behavior and operational evidence.
What should an eCommerce proposal include?
- Discovery, store architecture, and design
- Number of products and variations included
- Product-data preparation and import responsibilities
- Photography, writing, and media production
- Payment, tax, shipping, and pickup configuration
- Named integrations and assumptions
- Mobile and checkout testing
- Policies and customer-email setup
- Training, documentation, and launch support
- Hosting, backups, security, and maintenance
- Plugin, processor, service, and renewal costs
- Ownership, access, timeline, and change process
Frequently asked questions
How much does an eCommerce website cost?
Cost depends on catalog size, product variations, design, photography, data quality, payments, taxes, shipping, integrations, customer roles, and ongoing support. A written scope is more useful than a price based only on the number of products.
Is WooCommerce a good fit for a Wisconsin small business?
WooCommerce can be a flexible option for a business that wants a WordPress-based store and has a clear maintenance plan. Fit depends on operational needs, integrations, catalog complexity, internal skills, and long-term ownership—not platform popularity alone.
Can I launch with a small catalog and add products later?
Yes, if the categories, product fields, photography standards, shipping rules, and management workflow are planned for growth. Start with a focused, complete catalog instead of publishing many unfinished listings.
Who is responsible for sales tax?
The business is responsible for understanding its obligations. Store software and connected services can assist with calculation and collection, but a qualified tax professional should advise on nexus, registration, taxability, filing, and jurisdiction-specific rules.
How long does it take to build an online store?
Timing depends heavily on product data, photography, policies, integration access, shipping and tax decisions, approvals, and testing. Content and operational readiness often determine the schedule more than the visual build.
Plan the operation, then build the store
Fox Valley Web Design has built and supported online stores for Wisconsin businesses for more than two decades. Explore our eCommerce website services and client portfolio, then request a practical eCommerce project plan and quote.
Managed WordPress Hosting: Security, Backups & Updates for Wisconsin Businesses
Short answer: Managed WordPress hosting means someone is responsible for more than storing website files. A useful managed plan should clearly cover software updates, backups, restoration, SSL, security monitoring, performance, uptime response, email or DNS responsibilities, and access to a real support team.
No host can promise that a website will never fail or be attacked. The value of management is preparation: reducing avoidable risk, detecting problems, preserving recoverable backups, and knowing who will respond.
Hosting is infrastructure; management is responsibility
Basic hosting gives a website server resources and a connection to the internet. The website owner may still be responsible for WordPress updates, plugin compatibility, backups, malware cleanup, form delivery, domain records, and troubleshooting.
Managed hosting assigns some or all of those jobs to a provider. Because the phrase has no universal checklist, ask exactly what “managed” includes. A low monthly price is not a bargain if essential maintenance is excluded or nobody can restore the site when something breaks.
1. WordPress core, theme, and plugin updates
WordPress sites depend on several moving parts. Core, themes, and plugins receive feature, compatibility, and security updates. Leaving them untouched can create risk; applying every update blindly on a live site can also cause problems.
A management plan should explain:
- Which updates are automatic and which are reviewed.
- How compatibility is checked.
- Whether a backup is taken before a significant update.
- How the site is tested afterward.
- Who responds if an update causes an error.
The official WordPress update documentation recommends keeping WordPress current and backing up before an upgrade.
2. Backups that can actually be restored
A backup is useful only if it contains the required files and database, is stored safely, and can be restored within an acceptable time. Ask about frequency, retention, storage location, encryption, restoration, and testing.
- Frequency: Is the site backed up daily, hourly, or on another schedule?
- Retention: How many restore points are available?
- Separation: Is a copy stored outside the same server or account?
- Scope: Are both the database and uploaded files included?
- Restoration: Who performs a restore, and is there a fee?
- Testing: Has the restoration process been verified?
A frequently changing eCommerce or membership site may need a different backup schedule than a brochure site updated once a month.
3. SSL and secure connections
SSL enables encrypted HTTPS connections between a visitor’s browser and the website. The certificate should renew reliably, and the site should avoid mixed-content errors that load some resources insecurely.
SSL is essential, but it is not complete website security. It does not replace updates, strong authentication, access controls, backups, or monitoring.
4. Account security and least-privilege access
Every administrator account increases exposure. Remove former staff and vendors, avoid shared logins, assign the least access each person needs, and use strong unique passwords with multi-factor authentication where available.
The plan should also define who controls the domain registrar, DNS, hosting account, WordPress administrator accounts, analytics, email provider, and paid licenses. The business should retain appropriate ownership and recovery access.
5. Malware, vulnerability, and file monitoring
Security tools can monitor suspicious changes, known vulnerabilities, login activity, and malicious files. Ask what is monitored, how often checks run, who receives alerts, and what cleanup is included.
Be cautious with vague promises such as “military-grade” or “unhackable.” A useful provider explains prevention, detection, response, recovery, and the customer’s responsibilities.
6. Firewall and login protection
Depending on the hosting stack, protection may include a web application firewall, rate limits, bot filtering, login attempt controls, and blocking of known malicious traffic. These layers should be configured with care so legitimate customers, forms, search crawlers, and integrations continue to work.
7. Performance and resource monitoring
Hosting affects performance, but so do image sizes, plugins, theme code, databases, fonts, video, tracking scripts, and third-party services. Ask whether the provider monitors response time, resource use, storage, and errors—and whether performance work on the website itself is included.
A good plan distinguishes an infrastructure limit from a page-level problem and recommends the appropriate fix instead of treating every issue as “the server.”
8. Uptime monitoring and incident response
Monitoring should check whether important pages are reachable and alert someone who can investigate. Ask about the monitoring interval, support hours, escalation process, communication during an incident, and treatment of third-party outages.
Review the service agreement for uptime language and exclusions. No infrastructure is failure-proof; the response plan matters.
9. Forms and transactional email
A page can appear healthy while quote requests or order emails silently fail. Managed support should clarify whether it tests important forms, monitors delivery, configures authenticated sending, or supports a transactional email service.
For critical leads, store submissions securely in WordPress or an approved connected system when appropriate, and test both the customer confirmation and internal notification.
10. Domain and DNS support
The domain registration, website hosting, DNS, and email may be handled by different companies. A DNS mistake can interrupt the website or email even when the web server is fine.
Keep registrar ownership in the business’s name, enable multi-factor authentication and renewal safeguards, document the DNS provider, and know which company is responsible for changes.
11. Staging and change management
A staging site provides a separate place to test significant design, plugin, or code changes. Ask whether staging is available, how data is copied, how privacy is protected, and how approved changes move to production.
For eCommerce, membership, booking, and frequently updated sites, a provider should take care not to overwrite new live orders or user data when deploying changes.
12. Human support and scope
Know how to reach support, who answers, typical response expectations, and what is billable. “Managed” may or may not include content edits, new pages, plugin licenses, email support, SEO, accessibility work, or custom development.
Fox Valley Web Design’s current managed website hosting offering lists cloud hosting, SSL certificates, daily backups, malware protection, updates, and Wisconsin-based phone support. A written proposal should confirm the exact scope for the specific website.
Questions to ask a WordPress hosting provider
- Who owns the hosting account and domain?
- Which WordPress, theme, and plugin updates do you handle?
- How often are backups created, how long are they retained, and where are they stored?
- Who restores the site, and what is the expected process?
- What security and uptime monitoring is active?
- What happens when malware or a vulnerability is detected?
- Are SSL, staging, caching, and transactional email included?
- Do you test forms and key transactions?
- What support hours and escalation path apply?
- Which changes are included, and which are billed separately?
- How can the site and data be moved if the business leaves?
- What documentation and administrator access will the business retain?
Frequently asked questions
Is managed WordPress hosting worth it for a small business?
It can be when the business depends on the website and does not have someone qualified to manage updates, backups, monitoring, and incidents. Compare the included responsibilities and response process, not only storage and bandwidth.
Does managed hosting make a WordPress site hack-proof?
No. Good management can reduce risk and improve detection and recovery, but no responsible provider should guarantee that a website can never be compromised.
How often should a WordPress site be backed up?
The schedule should reflect how often data changes and how much loss the business can accept. A brochure site and an active online store have different recovery needs. Confirm both frequency and retention.
Are business email and website hosting the same thing?
Not necessarily. Email may run through Microsoft 365, Google Workspace, a hosting mailbox, or another provider. Document where each service lives and who supports it before any DNS change.
What should I receive if I change hosting providers?
The business should have appropriate access to the domain, website files, database, content, media, and relevant account information, subject to the agreement and paid licenses. Clarify migration and ownership terms before signing.
Give the website a responsible owner
Fox Valley Web Design hosts and supports WordPress websites for businesses in Green Bay, Appleton, the Fox Valley, and throughout Wisconsin. If you want one local team responsible for the website from build through ongoing care, request a hosting and website-care quote or call (920) 434-9772.
Mobile Website Redesign Checklist for Wisconsin Small Businesses
Short answer: A website is ready for a redesign when it no longer makes the next step easy for customers—especially on a phone. Slow pages, tiny text, confusing navigation, stale content, weak calls to action, broken forms, and an outdated visual identity are business problems, not cosmetic details.
Use this 15-point mobile-first checklist to decide whether your current site needs a focused repair, a content overhaul, or a complete redesign.
1. Can a phone visitor understand the business in five seconds?
Open the homepage on a phone and look only at the first screen. It should make three things clear: who the business serves, what it provides, and what the visitor should do next. A clever headline is not enough if a potential customer still has to guess.
A strong first screen usually includes a specific value statement, one primary action, readable type, and a relevant visual. If the company name or industry is not self-explanatory, spell it out.
2. Is the mobile navigation simple?
A mobile menu should open quickly, use plain labels, and keep the most important paths near the top. Long menus, overlapping dropdowns, tiny tap targets, or links that require precision create friction before a visitor reaches the content.
- Keep the top-level choices focused.
- Use customer language such as Services, Work, About, and Contact.
- Make the phone number and quote or contact action easy to find.
- Test every submenu with one thumb.
3. Are calls to action visible and consistent?
Every important page should give the visitor a sensible next step. “Request a Quote,” “Call Now,” “Schedule a Visit,” and “Shop Products” are clearer than a generic “Learn More” when the visitor is ready to act.
Choose one primary action and use it consistently. Secondary actions can support visitors who are still comparing options, but five competing buttons usually weaken all of them.
4. Is every line of text comfortable to read?
Phone visitors should not pinch, zoom, or rotate the screen to read. Check font size, line spacing, contrast, paragraph width, and the space around headings. Dense blocks of copy can be broken into short paragraphs, descriptive headings, and useful lists without making the content shallow.
5. Do buttons and forms work with a thumb?
Buttons should be easy to tap without hitting a neighboring element. Forms should request only the information needed for the next step, use the correct mobile keyboard for phone and email fields, show clear error messages, and confirm a successful submission.
Test forms on real iPhone and Android devices. A form that works with a mouse can still fail when autofill, a mobile keyboard, or a sticky element changes the available screen space.
6. Does the layout avoid awkward empty space and overlap?
Responsive layouts need deliberate spacing at each width. Watch for oversized gaps, headings covered by badges, text spilling outside cards, floating buttons blocking content, and stacked columns that retain desktop-sized margins. These issues make a site feel unfinished even when every element technically appears.
7. Does the website load without making visitors wait?
Large images, autoplay media, excessive plugins, third-party scripts, and old theme code can slow a page. Pay special attention to the first visible section, navigation response, layout movement during loading, and the speed of forms or interactive features.
Performance is not a one-time score. It should be tested on representative pages and monitored after content, plugins, tracking, or hosting changes.
8. Does the site use real, current photography?
Visitors can often recognize generic stock photography. Current photos of the team, facility, projects, products, and service area help people understand what they are buying and who will deliver it. They also give sales, social media, and business listings a consistent source of visual content.
Fox Valley Web Design provides commercial photography, drone photography, and video production in-house.
9. Is the content still accurate?
Review services, staff, hours, locations, pricing language, certifications, equipment, policies, and contact details. Remove expired announcements and unsupported claims. A beautiful redesign cannot build trust if the information is outdated.
Also look for pages that say nearly the same thing. Combining thin or redundant content can make the site easier to navigate and maintain.
10. Does each service have enough information?
A single paragraph listing ten services rarely answers the questions of ten different customers. Important services often deserve focused pages that explain who they are for, what is included, how the process works, common concerns, relevant examples, and the next step.
This structure helps visitors make a decision and gives search systems clearer information to understand. Learn more about search engine optimization and AI search optimization.
11. Can visitors see proof?
Claims become more believable when they are supported by recent projects, testimonials, photographs, credentials, process details, or measurable examples. Place proof near the service it supports instead of hiding everything on one separate page.
For inspiration, review the Fox Valley Web Design client portfolio.
12. Are titles, headings, and links descriptive?
Every page needs a clear topic. The browser title and main heading should describe the page, subheadings should help a scanning reader, and link text should explain the destination. “Commercial Photography for Wisconsin Manufacturers” is more useful than “Services,” and “View our eCommerce work” is clearer than “Click here.”
13. Is the website accessible to more people?
Accessibility belongs in the redesign from the beginning. Review keyboard navigation, visible focus states, text contrast, image alternatives, form labels, heading order, link meaning, captions, and motion. Automated tools can help identify problems, but real keyboard and screen-reader checks add essential context.
14. Is the platform safe and maintainable?
An old site may depend on abandoned plugins, unsupported software, unknown administrator accounts, or a hosting setup nobody actively manages. Before redesigning, inventory the domain, DNS, hosting, analytics, form destinations, licenses, backups, and administrator access.
The new plan should assign responsibility for software updates, backups, security monitoring, content changes, and support. Read about managed hosting and website security.
15. Can you measure whether the website works?
Decide what success means before launch. Useful measurements may include qualified calls, completed quote forms, appointments, purchases, directions, downloads, applications, or engagement with key service pages. Analytics should support business decisions, not simply produce a monthly traffic number.
Repair, refresh, or redesign?
Choose a focused repair when:
- The overall structure and branding still work.
- The problems are limited to a few mobile layouts, forms, or performance issues.
- The platform is current and maintainable.
Choose a content and visual refresh when:
- The navigation is sound but the copy, photos, or styling feel stale.
- Services and calls to action need clarification.
- The site needs stronger proof and better search-focused content.
Choose a full redesign when:
- The site is difficult to use on mobile.
- The platform or plugins are no longer dependable.
- The business, brand, services, or audience have significantly changed.
- Small fixes keep creating new problems.
- The site cannot support needed eCommerce, integrations, or content growth.
Frequently asked questions
How often should a business website be redesigned?
There is no universal calendar. Redesign when customer needs, business goals, brand, content, technology, or mobile usability have outgrown the current site. A well-maintained website can evolve for years; an unsupported one can become a liability much sooner.
Can a redesign hurt SEO?
It can if valuable content is removed, URLs change without redirects, titles are weakened, internal links disappear, or indexing settings are mishandled. Inventory current URLs and performance before launch, preserve useful content, map redirects, and verify the live site afterward.
Should mobile design come before desktop design?
The important point is to plan for all screens, not treat mobile as an afterthought. Starting with the smallest screen often forces clearer priorities, while wider layouts can then add space and supporting detail.
How do I test a redesign before launch?
Check representative phones, tablets, laptops, and desktop widths; test navigation, forms, calls, email links, purchases, keyboard use, performance, analytics, search settings, and error pages. Ask someone unfamiliar with the project to complete the most important task.
What should I prepare for a redesign consultation?
Bring your goals, current pain points, customer questions, priority services, examples you like, brand files, existing photography, required integrations, domain and hosting details, decision-makers, budget range, and desired timeline.
See what your website needs next
Fox Valley Web Design has built custom websites in-house since 1997 for businesses in Green Bay, Appleton, the Fox Valley, and beyond. Explore our website design and development services, then request a free website evaluation and quote.
Claude Fable 5: Anthropic’s Most Powerful AI Is Now Open to Everyone
There is big news in the AI world. On June 9, 2026, Anthropic launched Claude Fable 5 — the first of its new Mythos-class models, a tier that sits above the familiar Opus line in raw capability. After a brief pause shortly after launch, Fable 5 was redeployed on July 1 and is now available to everyone.
What Makes Fable 5 Different
Fable 5 is the most capable AI model Anthropic has ever made generally available. It leads nearly every major benchmark, and the longer and more complex the task, the wider its lead grows. It reads charts, screenshots, and detailed figures with state-of-the-art accuracy, and it can work on its own for hours at a time.
The early numbers are striking. During testing, payments company Stripe reported that Fable 5 compressed months of engineering into days — completing in a single day a code migration that would have taken a full team more than two months by hand.
Fable 5 also shares its brain with Claude Mythos 5, a version reserved for vetted cybersecurity and research partners. The difference is safety: Fable 5 ships with new safeguard classifiers, and when a request touches sensitive territory like cybersecurity or biology, the conversation is handed to Claude Opus 4.8 instead. Anthropic says this happens in fewer than 5% of sessions.
Pricing lands at $10 per million input tokens and $50 per million output tokens — less than half the cost of the preview model before it — with subscription access rolling out in stages while capacity catches up.
What This Means for Wisconsin Businesses
You don’t need to be a software company for this to matter. AI models this capable are already changing how customers find local businesses. More people ask AI assistants for recommendations instead of scrolling through search results, and models like Fable 5 will only accelerate that shift.
AI discovery is broader than one assistant. Customers may ask Claude, ChatGPT, Gemini, Meta AI, or Grok for advice, or search through Google AI Overviews and AI Mode, Perplexity, ChatGPT Search, and Copilot Search in Bing.
That is exactly why we offer AI Search Engine optimization (AEO) alongside traditional SEO. Websites that are structured clearly, load fast, and answer real questions are the ones AI assistants can read, trust, and recommend. The businesses that prepare now will be the ones AI sends customers to later.
Fox Valley Web Design has been building websites in Northeast Wisconsin since 1997, and we have watched every wave of the internet arrive — search engines, smartphones, social media, and now AI. The technology changes, but our approach stays the same: businesses that invest in doing it right come out ahead.
Curious what AI search could mean for your website? Request a quote and we will take a look together. You can read the full details in Anthropic’s official announcement.
Happy Thanksgiving to all our clients, friends & family!
Happy Thanksgiving to our amazing clients, friends, and family! 🦃🍂
As we gather around the table this year, we want to take a moment to express our gratitude. Thank you for trusting us with your website development needs! Without you, we’d just be a bunch of techies arguing over the latest AI programs while eating cold pizza.
May your turkey be juicy, your pie be plentiful, and your Wi-Fi signal be strong!
Wishing you all a day filled with laughter, love, and maybe a little too much pumpkin spice. Cheers to you and your families!
With gratitude,
Gary, Amy, & Nicholas Arndt
Fox Valley Web Design LLC
PS.
Why did the turkey join a band on Thanksgiving?
Because it had the drumsticks! 🥁🦃