Dark mode for a company website: when it helps and when it hides the details
Decide whether a company website needs dark mode, then test both palettes, user choice, images and forms.
Article language: English

In this article
Dark mode can give a website character. It can also send a chart caption to sleep before the rest of the interface. Introduce it when it meets your audience's needs and you can maintain two complete palettes. Simply reversing black and white is not enough. Check text, images, forms and how the choice is remembered before an elegant switch offers customers a less readable version of your offer.
Start with tasks: does a customer read for a long time, examine photographs of materials, compare services or simply look up contact details? Prepare a representative part of the website in both palettes and test the same actions. The plan below helps you assess the investment, agree switching rules and review the result without assuming that a dark background is more comfortable for everyone.
Separate the brand's character from an additional feature
A site can use a dark identity as its primary appearance and have no switch at all. It can also start light and offer an additional dark palette. These are different decisions. The first concerns the brand's presentation; the second gives visitors control and increases the work needed for design, implementation and later checks.
Imagine an architectural studio. Large photographs of completed projects look good on a navy background, but clients also want to read long technical descriptions and compare materials. Instead of assuming one answer for the whole site, test two versions of that particular task. What looks striking on the first screen may not work as well over several minutes.
Do not justify the choice with unverified health benefits, energy savings on every device or increased sales. Those claims need separate evidence and depend on conditions. A concrete reason is enough: a particular audience wants a choice, the content works in both palettes and the team can maintain them.
Write down the decision criteria. If the main problem is an unclear description of the service, another colour theme will not solve it. If readers return to a large library and ask for a lighter or darker view, a small trial may tell you more than another debate about taste in front of a designer's monitor.
Decide who chooses the palette and how that decision can be changed
MDN describes prefers-color-scheme as a way to detect a light or dark theme preference communicated by the system or browser. This can provide a starting point consistent with the visitor's setting. It does not decide what should happen after a manual choice on the site.
One practical approach offers three settings: light, dark and system. If you offer only two, make the switch's meaning clear. A moon alone could indicate either the current state or the action that will happen next. A visitor should not have to experiment to work out which palette is selected.
Agree the order of precedence and what is remembered. Does a manual choice survive a refresh? Does it apply only in this browser, or follow a signed-in account? What happens if browser data is removed? You do not need to explain the whole mechanism to visitors, but the implementation team should be able to describe and demonstrate the behaviour.
Switch themes halfway through completing a form too. The text entered, selected option and place where the person continues should behave as agreed. If changing the appearance resets data or closes a panel, the customer pays for a decision that was supposed to make the site easier to use. Add this to acceptance testing without creating a separate scenario for every field: use a genuinely long description and check it after switching palettes.
Also change the system setting while the page is open. If the visitor already chose a palette manually, an automatic switch could contradict that decision. Agree such rules before implementation. Later it is difficult to distinguish intended behaviour from an error if the specification contains only a drawing of a sun and moon.
Build the second palette around element roles
List the roles of colours: page and card backgrounds, primary and secondary text, links, borders, the highlight for the element with keyboard focus, errors and success. Each role needs an equivalent in both palettes. Do not copy values mechanically or darken all images with one filter. The change should preserve meaning, not just create a general impression of darkness. Organise these roles as brand design tokens so the meaning survives across components. The guide to brand design tokens (in Polish) explains how to record these roles.
A brand's gold may work on navy but lose legibility on a lighter card. Secondary text that is clear enough on white may almost disappear against another background. Test the actual combinations that appear next to each other. A colour's name in a design file does not establish how it behaves in a particular place.
W3C explains minimum text contrast in criterion 1.4.3: the general threshold is 4.5:1, or 3:1 for sufficiently large text, subject to the stated exceptions. Assess both palettes separately. Measuring a few colours alone is not a complete accessibility assessment.
Combine these checks with selecting typography for a premium website. A thin typeface, long line and very small caption can make reading difficult even when the contrast measurement passes. Finally, read a real longer text rather than judging only a sample of three words. The guide to website typography (in Polish) considers legibility beyond colour contrast.
Images and marks need their own decision
Some photographs have a light background that stands out sharply against a dark page. That need not be an error. If the white belongs to the actual product or document, removing it may alter the message. Consider a frame, spacing or another crop instead of automatically reworking the material.
Inspect transparent marks, diagrams and illustrations on both backgrounds. Dark lines may still be technically present but become invisible. A mark intended for a dark background should be the correct file approved for the brand, not an accidental colour inversion. The guide to brand photography on a website (in Polish) discusses choosing and preparing images for their roles.
Look at images that load late too. Does their placeholder background suit the active palette? Does a large white rectangle appear briefly? This is easy to miss on the author's fast computer, so test with a slower connection and after clearing the cache.
Check icons and their labels separately. An icon must still mean the same action in the second theme. Changing its colour should not remove state information or replace a necessary label. Darkness can create atmosphere, but it should not take over the instruction manual. For names and states, the article on icon meanings and labels (in Polish) offers further context.

