Business website accessibility: keyboard, contrast and structure
Review keyboard access, visible focus, contrast, headings, zoom and forms with a practical WCAG-informed acceptance process.
Article language: English

In this article
Try to find a service and send a question without touching your mouse. If you lose track of where the keyboard focus is or cannot close the menu, you have found a barrier that impressive photography will not conceal. Website accessibility means being able to read the content and complete a task using different ways of interacting with the site. Check the keyboard, visible focus—the indication of the active element—contrast, structure and messages. A button that enlarges text cannot do that work for the whole site.
This article describes a basic functional review, with references to selected criteria in the Web Content Accessibility Guidelines (WCAG). It is neither an assessment of a particular company's legal obligations nor confirmation that a site fully conforms to the standard. A full evaluation requires a defined scope, level and appropriate methodology. The checks proposed here can reveal real barriers and help you prepare fixes that can be verified.
Define the scope before opening a tool
Record the addresses and functions included in the review: the home page, service offer, an article, menu, form and documents. Add states that are not visible when a page first opens: a field error, an expanded panel, sending, success and no search results. A page can work correctly in its initial state and block someone after their first action. If the offer uses a spatial presentation, include a route without the 3D scene, with the same important information and an accessible way to continue. See also the article on an alternative to a 3D scene (in Polish).
Choose representative scenarios. One person wants to find what a service includes, read the terms and send a short question. Another returns to an article through an old link. Describe the task without naming a particular button. That lets you test the visitor's route rather than their ability to repeat the designer's instructions.
Record the requirements in the brief for a premium website (in Polish) beforehand. The handover should not be the first time anyone discovers that a form must work with a keyboard or a menu must not cover the active field. Also decide who will confirm each fix and how evidence will be kept.
Go through the site using only a keyboard
Put the mouse aside and start by opening the address. Move forward with Tab and back with Shift+Tab. Check that links and buttons activate as they normally should. Open the menu, the questions panel and the contact page. See whether you can reach every important action and leave each open element.
WCAG criterion 2.1.1 covers keyboard operation, with a defined exception for functions that depend on the path of a movement. An ordinary B2B menu or form does not qualify for that exception simply because it was originally designed around a pointer.
Record specific barriers: “After opening the menu, I cannot reach Contact,” or “A closed answer still contains a link in the Tab order.” A description like that points towards a fix. “The keyboard does not work” leaves the person fixing it with too much to guess and makes a retest harder.
Check focus visibility and order
Focus indicates where a keyboard user is currently working. It needs to be visible against both dark and light backgrounds. WCAG criterion 2.4.7 describes a visible focus indicator. A hover effect alone does not establish that the criterion is met.
Compare the navigation order with the layout and meaning of the content. After a heading, do you reach the relevant action or a hidden decoration? Does a fixed bar cover the element that has just received focus? Do not try to repair a chaotic order by assigning arbitrary numbers to successive controls. Check the structure of the document and its interactive elements.
After closing a large menu, the user should be able to tell where they are. Record the intended return to the control that opened it. Do not move focus every time a decorative image changes. The article on website microinteractions (in Polish) explores states and transitions in more detail.
Review structure beyond appearance
Check the page title and the list of headings. Sections should form a logical order, not a collection of words enlarged for effect. W3C WAI explains page regions and content structure. Appropriate markup also helps people using assistive technologies navigate the material.
Consider links read without the full paragraph around them. Five identical “more” links on cards may need better context. A button should have a name that matches its function, and an element that leads to a new page should be a link. Appearance alone does not tell the browser what role an element has.
B2B website information architecture helps organise the site as a whole. More detail is available in the article on B2B website information architecture (in Polish). Accessibility does not replace that work. A site can have correct markup and still use names for its services that people do not understand. A handover therefore needs both technical checks and a review of whether the communication makes sense.
Measure contrast in the states people actually encounter
WCAG criterion 1.4.3 sets text contrast requirements: at level AA, generally at least 4.5:1, or 3:1 for large text as defined by the criterion, with specified exceptions. Do not judge compliance by eye alone or from the colour names in a brand guide.

