This is my discussion blog. The way it works is that when any pages in this wiki have a discussion page created for them, the discussion pages show up below. Also, any comments on my blog posts also show up here.
@Joey
Sectioning using "article" is helpful, as they provide semantics about the web page layout, but they are not considered to be a navigational landmark, so not all screen readers support navigating by "article" sections. From ARIA: article role
"Articles are not considered a navigational landmark, but many assistive technologies that support landmarks also support a means to navigate among articles. ..."
"header" elements are turned into navigational landmarks when they are descendants of the "body" element and this type of landmark is the "banner". They are the converse of a "footer" element which transform into "content info" landmark when it is directly child of "body". As navigational landmarks they are just meant for the whole page and not for individual sections of the page.
In Section 4.1 of WAI-ARIA Authoring Practices 1.1 is described which HTML semantic region elements get turned into aria landmarks.
Finally, headings are what most screen readers go to first for navigation of a web page. So for those reasons I'd recommend making the article titles headings. If you don't want to literally make them a "h1-6" because it would mess with your CSS then you can just set aria attributes which will change how the page is understood by assisstive tech but not affect any visual rendering of the page. a role="heading" aria-level="2"Lemons/a (using _ instead of angular brackets)
@samuel.kacer, the sections of the blog are inside html article tags, and the heading of each is inside a html header tag. That seems like sufficient semantic information to me..
I guess what I'll suggest is, if there's some reason that's not sufficient, you file a bug report on https://ikiwiki.info which is what the blog uses.
Hi,
I just stumbled onto your blog yesterday while searching for information on FRP in Haskell. Really cool stuff using Haskell for home automation in embedded systems!
I just wanted to post a comment because I noticed you include nice alt text on your images, which I greatly appreciate as a blind person. One other note on accessibility is that navigating around your blog would be easier if the article headings were some sort of HTML heading like
. Screen readers give shortcuts for jumping between different headings, so having sections of a webpage of intrest start with headings means as a screen reader user I could very easily switch between them instead of scrolling through the whole article before finding the beginning of the next one.
Just thought I would mention it since it seems you already care about accessibility.
Oh and happy late birthday!
Regards, Sam
Happy birthday, Joey! Feliz aniversário, Joey!
Mom brings it. I make it.
little sis
Startech ST4200USBM.
But uhubctl's home page has a good list of all known usable hubs, many much cheaper.
git-annex seems really cool! I'm one of those users who has large repository of source files I want to track with "vanilla git" and one subdirectory of very large files I want to manage with git-annex. Pardon me if this is mention elsewhere, but how can I set up git annex v7 to only annex files I explicitly "git annex add" and otherwise leave "git add" unchanged?
Thanks for all of your hard work. Your many projects and experiments in off-grid living are an inspiration.
There's a more general library that could be factored out of arduino-copilot, perhaps, to support other micros that don't use arduino sketches being programmed FRP style.
I don't know if bSpokeLight's image processing could be done in the Copilot DSL. Maybe.
It might be fun to use this to reimplement the C code that I wrote for https://github.com/nomeata/bSpokeLight
As the sun sets on another decade, I hope you post another writing reflecting on the past 10 years, the changes, and some milestones. I hope to join you in my own western island of Offgridistan in the not-so-distant future.
Using this library in git-annex, I saw a real-world speedup of 30%
in git annex find. That command has to read a list of files from
git ls-files, and read all their symlinks, and check if the symlinks are
broken or not. So there's a fair amount of IO, but FilePath overhead was
still significant and worth eliminating.
As far as I remember, yahoo groups didn't just offer a mailing list, but also storage for shared files (and I've seen the feature used extensively); those files haven't been pushed to anybody's mailbox and so are at a higher risk of disappearing (if the submitter doesn't have them properly¹ backed up themselves and is still available to re-upload them elsewhere, of course).
¹ once locally for ease of retrieval, once 30km away, 30 meters up from ground level, once 30 km away from both locations, 30 meters underground.
