<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (rybesh)</title>
    <link>https://pinboard.in/u:rybesh/public/</link>
    <description>recent bookmarks from rybesh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://hidde.blog/popover-semantics/"/>
	<rdf:li rdf:resource="https://www.w3.org/WAI/ARIA/apg/"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role"/>
	<rdf:li rdf:resource="https://cloudfour.com/thinks/mac-voiceover-testing-the-simple-way/"/>
	<rdf:li rdf:resource="https://www.smashingmagazine.com/2021/03/complete-guide-accessible-front-end-components/"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en-US/docs/Tools/Accessibility_inspector"/>
	<rdf:li rdf:resource="https://www.w3.org/WAI/PF/aria-practices/"/>
	<rdf:li rdf:resource="http://www.w3.org/WAI/demos/bad/"/>
	<rdf:li rdf:resource="http://www.tiresias.org/fonts/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://hidde.blog/popover-semantics/">
    <title>Semantics and the popover attribute: which role to use when? | hidde.blog</title>
    <dc:date>2024-05-13T20:35:52+00:00</dc:date>
    <link>https://hidde.blog/popover-semantics/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[With the new popover attribute in HTML, we can put elements in the top layer and allow them to disappear with ‘light dismiss’. This attribute adds behaviour, not semantics: you're supposed to add your own role when it makes sense. In this post, we'll look at different roles that could make sense for your popover-behaved elements.]]></description>
<dc:subject>html semantics design accessibility css ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:303efff5f1cd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semantics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/WAI/ARIA/apg/">
    <title>ARIA Authoring Practices Guide | APG | WAI | W3C</title>
    <dc:date>2023-01-04T21:34:06+00:00</dc:date>
    <link>https://www.w3.org/WAI/ARIA/apg/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Learn to use the accessibility semantics defined by the Accessible Rich Internet Application (ARIA) specification to create accessible web experiences. This guide describes how to apply accessibility semantics to common design patterns and widgets. It provides design patterns and functional examples complemented by in-depth guidance for fundamental practices.

]]></description>
<dc:subject>html accessibility design patterns</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b6f65c18a1af/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:patterns"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role">
    <title>ARIA: button role - Accessibility | MDN</title>
    <dc:date>2022-09-06T19:46:57+00:00</dc:date>
    <link>https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The button role identifies an element as a button to assistive technology such as screen readers. A button is a widget used to perform actions such as submitting a form, opening a dialog, canceling an action, or performing a command such as inserting a new record or displaying information. Adding role="button" tells assistive technology that the element is a button but provides no button functionality.]]></description>
<dc:subject>accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:19771414c623/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cloudfour.com/thinks/mac-voiceover-testing-the-simple-way/">
    <title>Mac VoiceOver Testing the Simple Way – Cloud Four</title>
    <dc:date>2022-08-26T21:02:51+00:00</dc:date>
    <link>https://cloudfour.com/thinks/mac-voiceover-testing-the-simple-way/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An easy-to-follow, repeatable guide to make testing with VoiceOver on a Mac as simple as possible.]]></description>
<dc:subject>accessibility testing howto</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b543b6224a17/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.smashingmagazine.com/2021/03/complete-guide-accessible-front-end-components/">
    <title>A Complete Guide To Accessible Front-End Components — Smashing Magazine</title>
    <dc:date>2021-03-22T21:55:57+00:00</dc:date>
    <link>https://www.smashingmagazine.com/2021/03/complete-guide-accessible-front-end-components/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Reliable accessible components: from tabs and tables to toggles and tooltips.]]></description>
<dc:subject>web accessibility reference</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6fca13021ead/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.mozilla.org/en-US/docs/Tools/Accessibility_inspector">
    <title>Accessibility Inspector - Firefox Developer Tools | MDN</title>
    <dc:date>2019-11-01T17:00:14+00:00</dc:date>
    <link>https://developer.mozilla.org/en-US/docs/Tools/Accessibility_inspector</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Accessibility Inspector provides a means to access important information exposed to assistive technologies on the current page via the accessibility tree, allowing you to check what's missing or otherwise needs attention. This article takes you through the main features of the Accessibility Inspector and how to use it.]]></description>
<dc:subject>accessibility firefox tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:251b8d79d434/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:firefox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/WAI/PF/aria-practices/">
    <title>WAI-ARIA 1.0 Authoring Practices</title>
    <dc:date>2016-01-20T14:32:57+00:00</dc:date>
    <link>https://www.w3.org/WAI/PF/aria-practices/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document provides readers with an understanding of how to use WAI-ARIA [ARIA] to create accessible rich internet applications. It describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. This document is directed primarily to Web application developers, but the guidance is also useful for user agent and assistive technology developers. ]]></description>
<dc:subject>web interface accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9466e3595a74/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/WAI/demos/bad/">
    <title>Before and After Demonstration: Overview</title>
    <dc:date>2012-02-01T20:10:59+00:00</dc:date>
    <link>http://www.w3.org/WAI/demos/bad/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Before and After Demonstration is a multi-page resource that shows an inaccessible website and a retrofitted version of this same website. Each web page includes inline annotations that can be activated to highlight some of the key accessibility barriers or repairs. Each web page is also accompanied by an evaluation report to inform the developers on the level of conformance to the Web Content Accessibility Guidelines (WCAG).]]></description>
<dc:subject>accessibility interface design standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:85a0d73b99d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tiresias.org/fonts/">
    <title>Tiresias family of fonts</title>
    <dc:date>2008-06-11T12:31:25+00:00</dc:date>
    <link>http://www.tiresias.org/fonts/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The DVB (Digital Video Broadcasting) has adopted the Tiresias Screenfont as the standard font for the MHP (Multimedia Home Platform), which many set-top box and digital TV manufacturers are using as their standard development platform.
]]></description>
<dc:subject>tv typography fonts design accessibility interface</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:9d348cc46278/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tv"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:typography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:fonts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>