https://webpro.company/blog/tag/wcag/ Web accessibility under the WCAG standard — why it matters for all commercial websites, not just public-sector ones. en-US Thu, 18 Jun 2026 06:00:00 GMT https://webpro.company/blog/e-commerce-accessibility-after-2025-deadline https://webpro.company/blog/e-commerce-accessibility-after-2025-deadline Thu, 18 Jun 2026 06:00:00 GMT WCAG E-commerce Audit E-commerce accessibility is not only about colour contrast and image alt text. If a user cannot find a product, use the cart, complete payment or recover from a form error, the service is not really usable. From 28 June 2025, accessibility requirements apply to many services in Estonia and across the EU. The Estonian Consumer Protection and Technical Regulatory Authority explains that the requirements come from national legislation implementing the European Accessibility Act. For an online shop, the practical question is simple: can a person complete the service if they do not use a mouse, use a screen reader, zoom the page or make a mistake in a form? Do not test only the homepage Many accessibility checks start with the homepage. In e-commerce, the real risk is usually inside the… https://webpro.company/blog/website-accessibility-wcag-and-business-risk https://webpro.company/blog/website-accessibility-wcag-and-business-risk Sat, 25 Apr 2026 06:00:00 GMT WCAG An accessible website is not only about screen readers. It means that people can navigate, read, complete forms, finish purchases and ask for help. Accessibility is often invisible until someone cannot use the page. A button cannot be opened with a keyboard. A form does not explain what went wrong. Contrast is too weak. Checkout works with a mouse but not with assistive technology. Headings look correct visually, but the actual structure is broken. These problems do not affect only people with permanent disabilities. The same website must work for a person with an injured hand, reduced vision, a phone used in bright light, no ability to listen to audio or a form that is simply too hard to understand. Who should care Accessibility matters to public sector organisations, healthcare,… https://webpro.company/blog/european-accessibility-act-online-shops https://webpro.company/blog/european-accessibility-act-online-shops Tue, 10 Feb 2026 06:00:00 GMT E-commerce WCAG The European Accessibility Act turns accessibility into a practical business requirement for many services, not only a goodwill topic. What to check in an online shop The European Accessibility Act covers, among other things, e-commerce and digital services. For an online shop, the purchase journey must be usable for people with different needs. Check: menus, search and filters with a keyboard; readability of product information, price and availability; cart and form error messages; clarity of payment and delivery choices; contrast, focus and button size. Why technical testing is necessary A visually polished shop can still fail accessibility testing. The most common problems appear in dynamic parts: filters, carts, modals, forms and payment flows. WebPro can check these areas with… https://webpro.company/blog/wcag-22-practical-guide https://webpro.company/blog/wcag-22-practical-guide Tue, 03 Feb 2026 06:00:00 GMT WCAG WCAG 2.2 changes are practical: users must be able to move, complete forms and recover from mistakes without the interface blocking them. What WCAG 2.2 emphasises WCAG 2.2 adds criteria related to visible focus, dragging alternatives, target size and input assistance. In a practical check, review: whether keyboard navigation follows a logical order; whether focus is visible and does not disappear inside modals; whether buttons and links are large enough; whether form errors are understandable; whether critical actions are not mouse-only. Why business should care Accessibility is not only a public-sector requirement. If the checkout, enquiry form or self-service flow does not work with assistive technology, the company loses users and increases legal risk. WebPro audit and testing helps… https://webpro.company/blog/drupal-for-public-sector https://webpro.company/blog/drupal-for-public-sector Thu, 10 Jul 2025 06:00:00 GMT Drupal WCAG GDPR Government and education websites have specific requirements: WCAG accessibility, data protection, long-term support and open source. Drupal meets all of them. Public sector websites are not simply marketing pages. They must be accessible to all users regardless of disability, operate for years without platform replacement, comply with data protection requirements, and be developable through competitive procurement — which means open source. Why Drupal, not other CMS platforms Open source with no licence costs. Drupal is distributed under the GNU GPL licence — government and public sector institutions pay no licence fees. The platform code is auditable, which matters in security assessment contexts. WCAG accessibility. Drupal supports WCAG 2.1 AA in Core and in most widely used themes.… https://webpro.company/blog/european-accessibility-act-2025 https://webpro.company/blog/european-accessibility-act-2025 Thu, 03 Apr 2025 06:00:00 GMT WCAG E-commerce The European Accessibility Act is no longer a future concern — it is in force. Here is what every online store needs to know. European Parliament and Council Directive 2019/882, known as the European Accessibility Act (EAA), entered into force in member state legislation in June 2025. From that date, online stores and certain digital services are required to meet accessibility requirements. Who the EAA applies to The EAA applies to: E-commerce services (online stores) Banking and financial services Transport services Telecommunications services Media services If you sell goods or services to EU consumers online, the EAA applies to you. Exception: Microenterprises (fewer than 10 employees and annual turnover under €2 million) are exempt in certain cases. What accessibility means in… https://webpro.company/blog/screen-reader-testing-practice https://webpro.company/blog/screen-reader-testing-practice Wed, 06 Mar 2024 06:00:00 GMT WCAG Testing WCAG checklists and automated tools are a good start — but screen reader testing shows what actually works and what does not. Why screen reader testing is necessary Automated accessibility tools (axe, Lighthouse, WAVE) check code structure — whether alt texts exist, whether headings are in order, whether colour contrast meets the standard. This covers roughly 30% of accessibility issues. The remaining 70% — whether navigation is logical, whether focus moves sensibly, whether modal dialogs behave as expected, whether dynamic content is accessible — can only be discovered through real use. Screen reader testing shows the site as a user who does not use a mouse experiences it. Which screen readers exist NVDA (Windows, free) — the most widely used screen reader on Windows. Ideal for… https://webpro.company/blog/accessibility-audit-what-it-covers https://webpro.company/blog/accessibility-audit-what-it-covers Tue, 13 Feb 2024 06:00:00 GMT WCAG Audit An accessibility audit is more than looking at a Lighthouse score. Here is what a professional audit covers and what you receive as a result. Why automated testing alone is not enough Automated tools (axe, Lighthouse, WAVE) are fast and useful — but they find only about 30% of accessibility issues. The rest require human judgement: Does alt text describe the image or just say "image"? Does the error message explain what went wrong? Is navigation logical to a screen reader user? Is the focus order sensible? What an accessibility audit covers Automated scan Automated tests (axe-core, Lighthouse) are run across all main pages. This gives a quick overview and a baseline. Keyboard navigation The entire site is tested without a mouse. Checked: Can every interactive element be reached with… https://webpro.company/blog/color-contrast-and-font-accessibility https://webpro.company/blog/color-contrast-and-font-accessibility Thu, 18 Jan 2024 06:00:00 GMT WCAG UX Colour contrast is one of the most important and measurable aspects of accessibility. Here are the requirements, tools and common mistakes. Why colour contrast matters Roughly 8% of men and 0.5% of women have some form of colour blindness. Many older users also have reduced contrast sensitivity. Low-contrast text affects even people with normal vision when reading a screen in bright sunlight. Colour contrast is not just an accessibility question — it is a readability question. WCAG contrast requirements Level AA (minimum): Normal text (below 18pt): contrast ratio of at least 4.5:1 Large text (18pt+ or bold 14pt+): contrast ratio of at least 3:1 UI components (buttons, input field borders): at least 3:1 Level AAA (higher standard): Normal text: at least 7:1 Large text: at least 4.5:1…