mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-23 12:52:10 +00:00
Compare commits
4 commits
603bbd8fa2
...
48a9088ca1
Author | SHA1 | Date | |
---|---|---|---|
|
48a9088ca1 | ||
|
3c4d8381fd | ||
|
2ceeed427e | ||
|
854ad8dcce |
3 changed files with 33 additions and 3 deletions
12
content/notes/demise-of-dtds.md
Normal file
12
content/notes/demise-of-dtds.md
Normal file
|
@ -0,0 +1,12 @@
|
|||
---
|
||||
title: "Demise of DTDs"
|
||||
date: 2022-06-08T00:13:46-07:00
|
||||
replyURI: "https://hackers.town/@theruran/108440475936938471"
|
||||
replyTitle: "ever looked into writing your own DTD?"
|
||||
replyType: "SocialMediaPosting"
|
||||
replyAuthor: "theruran"
|
||||
replyAuthorURI: "https://hackers.town/@theruran"
|
||||
---
|
||||
People have mostly moved on from DTDs. In HTML-land, they use the Living Standard; in XML land, they stick to boring existing parsing rules and use XML namespaces. In both, they use RDF vocabularies to describe RDF-based structured data.
|
||||
|
||||
I'm curious as to why you're interested in creating a new DTD. I think that unless you plan on creating a new SGML-based language, you're better served by namespaces.
|
15
content/notes/resize-and-reflow.md
Normal file
15
content/notes/resize-and-reflow.md
Normal file
|
@ -0,0 +1,15 @@
|
|||
---
|
||||
title: "Resize and reflow"
|
||||
date: 2022-06-07T23:38:39-07:00
|
||||
replyURI: "https://yatil.net/blog/resize-text-reflow"
|
||||
replyTitle: "WCAG SC 1.4.4 Resize Text and 1.4.10 Reflow"
|
||||
replyType: "BlogPosting"
|
||||
replyAuthor: "Eric Eggert"
|
||||
replyAuthorURI: "https://yatil.net"
|
||||
---
|
||||
|
||||
This is a good article on the difference between SC 1.4.4 and 1.4.10. However, I don't think these criteria go far enough:
|
||||
|
||||
Even narrower viewports exist. KaiOS devices tend to have 240 px viewports; smartwatches tend to have half the width of a phone while emulating a phone width (Apple Watches can be instructed not to do this with a proprietary `meta` tag). Of course, making sites watch-compatible is a stretch, but support for feature phones running KaiOS should be reasonable. I wrote about this more in <cite>[Best practices for inclusive textual websites](https://seirdy.one/posts/2020/11/23/website-best-practices/)</cite>.
|
||||
|
||||
Another thing worth remembering is that users can change default fonts or override sire-set fonts. Don't just test with default default fonts; test with something wider. These criteria should specify some font metrics or (royalty free) representative wide fonts to use for testing.
|
|
@ -1,9 +1,12 @@
|
|||
<form
|
||||
itemprop="potentialAction" itemscope="" itemtype="https://schema.org/SearchAction"
|
||||
action="https://searchmysite.net/search/" method="get">
|
||||
<label for="search">Search this site (powered by <a rel="nofollow" href="https://searchmysite.net/">Search My Site</a>):</label>
|
||||
action="https://searchmysite.net/search/" method="get" role="search">
|
||||
<label for="search">
|
||||
Search this site (powered by <a rel="nofollow" href="https://searchmysite.net/">Search My Site</a>):
|
||||
</label>
|
||||
<div><!--We need the extra divs to serve as pseudo-table-cells.-->
|
||||
<input id="search" itemprop="query" type="search" value="domain:seirdy.one " name="q" />
|
||||
<input id="search" type="search" itemprop="query"
|
||||
value="domain:seirdy.one " name="q" spellcheck="true" />
|
||||
<div><input type="submit" value="search" /></div>
|
||||
</div>
|
||||
</form>
|
||||
|
|
Loading…
Reference in a new issue