{"id":1787,"date":"2026-10-20T12:51:12","date_gmt":"2026-10-20T10:51:12","guid":{"rendered":"https:\/\/cms.fauves.agency\/?p=1787"},"modified":"2026-10-28T15:56:07","modified_gmt":"2026-10-28T14:56:07","slug":"is-a-compliant-website-really-accessible","status":"publish","type":"post","link":"https:\/\/cms.fauves.agency\/en\/index.php\/2026\/10\/20\/is-a-compliant-website-really-accessible\/","title":{"rendered":"Is a compliant website really accessible?"},"content":{"rendered":"<p><strong>I still often see accessibility treated as a final step: an audit is commissioned, the reported issues are fixed, and the website is then considered accessible.<\/strong> That is a good start. But, for me, it is not enough proof.<\/p>\n<p>A website can meet a large proportion of the WCAG success criteria and still be frustrating, confusing or impossible to use for a disabled person. When I work on a website, I am interested in a more practical question: can someone find the information, understand what is expected of them and complete what they came to do without having to ask for help?<\/p>\n<p>That distinction guides how I approach accessible website design. Standards provide an essential framework. But they cannot replace observing how people actually use a service.<\/p>\n<h2>Accessible website design: why I do not stop at WCAG compliance<\/h2>\n<p>The <a href=\"https:\/\/www.w3.org\/WAI\/standards-guidelines\/wcag\/\" target=\"_blank\" rel=\"noopener noreferrer\">WCAG<\/a> have given teams, organisations and regulators a shared language. They provide specific reference points: text alternatives, keyboard navigation, contrast, heading structure, error messages, focus states and text resizing. Without that framework, everyone would decide for themselves what is acceptable.<\/p>\n<p>So I do not set them against user experience. On the contrary, they are the foundation I aim to build in from the design stage. But a standard checks conditions. It cannot, by itself, experience an entire user journey.<\/p>\n<p>An element may be technically keyboard accessible while the tab order remains illogical. Text may be enlarged without the page remaining genuinely readable or usable. A form may follow the markup rules and still leave someone without a clear answer when an error occurs. Compliance is a necessary minimum. It does not automatically guarantee usability.<\/p>\n<h2>What tools and audits do not tell me<\/h2>\n<p>Automated tools are useful. They help identify recurring defects quickly, monitor quality over time and prevent some obvious regressions from reaching production.<\/p>\n<p>But they read code and rules, not lived situations. They cannot tell whether a button label is ambiguous, a modal provides enough context, form errors are understandable, or someone can actually complete a task with the tools they normally use.<\/p>\n<p>That is why I do not limit the question to, \u201cdoes the page pass?\u201d. The useful question is: \u201ccan someone complete the action that matters without relying on outside help?\u201d<\/p>\n<h2>The ways of using a service that I try not to overlook<\/h2>\n<p>When people discuss accessibility, they often first think of blind and partially sighted people. That is essential, but the subject is broader. An interface can also create barriers for deaf and hard-of-hearing people, people with reduced mobility, cognitive or learning difficulties, or people who use assistive technologies.<\/p>\n<p>I also try not to reduce the issue to permanent situations. Someone with an arm in a cast, a parent holding a child, or a person looking at their phone in noise or bright sunlight may encounter a context-related barrier. That does not minimise disability. It is a reminder that a service designed for different ways of using it is usually more robust for everyone.<\/p>\n<p>In practice, this means not depending on a single gesture, sense or speed of interaction. An important action should be possible with a keyboard as well as a pointer, with understandable labels, sufficient time and clear feedback about what has just happened.<\/p>\n<h3>Movement should help, not demand attention<\/h3>\n<p>I am not trying to remove every animation. A transition can explain that a panel has opened or that a form has been submitted. But continuous, automatic or decorative movement can distract from the task and make concentration more difficult for some people.<\/p>\n<p>The <code>prefers-reduced-motion<\/code> system preference makes it possible to offer a calmer version to someone who has chosen to reduce animations on their device. For me, the right question is simple: does this movement help someone understand, or does it demand attention without providing useful information?<\/p>\n<h2>I test a journey, not just a page<\/h2>\n<p>For an organisation, the useful question is rarely, \u201cis our website accessible?\u201d. I prefer to ask: can someone actually complete the tasks that matter? Find important information, compare an offer, contact the organisation, fill in and correct a form, book, pay or follow up a request.<\/p>\n<p>This approach exposes what an isolated page can easily hide: implicit instructions, poorly announced changes of context, vague buttons, errors that are hard to correct, or steps that depend on visual information alone.<\/p>\n<p>Testing with disabled people can reveal these barriers in very concrete ways. It does not replace a serious WCAG assessment, just as a single person\u2019s feedback cannot represent every way of using a service. The <a href=\"https:\/\/www.w3.org\/WAI\/test-evaluate\/involving-users\/\" target=\"_blank\" rel=\"noopener noreferrer\">W3C recommends combining<\/a> the involvement of people concerned with conformance evaluation. That combination seems the most honest approach to me.<\/p>\n<h2>Why I prefer to discuss cost at the start of a project<\/h2>\n<p>Taking accessibility seriously takes time, skills and sometimes a dedicated budget. Building robust components, reviewing content, testing with a keyboard, fixing forms and checking critical journeys are part of the work. Bringing in an independent body for an audit, or organising tests with disabled people, also adds a cost.<\/p>\n<p>I prefer to say that from the outset rather than presenting accessibility as an easy option to add at the end. An independent audit, such as those offered by <a href=\"https:\/\/anysurfer.be\/en\/services\/audits\" target=\"_blank\" rel=\"noopener noreferrer\">AnySurfer<\/a>, is a paid expert assessment service. Usability testing has a separate budget: scenarios must be prepared, participants recruited and paid, sessions facilitated, findings analysed and then addressed.<\/p>\n<p>That does not mean every website must immediately fund a label or a full user study. The appropriate level of effort depends on the service, its audience, the risks and the applicable obligations. But the choice should be deliberate. Leaving the issue until the end often means discovering structural problems when they are more expensive to fix.<\/p>\n<p>In Belgium, digital accessibility is already a legal obligation for public-sector services. Since 28 June 2025, some consumer-facing private services, including e-commerce, have also been covered by new European requirements. These obligations do not simply depend on the size of a business: they depend on the service offered and the intended audience. The <a href=\"https:\/\/economie.fgov.be\/fr\/themes\/entreprises\/guidance\/accessibilite\/accessibilite-guidelines-pour-0\" target=\"_blank\" rel=\"noopener noreferrer\">Federal Public Service Economy guidance<\/a> explains, among other things, the framework that applies to e-commerce in Belgium.<\/p>\n<h2>What I take from WCAG and AnySurfer<\/h2>\n<p>WCAG 2.2 remains a very useful quality baseline today. The work under way on WCAG 3 also points to an interesting shift: more attention to users\u2019 functional needs and the outcomes they need to achieve, rather than only a list of technical checks.<\/p>\n<p>I also value AnySurfer\u2019s approach in Belgium because it connects the skills of the teams, the quality of the delivered product and the client\u2019s ability to maintain that quality over time. An interface does not stay accessible by magic once it is live. Content changes, new features appear and teams change.<\/p>\n<p>In 2023, I completed AnySurfer\u2019s <i>Web accessibility training for developers<\/i>. Not to present myself as an all-knowing expert, but to better understand my responsibilities as a developer and keep improving my practice.<\/p>\n<h2>How I approach accessibility at Fauves<\/h2>\n<p>I do not see accessibility as a perfect state that can be reached once and for all. It is ongoing attention: checking, correcting, learning and doing better at every stage.<\/p>\n<ul>\n<li><strong>Define the critical journeys.<\/strong> Identify the tasks that must not leave anyone behind.<\/li>\n<li><strong>Design with accessible principles.<\/strong> Plan robust components, understandable content, visible states and consistent navigation.<\/li>\n<li><strong>Check regularly.<\/strong> Combine manual review, automated tests and checks against the relevant WCAG criteria.<\/li>\n<li><strong>Test when the project warrants it.<\/strong> Observe concrete tasks with people concerned and incorporate their feedback early enough to make changes.<\/li>\n<li><strong>Maintain quality.<\/strong> Train the people who publish content, document decisions and recheck changes to the website.<\/li>\n<\/ul>\n<p>At Fauves, I want to keep making this approach more concrete, more verifiable and more sustainable, including by starting the steps needed to obtain an AnySurfer label.<\/p>\n<h2>Key takeaway<\/h2>\n<p>A compliant website is better than a non-compliant one. But a genuinely accessible website is not judged by its code compliance alone. It is judged by whether people, in all their diversity, can understand, navigate and take action without encountering unnecessary barriers.<\/p>\n<p>Standards point the way. The people concerned tell us whether we have got there.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>WCAG compliance is essential, but it does not by itself prove that someone can use a service independently.<\/p>\n","protected":false},"author":1,"featured_media":1788,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[105],"tags":[],"class_list":["post-1787","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-experience"],"acf":{"related_posts":null,"selected_cta_key":""},"rank_math_meta":{"rank_math_seo_score":"59","rank_math_title":"Accessible website design: is compliance enough?","rank_math_description":"Website accessibility is about more than WCAG compliance. I explain what I check to make sure a user journey remains genuinely usable.","rank_math_focus_keyword":"accessible website design","rank_math_facebook_title":"Accessible website design: is compliance enough?","rank_math_facebook_description":"Website accessibility is about more than WCAG compliance. I explain what I check to make sure a user journey remains genuinely usable.","rank_math_twitter_title":"Accessible website design: is compliance enough?","rank_math_twitter_description":"Website accessibility is about more than WCAG compliance. I explain what I check to make sure a user journey remains genuinely usable."},"selected_cta":[],"wpml_current_locale":"en_US","wpml_translations":{"fr_FR":{"locale":"fr_FR","id":1774,"slug":"site-conforme-vraiment-accessible","post_title":"Un site conforme est-il vraiment accessible ?","href":"https:\/\/cms.fauves.agency\/index.php\/2026\/10\/20\/site-conforme-vraiment-accessible\/"}},"_links":{"self":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1787?lang=en"}],"collection":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts?lang=en"}],"about":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/types\/post?lang=en"}],"author":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/users\/1?lang=en"}],"replies":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/comments?lang=en&post=1787"}],"version-history":[{"count":2,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1787\/revisions?lang=en"}],"predecessor-version":[{"id":1795,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1787\/revisions\/1795?lang=en"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/media\/1788?lang=en"}],"wp:attachment":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/media?lang=en&parent=1787"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/categories?lang=en&post=1787"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/tags?lang=en&post=1787"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}