Check menus, captions, labels, messages and button text. Also examine hover, selected and error states. Pale gold may work as decoration, but a particular shade may not suit small text on a cream background. The result depends on the pair of colours and the element's role.
Text over a photograph needs checking in every intended crop. A large dark area on the left may disappear on a phone, while a bright reflection moves under the lettering. Reviewing the photograph and typography of a premium website (in Polish) together is more useful than approving those layers in separate presentations.
Enlarge the content and narrow the view
Check the text at 200% enlargement. WCAG criterion 1.4.4 describes how content behaves at that scale. Then test a narrow layout. The reflow criterion refers, among other things, to a width equivalent to 320 CSS pixels for vertically scrolling content, with exceptions where a two-dimensional layout is needed.
Go through the entire journey, not just the heading. Look for clipped labels, ordinary paragraphs that scroll horizontally and buttons that cover other information. Check a long email address, a title in the target language and an error message. These often reveal the limits of fixed heights and widths.
Do not remove information to make it fit the screen. First change the layout and let text wrap where it should. A table that requires comparison in two dimensions may need different treatment from a paragraph, but that exception should not excuse overflow across the whole site. Record where the problem occurs and what content disappears.
Review images, the form and its messages
Alternative text should depend on what an image does. A decorative image may have empty alt text; an informative image needs an equivalent of its relevant meaning; an image used as a button needs a description of the action. The article on brand photography on a website (in Polish) explores the choice and its context. Do not add hidden advertising phrases in place of information.
Check the form from label to confirmation. Is it clear which fields are required? Does an error explain how to correct it? Does the information entered remain after a failed attempt? A red outline alone does not explain what happened. The information needs to be available where the person is carrying out the action.
The article on the B2B website contact form (in Polish) describes the process in more detail. Check the form with a screen reader too, or involve someone competent to conduct that test. If you plan a session with users, prepare a study with people who use assistive technologies (in Polish), taking account of how they normally work. An automated scanner cannot independently decide whether a message is understandable or whether the sequence of actions makes sense.
How should fixes be prioritised?
Start with a barrier that prevents the main task: an inaccessible menu, a keyboard trap or a form without an understandable error. Then fix obstacles that make orientation and reading difficult. Do not set priorities solely by the number of occurrences in a tool's report. One problem can block the entire route to contact.
A working example: the menu's close button is visible, but the keyboard cannot reach it. The first fix concerns the control and the focus path. Only after that is confirmed should you refine the panel's fade-out timing. Record a test of the return to the content as well, so fixing one step does not leave the user in an invisible layer.
Include icons and their labels (in Polish) in the basic review. Check whether an action has a clear name even when someone cannot recognise the drawing. This is particularly easy to miss when the only cue is a download, close or open-panel symbol.
Record barriers so the fix can be checked
A useful issue report includes the address, state, steps, expected result and observed result. Add the related criterion if it has been established, and evidence such as a recording or description. Do not publish information entered by a real customer. Test material is usually enough to reproduce the issue.
Distinguish a tool's result from a confirmed barrier. A warning may need human judgement, and the absence of warnings does not mean full conformance. Also state which functions were not checked. An honest report scope helps plan the next evaluation and keeps a basic review distinct from certification of the whole site.
- Every important action has a keyboard route.
- Focus remains visible and its context is clear.
- Headings and labels describe the actual function.
- Contrast has been measured in the relevant states.
- Enlargement and a narrow view preserve the content.
- Errors have a procedure for checking them again.
When retesting, also perform the step before and the step after the fixed element. A change to focus order can help in one place while making it harder to return to the offer. Alongside confirmation of the fix itself, you therefore need a short test of the surrounding journey. Add the site version and result to the report, so an old observation is not mistaken for an assessment of a later implementation.
Include that evidence in the finished website handover. The topic is discussed in the article on website acceptance checks (in Polish). If you want to define the scope of accessibility improvements, explore Aeneia Design.











