Local service guide
Website Design in Portland, OR: Hiring Guide
For Website Design in Portland, OR, ask designers to quote a written brief covering customer tasks, content, integrations, testing, account ownership, and support. Compare the build price with recurring charges before choosing. Assign privacy and accessibility responsibilities, and require a demonstration of your booking, inquiry, or checkout process before approving launch.
Prepare a brief around customer tasks
Describe what a visitor should accomplish and what your staff must do afterward. For an appointment business, specify booking, cancellation, confirmation messages, and who receives inquiries. For a shop, define product options, pickup instructions, checkout, and stock updates. Ask candidates to demonstrate a comparable customer task on a site from their portfolio.
Prepare a page list, approved business details, and photos you have permission to use. Name one person who can approve content. Include your address, hours, contact methods, and customer instructions for reaching your premises. Identify the information your staff should edit without asking the designer.
For a redesign, list pages and content you want to retain. Request a migration plan covering changed page addresses, business email, forms, and launch recovery. Ask the designer to show you the replacement on a preview site and explain the switchover before you approve it.
Compare itemized quotes and ongoing charges
Give bidders the same brief and request separate prices for design and build, content preparation, migration, testing, and training. Ask each bidder to list recurring charges for hosting, platform subscriptions, extensions, and outside services. Require written exclusions and a process for pricing changes.
Build your budget from quotes for your specific project. Compare what you will pay at launch with what you will pay to operate and maintain the site. Ask bidders to tie milestones to deliverables, including your deadlines for supplying content and approving revisions. Agree on how both sides will handle delays.
Confirm who owns the domain account, website administrator account, design files, and paid licenses. Request any transfer restrictions in writing. Set payment milestones around work you can inspect, and define the defect correction period, support contact, and charges for later edits.
Make accessibility part of acceptance
Portland's digital-services playbook recommends reviewing content structure, media, forms, keyboard navigation, and error messages. It calls for documented issues, completed fixes, and follow-up actions. Use this municipal guidance as a practical reference when defining the testing report for your business site. [3]
Ask the designer to demonstrate your main customer journey using a keyboard. Include form labels, error instructions, image alternatives, and text contrast in the agreed review. Name the booking, payment, or other outside components that need testing, and decide who will coordinate fixes with their vendors.
In its February 2026 automated evaluation of one million leading homepages, WebAIM detected low-contrast text on 83.9%, missing image alternatives on 53.1%, and missing form labels on 51%. These worldwide findings offer priorities for testing; they do not measure Portland businesses or predict problems on your site. [4]
WebAIM explains that automated tools cannot detect all conformance failures. A scan without detected errors does not establish accessibility. Portland also calls for manual testing. Request an automated report alongside documented manual checks of the pages and interactions in your contract. [2] [4]
Resolve Oregon privacy requirements before tracking
Oregon DOJ says the Consumer Privacy Act generally covers businesses operating in Oregon or serving Oregon residents that control or process at least 100,000 consumers' personal data in a calendar year, or at least 25,000 while deriving over 25% of annual gross revenue from personal-data sales. Exceptions and exclusions exist. Ask your legal adviser to assess applicability and provide implementation requirements. [1]
For covered controllers, Oregon DOJ identifies privacy notices, consumer contact and rights mechanisms, and opt-out controls among the obligations. It says a cookie banner may suffice for some entities but not all. Before approving controls, ask the designer to inventory forms, analytics, advertising tools, and services that receive customer data. [1]
Assign someone to approve privacy wording and handle consumer requests. Oregon DOJ describes processors as contractually bound by a controller's instructions when processing data on its behalf. If your designer will handle personal data for your covered business, settle the processing instructions and responsibilities before providing access. [1]
Check launch and handover with your staff
Have a staff member submit an inquiry, complete a booking, or place an agreed test order. Confirm receipt and the next staff action. Review the site on a phone, check business details, and practice editing a page. Record unresolved issues with an owner and correction date.
Ask the designer to demonstrate the published pages and visible source links where you use sourced information. Include table headers, any structured data matching visible content, and the intended canonical address and indexing settings in the handover checks. Request a review of crawler policies against your business's stated preferences.
Collect account access, renewal information, recovery instructions, and an editing guide. Agree on who handles backups, updates, support requests, and privacy or accessibility changes. Have the designer explain the maintenance terms and the steps for moving to another provider.
Common accessibility failures in WebAIM's 2026 homepage sample
Local details that affect your job
Oregon opt-out signals affect the tracking brief
Businesses and nonprofits meeting Oregon Consumer Privacy Act thresholds must honor qualifying opt-out preference signals from January 1, 2026. Oregon DOJ names Global Privacy Control as an example and requires a clear website link for exercising opt-out rights. If your business falls within scope, request a demonstration that the tracking setup honors the signal. Assign staff responsibility for handling requests and ask the designer to document the test. [1]
City service contracts need a defined accessibility scope
Portland says its Title II web and app rule covers City public-facing services, including content supplied through outside arrangements. The City identifies April 26, 2027 as its compliance deadline and WCAG 2.1 AA as the technical standard. If you supply an online service for the City, confirm covered content, testing evidence, and remediation responsibilities with the City project owner before requesting bids. This guidance concerns municipal services and does not establish the same deadline for every private business. [2]
Match your brief to the customer task
| Your project | Scope to request | Acceptance demonstration |
|---|---|---|
| Business information site | Approved copy, contact form, page design, and staff editing | Submit an inquiry and have staff update opening hours |
| Appointment service | Booking integration, confirmations, cancellation steps, and support ownership | Complete a booking and confirm staff receipt |
| Online store | Product entry, checkout, pickup or delivery rules, and handover | Place an agreed test order and follow the fulfillment steps |
| Existing-site redesign | Content inventory, migration, changed-address handling, and recovery | Check retained content, forms, and the launch recovery procedure |
| City public-facing service | Confirm Title II coverage and WCAG 2.1 AA requirements with the City | Review automated results, manual testing, and remediation responsibilities |
Your hiring checklist
- Describe the main customer task and list the pages and integrations needed.
- Provide approved content, business details, photos, and a named content approver.
- Compare itemized build fees, recurring charges, exclusions, and change terms.
- Confirm account ownership, access, license transfer terms, and recovery arrangements.
- Agree on automated and manual accessibility checks with documented fixes.
- Assess Oregon privacy applicability and assign responsibility for controls and requests.
- Test customer transactions, published pages, staff editing, and agreed site settings.
- Collect training, renewal details, maintenance terms, and a migration or recovery plan.
Frequently Asked Questions
How should I budget for a business website?
Obtain itemized quotes for the same page list, content responsibilities, integrations, and testing requirements. Compare build costs with recurring hosting, subscription, maintenance, and support charges. Ask each bidder to identify exclusions and price changes before choosing.
Does every Oregon business need Global Privacy Control support?
Oregon DOJ says covered controllers must accept universal opt-out mechanisms from January 1, 2026. The Consumer Privacy Act has applicability thresholds, exceptions, and exclusions. Have your legal adviser establish your obligations before the designer specifies or removes controls. [1]
Does an automated accessibility scan finish testing?
WebAIM says an absence of detected errors does not establish accessibility or conformance. Portland also calls for manual tests. Ask your designer to document manual checks of the customer journeys and outside components included in your agreement. [2] [4]
What should I receive at handover?
Request administrator access, domain and hosting account details, renewal information, editing instructions, and recovery procedures. Confirm which files and licenses you can transfer, what support costs, and who will fix unresolved defects.
Sources and scope
This guide combines the sources below with practical planning guidance. Figures apply to the stated geography and period; request a written quote for your property.