<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>Accessibility Developer Guide</title>
        <link>https://www.accessibility-developer-guide.com</link>
        <description></description>
        <lastBuildDate>Thu, 05 Mar 2026 13:15:02 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <image>
            <title>Accessibility Developer Guide</title>
            <url>https://www.accessibility-developer-guide.com/img/logo/adg.svg</url>
            <link>https://www.accessibility-developer-guide.com</link>
        </image>
        <copyright>MIT</copyright>
        <item>
            <title><![CDATA[Widgets simply working for all]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/semantics/widgets</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/semantics/widgets</guid>
            <pubDate>Thu, 05 Mar 2026 13:15:02 GMT</pubDate>
            <description><![CDATA[HTML supports interactive controls for most requirements. But what about additional interaction patterns that do not offer an HTML equivalent? The key is to use semantic HTML and standard controls where possible, enhance them with ARIA when needed, style them with CSS, and add interactivity with JavaScript. This approach leverages native browser behavior and ensures widgets work for everyone.]]></description>
        </item>
        <item>
            <title><![CDATA[Legal requirements for accessibility]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/legal</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/legal</guid>
            <pubDate>Thu, 05 Mar 2026 07:49:06 GMT</pubDate>
            <description><![CDATA[While ensuring that everyone can participate in the digital world remains a fundamental moral imperative, an increasing number of countries now enforce accessibility through comprehensive legislation, transforming inclusive design from a voluntary "nice-to-have" into a mandatory requirement for digital products and services.]]></description>
        </item>
        <item>
            <title><![CDATA[European Accessibility Act]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/legal/eaa</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/legal/eaa</guid>
            <pubDate>Thu, 05 Mar 2026 07:49:06 GMT</pubDate>
            <description><![CDATA[The European Accessibility Act (EAA) is a key piece of EU legislation designed to harmonise accessibility requirements across all member states. Its purpose is to ensure that people with disabilities can access products and services independently, both in physical and digital environments.]]></description>
        </item>
        <item>
            <title><![CDATA[Configuring VMware Fusion on macOS]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/windows/vmware-on-macos</link>
            <guid>https://www.accessibility-developer-guide.com/setup/windows/vmware-on-macos</guid>
            <pubDate>Tue, 03 Mar 2026 12:00:42 GMT</pubDate>
            <description><![CDATA[On macOS, running Windows as a virtual machine needs some special configuration, especially to integrate it seamlessly into the daily workflow. Once properly set up, accessibility testing on macOS will be as comfortable as it gets.]]></description>
        </item>
        <item>
            <title><![CDATA[Tablist widgets (or: tab panels, tabs)]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/tablists</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/tablists</guid>
            <pubDate>Thu, 05 Feb 2026 13:19:48 GMT</pubDate>
            <description><![CDATA[Tablists are used to divide complex page content into smaller, more manageable sections. Each section is represented by a tab label that allows users to display one panel at a time. In this sense, tablists can be understood as small, self-contained page fragments within a larger page.]]></description>
        </item>
        <item>
            <title><![CDATA[Colours and contrast]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast</guid>
            <pubDate>Thu, 04 Dec 2025 10:36:37 GMT</pubDate>
            <description><![CDATA[Visual elements like for example text, icons, input fields and charts need to be easily perceivable. On the most basic level that means that they have to clearly stand out from their background. But it's also important that they can be easily distinguished from similar elements around them – for example links embedded in a text paragraph.]]></description>
        </item>
        <item>
            <title><![CDATA[ARIA - when HTML simply is not enough]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/aria</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/aria</guid>
            <pubDate>Thu, 04 Dec 2025 10:36:37 GMT</pubDate>
            <description><![CDATA[There are indeed situations where standard HTML does not provide functionalities for all the requirements developers may have for implementing modern and interactive websites. For this, the Accessible Rich Internet Applications (ARIA) technical specification was introduced. In this chapter, we introduce how it is purposely used, show its potential as well as its shortcomings (and alternatives, if needed).]]></description>
        </item>
        <item>
            <title><![CDATA[Introduction to keyboard only usage]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/keyboard-only</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/keyboard-only</guid>
            <pubDate>Thu, 04 Dec 2025 10:36:37 GMT</pubDate>
            <description><![CDATA[Due to physical restrictions, many users cannot control a pointing device like a mouse or touch screen. So they rely on keyboard usage only, and thus, software must be fully functional with a keyboard only. In this chapter, you will learn everything you need to know about browsing websites using a keyboard only.]]></description>
        </item>
        <item>
            <title><![CDATA[Semantics and their importance for accessibility]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/semantics</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/semantics</guid>
            <pubDate>Thu, 04 Dec 2025 10:36:37 GMT</pubDate>
            <description><![CDATA[While today's trend goes for more and more fancy visuals everywhere, it is still important to mark up content with proper HTML. In this chapter, you will get familiar with the concept of "semantics", and why they are indispensable in website development.]]></description>
        </item>
        <item>
            <title><![CDATA[Web Components]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/web-components</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/web-components</guid>
            <pubDate>Thu, 04 Dec 2025 10:36:37 GMT</pubDate>
            <description><![CDATA["Web Components" is an umbrella term for three main technologies: Custom elements, shadow DOM and HTML templates. Using these technologies allows us to create reusable, optionally encapsulated components. There are some important caveats regarding accessibility we need to keep in mind when authoring web components.]]></description>
        </item>
        <item>
            <title><![CDATA[How to read websites using a mobile screen reader]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/mobile/reading-websites</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/mobile/reading-websites</guid>
            <pubDate>Tue, 05 Aug 2025 16:23:07 GMT</pubDate>
            <description><![CDATA[For a sighted person, it’s hard to imagine how a screen reader user surfs the internet. For a web developer with accessibility in mind, it’s crucial to have a basic knowledge about this topic. So be ready to get a concrete idea of the main strategies available to read a website using a mobile screen reader!]]></description>
        </item>
        <item>
            <title><![CDATA[Marking elements as the current one using aria-current]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/current</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/current</guid>
            <pubDate>Fri, 13 Jun 2025 12:21:25 GMT</pubDate>
            <description><![CDATA[ARIA provides an attribute which allows to mark an element in a set of elements as the current one.]]></description>
        </item>
        <item>
            <title><![CDATA[Grouping form controls with fieldset and legend]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/grouping-with-fieldset-legend</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/grouping-with-fieldset-legend</guid>
            <pubDate>Wed, 04 Jun 2025 20:38:17 GMT</pubDate>
            <description><![CDATA[Grouping form controls in a meaningful way can make them much easier to handle for everyone. While most controls can be grouped, some must be grouped. The fieldset/legend structure is available for exact that - it can even be nested. And if its visual limitations are a problem, ARIA can be of help.]]></description>
        </item>
        <item>
            <title><![CDATA[Placing non-interactive content between form controls]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/non-interactive-content</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/non-interactive-content</guid>
            <pubDate>Thu, 03 Apr 2025 09:34:24 GMT</pubDate>
            <description><![CDATA[Screen reader interaction with forms usually happens in focus mode. So if there are any non-interactive elements (like a paragraph) in the form, they are prone to be missed. To prevent this, they need to be attached specifically to the form controls. There are several ways to achieve this goal.]]></description>
        </item>
        <item>
            <title><![CDATA[Adding descriptions to elements using aria-describedby]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/describedby</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/describedby</guid>
            <pubDate>Sat, 12 Oct 2024 21:57:32 GMT</pubDate>
            <description><![CDATA[ARIA provides an attribute which allows to attach other elements as descriptions to an element. They work pretty non-uniformly in modern browsers and screen readers, and as such they must be used with extreme caution.]]></description>
        </item>
        <item>
            <title><![CDATA[Spanning multiple rows and columns]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/spanning-rows-cols</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/spanning-rows-cols</guid>
            <pubDate>Sun, 28 Jul 2024 19:25:39 GMT</pubDate>
            <description><![CDATA[Spanning rows and columns is a standard HTML feature and exists for decades already. Be sure not to overuse them though, as they can be tricky for screen readers, especially in complex data tables. And in general: keep your tables simple.]]></description>
        </item>
        <item>
            <title><![CDATA[Privacy Policy]]></title>
            <link>https://www.accessibility-developer-guide.com/introduction/privacy-policy</link>
            <guid>https://www.accessibility-developer-guide.com/introduction/privacy-policy</guid>
            <pubDate>Thu, 25 Jul 2024 07:49:47 GMT</pubDate>
            <description><![CDATA[In order for us to provide you the best possible experience on our guide, we need to collect and process certain information.]]></description>
        </item>
        <item>
            <title><![CDATA[PDF Accessibility Checker]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/pdf-accessibility-checker</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/pdf-accessibility-checker</guid>
            <pubDate>Sun, 05 May 2024 20:33:42 GMT</pubDate>
            <description><![CDATA[The PDF Accessibility Checker (PAC) provides a fast way to test the accessibility of PDF files. On one hand, it checks whether the PDF/UA standard is met. On the other hand, it offers a great preview feature that visually displays the document similar to the way a screen reader perceives it, making it easy to spot problems in both sequence and meaning of elements.]]></description>
        </item>
        <item>
            <title><![CDATA[Total Validator]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/totalvalidator</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/totalvalidator</guid>
            <pubDate>Sun, 05 May 2024 20:33:42 GMT</pubDate>
            <description><![CDATA[Total Validator checks your website regarding various web and accessibility standards by the press of a button. Building valid code is one of the highest goals developers should strive for. Total Validator helps a lot with achieving this.]]></description>
        </item>
        <item>
            <title><![CDATA[Relevant combinations of screen readers and browsers]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/relevant-combinations</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/relevant-combinations</guid>
            <pubDate>Fri, 05 Apr 2024 14:11:12 GMT</pubDate>
            <description><![CDATA[To reach as many users as possible, it's a pragmatic approach to support the most widely used combinations of browsers and screen readers. Here you learn, which those are. Other requirements may only apply in closed environments that are only open to a specific, deterministic group of users.]]></description>
        </item>
        <item>
            <title><![CDATA[Responsive tables]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/responsive</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/responsive</guid>
            <pubDate>Thu, 04 Apr 2024 07:30:52 GMT</pubDate>
            <description><![CDATA[The introduction of smartphones increasingly led web designers to avoid traditional "bulky" HTML tables - because these would exceed the limited screen dimensions. Others tried to find ways to change the layout of tables so they would not need so much horizontal space anymore. Responsive tables were born. But to make them accessible, the use of some ARIA is essential.]]></description>
        </item>
        <item>
            <title><![CDATA[Semantics provide meaning]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/semantics/meaning</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/semantics/meaning</guid>
            <pubDate>Thu, 07 Mar 2024 13:53:09 GMT</pubDate>
            <description><![CDATA[Not surprisingly, HTML (Hyper Text Markup Language) is exactly that: a markup language. This means that it is not only plain text, but text marked up with meaning - so called "semantics". For this, HTML offers a lot of tags, each with an inherent, unique semantic meaning. And it is absolutely crucial that those tags are used properly.]]></description>
        </item>
        <item>
            <title><![CDATA[Accessibility helper tools]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Beneath big players like browsers and screen readers, there is a vast number of software that helps in developing accessible websites. In this chapter, you will find a collection of our favourite helper tools. Some of them are third party software, others are integrated into Windows.]]></description>
        </item>
        <item>
            <title><![CDATA[HTML 5's headings outline algorithm]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings/html-5-outline</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings/html-5-outline</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[The idea behind HTML 5's heading algorithm is great: it promises to offer valid and highly accessible heading outlines that can be much easier to implement than traditional ones. Sadly, it was never really picked up by any browser or screen reader, and the HTML 5.2 draft advises against using it any further.]]></description>
        </item>
        <item>
            <title><![CDATA[Chrome installation and configuration]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/chrome</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/chrome</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Being the favourite browser of many web developers anyway, Chrome also has some nice features and extensions that are useful in the daily accessibility workflow.]]></description>
        </item>
        <item>
            <title><![CDATA[Microsoft Edge installation and configuration]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/edge</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/edge</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Edge replaces Microsoft's legacy browser Internet Explorer 11 (IE 11) and is based on the same Chromium open-source code base as Google Chrome.]]></description>
        </item>
        <item>
            <title><![CDATA[Firefox installation and configuration]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/firefox</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/firefox</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Being one of the most sympathetic browsers available, Firefox (FF) is widely used and loved by people with special needs, especially technology-adept ones. One of FF's main characteristics is its high conformance regarding web standards, including those related to accessibility.]]></description>
        </item>
        <item>
            <title><![CDATA[Bookmarklets]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/bookmarklets</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/bookmarklets</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Bookmarklets are bookmarks that contain JavaScript instead of a URL. You can execute them while reading a webpage, and they typically do some quick analysis and display their results.]]></description>
        </item>
        <item>
            <title><![CDATA[Colour Contrast Analyser]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/colour-contrast-analyser</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/colour-contrast-analyser</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Having sufficient contrast between foreground and background colours is an essential part of usability in general and accessibility in particular. The Colour Contrast Analyser (CCA) is a tool that calculates the contrast between two colours and automatically evaluates the returned value against the Web Content Accessibility Guidelines.]]></description>
        </item>
        <item>
            <title><![CDATA[Browser extensions]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Browser extensions are software modules for customizing and extending a web browser. Browsers typically allow users to install a variety of extensions, including those that make development and testing easier.]]></description>
        </item>
        <item>
            <title><![CDATA[Windows High Contrast Mode]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/high-contrast-mode</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/high-contrast-mode</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Windows high contrast mode (Win HCM) changes the colours on the screen to a specific high-contrast scheme. It is used by visually impaired people. It is a useful tool to ensure that visual information is not conveyed with purely decorative styles.]]></description>
        </item>
        <item>
            <title><![CDATA[axe DevTools]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions/axe-devtools</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions/axe-devtools</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[An accessibility checker for developers, testers, and designers. Find and fix accessibility issues during website development.]]></description>
        </item>
        <item>
            <title><![CDATA[HeadingsMap]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions/headingsmap</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions/headingsmap</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[HeadingsMap generates an index of any web document structured with headings and sections. It shows the headings structure, the errors in the structure (ie. incorrect levels), and it works as HTML5 Outliner too.]]></description>
        </item>
        <item>
            <title><![CDATA[WAVE toolbar]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions/wave-toolbar</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions/wave-toolbar</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[WAVE toolbar gives you a very quick first impression about the quality of the current webpage’s accessibility. At the press of a button, it provides visual cues by injecting icons and detailed information right into the page.]]></description>
        </item>
        <item>
            <title><![CDATA[Web Developer toolbar]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions/web-developer-toolbar</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/browser-extensions/web-developer-toolbar</guid>
            <pubDate>Sat, 27 Jan 2024 12:50:00 GMT</pubDate>
            <description><![CDATA[Probably well known by most web developers already, the Web Developer toolbar extension adds various tools to the browser that are incredibly useful for all sorts of code inspection and debugging. It can sometimes even be seen as a screen reader substitute — if you know its limitations.]]></description>
        </item>
        <item>
            <title><![CDATA[Web browsers]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers</guid>
            <pubDate>Thu, 18 Jan 2024 21:12:44 GMT</pubDate>
            <description><![CDATA[For developing accessible websites, you need some common Windows web browsers. In this chapter, you will learn how to install and configure them. Additionally, we introduce some useful extensions that will support you in your daily routine.]]></description>
        </item>
        <item>
            <title><![CDATA[Windows operating system]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/windows</link>
            <guid>https://www.accessibility-developer-guide.com/setup/windows</guid>
            <pubDate>Thu, 18 Jan 2024 21:12:44 GMT</pubDate>
            <description><![CDATA[To ensure the accessibility of websites, the most important software is native Windows software, such as desktop screen readers. In this chapter, you will learn how to prepare everything for the upcoming installation tasks. And if you want to keep your own Windows working environment clean (or if you aren't using Windows anyway), we suggest you set up a dedicated Windows installation within a virtual machine.]]></description>
        </item>
        <item>
            <title><![CDATA[About this initiative]]></title>
            <link>https://www.accessibility-developer-guide.com/introduction/about</link>
            <guid>https://www.accessibility-developer-guide.com/introduction/about</guid>
            <pubDate>Thu, 18 Jan 2024 12:10:50 GMT</pubDate>
            <description><![CDATA[The «Accessibility Developer Guide», in its entirety, is the result of many years of hands-on practice in the field of testing websites for accessibility, as well as developing accessible web applications. The daily experience of user experts with special needs, blended together with the profound technical knowledge of fullstack web developers, resulted in forming the «Accessibility Alliance».]]></description>
        </item>
        <item>
            <title><![CDATA[How to use this guide]]></title>
            <link>https://www.accessibility-developer-guide.com/introduction/how-to-use</link>
            <guid>https://www.accessibility-developer-guide.com/introduction/how-to-use</guid>
            <pubDate>Tue, 02 Jan 2024 16:06:11 GMT</pubDate>
            <description><![CDATA[This guide aims to provide a comprehensive resource for both beginners looking for a pragmatic way to dive into the world of accessibility, as well as seasoned experts wanting to extend their knowledge and embrace new inspirations. Here you will find out how to read through our guide, and how to stay up to date.]]></description>
        </item>
        <item>
            <title><![CDATA[Screen readers]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/screen-readers</link>
            <guid>https://www.accessibility-developer-guide.com/setup/screen-readers</guid>
            <pubDate>Tue, 02 Jan 2024 16:06:11 GMT</pubDate>
            <description><![CDATA[Operating websites with screen readers is one of the most efficient techniques to ensure accessibility. For beginners, screen reader usage can be a bit confusing at first, especially if the software is not configured properly for testing purposes. In this chapter, you will learn how to install and configure both mobile and desktop screen readers in a way for you to use them conveniently.]]></description>
        </item>
        <item>
            <title><![CDATA[Contribute to this guide]]></title>
            <link>https://www.accessibility-developer-guide.com/contribution</link>
            <guid>https://www.accessibility-developer-guide.com/contribution</guid>
            <pubDate>Tue, 02 Jan 2024 12:57:04 GMT</pubDate>
            <description><![CDATA[This guide is the result of tight collaboration between accessibility experts and web developers. Its content by far is not exhaustive yet: there remain a lot of topics to talk about, and due to the fast evolution of web technologies, there certainly will always be.]]></description>
        </item>
        <item>
            <title><![CDATA[How to handle forms]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/handling</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/handling</guid>
            <pubDate>Tue, 02 Jan 2024 12:55:21 GMT</pubDate>
            <description><![CDATA[Forms consist of many interactive elements. To work through and understand the examples in this chapter, besides knowing keyboard only usage, it is good to have a screen reader at hand and know how to handle it. In addition to this, there are some tools and bookmarklets that can be a huge help in your development workflow.]]></description>
        </item>
        <item>
            <title><![CDATA[General bad headings example]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings/bad-example</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings/bad-example</guid>
            <pubDate>Tue, 02 Jan 2024 12:55:21 GMT</pubDate>
            <description><![CDATA[To be meaningful, heading outlines must be coherent on both a technical and textual level. While headings often are omitted completely by naive web developers, existing heading outlines can suffer of various accessibility problems on both a syntactical and a semantical level.]]></description>
        </item>
        <item>
            <title><![CDATA[How to handle headings]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings/handling</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings/handling</guid>
            <pubDate>Tue, 02 Jan 2024 12:55:21 GMT</pubDate>
            <description><![CDATA[Headings are solely browsable elements and do not offer any interactivity. To work through and understand the examples in this chapter, it is good to have a screen reader at hand and know how to handle it. In addition to this, there are some tools and bookmarklets that can be a huge help in your development workflow.]]></description>
        </item>
        <item>
            <title><![CDATA[How to handle tables]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/handling</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/handling</guid>
            <pubDate>Tue, 02 Jan 2024 12:55:21 GMT</pubDate>
            <description><![CDATA[Tables consist of solely browsable elements and do not offer any interactivity. To work through and understand the examples in this chapter, it is good to have a screen reader at hand and know how to handle it. In addition to this, there are some tools and bookmarklets that can be a huge help in your development workflow.]]></description>
        </item>
        <item>
            <title><![CDATA[Contents Structured]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/bookmarklets/contents-structured</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/bookmarklets/contents-structured</guid>
            <pubDate>Tue, 02 Jan 2024 12:55:21 GMT</pubDate>
            <description><![CDATA[This bookmarklet highlights a lot of typical semantic HTML elements, conveying their tag names. This makes inspection of the current page's semantic structure pretty easy.]]></description>
        </item>
        <item>
            <title><![CDATA[h123]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/bookmarklets/h123</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/bookmarklets/h123</guid>
            <pubDate>Tue, 02 Jan 2024 12:55:21 GMT</pubDate>
            <description><![CDATA[This bookmarklet provides an efficient way to display the current webpage's heading outline, very close to how screen readers do. In addition, it has some pretty useful features like displaying potentially incorrectly hidden headings.]]></description>
        </item>
        <item>
            <title><![CDATA[HTML_CodeSniffer]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools/bookmarklets/html-codesniffer</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools/bookmarklets/html-codesniffer</guid>
            <pubDate>Tue, 02 Jan 2024 12:55:21 GMT</pubDate>
            <description><![CDATA[This bookmarklet analyses the displayed page's HTML source and detects violations of the coding standard. It offers a huge amount of predefined rules and can be extended with custom rules.]]></description>
        </item>
        <item>
            <title><![CDATA[Indicating form controls as required using asterisks (*)]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/required</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/required</guid>
            <pubDate>Sat, 21 Oct 2023 15:31:22 GMT</pubDate>
            <description><![CDATA[Asterisk (*) next to a form control's label usually indicates it as "required". Oftentimes, this asterisk's purpose is then explained somewhere else on the page. Many users (especially screen reader users) may be confused with that, so make sure this information is easily accessible.]]></description>
        </item>
        <item>
            <title><![CDATA[Sticky table headers]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/sticky-headers</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/sticky-headers</guid>
            <pubDate>Thu, 19 Oct 2023 08:39:36 GMT</pubDate>
            <description><![CDATA[In some situations, table headers need to be placed at a specific place on screen, and remain there, even when scrolling. Especially when tables are very long, it is useful to make the table header sticky on top so visual users always see it, even when scrolling vertically.]]></description>
        </item>
        <item>
            <title><![CDATA[Getting a free Windows virtual machine from Microsoft]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/windows/virtual-machines</link>
            <guid>https://www.accessibility-developer-guide.com/setup/windows/virtual-machines</guid>
            <pubDate>Thu, 29 Jun 2023 07:05:54 GMT</pubDate>
            <description><![CDATA[Microsoft offers free Windows virtual machine images for development. This is the easiest way to get your needed Windows environment up and running quickly for testing purposes.]]></description>
        </item>
        <item>
            <title><![CDATA[NVDA installation and configuration]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/screen-readers/nvda</link>
            <guid>https://www.accessibility-developer-guide.com/setup/screen-readers/nvda</guid>
            <pubDate>Wed, 17 May 2023 16:43:19 GMT</pubDate>
            <description><![CDATA[NVDA (Non Visual Desktop Access) is a lightweight and reliable open source desktop screen reader. Because of its firm compliance to standards, it is the desktop screen reader of choice when developing accessible websites. After using it for a while, you will respect it as a firm but fair teacher.]]></description>
        </item>
        <item>
            <title><![CDATA[Changing a table's visual layout]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/layout-changes</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/layout-changes</guid>
            <pubDate>Sun, 26 Feb 2023 18:09:35 GMT</pubDate>
            <description><![CDATA[Sometimes it is necessary to style tables visually in a way that standard tables are not capable of. For example, with some CSS, it is possible to stack all cells of a table vertically on top of each other. This provides a lot of new ways of styling a table. But as this potentially also changes its semantics, ARIA must be used to ensure accessibility.]]></description>
        </item>
        <item>
            <title><![CDATA[The "table of divs" experiment]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/table-of-divs-experiment</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/table-of-divs-experiment</guid>
            <pubDate>Sun, 26 Feb 2023 18:09:35 GMT</pubDate>
            <description><![CDATA[Instead of using traditional HTML table elements, it is also possible to convert a structure of non-table elements into a table using ARIA. This is an experiment, and we explicitly do not recommend using this on productive websites. So please, kids, do not try this at home!]]></description>
        </item>
        <item>
            <title><![CDATA[VoiceOver/iOS configuration]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/screen-readers/voiceover-ios</link>
            <guid>https://www.accessibility-developer-guide.com/setup/screen-readers/voiceover-ios</guid>
            <pubDate>Thu, 26 Jan 2023 08:52:53 GMT</pubDate>
            <description><![CDATA[VoiceOver/iOS is the most advanced mobile screen reader. It is pre-installed on iOS devices, easy to understand, and the most used mobile screen reader in Western countries. Because of its reliable and easy activation shortcut, it is the mobile screen reader of choice when developing accessible websites.]]></description>
        </item>
        <item>
            <title><![CDATA[How to calculate colour contrast]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/how-to-calculate</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/how-to-calculate</guid>
            <pubDate>Thu, 26 Jan 2023 08:48:58 GMT</pubDate>
            <description><![CDATA[There is a mathematical formula to calculate the contrast ratio between two colours. Using this formula for contrast evaluation is always better than relying only on your eyes.]]></description>
        </item>
        <item>
            <title><![CDATA[Accordions]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/accordion</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/accordion</guid>
            <pubDate>Mon, 18 Oct 2021 09:31:08 GMT</pubDate>
            <description><![CDATA[Accordions contain of a number of content panels, each of wich can be expanded or collapsed vertically by the user.]]></description>
        </item>
        <item>
            <title><![CDATA[Sensible usage of ARIA roles and attributes]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage</guid>
            <pubDate>Wed, 22 Sep 2021 12:19:12 GMT</pubDate>
            <description><![CDATA[There are some ARIA roles and attributes that we use and recommend in our daily business, especially regarding JavaScript widgets. They are well supported by screen readers, and if you know their peculiarities, they can be very helpful in creating accessible websites. However, we often describe and recommend alternative techniques with traditional HTML.]]></description>
        </item>
        <item>
            <title><![CDATA[What is a "Proof of concept"?]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/proof-of-concept</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/proof-of-concept</guid>
            <pubDate>Wed, 22 Sep 2021 12:19:12 GMT</pubDate>
            <description><![CDATA[All our widgets are so called "Proofs of concepts" (POCs), meaning they show how an interaction pattern can be implemented in an accessible way. As such, they are intended to serve as inspiration for your own implementations, but are not meant to be copied 1:1 into real projects.]]></description>
        </item>
        <item>
            <title><![CDATA[The purpose behind the WAI-ARIA standard]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/aria/purpose</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/aria/purpose</guid>
            <pubDate>Wed, 22 Sep 2021 10:43:00 GMT</pubDate>
            <description><![CDATA[When it comes to requirements of modern interactive websites, sometimes the semantic vocabulary of HTML may not be enough anymore. To fill this gap, the Accessible Rich Internet Application (ARIA) specification was introduced: it describes how to add semantics to HTML content in order to make user controls and dynamic content more accessible. However, there are pitfalls you need to know about.]]></description>
        </item>
        <item>
            <title><![CDATA[How screen readers work - and why they seem so buggy]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/so-buggy</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/so-buggy</guid>
            <pubDate>Wed, 22 Sep 2021 10:43:00 GMT</pubDate>
            <description><![CDATA[Sitting on top of another application, screen readers announce the underlying content - often trying to compensate for inadequate presentation by both the underlying application (ie. browser) and its content (ie. website). This is a very hard task and prone to regressions, as we try to explain here.]]></description>
        </item>
        <item>
            <title><![CDATA[Hiding elements from all devices]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/hiding-elements/from-all-devices</link>
            <guid>https://www.accessibility-developer-guide.com/examples/hiding-elements/from-all-devices</guid>
            <pubDate>Fri, 20 Aug 2021 07:10:22 GMT</pubDate>
            <description><![CDATA[To hide an element from all devices means just that: no single device will perceive it anymore (although the element still is present in the DOM). This can be achieved using either an HTML attribute or CSS attributes.]]></description>
        </item>
        <item>
            <title><![CDATA[General good table example]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/good-example</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/good-example</guid>
            <pubDate>Tue, 25 May 2021 09:36:48 GMT</pubDate>
            <description><![CDATA[Tables are widely used to display tabular data, be it complex or simple. HTML provides for accessibility, so cleanly laid out and marked up tables are already fully accessible all by themselves.]]></description>
        </item>
        <item>
            <title><![CDATA[Internet Explorer 11 installation and configuration]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/internet-explorer-11</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/internet-explorer-11</guid>
            <pubDate>Mon, 22 Mar 2021 14:23:16 GMT</pubDate>
            <description><![CDATA[Microsoft's legacy browser (and every serious web developers' longtime nemesis) Internet Explorer 11 (IE 11) is not officially supported any more. See Edge for its successor.]]></description>
        </item>
        <item>
            <title><![CDATA[Configuring VMware Workstation Pro on Windows (and Linux)]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/windows/vmware-on-windows-linux</link>
            <guid>https://www.accessibility-developer-guide.com/setup/windows/vmware-on-windows-linux</guid>
            <pubDate>Mon, 22 Mar 2021 10:01:04 GMT</pubDate>
            <description><![CDATA[Even if you are already running Windows as your operating system, it is highly recommended making the initial effort needed to set up another Windows within a virtual machine, configured specifically for accessibility testing. This keeps your own system clean and makes accessibility testing much more comfortable.]]></description>
        </item>
        <item>
            <title><![CDATA[Why Windows is a must-have for accessible website development]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/windows/why</link>
            <guid>https://www.accessibility-developer-guide.com/setup/windows/why</guid>
            <pubDate>Mon, 22 Mar 2021 08:53:00 GMT</pubDate>
            <description><![CDATA[To ensure a website is accessible to as many users as possible, it is important to make sure it is working on the most widespread assistive software. At the time being, most users with special needs have Windows-specific software running. That's the reason why you need to have a Windows environment available to you, whether you like it or not.]]></description>
        </item>
        <item>
            <title><![CDATA[How to browse websites using a keyboard only]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/keyboard-only/browsing-websites</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/keyboard-only/browsing-websites</guid>
            <pubDate>Thu, 04 Feb 2021 20:31:56 GMT</pubDate>
            <description><![CDATA[Browsing a website (which means opening it, reading its content and interacting with the available controls) using a keyboard only is delightfully easy. Browsers offer all this functionality with only a few keys on the keyboard. And maybe you use most of those keys already on a daily basis.]]></description>
        </item>
        <item>
            <title><![CDATA[Marking elements expandable using aria-expanded]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/expanded</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/expanded</guid>
            <pubDate>Thu, 04 Feb 2021 20:30:27 GMT</pubDate>
            <description><![CDATA[ARIA provides an attribute which allows to describe the expandability status of an element. It works pretty uniformly in modern browsers and screen readers, and as such is a good solution for many situations where an element's visibility should can be toggled.]]></description>
        </item>
        <item>
            <title><![CDATA[Controlling a computer with a keyboard only]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/keyboard-only/controlling-a-computer</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/keyboard-only/controlling-a-computer</guid>
            <pubDate>Thu, 04 Feb 2021 20:30:09 GMT</pubDate>
            <description><![CDATA[Many users control a computer using keyboard only, so no mouse or similar pointing device is available. Thus, it's crucial that any software (including websites) is operable by keyboard only. This does not only benefit disabled users, but also power users.]]></description>
        </item>
        <item>
            <title><![CDATA[Visually hidden table headers]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/hidden-headers</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/hidden-headers</guid>
            <pubDate>Wed, 18 Nov 2020 20:25:49 GMT</pubDate>
            <description><![CDATA[Sometimes, table headers are not provided in the visual layout. This is feasible, as visual users often recognise the larger context of tables without the need for visual headers. For screen reader users though, table headers are always necessary.]]></description>
        </item>
        <item>
            <title><![CDATA[Dialog widget (or: modal, popup, lightbox, overlay, alert)]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/dialog</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/dialog</guid>
            <pubDate>Thu, 17 Sep 2020 05:26:55 GMT</pubDate>
            <description><![CDATA[Dialogs display some information on top of a page. They are typically used to react upon a user action, for example to display a notice or to ask for some input like confirming something. There are dialogs that disable the rest of the page in the background (modal), while others do not (non-modal).]]></description>
        </item>
        <item>
            <title><![CDATA[Basic structure of an accessible HTML file]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/html_boilerplate</link>
            <guid>https://www.accessibility-developer-guide.com/examples/html_boilerplate</guid>
            <pubDate>Wed, 01 Jul 2020 15:35:39 GMT</pubDate>
            <description><![CDATA[An HTML file has a clearly defined structure that allows any browser to render the content correctly. To make an HTML file accessible you need to know the basic structure and its roles.]]></description>
        </item>
        <item>
            <title><![CDATA[Examples of accessibility patterns]]></title>
            <link>https://www.accessibility-developer-guide.com/examples</link>
            <guid>https://www.accessibility-developer-guide.com/examples</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[There often exist various approaches to solving an accessibility requirement, but usually one specific solution stands out clearly. The chapters in this 4th part of our guide, the Examples part, contain our collection of such rock-solid and inspiring solutions. They are available as real-life code examples (ready for copy&paste), and as such can be executed and played with directly in the browser.]]></description>
        </item>
        <item>
            <title><![CDATA[Introduction to screen reader usage]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[To develop accessible modern websites, it's absolutely crucial to have basic skills in both reading and interacting with websites using screen readers. In this chapter, you will learn everything you need to know about using both mobile and desktop screen readers to browse the web.]]></description>
        </item>
        <item>
            <title><![CDATA[General bad form example]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/bad-example</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/bad-example</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Even in technically fully valid forms, there can be a lot messed up semantically, making it hardly accessible in many ways. Be it missing or improperly implemented elements - here we show the most common problems and explain them.]]></description>
        </item>
        <item>
            <title><![CDATA[General good form example]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/good-example</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/good-example</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Forms are widely used to accept user input, be it for transferring it to the server or to act upon it locally using some JavaScript. HTML provides for accessibility, so cleanly laid out and marked up form controls are already fully accessible all by themselves. Still, screen readers may sometimes announce specific elements a bit irritatingly.]]></description>
        </item>
        <item>
            <title><![CDATA[Grouping form controls with headings]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/grouping-with-headings</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/grouping-with-headings</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[It sometimes feels necessary to group complex forms visually using headings. As traditionally used headings are non-focusable elements, you have to make sure that they are not missed by screen reader users in focus mode.]]></description>
        </item>
        <item>
            <title><![CDATA[Forms within tables]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/in-tables</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/in-tables</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Sometimes it is necessary to have form controls within tables. And while tables provide their own labelling mechanism, it is important that each and every control still has its dedicated label.]]></description>
        </item>
        <item>
            <title><![CDATA[Validation messages]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/validation-messages</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/validation-messages</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Data submitted in a form is usually validated in some way. And if there is any unacceptable data, the form is traditionally re-displayed, together with validation messages. In such a case, it is important to immediately inform screen reader users, so they know that they have to look at their data and submit again.]]></description>
        </item>
        <item>
            <title><![CDATA[Adding visually hidden headings to complete a page's outline]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings/visually-hidden-headings</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings/visually-hidden-headings</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Not only the main content of a web page needs to be marked up using headings, but also other elements like header, navigation, footer, etc. As the visual design usually does not include those headings, they need to be visually hidden by moving them off-screen.]]></description>
        </item>
        <item>
            <title><![CDATA[Noticing screen readers using alert role]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/alert</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/alert</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[ARIA provides a role which makes screen readers announce an element immediately after its addition to the DOM (using JavaScript). While this works in most browsers and screen readers, it must be used with extreme caution as it interrupts the screen reader's current output.]]></description>
        </item>
        <item>
            <title><![CDATA[Labelling elements using aria-label and aria-labelledby]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/label-labelledby</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/label-labelledby</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[ARIA provides attributes which override the accessible label of an element. As they are treated differently in modern browsers and screen readers, they must be used with caution. They also have some noticeable side effects. There exist alternative techniques that are much more robust.]]></description>
        </item>
        <item>
            <title><![CDATA[Marking elements activatable using aria-pressed]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/pressed</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/pressed</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[ARIA provides an attribute which allows to mark an element as activatable. It works pretty uniformly in modern browsers and screen readers. Still, for most situations there exist alternative techniques that are more robust.]]></description>
        </item>
        <item>
            <title><![CDATA[Autosuggest widget (or: autocomplete, lookahead, typeahead)]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/autosuggest</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/autosuggest</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Autosuggests offer a number of possible values, usually presented as some sort of a dropdown element, allowing to select one. By entering a filter string, the possible values are filtered.]]></description>
        </item>
        <item>
            <title><![CDATA[Datepicker widget]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/datepicker</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/datepicker</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Datepickers are an easy and intuitive way to let users pick a date. They usually offer their options below their respective form control in a table-like design which can be toggled visible. Some date pickers also offer time settings.]]></description>
        </item>
        <item>
            <title><![CDATA[Dropdown widget (or: menu, pulldown)]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/dropdown</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/dropdown</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Dropdowns allow to toggle an element's visibility. They usually contain some sort of navigation, be it a bare list of links, or more complex elements. They can offer one to multiple nesting levels.]]></description>
        </item>
        <item>
            <title><![CDATA[Tooltip widgets (or: screen tip, balloon)]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/tooltips</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/tooltips</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Tooltips present information about a specific element in a small container on top of all other content. It is typically only displayed upon interacting with the related element in some way. Depending on the richness of its content, it is shown upon hovering or focusing the related element, or by manually toggling its visibility.]]></description>
        </item>
        <item>
            <title><![CDATA[Colour is not enough]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/colour-is-not-enough</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/colour-is-not-enough</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[The purpose of contrast is allowing people to see and distinguish different parts of an interface. Colour is an important factor in this context, but it has some clear limitations. That is why relying on colour alone is usually not a good strategy.]]></description>
        </item>
        <item>
            <title><![CDATA[How to implement websites that are ready for screen reader usage]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/how-to-implement</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/how-to-implement</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[If a website is optimised already for use with a keyboard only, it will also work in many respects with a screen reader. Still, some close attention needs to be paid, especially regarding semantics and custom interactivity.]]></description>
        </item>
        <item>
            <title><![CDATA[Screen readers process contents in a linear way using a cursor]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/linear-processing-using-cursor</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/linear-processing-using-cursor</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Sighted users perceive a webpage as a two-dimensional, graphical area. Meanwhile, screen reader users perceive a page in a one-dimensional (linear), textual way: one element after the other, from top to bottom. Similar to reading a book, browsing websites in this way is usually considerably slow, as a lot of time is needed to get a proper overview of a full page.]]></description>
        </item>
        <item>
            <title><![CDATA[Mobile screen readers]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/mobile</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/mobile</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Mobile screen readers are easy to understand and control. They offer a quick and pretty robust way of testing websites on accessibility, revealing many potential accessibility issues. As they are pre-installed on any modern smartphone and do not require a lot of configuration, they are pragmatic testing tools at call - especially for beginners.]]></description>
        </item>
        <item>
            <title><![CDATA[Screen readers do not convey visual attributes]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/no-visual-attributes</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/no-visual-attributes</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Similar to the reading of a traditional book, screen readers only announce plain content, enriched with semantical information. Visual attributes are totally ignored. Interestingly, some CSS still does have influence on screen readers.]]></description>
        </item>
        <item>
            <title><![CDATA[Desktop screen readers]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Desktop screen readers are rather complex to understand and control, as they offer many features and ways to interact with websites. Compared to mobile screen readers, they deliver a both broader and more detailed picture on the robustness of a website, revealing most potential accessibility issues. As such, they are indispensable testing tools.]]></description>
        </item>
        <item>
            <title><![CDATA[What screen readers are - and why they are so important to accessibility testing]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/what-and-why</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/what-and-why</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Blind people are only one of many groups of people with special needs. Still, to develop and test accessible websites, screen readers are considered the most important addition to a web developer's toolset. But why is that? And what are screen readers anyway?]]></description>
        </item>
        <item>
            <title><![CDATA[JAWS installation and configuration]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/screen-readers/jaws</link>
            <guid>https://www.accessibility-developer-guide.com/setup/screen-readers/jaws</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[JAWS (Job Access With Speech) is one of the most-used desktop screen readers. Therefore it's very important to ensure its compatibility with your websites. Due to its heavy weight, JAWS is a rather clumsy companion while developing, but it's absolutely crucial to fire it up every now and then for counterchecking accessibility on desktop.]]></description>
        </item>
        <item>
            <title><![CDATA[TalkBack configuration]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/screen-readers/talkback</link>
            <guid>https://www.accessibility-developer-guide.com/setup/screen-readers/talkback</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[TalkBack is the mobile screen reader of Android. It is pre-installed on Android devices, easy to understand, and the most used mobile screen reader in non-Western countries. Because of its rather unreliable activation shortcut, TalkBack is a bit less convenient than VoiceOver/iOS, but still needs to be used for frequent counterchecking accessibility on mobile platforms.]]></description>
        </item>
        <item>
            <title><![CDATA[How to interact with websites using a mobile screen reader]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/mobile/interacting-with-websites</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/mobile/interacting-with-websites</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Modern websites offer a lot of interactivity - long gone are the times of static pages. Even complex widgets can be controlled relatively easy using mobile screen readers. And while there are pretty advanced gestures for some native applications, the interaction with websites fortunately is surprisingly easy.]]></description>
        </item>
        <item>
            <title><![CDATA[Browse and focus modes]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/browse-focus-modes</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/browse-focus-modes</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[The relevant desktop screen readers on Windows offer different ways of interacting with the underlying application. The most common ones are browse mode and focus mode. We cannot overestimate the importance of thoroughly knowing their differences.]]></description>
        </item>
        <item>
            <title><![CDATA[The Insert modifier key]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/insert-modifier-key</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/insert-modifier-key</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Desktop screen readers are usually controlled with the keyboard only. Offering tons of functionalities, all of them ought to be triggered by keyboard shortcuts. But what to do if none of the standard keyboard combinations are available anymore?]]></description>
        </item>
        <item>
            <title><![CDATA[How to interact with websites using a desktop screen reader]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/interacting-with-websites</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/interacting-with-websites</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[Due to the differences between browse and focus modes in desktop screen readers, interacting with form controls or widgets can be a bit of a challenge at first. In the end, well-built components can always be understood and controlled by screen reader users, regardless of the given complexities.]]></description>
        </item>
        <item>
            <title><![CDATA[Desktop screen reader keyboard shortcuts]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/screenreader-shortcuts</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/screenreader-shortcuts</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[While desktop screen readers literally have dozens (if not hundreds) of keyboard shortcuts, only a fraction of them is needed for everyday usage. The following cheat-sheet lists the most important ones.]]></description>
        </item>
        <item>
            <title><![CDATA[How to read websites using a desktop screen reader]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/reading-websites</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/reading-websites</guid>
            <pubDate>Wed, 03 Jun 2020 17:50:27 GMT</pubDate>
            <description><![CDATA[While mobile screen readers already offer a pretty good idea of how it is to surf the internet as a blind person, they offer way less features (and thus complexity) than desktop ones. So be ready to get a concrete idea of the main strategies available to read a website using a desktop screen reader!]]></description>
        </item>
        <item>
            <title><![CDATA[Error 404 - Page not found.]]></title>
            <link>https://www.accessibility-developer-guide.com/</link>
            <guid>https://www.accessibility-developer-guide.com/</guid>
            <pubDate>Tue, 07 Apr 2020 11:43:31 GMT</pubDate>
            <description><![CDATA[Please use the menu or the search to find the content you have been looking for.]]></description>
        </item>
        <item>
            <title><![CDATA[Welcome to the Accessibility Developer Guide!]]></title>
            <link>https://www.accessibility-developer-guide.com/</link>
            <guid>https://www.accessibility-developer-guide.com/</guid>
            <pubDate>Wed, 18 Dec 2019 15:20:56 GMT</pubDate>
            <description><![CDATA[If you want to learn more about designing and implementing fully accessible websites, you've come to the right place.]]></description>
        </item>
        <item>
            <title><![CDATA[Knowledge about accessibility]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge</guid>
            <pubDate>Tue, 17 Dec 2019 12:55:50 GMT</pubDate>
            <description><![CDATA[To begin developing accessible websites, some basic knowledge about the required tools and techniques is needed. The chapters in this 3rd part of our guide, the Knowledge part, will support you to get acquainted with various important topics of rather theoretical nature - with high practical value though. They will prepare you to actively dive into the world of accessible website development.]]></description>
        </item>
        <item>
            <title><![CDATA[Colour contrast for graphical objects]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/graphical-objects</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/graphical-objects</guid>
            <pubDate>Tue, 17 Dec 2019 12:55:50 GMT</pubDate>
            <description><![CDATA[The term "graphical object" typically applies to stand-alone icons and to information graphics. The visual complexity of such objects often requires some differentiation with regards to contrast. The focus lies on the parts of the graphical object required to understand the content.]]></description>
        </item>
        <item>
            <title><![CDATA[How to examine colour contrast]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/how-to-examine</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/how-to-examine</guid>
            <pubDate>Tue, 17 Dec 2019 12:55:50 GMT</pubDate>
            <description><![CDATA[Calculating contrast ratios is complex. Fortunately there are contrast calculators which take care of the math. We only need to provide the correct colour codes – which has a few potential pitfalls.]]></description>
        </item>
        <item>
            <title><![CDATA[Colour contrast for text]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/text</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/text</guid>
            <pubDate>Tue, 17 Dec 2019 12:55:50 GMT</pubDate>
            <description><![CDATA[There is a general minimal colour contrast level for all kinds of text. As an exception, large text can have slightly lower contrast. This requirement applies to both "real" text and rasterised text on images.]]></description>
        </item>
        <item>
            <title><![CDATA[Colour contrast for user interface components]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/user-interface-components</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/colours-and-contrast/user-interface-components</guid>
            <pubDate>Tue, 17 Dec 2019 12:55:50 GMT</pubDate>
            <description><![CDATA["User Interface (UI) components" are interactive elements, ranging from simple buttons and input fields to complex UI widgets. Just as for text there is a general minimal contrast level that needs to be reached to make their functionality and content accessible.]]></description>
        </item>
        <item>
            <title><![CDATA[Setup of the accessibility environment]]></title>
            <link>https://www.accessibility-developer-guide.com/setup</link>
            <guid>https://www.accessibility-developer-guide.com/setup</guid>
            <pubDate>Tue, 10 Dec 2019 14:06:01 GMT</pubDate>
            <description><![CDATA[For creating websites with accessibility in mind, you need to have some specific software at hand. The chapters in this second part of our guide, the Setup part, will teach you how to set up all of the software. The complete setup is tailored to the needs of developers, but for readers with lesser demands, we also provide a pragmatic minimal version of the setup.]]></description>
        </item>
        <item>
            <title><![CDATA[General bad table examples]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/bad-examples</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/bad-examples</guid>
            <pubDate>Tue, 10 Dec 2019 09:40:44 GMT</pubDate>
            <description><![CDATA[Oftentimes, developers forget to mark up a table's header cells with the proper HTML tag. Instead, they are styled only visually as headers. But tables lacking proper header cells are tricky to navigate by screen reader users, and the more complex they are, the less they can be understood.]]></description>
        </item>
        <item>
            <title><![CDATA[Bad ARIA practices]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/aria/bad-practices</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/aria/bad-practices</guid>
            <pubDate>Thu, 31 Jan 2019 15:50:23 GMT</pubDate>
            <description><![CDATA[There are certain situations where ARIA is a good (and maybe the only) way to go. But if done wrong, usage of ARIA often leads to even worse accessibility. Especially accessibility novices tend to misuse ARIA to "optimise" smelly code.]]></description>
        </item>
        <item>
            <title><![CDATA[How to implement websites that are ready for keyboard only usage]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/keyboard-only/how-to-implement</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/keyboard-only/how-to-implement</guid>
            <pubDate>Thu, 31 Jan 2019 15:16:39 GMT</pubDate>
            <description><![CDATA[Fortunately, to make sure a website is ready to be used by keyboard only, there is very little you need to consider. Still, a lot can go wrong if not paying attention, and bad old habits of some web developers seem to be hard to overcome.]]></description>
        </item>
        <item>
            <title><![CDATA[Introduction to our guide]]></title>
            <link>https://www.accessibility-developer-guide.com/introduction</link>
            <guid>https://www.accessibility-developer-guide.com/introduction</guid>
            <pubDate>Wed, 26 Sep 2018 22:08:52 GMT</pubDate>
            <description><![CDATA[The «Accessibility Developer Guide» is an initiative of «Access for all», Swiss Foundation for technology adapted to people with disabilities. It is developed and maintained in collaboration with a number of acclaimed web agencies. The vision behind the Accessibility Developer Guide is to bridge the gap between providers of websites and users with special needs.]]></description>
        </item>
        <item>
            <title><![CDATA[A license for 100% true Open Source]]></title>
            <link>https://www.accessibility-developer-guide.com/introduction/license</link>
            <guid>https://www.accessibility-developer-guide.com/introduction/license</guid>
            <pubDate>Fri, 31 Aug 2018 07:17:01 GMT</pubDate>
            <description><![CDATA[The Accessibility Developer Guide is published under the MIT License.]]></description>
        </item>
        <item>
            <title><![CDATA[External content in iframes]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings/iframes</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings/iframes</guid>
            <pubDate>Fri, 15 Jun 2018 20:19:31 GMT</pubDate>
            <description><![CDATA[Iframes allow to include any external content into a page. As such, precaution must be taken that external content does not mess up the semantics of the surrounding content with improper heading levels and hierarchies.]]></description>
        </item>
        <item>
            <title><![CDATA[Removing semantics using presentation role]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/presentation</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/presentation</guid>
            <pubDate>Fri, 15 Jun 2018 20:16:31 GMT</pubDate>
            <description><![CDATA[ARIA provides a role which removes the inherent semantics of an element. While this works in most browsers and screen readers, it is rarely needed.]]></description>
        </item>
        <item>
            <title><![CDATA[HTML 5 client side validations]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms/html-5-validations</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms/html-5-validations</guid>
            <pubDate>Fri, 15 Jun 2018 18:17:53 GMT</pubDate>
            <description><![CDATA[HTML 5 client side validations are a very useful feature: they allow rudimentary validation of user data without submitting anything to the server. They are supported to a high degree by modern browsers and screen readers. Still, you should obviously never think of them as a complete replacement for server side data validation.]]></description>
        </item>
        <item>
            <title><![CDATA[Hiding elements from screen readers using aria-hidden]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/hidden</link>
            <guid>https://www.accessibility-developer-guide.com/examples/sensible-aria-usage/hidden</guid>
            <pubDate>Thu, 14 Jun 2018 21:29:55 GMT</pubDate>
            <description><![CDATA[ARIA provides an attribute which allows to hide elements from screen readers. It works pretty uniformly on non-focusable elements in modern browsers and screen readers, but it still has some very odd peculiarities. So you better try to create solutions that do not need it.]]></description>
        </item>
        <item>
            <title><![CDATA[Carousels (or: slideshow, slider)]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets/carousel</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets/carousel</guid>
            <pubDate>Thu, 14 Jun 2018 08:23:03 GMT</pubDate>
            <description><![CDATA[Very similar to tablists, carousels also help to split up a page's content into smaller and thus more digestible parts which can be toggled visible one at a time.]]></description>
        </item>
        <item>
            <title><![CDATA[Forms]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/forms</link>
            <guid>https://www.accessibility-developer-guide.com/examples/forms</guid>
            <pubDate>Tue, 12 Jun 2018 09:30:49 GMT</pubDate>
            <description><![CDATA[Forms provide interactivity with websites. If coded properly, basic forms are natively accessible. And to achieve advanced functionalities, more sophisticated techniques are available.]]></description>
        </item>
        <item>
            <title><![CDATA[Heading outlines]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings</guid>
            <pubDate>Tue, 12 Jun 2018 09:30:49 GMT</pubDate>
            <description><![CDATA[Like a traditional book's table of contents, a proper heading outline allows screen reader users to quickly get an overview over the available areas of a page (including header, main, footer, and alike), and their respective contents. Furthermore, a comprehensive heading outline supports quick navigation inside all those contents.]]></description>
        </item>
        <item>
            <title><![CDATA[Hiding elements correctly]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/hiding-elements</link>
            <guid>https://www.accessibility-developer-guide.com/examples/hiding-elements</guid>
            <pubDate>Tue, 12 Jun 2018 09:30:49 GMT</pubDate>
            <description><![CDATA[There are cases when some element on a page needs to be hidden in some way: for example you want to show some content to one audience, but not to another one. In this chapter, you learn how to do this properly. Much is possible, but there are some pitfalls you really need to know about.]]></description>
        </item>
        <item>
            <title><![CDATA[Data tables]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables</guid>
            <pubDate>Tue, 12 Jun 2018 09:30:49 GMT</pubDate>
            <description><![CDATA[Tables allow to present complex data in a structured manner. They have a long history: from layout tables around the 2000's to today's need for responsive tables. Traditional tables are fully accessible, but you still should try to keep them as simple as possible. Even in more advanced use cases, they can be fully accessible - if you know how to do them right.]]></description>
        </item>
        <item>
            <title><![CDATA[Alternative techniques for labelling page regions]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings/alternative-techniques</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings/alternative-techniques</guid>
            <pubDate>Wed, 16 May 2018 09:50:27 GMT</pubDate>
            <description><![CDATA[Although headings are the most widely known technique to label page regions (like header, navigation, etc.), there exist other ways to label content in HTML. In our opinion though, headings are both the most expressive and simple technique. But let's examine the situation a bit deeper.]]></description>
        </item>
        <item>
            <title><![CDATA[General good headings example]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings/good-example</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings/good-example</guid>
            <pubDate>Wed, 16 May 2018 09:50:27 GMT</pubDate>
            <description><![CDATA[Structuring content with headings is always a good thing: no published book containing structured text could ever live without it. Headings allow to skim through the book, and the table of contents (TOC) of a book is based on them. On websites, headings work the exact same way as they do on print documents.]]></description>
        </item>
        <item>
            <title><![CDATA[Regarding search engine optimisation, is it okay to have multiple headings on level 1?]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/headings/multiple-h1-okay-for-seo</link>
            <guid>https://www.accessibility-developer-guide.com/examples/headings/multiple-h1-okay-for-seo</guid>
            <pubDate>Wed, 16 May 2018 09:50:27 GMT</pubDate>
            <description><![CDATA[Websites optimised for accessibility also result in better search engine rankings. The question regarding multiple headings on level 1 often concerns search engine optimisation (SEO) experts. While we do have a clear opinion on it (based on years of experience and intense debates with various experts) we also offer alternative solutions.]]></description>
        </item>
        <item>
            <title><![CDATA[Hiding elements visually by moving them off-screen]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/hiding-elements/visually</link>
            <guid>https://www.accessibility-developer-guide.com/examples/hiding-elements/visually</guid>
            <pubDate>Wed, 16 May 2018 09:50:27 GMT</pubDate>
            <description><![CDATA[To hide an element visually means: visually (on a computer screen) it is not perceivable anymore, but non-visual clients (for example screen readers) still perceive it. There is no official technique for doing this, but there's a well proven workaround.]]></description>
        </item>
        <item>
            <title><![CDATA[Multiple header cells in a table support identification]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/tables/multiple-headers</link>
            <guid>https://www.accessibility-developer-guide.com/examples/tables/multiple-headers</guid>
            <pubDate>Wed, 16 May 2018 09:50:27 GMT</pubDate>
            <description><![CDATA[A table's header cells are in charge of making the corresponding data cells distinguishable, so users can easily identify data cells and navigate through the table flawlessly. But sometimes it is hard to find the correct cells that fit in this respect, so you can try to introduce another one - or to use a combination of cells.]]></description>
        </item>
        <item>
            <title><![CDATA[Interactive widgets]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets</guid>
            <pubDate>Tue, 15 May 2018 09:04:15 GMT</pubDate>
            <description><![CDATA[Being the most promising technique for modern websites, JavaScript can be the most challenging one for accessibility. If done right, they both truly complement each other.]]></description>
        </item>
        <item>
            <title><![CDATA[Hiding elements from screen readers using aria-hidden]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/hiding-elements/from-screen-readers</link>
            <guid>https://www.accessibility-developer-guide.com/examples/hiding-elements/from-screen-readers</guid>
            <pubDate>Tue, 15 May 2018 08:57:35 GMT</pubDate>
            <description><![CDATA[To hide an element from screen readers means: visually (on a computer screen) it is perceivable, but non-visual clients (for example screen readers) ignore it. This is done easily using ARIA, but you should never try this on focusable elements.]]></description>
        </item>
        <item>
            <title><![CDATA[Regarding search engine optimisation, is it okay to hide elements?]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/hiding-elements/okay-for-seo</link>
            <guid>https://www.accessibility-developer-guide.com/examples/hiding-elements/okay-for-seo</guid>
            <pubDate>Wed, 02 May 2018 08:46:11 GMT</pubDate>
            <description><![CDATA[Search engine optimisation (SEO) experts often are concerned about hiding elements visually. This due to the fear of being penalised for SEO fraud. But today's search engines are very smart, and sensible optimisation of content for accessibility reasons is honoured by them.]]></description>
        </item>
        <item>
            <title><![CDATA[Semantics support interaction]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge/semantics/interaction</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge/semantics/interaction</guid>
            <pubDate>Wed, 02 May 2018 08:46:11 GMT</pubDate>
            <description><![CDATA[Semantic HTML does not only provide meaning to content elements, it also provides the foundation for elements' interactivity. Be it links, buttons or various form inputs - browsers know exactly how to deal with them, and they provide the user with everything needed for proper interaction with the website.]]></description>
        </item>
    </channel>
</rss>