C.R.E.A.M

[coalcube]

Coal ruins exchanges around me - spitey spitey fic y'all. 

Sign-ups: Fri 15 Oct to Sat 23 Oct (Countdown)
Assignments out by: Mon 25 Oct
Default deadline: Sat 11 Dec
Assignment deadline: Sat 18 Dec
Reveals: Sat 25 Dec

Mini-Challenges:
Yuleporn | Make the Yuletide Gay | Jewltide | Three Turtle Doves 
YuleBuilding | Two for One | Crueltide | Yuletunes | Yule Be First
YuleSwaps | IF | Wrapping Paper | Yumadrin | MultiLingYule
....and a Partridge in a Pear Tree!

Yuletide Discord for Hippos & Exchanges After Dark Discords for Namespace drama 18+ discussion. Google Group for PHs.

yuletide | yuletide_admin | Writing Post
2021 Collection | 2021 App (bonus) | Letter Post

Flat / Recent | Top-Level (Last) | FAQ | Search

Comments

[(Anonymous)]

Some people do really elaborate coding and I am in awe. I just do simple jumps because I want to make it easier for people but I don't know or have a lot of time to mess around with fancier coding.

What I do:

Intro
Html for Fandom Jumps
General Likes and DNWs
Fandom section 1 (ends with a "return to top" jump)
Fandom section 2 (ends with a "return to top" jump)
Fandom section 3 (ends with a "return to top" jump)
Signoff

And how I do the html is:

Each one of the fandom sections is set up under a different lj cut. Then for the fandom jumps html, I put:

<*a href="cutlink1address"*> (update the cut link for each section)

And for the back to top html, I put:

<*a href="letterlink">

(Take out asterisks, of course, those are in there to make it display in this comment properly)

[(Anonymous)]

Elaborate coding is cool and all, but clear and readable is really the important part- it doesn't need to be fancy.

[(Anonymous)]

And if you want fancy coding for clear readability, using html header tags -

<h1>like this</h1>

<h4>or this</h4>

can actually be better because things like screenreaders, autosummaries, and keyboard controls can parse them.

[(Anonymous)]

Can you explain this in more detail, or link an explanation?

[(Anonymous)]

Not CYRT, but the proper use of "semantic markup" means that it's easier for content to be programmatically understood for accessibility. By using HTML tags that sort of "call a duck a duck," things like screen readers can more easily understand how to process a document. H1-5 tags, for example, give an understanding of heading levels - 1 being the most important (usually the document title) and 5 being the least. They can be read differently than general body text and be jumped to by readers, as an example of how it can be more accessible.

For a longer write up, articles like the following can be helpful.
https://uxdesign.cc/semantic-html-the-foundation-of-web-accessibility-e5bbecad7c17

[(Anonymous)]

html is fundamentally a "markup" language. That means it's meant to leave signs in the webpage telling software what to do with the content. When you do things like change font size and color, it might look fine, but all the software knows is that the type is big and a funny color.

the "header" tags, instead, tell the software that this is a heading, and it should do with it what it does with a heading.

This means - people's journal styles, browser settings, and custom HTML will display it in a way that means "heading" to them, even if it's not the same colors or sizes you would have picked.

- devices like screenreaders can tell the people listening to them that "this is a header"

- devices to help people navigate through a page - like screenreaders, or special controls for people with limited dexterity - can let the user tell them to easily skip to the next heading.

- programs that try to actually parse the text can use the header tags to figure out the structure. For example there are programs that will try to generate an "outline" of a page, like an automatic table of contents, and they can use header tags to do this

Basically any time you want a section heading or title to stand out, it's better to use a header tag than messing with color/size/etc manually or just using bold an italic.

The header tags are numbered h1 and so on, you use them just like you would a Bold or Italic tag, and they look like this (it will vary based on page style, they look mostly red to me because I'm logged out and using DW basic):

Header 1

Header 2

Header 3

Header 4

Header 5