Test the form beyond its ideal initial state
An empty field with an elegant label and even border is easy to approve. Harder states include errors, browser autofill, text selection, a selection list and a disabled button. Each should remain recognisable. A customer should not have to hunt for an error by playing hot and cold when everything happens to be graphite grey.
The color-scheme property described by MDN communicates supported schemes to the browser and affects, among other things, its default form controls. It does not replace designing colours for the remaining elements. Include both mechanisms in the specification so that part of the interface does not look as if it came from another website.
Run the complete scenario: enter data, trigger an error in one field, correct it and confirm submission. Repeat with a keyboard and on a phone. Check messages during a slow response and a missing connection. A light-palette test does not replace a dark-palette test: differences often appear in states absent from the main design.
Compare the result with contact form design. In both palettes the customer should understand the same requirements and receive the same submission information. The second theme should not be a reduced-function version of the first. The guide to B2B contact forms (in Polish) follows the message from entry to delivery.
Inspect switching, refreshes and material beyond the page
Changing themes does not require a spectacular animation. If you use one, check that it does not prevent a quick change back and that the final state is clear without motion. The guide to website microinteractions (in Polish) explores clear states and use without motion. More important than the effect is that the choice actually works.
Open the site directly at an article and a service page, then refresh. Watch for a visibly different palette appearing before the correct one. Check transitions between pages. Do not judge only the screen where the designer just clicked the switch; visitors may arrive from saved links.
Remember embedded third-party elements. A calendar, video or partner form may have its own appearance and limited customisation. Decide whether the contrast with the surrounding site is acceptable and whether the surrounding design makes it difficult to use. Do not promise complete theme support where your team does not control the content.
Finally, check the print version of the site. The guide to designing a website for print (in Polish) explains how to preserve the relevant content. A selected dark theme should not thoughtlessly turn an offer into several pages of heavy background. Screens and print have different conditions; prepare deliberately for both.
Read charts and comparisons without relying on a dramatic background
If the site presents data, check it separately from ordinary text. Series colours, legends, grids and markers may need a second set of values. Changing the chart background while leaving every line in its existing shade is not enough. The visitor should still recognise the same relationship, not merely see the same shape. Set out shared rules in the brand's visual language for charts, preserving their meaning in both palettes. For labels, scales and data meaning, see the article on charts in a brand’s visual language (in Polish).
In a hypothetical comparison of service options, check the column name, description of conditions and indication of the selected scope. If a highlighted card no longer stands apart from its neighbours, add a clear description or another orderly cue. Do not assume a stronger glowing border solves every distinction. Clear information matters more.
Check material pasted in by editors too. A diagram with a white rectangle in the middle or a table with a hard-coded text colour can bypass the palette system. Show editors how to recognise and correct such material in publishing instructions. They do not need every technical detail, but should know when to request another version of a graphic.
A useful test is to ask someone to find one specific conclusion in the data in both palettes. If they reach a different answer or miss a condition, record where the problem occurs. Saying that a chart is prettier does not answer whether it still explains the offer correctly.
Agree the cost of maintaining another element
Before commissioning the feature, ask how new cards, forms and illustrations will be added. Will an element using existing colour roles receive both versions automatically? Which materials need separate preparation? The answer helps assess ongoing editorial work, not just the cost of the initial implementation.
Record limitations in acceptance too. If an external calendar stays light, agree whether that is a deliberate choice. If the new palette covers only part of the site, make the boundary clear enough that visitors do not mistake it for a failure. You need not pretend to control every dependency, but you should know where control ends.
Prepare a short set of example elements in both themes for future work. It lets the team compare a new component against the accepted presentation. The decision to offer dark mode then remains part of a maintained site system instead of becoming a project whose purpose only the original button's author remembers.
Decide after a small but complete trial
Prepare one long description, a service card, a transparent image, part of a table and a form with all its states. This is a representative sample for discussion, not a promise to cover every future case. Assess whether both palettes retain readability and meaning without manually correcting every new page.
If the trial reveals many exceptions, estimate their maintenance before adding a switch across the site. It may be better to refine one primary theme or limit the feature's scope. If both work consistently, document rules for future elements so the next publication does not introduce a bright island in a dark sea.
For the website acceptance review, record the result for each palette, the selection method and cases tested after refresh. Include actual colours and views of form states. Looking good does not establish that a customer can read an important condition and complete a task. The guide to website acceptance (in Polish) describes how to record and repeat checks.
If you are considering an additional theme, see the scope of Aeneia Design.








