zeba.one - Digital Accessibility

Digital accessibility audit

Make it easier for others to use your website – ensure WCAG compliance

How does it work? How to verify a website?

List of tested page elements

See categories of tested elements compliant with verification contained in the WCAG standard.

When to order a manual audit (auditor) and when automatic?

To clarify the difference and choose the appropriate report, just answer a few basic questions.

Do you know what the current accessibility state of our site is?
If you haven't previously performed a site audit - we recommend doing an automatic audit as the first step. After performing such an audit - you'll see what level of site compliance with accessibility principles is. If it's low, you should change it as soon as possible. You can always send the automatic report for a more detailed manual audit (auditor).

I don't have experience or technical skills, what should I do?
Definitely at the beginning, perform an automatic audit. If its result is bad, you can contact us and perform an in-depth audit, where you can see what needs to be changed on your site to be accessible. In the recommendations of such an audit, there is information - how to implement the change. Such an audit can be sent to the company taking care of the site - it is sufficient to implement changes. You can always contact us, we will help with implementing changes.

Why spend more money on a manual audit? The price difference is very large.
That's true. This is because in the case of a manual audit, an experienced auditor reviews every element of the site very thoroughly, tests it on many devices and subjects it to several tests. This is a complicated and labor-intensive activity. Manual audit is the best way to verify a site in terms of WCAG, but not for everyone the costs that need to be incurred are acceptable. Remember that after an automatic audit, you can always commission a manual audit - financially on package upgrade - you won't lose anything.

Detailed description of tested functions and differences in audits

Below are all tested functionalities divided into tested elements.

Tested element

Automatic

Auditor

Color matching and contrast - evaluation of page element contrast and verification of how information is conveyed to the user through color

-

Yes

Focus visibility and keyboard tests - verification whether the entire page can be navigated with keyboard only, whether focus doesn't "disappear" and whether the order of navigating through elements makes sense.

-

Yes

Text understanding analysis - plain language - assessment whether page content is written in plain and understandable language

-

Yes

Alternative text comprehensibility - verification whether image has alt attribute, but won't assess whether its content is sensible, understandable and contextually appropriate.

-

Yes

Navigation logic and consistency - checking whether menus, buttons and user paths are logical and easy to understand.

-

Yes

Screen reader operation - "audibility" consultation - how screen reader reads content to check e.g. header order, button labels or missing descriptions.

-

Yes

Responsiveness in practice - technical verification of different page sizes, in terms of whether elements don't overlap, disappear or act strangely on different devices.

-

Yes

Error message operation - assessment whether error messages in forms are understandable, visible and accessible to screen readers.

-

Yes

Headers analysis - helps assess page structure and its accessibility for people using screen readers. Headers should be logically ordered, unique and well described to facilitate navigation.

Presence of top-level header

Yes

Yes

Header hierarchy (correct order)

Yes

Yes

Top-level header uniqueness

Yes

Yes

Existence of empty headers

Yes

Yes

Images analysis - ALT tags in images are crucial for accessibility because they describe graphic content to users who cannot see it, e.g. blind people using screen readers. ALT is also important in case of image loading problems – then instead of empty space, a description appears.

Alternative text existence

Yes

Yes

Decorative images verification

Yes

Yes

Link descriptions verification

Yes

Yes

Description for content-rich images

Yes

Yes

Information transmission through background-image verification

Yes

Yes

Image optimization check

Yes

Yes

Links analysis - links as an important navigation element should be unambiguous, readable and accessible to all users, including people using screen readers and keyboard navigation. Link analysis includes checking their content, attribute correctness and compliance with accessibility principles.

Links with no content

Yes

Yes

Links with href="#"

Yes

Yes

Links with href="javascript:void(0)"

Yes

Yes

Links with no alternative text

Yes

Yes

Links with ambiguous content

Yes

Yes

Forms analysis - forms on websites should be accessible to all users, including people using screen readers and navigating with keyboard. Analysis includes correctness of field markings, labels and button accessibility.

'input' and 'textarea' fields without 'label'

Yes

Yes

'label' tags without 'for' or for not matching field 'id'

Yes

Yes

'button' and 'submit' buttons without content

Yes

Yes

Required fields without proper marking

Yes

Yes

Fields with placeholder instead of label

Yes

Yes

Tables analysis - tables are used to present data in an organized way. To be accessible, they must be properly marked and readable for assistive technologies. Table analysis includes checking their structure, header markings and compliance with WCAG principles.

'caption' presence in table

Yes

Yes

Proper header and row marking in tables

Yes

Yes

Proper header connection with table rows

Yes

Yes

Using tables not for graphic layouts

Yes

Yes

Keyboard accessibility analysis - keyboard accessibility is a key WCAG aspect that allows users to navigate the page without using a mouse. Websites should be fully operable via keyboard, and interactive elements should have logical navigation order.

Tabindex presence in interactive elements

Yes

Yes

Verification of keyboard-inaccessible elements

Yes

Yes

Verification of elements interfering with keyboard use

Yes

Yes

ARIA elements keyboard accessibility

Yes

Yes

Buttons analysis - buttons are key elements of user interaction with the page. They must be properly marked and accessible so that users using screen readers and keyboard navigation can operate them correctly.

Proper button description using ARIA

Yes

Yes

Verification of buttons read by screen readers

Yes

Yes

Proper button description at role level

Yes

Yes

No button hiding through ARIA

Yes

Yes

Meta tags analysis - meta tags help both users and assistive technologies recognize page content and function. Lack of appropriate tags can negatively affect readability, accessibility and site perception in search engines.

Page description through meta title

Yes

Yes

Title length verification

Yes

Yes

Additional page description occurrence

Yes

Yes

Additional description length verification

Yes

Yes

Meta viewport existence

Yes

Yes