blog

commit

9f567dd468ad71967eeb133efcbeb5118a5066b9

parent

10f87ea2cb82b3889e7dc2a6f66568b295aeea77

Author

Tobias Bengfort <tobias.bengfort@posteo.de>

Date

2023-06-07 07:21

typos

Diffstat

1 files changed, 2 insertions, 2 deletions

diff --git a/_content/posts/2018-10-28-aria-quirks/index.md b/_content/posts/2018-10-28-aria-quirks/index.md

@@ -4,7 +4,7 @@ it into this blog post instead.*
    4     4 Like most web developers I had heard of ARIA. I had skimmed through the specs.
    5     5 But honestly, the [boostrap documentation][1] is still my go-to resource for
    6     6 actual usage. Some day I wanted to implement some assistive technology myself.
    7    -1 This is when found some unexpected quirks.
   -1     7 This is when I found some unexpected quirks.
    8     8 
    9     9 In my opinion, most of these quirks should be fixed. But maybe there are
   10    10 legitimate reasons why things have been defined this way. If you have an
@@ -66,7 +66,7 @@ operating systems. The layers in between are defined in different specs:
   66    66 -	The mapping between ARIA and OS APIs is defined in the [Core Accessibility API Mappings (Core-AAM)](https://www.w3.org/TR/core-aam-1.1/).
   67    67 -	Some additional parts have been split out, e.g. the [Accessible Name and Description Computation](https://www.w3.org/TR/accname-1.1/).
   68    68 
   69    -1 # Qirks
   -1    69 # Quirks
   70    70 
   71    71 Now with the introduction out of the way, let's get to the weird stuff. We
   72    72 start slow though.