<?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>Sun, 06 May 2018 00:00:00 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/assets/img/logo/adg.svg</url>
            <link>https://www.accessibility-developer-guide.com</link>
        </image>
        <copyright>MIT</copyright>
        <item>
            <title><![CDATA[접근성 개발자 지침에 오신 여러분 환영합니다!]]></title>
            <link>https://www.accessibility-developer-guide.com/</link>
            <guid>https://www.accessibility-developer-guide.com/</guid>
            <pubDate>Sun, 06 May 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[완전히 접근 할 수 있는 웹 사이트를 설계하고 구현하는 방법에 대해 자세히 알아보고 싶다면, 제대로 찾아 오셨습니다.]]></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>Sun, 06 May 2018 00:00:00 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[Contribute to this guide]]></title>
            <link>https://www.accessibility-developer-guide.com/contribute</link>
            <guid>https://www.accessibility-developer-guide.com/contribute</guid>
            <pubDate>Mon, 03 May 2021 00:00:00 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[Examples of accessibility patterns]]></title>
            <link>https://www.accessibility-developer-guide.com/examples</link>
            <guid>https://www.accessibility-developer-guide.com/examples</guid>
            <pubDate>Mon, 02 Apr 2018 00:00:00 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[지침 소개]]></title>
            <link>https://www.accessibility-developer-guide.com/introduction</link>
            <guid>https://www.accessibility-developer-guide.com/introduction</guid>
            <pubDate>Wed, 06 Jun 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[«접근성 개발자 지침»은 장애인을 위한 기술에 대한 스위스 재단인 «모두를 위한 접근»의 이니셔티브입니다. 여러 유명한 웹 에이전시들과 협력하여 개발 및 유지 관리됩니다. 접근성 개발자 지침의 비전은 웹 사이트 제공자와 특정 요구 사항이 있는 사용자 간의 격차를 해소하는 것입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[접근성 관련 지식]]></title>
            <link>https://www.accessibility-developer-guide.com/knowledge</link>
            <guid>https://www.accessibility-developer-guide.com/knowledge</guid>
            <pubDate>Sun, 15 Dec 2019 00:00:00 GMT</pubDate>
            <description><![CDATA[접근 가능한 웹 사이트 개발을 시작하려면, 필요한 도구 및 기술에 대한 몇 가지 기본 지식이 필요합니다. 지침의 이 세 번째 파트, 지식 파트의 챕터들은 다소 이론적인 성격의 (하지만 실질적인 가치가 높습니다) 다양한 중요한 주제를 알 수 있도록 지원합니다. 여러분을 접근 가능한 웹 사이트 개발의 세례로 적극적으로 뛰어들도록 준비시킬 것입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[접근성 환경 설정]]></title>
            <link>https://www.accessibility-developer-guide.com/setup</link>
            <guid>https://www.accessibility-developer-guide.com/setup</guid>
            <pubDate>Mon, 02 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[접근성을 염두에 두고 웹 사이트를 만드려면 몇 가지 특정 소프트웨어가 있어야 합니다. 지침의 두 번째 파트 인 설정 파트의 챕터는 모든 소프트웨어를 설정하는 방법을 설명합니다. 전체 설정은 개발자의 요구에 맞춰져 있지만, 요구 사항이 적은 독자를 위해 실용적인 최소 버전의 설정도 제공합니다.]]></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>Sat, 12 May 2018 00:00:00 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>Wed, 02 May 2018 00:00:00 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>Wed, 02 May 2018 00:00:00 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[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>Sun, 02 Sep 2018 00:00:00 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[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>Sun, 13 May 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[There are some ARIA roles and attributes that we use and recommend in our daily business, especially regarding JavaScript widgets. If you know their peculiarities, they sometimes can be pretty helpful (with predictable risk). But often we also offer alternative techniques: if feasible, we use (and recommend) them instead of ARIA.]]></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>Wed, 02 May 2018 00:00:00 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[Interactive widgets]]></title>
            <link>https://www.accessibility-developer-guide.com/examples/widgets</link>
            <guid>https://www.accessibility-developer-guide.com/examples/widgets</guid>
            <pubDate>Mon, 14 May 2018 00:00:00 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[이 이니셔티브에 대해]]></title>
            <link>https://www.accessibility-developer-guide.com/introduction/about</link>
            <guid>https://www.accessibility-developer-guide.com/introduction/about</guid>
            <pubDate>Tue, 12 Nov 2019 00:00:00 GMT</pubDate>
            <description><![CDATA[«접근성 개발자 지침» 전체는 접근 가능한 웹 어플리케이션을 개발할 뿐 아니라 접근성에 대해 웹 사이트를 테스트 하는 분야에서의 수 년간의 실무 경험의 결과입니다. 특정 요구 사항을 가진 사용자 전문가의 일상적인 경험이, 풀스택 웹 개발자의 깊은 기술적 지식과 한데 섞여 «접근성 연합»이 형성되었습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[본 지침 사용 방법]]></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, 12 Nov 2019 00:00:00 GMT</pubDate>
            <description><![CDATA[본 지침은 접근성의 세계로 뛰어들 실용적인 방법을 찾고 있는 입문자와 지식을 확장하고 새로운 영감을 받아들이려는 노련한 전문가 모두에게 포괄적인 리소스를 제공하는 것을 목표로 합니다. 지침을 읽는 방법과 최신 상태를 유지하는 방법을 확인할 수 있습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[100% 진정한 오픈 소스 라이센스]]></title>
            <link>https://www.accessibility-developer-guide.com/introduction/license</link>
            <guid>https://www.accessibility-developer-guide.com/introduction/license</guid>
            <pubDate>Fri, 15 Jun 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[접근성 개발자 지침은 MIT 라이센스에 따라 게시됩니다.]]></description>
        </item>
        <item>
            <title><![CDATA[개인정보보호방침]]></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, 30 Apr 2020 00:00:00 GMT</pubDate>
            <description><![CDATA[본 지침에서 가능한 최상의 경험을 제공하기 위해 특정 정보를 수집하고 처리해야 합니다.]]></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>Wed, 02 May 2018 00:00:00 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[색상과 대비]]></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>Sun, 15 Dec 2019 00:00:00 GMT</pubDate>
            <description><![CDATA[예를 들어 텍스트, 아이콘, 입력 필드 및 차트와 같은 시각적 요소는 쉽게 인식 할 수 있어야 합니다. 기장 기본적인 수준에서, 배경에서 뚜렷하게 눈에 띄어야 함을 의미합니다. 또한 예를 들어 텍스트 문단에 포함 된 링크와 같이 주변의 유사항 요소들로부터 쉽게 구별될 수 있어야 하는 것도 중요합니다.]]></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>Wed, 02 May 2018 00:00:00 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[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>Tue, 07 Apr 2020 00:00:00 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[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>Wed, 02 May 2018 00:00:00 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[웹 브라우저]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers</guid>
            <pubDate>Wed, 02 May 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[접근 가능한 웹 사이트를 개발하려면, 몇 가지 일반적인 Windows 웹 브라우저가 필요합니다. 이 챕터에서는, 이들을 설치하고 구성하는 방법을 배웁니다. 또한, 일상 루틴에서 도움이 될 몇 가지 유용한 확장 기능과 북마클릿을 소개합니다.]]></description>
        </item>
        <item>
            <title><![CDATA[접근성 보조 도구]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/helper-tools</link>
            <guid>https://www.accessibility-developer-guide.com/setup/helper-tools</guid>
            <pubDate>Mon, 02 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[스크린리더와 브라우저 (확장 포함) 같은 큰 플레이어 아래에, 접근 가능한 웹사이트를 개발하는데 도움이 되는 다양한 소프트웨어가 있습니다. 이 챕터에서, 우리가 좋아하는 보조 도구 모음을 찾을 수 있습니다. 그들 중 일부는 서드파티 소프트웨어이고, 다른 일부는 Windows에 통합되어 있습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[스크린리더]]></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, 07 Apr 2020 00:00:00 GMT</pubDate>
            <description><![CDATA[스크린리더로 웹 사이트를 운영하는 것은 접근성을 보장하는 가장 효율적인 기법 중 하나입니다. 초심자의 경우, 스크린리더 사용이 처음에는 약간 혼란스러울 수 있고, 특히 소프트웨어가 테스트 목적으로 적절하게 구성되지 않은 경우 더욱 그렇습니다. 이 챕터에서는 모바일과 데스크탑 스크린리더를 편리하게 사용할 수 있도록 설치하고 구성하는 방법을 배웁니다.]]></description>
        </item>
        <item>
            <title><![CDATA[Windows 운영 체제]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/windows</link>
            <guid>https://www.accessibility-developer-guide.com/setup/windows</guid>
            <pubDate>Mon, 22 Mar 2021 00:00:00 GMT</pubDate>
            <description><![CDATA[웹 사이트의 접근성을 보장하기 위해, 가장 중요한 소프트웨어는 데스크탑 스크린리더와 같은 기본 Windows 소프트웨어 입니다. 이 챕터에서는, 향후 설치 작업을 위한 모든 것을 준비하는 방법을 배웁니다. Windows 작업 환경을 깨끗하게 유지하려면 (또는 Windows를 사용하지 않는 경우), 가상 머신 내에 전용 Windows 설치를 설정하는 것을 권장합니다.]]></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>Thu, 30 Apr 2020 00:00:00 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>Thu, 30 Apr 2020 00:00:00 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 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>Thu, 03 May 2018 00:00:00 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[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>Thu, 03 May 2018 00:00:00 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[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>Fri, 15 Jun 2018 00:00:00 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[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>Thu, 03 May 2018 00:00:00 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[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>Thu, 30 Apr 2020 00:00:00 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[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, 30 Apr 2020 00:00:00 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[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>Tue, 29 May 2018 00:00:00 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 be sure to make this information is easily accessible.]]></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>Thu, 30 Apr 2020 00:00:00 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[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>Tue, 01 May 2018 00:00:00 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 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, 03 Apr 2018 00:00:00 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[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>Tue, 03 Apr 2018 00:00:00 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[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>Wed, 18 Apr 2018 00:00:00 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[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>Tue, 01 May 2018 00:00: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[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 00:00:00 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[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>Tue, 15 May 2018 00:00:00 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[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>Tue, 03 Apr 2018 00:00:00 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[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>Tue, 29 Jun 2021 00:00:00 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[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>Sun, 13 May 2018 00:00:00 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>Tue, 03 Apr 2018 00:00:00 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[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>Sat, 24 Mar 2018 00:00:00 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[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>Tue, 15 May 2018 00:00:00 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[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>Mon, 14 May 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[ARIA provides an attribute which allows to mark an element in a set of elements as the current one. 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[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>Mon, 14 May 2018 00:00:00 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[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>Tue, 29 May 2018 00:00:00 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[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>Mon, 14 May 2018 00:00:00 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[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>Mon, 14 May 2018 00:00:00 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[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>Tue, 15 May 2018 00:00:00 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[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>Mon, 14 May 2018 00:00:00 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[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>Fri, 15 Jun 2018 00:00:00 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[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 00:00:00 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[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>Thu, 30 Apr 2020 00:00:00 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[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>Mon, 16 Apr 2018 00:00:00 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[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>Mon, 16 Apr 2018 00:00:00 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[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>Fri, 13 Apr 2018 00:00:00 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[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>Mon, 16 Apr 2018 00:00:00 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[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>Fri, 13 Apr 2018 00:00:00 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 a bit tricky for screen readers, especially in complex data tables. And in general: keep your tables simple.]]></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>Mon, 16 Apr 2018 00:00:00 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[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>Mon, 16 Apr 2018 00:00:00 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[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>Tue, 29 May 2018 00:00:00 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[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>Thu, 30 Apr 2020 00:00:00 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[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>Tue, 29 May 2018 00:00:00 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[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>Thu, 30 Apr 2020 00:00:00 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[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, 30 Apr 2020 00:00:00 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[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>Thu, 30 Apr 2020 00:00:00 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[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>Thu, 31 May 2018 00:00:00 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[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, 30 Apr 2020 00:00:00 GMT</pubDate>
            <description><![CDATA[Tablists help to split up a page's content into smaller and thus more digestible parts. Each part is minimally represented in a list of names, by which their visibility can be enabled one at a time. Tablists can be thought of as small page fragments inside a page.]]></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>Thu, 30 Apr 2020 00:00:00 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[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, 12 Apr 2018 00:00:00 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[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>Mon, 14 May 2018 00:00: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[색상은 충분하지 않습니다]]></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>Sun, 15 Dec 2019 00:00:00 GMT</pubDate>
            <description><![CDATA[대비의 목적은 사람들이 인터페이스의 다른 부분을 보고 구별할 수 있도록 하는 것입니다. 색상은 이 맥락에서 중요한 요소이지만, 몇 가지 분명한 한계가 있습니다. 그것이 색상에만 의존하는 것이 일반적으로 좋은 전략이 아닌 이유입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[그래픽 객체에 대한 색상 대비]]></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>Sun, 15 Dec 2019 00:00:00 GMT</pubDate>
            <description><![CDATA["그래픽 객체"라는 용어는 일반적으로 독립 된 아이콘과 정보 그래픽에 적용됩니다. 그러한 객체의 시각적 복합성은 종종 대비와 관련하여 약간의 차별화가 필요합니다. 내용을 이해하는데 필요한 그래픽 객체의 부분에 중점을 둡니다.]]></description>
        </item>
        <item>
            <title><![CDATA[색상 대비 계산 방법]]></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>Sun, 15 Dec 2019 00:00:00 GMT</pubDate>
            <description><![CDATA[두 색상 간의 명암비를 계산하는 수학 공식이 있습니다. 대비 평가를 위해 이 공식을 사용하는 것이 눈에만 의존 하는 것보다 항상 낫습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[색상 대비 검사 방법]]></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>Sun, 15 Dec 2019 00:00:00 GMT</pubDate>
            <description><![CDATA[명암비를 계산하는 것은 복잡합니다. 다행히 수학을 처리하는 대비 계산기가 있습니다. 몇 가지 잠재적인 위험이 있는 올바른 색상 코드만 제공하면 됩니다.]]></description>
        </item>
        <item>
            <title><![CDATA[텍스트에 대한 색상 대비]]></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>Sun, 15 Dec 2019 00:00:00 GMT</pubDate>
            <description><![CDATA[모든 종류의 텍스트에 대해 일반적인 최소 색상 대비 수준이 있습니다. 예외적으로, 큰 텍스트는 낮은 대비를 가질 수 있습니다. 이 요구 사항은 "실제" 텍스트와 이미지의 래스터화 된 텍스트 모두에 적용됩니다.]]></description>
        </item>
        <item>
            <title><![CDATA[유저 인터페이스 컴포넌트에 대한 색상 대비]]></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>Sun, 15 Dec 2019 00:00:00 GMT</pubDate>
            <description><![CDATA["유저 인터페이스 (UI) 컴포턴트"는 간단한 버튼과 입력 필드로부터 복잡한 UI 위젯에 이르는 대화형 엘리먼트입니다. 텍스트와 마찬가지로 그것의 기능과 콘텐츠가 접근 가능하도록 도달해야 하는 일반적인 최소 대비 수준이 있습니다.]]></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, 12 Apr 2018 00:00:00 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[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, 12 Apr 2018 00:00:00 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[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>Wed, 30 May 2018 00:00:00 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[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>Tue, 07 Apr 2020 00:00:00 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[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>Tue, 07 Apr 2020 00:00:00 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>Fri, 13 Apr 2018 00:00:00 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>Tue, 07 Apr 2020 00:00:00 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>Tue, 07 Apr 2020 00:00:00 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[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>Tue, 07 Apr 2020 00:00:00 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[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>Tue, 07 Apr 2020 00:00: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 and its content. This is a very hard task and prone to regressions, as we try to explain here.]]></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>Tue, 07 Apr 2020 00:00:00 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[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>Thu, 12 Apr 2018 00:00:00 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>
        <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>Tue, 07 Apr 2020 00:00:00 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[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, 12 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[HTML supports interactive controls for most requirements. But what about additional interaction patterns that do not offer an HTML equivalent? Surprisingly to many, standard browser behaviour is also a fool-proof way to provide even complex custom functionalities in the style of modern widgets. The trick is to simply use traditional form controls, change their visual design using CSS, and add the needed interactivity using JavaScript.]]></description>
        </item>
        <item>
            <title><![CDATA[북마클릿]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/bookmarklets</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/bookmarklets</guid>
            <pubDate>Fri, 09 Mar 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[북마클릿은 URL 대신 JavaScript를 포함하는 북마크입니다. 웹 페이지를 읽는 동안 실행할 수 있고, 일반적으로 빠른 분석을 수행하여 결과를 표시합니다.]]></description>
        </item>
        <item>
            <title><![CDATA[크롬 설치 및 구성]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/chrome</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/chrome</guid>
            <pubDate>Mon, 12 Mar 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[어쨌든 많은 웹 개발자가 즐겨 찾는 브라우저인 크롬은 일상적인 접근성 작업 흐름에 유용한 몇 가지 좋은 기능과 확장도 갖추고 있습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[마이크로소프트 엣지 설치 및 구성]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/edge</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/edge</guid>
            <pubDate>Mon, 22 Mar 2021 00:00:00 GMT</pubDate>
            <description><![CDATA[엣지는 마이크로소프트의 레거시 브라우저 인터넷 익스플로러 11 (IE 11)를 대체하며 구글 크롬처럼 오픈 소스 코드 기반의 동일한 크로미움을 기반으로 합니다.]]></description>
        </item>
        <item>
            <title><![CDATA[파이어폭스 설치 및 구성]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/firefox</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/firefox</guid>
            <pubDate>Mon, 12 Mar 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[사용 가능한 가장 호의적인 브라우저 중 하나인 파이어폭스(FF)는 특정 요구를 가진 특히 기술에 능숙한 사람들에게 널리 사용되고 사랑받고 있습니다. FF의 주요 특징 중 하나는 접근성과 관련된 것을 포함하여 웹 표준에 대한 높은 적합성입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[인터넷 익스플로러 11 설치 및 구성]]></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 00:00:00 GMT</pubDate>
            <description><![CDATA[마이크로소프트의 레거시 브라우저 (그리고 모든 정말 많은 웹 개발자의 오랜 천적인) 인터넷 익스플로러 11 (IE11)은 공식적으로 더 이상 지원되지 않습니다. 이후의 Edge를 참고하세요.]]></description>
        </item>
        <item>
            <title><![CDATA[색상 대비 분석기]]></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>Mon, 02 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[전경색과 배경색 사이에 충분한 대비를 갖는 것은 일반적으로 사용성 그리고 특히 접근성에 필수적인 부분입니다. 색상 대비 분석기 (CCA)는 두 색상 간의 대비를 계산하고 웹 콘텐츠 접근성 지침에 따라 반환 된 값을 자동으로 평가하는 도구입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[Windows 고대비 모드]]></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>Fri, 06 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[Windows 고대비 모드(Win HCM)는 화면을 특정 고대비 구성으로 변경합니다. 이것은 시각 장애인이 사용합니다. 시각 정보가 순수하게 장식적인 스타일로 전달되지 않도록 하는데 유용한 도구 입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[PDF 접근성 검사기]]></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>Fri, 06 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[PDF 접근성 검사기(PAC)는 PDF 파일의 접근성을 테스트 하는 빠른 방법을 제공합니다. 한편으로는 PDF/UA 표순이 충족되는지 확인합니다. 또 다른 한편으로는, 스크린리더가 인식하는 것과 유사한 방식으로 문서를 시각적으로 표시하는 훌륭한 미리보기 기능을 제공하여, 엘리먼트의 순서와 의미 모두에서 문제를 쉽게 발견할 수 있습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[TotalValidator]]></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>Mon, 09 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[TotalValidator는 버튼을 눌러 다양한 웹 및 접근성 표준에 대해 웹사이트를 검사합니다. 유효한 코드를 작성하는 것은 개발자가 추구해야 하는 가장 높은 목표 중 하나입니다. TotalValidator는 이를 달성하는데 많은 도움이 됩니다.]]></description>
        </item>
        <item>
            <title><![CDATA[JAWS 설치 및 구성]]></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>Thu, 30 Apr 2020 00:00:00 GMT</pubDate>
            <description><![CDATA[JAWS (Job Access With Speech)는 가장 많이 사용 되는 데스크탑 스크린리더 중 하나입니다. 따라서 웹 사이트와 이것의 호환성을 보장하는 것이 매우 중요합니다. 무겁기 때문에, JAWS는 개발 중 다소 세련되지 못한 도구이지만, 데스크탑에서 접근성을 점검하기 위해 매 번 실행하는 것이 절대적으로 중요합니다.]]></description>
        </item>
        <item>
            <title><![CDATA[NVDA 설치 및 구성]]></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>Thu, 30 Apr 2020 00:00:00 GMT</pubDate>
            <description><![CDATA[NVDA (Non Visual Desktop Access)는 가볍고 안정적인 오픈 소스 데스크탑 스크린리더입니다. 표준에 대한 확고한 준수 때문에, 접근성 개발 할 때 선택하는 데스크탑 스크린리더 입니다. 잠시 사용하고 나면, 확고 하면서도 타당한 선생님으로 존경하게 될 것입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[톡백 구성]]></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>Thu, 23 Apr 2020 00:00:00 GMT</pubDate>
            <description><![CDATA[톡백은 안드로이드의 모바일 스크린리더 입니다. 안드로이드 기기에 기본 설치되어 있고, 이해하기 쉬우며, 비 서구 국가에서 가장 많이 사용되는 모바일 스크린리더 입니다. 다소 신뢰할 수 없는 활성화 단축키 때문에, 톡백은 보이스오버/iOS보다 약간 덜 편리하지만, 모바일 플랫폼에서 접근성을 자주 대응하는데 여전히 사용할 필요가 있습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[보이스오버/iOS 구성]]></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>Tue, 07 Apr 2020 00:00:00 GMT</pubDate>
            <description><![CDATA[보이스오버/iOS는 가장 진보 된 모바일 스크린리더입니다. iOS 기기에 기본 설치되어 있고, 이해하기 쉬우며, 서구 국가에서 가장 많이 사용되는 모바일 스크린리더입니다. 안정적이고 쉬운 활성화 단축키 덕분에, 접근 가능한 웹사이트를 개발할 때 선택하는 모바일 스크린 리더입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[마이크로소프트에서 무료 Windows 가상 머신 받기]]></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>Mon, 22 Mar 2021 00:00:00 GMT</pubDate>
            <description><![CDATA[마이크로소프트는 마이크로소프트 인터넷 익스플로러와 마이트로소프트 엣지 테스트를 위해 무료 Windows 가상 머신을 제공합니다. 라이선스는 90일 사용 후 만료되지만, 활성화 전에 스탭샷을 생성하여, 쉽게 다시 재설정 할 수 있습니다. 이는 테스트 목적으로 Windows 환경을 빠르게 설정하고 실행할 수 있는 가장 쉬운 방법입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[macOS에 VMware Fusion 설정하기]]></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>Mon, 22 Mar 2021 00:00:00 GMT</pubDate>
            <description><![CDATA[macOS에서, Windows를 가상 머신으로 수행하려면, 특히 일상적인 워크플로에 매끄럽게 통합하려면 몇 가지 별도의 구성이 필요합니다. 일단 제대로 설정되면, macOS에서 접근성 테스트가 편안해 질 것입니다.]]></description>
        </item>
        <item>
            <title><![CDATA[Windows (및 Linux)에 VMWare Workstation Pro 구성하기]]></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 00:00:00 GMT</pubDate>
            <description><![CDATA[이미 운영 체제로 Windows를 실행하고 있더라도, 접근성 테스트를 위해 별도로 구성된 가상 머신 내에 다른 Windows를 설정하는데 필요한 초기 노력을 기울이는 것이 좋습니다. 이는 시스템을 깨끗하게 유지시키고 접근성 테스트를 좀 더 편안하게 합니다.]]></description>
        </item>
        <item>
            <title><![CDATA[접근 가능한 웹 사이트 개발에 Windows가 반드시 필요한 이유]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/windows/why</link>
            <guid>https://www.accessibility-developer-guide.com/setup/windows/why</guid>
            <pubDate>Thu, 30 Apr 2020 00:00:00 GMT</pubDate>
            <description><![CDATA[웹사이트에 가능한 많은 사용자가 접근 가능하도록 하려면, 가장 널리 사용되는 보조 소프트웨에에서 동작하는지 확인하는 것이 중요합니다. 현재 특정 요구 사항이 있는 대부분의 사용자는 Windows용 소프트웨어를 실행하고 있습니다. 이것이 원하든 원하지 않은 Windows 환경을 사용 할 수 있어야 하는 이유입니다.]]></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>Tue, 07 Apr 2020 00:00:00 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 보조 키]]></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>Tue, 07 Apr 2020 00:00:00 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>Tue, 07 Apr 2020 00:00:00 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[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>Tue, 07 Apr 2020 00:00:00 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[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>Tue, 07 Apr 2020 00:00:00 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 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>Thu, 23 Apr 2020 00:00:00 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[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>Thu, 23 Apr 2020 00:00:00 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[구조화 된 콘텐츠]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/bookmarklets/contents-structured</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/bookmarklets/contents-structured</guid>
            <pubDate>Mon, 22 Mar 2021 00:00:00 GMT</pubDate>
            <description><![CDATA[이 북마클릿은 태그 이름을 전달하는, 많은 일반적인 의미론적 HTML 엘리먼트를 강조 표시합니다. 이는 현재 페이지의 의미론적 구조를 매우 쉽게 검사할 수 있게 합니다.]]></description>
        </item>
        <item>
            <title><![CDATA[h123]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/bookmarklets/h123</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/bookmarklets/h123</guid>
            <pubDate>Fri, 06 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[이 북마클릿은 스크린리더가 수행하는 것과 매우 가까운 방법으로, 현재 웹 페이지의 제목 개요를 표시하는 효율적인 방법을 제공합니다. 또한 잠재적으로 올바르지 않게 숨겨진 헤딩을 표시하는 것과 같은 몇 가지 유용한 기능이 있습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[HTML 코드 탐지기]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/bookmarklets/html-codesniffer</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/bookmarklets/html-codesniffer</guid>
            <pubDate>Fri, 06 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[이 북마클릿은 표시된 페이지의 HTML 소스를 분석하고 코딩 표준 위반을 감지합니다. 엄청난 양의 사전 정의 된 규칙을 제공하고 사용자 정의 규칙으로 확장 될 수 있습니다.]]></description>
        </item>
        <item>
            <title><![CDATA[WAVE 도구 모음]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/chrome/wave-toolbar</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/chrome/wave-toolbar</guid>
            <pubDate>Fri, 06 Apr 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[WAVE 도구 모음은 현재 웹 페이지의 접근성의 품질에 대한 매우 빠른 첫 인상을 제공합니다. 버튼을 누르면, 아이콘과 세부 정보를 페이지에 바로 주입하여 시각적 단서를 제공합니다.]]></description>
        </item>
        <item>
            <title><![CDATA[웹 개발자 도구 모음]]></title>
            <link>https://www.accessibility-developer-guide.com/setup/browsers/firefox/web-developer-toolbar</link>
            <guid>https://www.accessibility-developer-guide.com/setup/browsers/firefox/web-developer-toolbar</guid>
            <pubDate>Thu, 10 May 2018 00:00:00 GMT</pubDate>
            <description><![CDATA[대부분의 엡 개발자가 이미 잘 알고 있는, 웹 개발자 도구 모음 확장은 파이어폭스에 모든 종류의 코드 검사 및 디버깅에 매우 유용한 다양한 도구를 추가합니다. 스크린리더의 제약을 알고 있다면 때때로 스크린리더의 대체로 볼 수도 있습니다.]]></description>
        </item>
    </channel>
</rss>