diff --git a/content/about/index.gmi b/content/about/index.gmi index 03438ba..5e03dc5 100644 --- a/content/about/index.gmi +++ b/content/about/index.gmi @@ -6,7 +6,7 @@ Online Handle: Seirdy I'm known as Rohan and as Seirdy. There are some differences between these personas, but the line between the two is blurry. It's fine to mix them up. -## Other versions of this website +## About this capsule This page's canonical location is on seirdy.one: @@ -27,6 +27,9 @@ My Web and Gemini content may be slightly different: I often phrase things diffe I have a Tor hidden Web service which mirrors this site's contents, except for the fact that it replaces some SVGs with PNGs. => http://wgq3bd2kqoybhstp77i3wrzbfnsyd27wt34psaja4grqiezqircorkyd.onion/ +Featured in: +=> gemini://nightfall.city/writers-lane/ Writer's Lane, Nightfall City + ## Location (Rohan, He/Him, meatspace) Currently living at home in California, USA diff --git a/content/about/index.md b/content/about/index.md index 52bf2da..45756d4 100644 --- a/content/about/index.md +++ b/content/about/index.md @@ -144,8 +144,8 @@ I think that at least one entry in that list has some problematic messages, but I've put together a periodically-updated [list of tracks](../music.txt) that I've rated 8/10 or higher in my mpd stickers database, auto-generated by some of my [mpd-scripts](https://git.sr.ht/~seirdy/mpd-scripts/tree/master/smart-playlists). I'm a fan of glitch, trailer music, and symphonic and power metal; I've also recently been getting into Japanese rock thanks to a few anime openings. Some of my favorite artists are The Glitch Mob, Pretty Lights, Beats Antique, Hammerfall, Badflower, Celldweller and Scandroid, Helloween, Two Steps from Hell, Nightwish, Mili, and MYTH & ROID. -Meta: other versions of this website ------------------------------------- +Meta: other versions of this site +--------------------------------- This website's canonical location is on seirdy.one. diff --git a/content/site-design.md b/content/site-design.md new file mode 100644 index 0000000..4c9fa41 --- /dev/null +++ b/content/site-design.md @@ -0,0 +1,101 @@ +--- +outputs: + - html +title: Site design standards +description: "The accessibility statement and design standards I hold myself to when creating seirdy.one" +date: "2022-06-10T00:00:00+00:00" +--- +This site may look simple on the surface, but I put a _lot_ of thought into it. I hold myself to a long list of requirements concerning accessibility, compatibility, privacy, security, and machine-friendliness. + +
Note: all references to "pixels" (px) in this section refer to CSS pixels.
+ +Accessibility statement +----------------------- + +I've made every effort to make seirdy.one as accessible as possible. + +### Conformance status + +The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag/) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. I've made sure seirdy.one is fully conformant with WCAG 2.2 level AA. + +Fully conformant means that the content fully conforms to the accessibility standard without any exceptions. + +### Additional accessibility considerations + +Additionally, I strive to conform to WCAG 2.2 level AAA wherever applicable. There are some AAA criteria that I do not currently meet: + + +SC 1.4.8 Visual Presentation +: I am in partial compliance with this criterion. Long article body text for articles should conform; with default browser fonts, they have an average character count per line below 80 characters. However, some lines may occasionally exceed this limit. Text outside of long article bodies has a longer line width, though. + +SC 2.4.9 Link Purpose (Link Only) +: I'm actually trying to follow this criterion, but it's a work in progress. Let me know if any link names can be improved! Link purpose _in context_ always makes sense. + +SC 3.1.5 Reading Level +: The required reading ability often exceeds the lower secondary education level, especially on more technical articles. + +SC 3.1.6 Pronunciation +: I do not yet provide any pronunciation information. + +I have only tested WCAG compliance in mainstream browser engines (Blink, Gecko, WebKit). + +I also go further than WCAG in many aspects: + +- Rather than follow SC 2.5.5's requirement to achieve a minimum tap target size of 44 by 44 pixels, I follow Google's more strict guidelines. These guidelines mandate that targets are at least 48-by-48 pixels, with no overlap against any other targets in a 56-by-56 pixel range. I try to follow this guideline for any interactive element that isn't a hyperlink surrounded by body text. + +- I ensure at least one such 56-by-56 px non-interactive region exists on the page, for users with hand tremors or or anyone who wants to tap the screen without clicking something. + +- I only set custom colors in response to the `prefers-color-scheme: dark` media query. These custom colors pass APCA contrast ratios, all being close to the ideal lightness contrast of 90. They are also autism- and overstimulation-friendly colors: yellow links are significantly de-saturated to reduce harshness. + +- I ensure that the page works on extremely narrow viewports without triggering two-dimensional scaling. It should work at widths well below 200 CSS pixels. + +### Assessment and evaluation + +I test each WCAG success criterion myself using the mainstream browser engines (Blink, Gecko, WebKit). I test using multiple screen readers: Orca (primary, with Firefox and Epiphany), NVDA (with Firefox and Chromium), Windows Narrator (with Microsoft Edge), Apple VoiceOver (with desktop and mobile Safari), and Android TalkBack (with Chromium). + +I also accept user feedback. Users are free to contact me through any means linked on my [About page](../about/). + +Finally, I supplement manual testing with automated tools. I run [axe-core](https://github.com/dequelabs/axe-core), the [IBM Equal Access Accessibility Checker](https://www.ibm.com/able/toolkit/verify/automated), [AInspector](https://github.com/ainspector/ainspector-for-firefox), the [WAVE Web Accessibility Evaluation Tool](https://wave.webaim.org/), and [ARC Toolkit](https://www.tpgi.com/arc-platform/arc-toolkit/). WAVE reports no errors; AXE is unable to determine certain contrast errors, but it otherwise reports no errors; IBM Equal Access reports no errors but some items that need review. + +Browser engine compatibility +---------------------------- + +This site sticks to Web standards: I regularly run [the Nu HTML Checker](https://github.com/validator/validator) and `xmllint` on every page and see no errors (I do [filter out false Nu positives](https://git.sr.ht/~seirdy/seirdy.one/tree/master/item/linter-configs/vnu_filter.jq) and report them upstream when I can). + +I also do cross-browser testing for both HTML and XHTML versions of my pages: + +- I maintain excellent compatibility with **mainstream engines:** Blink (Chromium and Edge), WebKit (Safari, Epiphany), and Gecko (Firefox). The hidden service also works well with the Tor Browser. + +- The site works well with **textual browsers.** Lynx and Links2 are first-class citizens for which all features work as intended. [w3m doesn't support soft hyphens](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830173), but the site is still otherwise usable in it. I maintain compatibility with these engines by making CSS a strictly-optional progressive enhancement and using semantic markup. + +- I also regularly test compatibility with **current alternative engines:** the SerenityOS browser, Servo, NetSurf, Dillo, and Goanna (Pale Moon's Gecko fork). I have excellent compatibility with Goanna and Servo. The site is usable in NetSurf, Dillo, and the SerenityOS browser; the always-expanded `