Yay Cloroform

Adult [ID:Profile pic by @squirreltastic . Overlord's head from Transformers over a bigender flag (pink, yellow, white, purple, blue). Header by Min An from Pexels. Semi transparent green leaves over a bright white background. End of ID]  Want to know more? Look into my blog, which doesn't make any fucking sense so welcome to the party.

[w-erewolfboy]

The noble archelon.

This took me weeks of carefully layering colours and washes and it looks so so good (even better in real life!)

[w-erewolfboy]

Image Description:

A mixed-media (primarily watercolour) painting of an archelon swimming among fronds of kelp. The painting is rendered in soft and bright colours, with luminous golds and yellows standing out among green-blue and the turtle in darker gray-blue-black tones. The texture of the painting is a bit fuzzy.

The archelon has a large wide shell like that of a leatherback sea turtle, wide and large front flippers with some visible scaly patches, and a pronounced hooked beak on its face.

[yinza]

Color version!

Available on Inprnt and in my Etsy shop!

[Image Description: Digital artwork of two fat women kissing. The woman on the left is light-skinned with pink hair pulled back in a braid. She wears a white T-shirt with purple trim, dark purple shorts, and matching ankle-high boots. Her arms are wrapped around the other woman’s waist. The woman on the right has light brown skin and darker pink hair styled in an undercut. She wears a dark red cropped tank top, a red miniskirt, and white sandals. She has one foot lifted and her arms looped around the first woman’s neck. /end ID]

[nattravn-art]

"Once I was a man, like you. But the lake helped me, to become something else."

Jakob Eilander Mr Owl is one of my favourite protagonists/antagonists in the Rusty Lake game series. I had to draw something showing his different (owl) faces.

[lintufriikki]

happy wavesday! 🐰🐱

i wanted to thank everyone for the overwhelming support on my soundkitty and shockbun plushies! they're in production now and will be heading to your homes within a few months 🥹 i hope you'll give them lots of hugs then! 💙💜

[aspec-mafia-official]

hey don't cry ok? qprs are real and you can have one <2

[ramiikin]

Started up skyrim again recently and had to paint a glitch I experienced, this game is still life changing so many years later

[usik-paleo-illust]

Doolysaurus

[parakeet]

just saw a 'comments' tab on someones blog you know where the following and likes tabs would be if enabled and it was just showing all the replies theyve made on peoples posts. this is fascinating when did this feature come out

[parakeet]

EMERGENCY - ITS AUTO ENABLED!

if you've made replies on posts there is now a tab on your blog showing every post youve replied to and your reply.

if this is not what you want, either go to your blog and click comments and disable it from there or just go to your individual blogs setting pages. just change it from blue to grey if you dont want everyone to see your replies AND the post you're replying to

PLEASE BE ADVISED that it is set to disabled for blogs that have not made any replies but it will turn ON if you reply with that blog in the future.! i just tested it with my main, which was greyed out but it turned on the moment i left a test reply

figured i'd get the word out bc i have not seen a single mention of this and i'm sure there are plenty of people who maybe comment on things they don't want on display for everyone to see on their blog lol. you can still look at your replies with it toggled off just no one else can, like locking the following and likes list

[parakeet]

so for some reason this feature was actually announced on the tumblr engineering blog. interesting choice not to reblog it to the staff or tumblr blog, esp considering they asked for user input on how to implement it, but i suppose considering the response to the last update maybe the replies would be too overwhelming...

so couple of clarifications. comments are disabled as default for primary blogs that have their likes disabled. they are seemingly enabled for all other blogs that have replied to posts

posts you comment on may show on your followers 'for you' page if you leave your replies publically available. they may, in the future, show in on your followers dashboard if your follower goes to their dash settings and enables this. apparently, if your likes are enabled, your followers can already see those on the dash if they've gone into preferences and selected to do so, which I was unaware of, and that seems to be disabled at default, but it's possible i disabled it previously and forgot about it ig

[askablindperson]

How do screenreaders navigate all the complex HTML and UI elements on a webpage? Like header bars and buttons and sidebars and other dividers on a page, and things like that.

This one may unfortunately be a little bit above my pay grade. I don’t know too much about the technicalities of HTML or web coding.

What I can tell you is that most of those elements are announced when we land on one and that we often use shortcut keys to jump to useful elements. We can quickly jump between headings, links, buttons, combo boxes, and form controls. If these things are not marked up properly, it can interfere with our ability to navigate the Page efficiently.

One of the most common accessibility barriers we face is actually unlabeled buttons. This is especially prevalent in mobile apps. It is not uncommon for me to download a new trendy app, only to open it and find that every single button in it is completely unlabeled so all I hear everywhere I touch is “button.” As you can imagine, this can make even the most simple apps completely unusable. Buttons must have accurate labels, not just the visual appearance of one. If the visual image on the button says submit, then the actual label should also say submit. This can also be a problem sometimes with unlabeled links.

Similarly, headings that are not actually marked as headings are a common issue. This is most common in documents rather than proper webpages—often times someone will make a word document and they will make a fake heading by just changing the font size to 40 without actually choosing the heading style. When a heading isn’t actually properly marked as a heading, this means that to a screen reader, all of that text is body text so we cannot use the heading shortcut to skip to different sections with different headings. Jumping between headings is a major way that many of us navigate webpages and documents quickly and get a sense of what kinds of information are present without having to manually arrow through all of it. It’s one of the closest things we have to skimming.

For things like side bars, these are often considered regions which we can also jump to with a shortcut. Sometimes these are also not correctly labeled or marked which can make them a little bit harder for us to find or understand what we are looking at when we are manually tabbing through links on it. However, if by sidebar you meant the visual divider, we do not interact with that element.

Dividers in general are not meant to be interacted with by a screen reader because it just adds clutter. One common piece of accessibility advice given is actually deliberately not to describe purely decorative dividers, such as a swirly line between paragraphs, because it adds unnecessary elements for us to move through and adds no functional benefit to us.

Beyond these things, my understanding of how it all works on a technical level comes to an end. I can tell you how I use a screen reader and I can tell you how I navigate websites in general terms, but I am definitely not a coder or web designer of any kind so I can’t get too far into the weeds of how it all works under the hood. I hope this is a useful enough explanation though to answer the broad strokes of your question.

[zombiethingy]

From a coder's perspective, there are two ways (that I know of) to make things as accessible as possible.

More information can generally be found by looking up "ARIA Roles" (here's a link to the Mozilla developer page about it to get you started: WAI-ARIA Roles)

Those roles are basically additional attributes on an HTML element that a screenreader can look at to figure out what that element was labelled as. For a lot of common HTML tags, like h1, table, button, ..., those roles are derived from the HTML tag and implicitly set. But if non-standard HTML is used, the additional aria attributes are needed to set this information.

The aria specification also includes other attributes, like aria-live (telling the screenreader that this element contains information that updates live/without a site refresh) or aria-busy (telling the screenreader that this element is displaying something that indicates a progress is happening) and more based on the specific element. There are also aria attributes to indicate if something is expanded or selected for example.

For (web) developers, I really recommend checking out the above link. I found the documentation really helpful.

[organicmatter]

guys i just found out about this site that does a daily guessing game, it’s phylogenetic wordle- so fun!!!

[askablindperson]

How do screenreaders navigate all the complex HTML and UI elements on a webpage? Like header bars and buttons and sidebars and other dividers on a page, and things like that.

This one may unfortunately be a little bit above my pay grade. I don’t know too much about the technicalities of HTML or web coding.

What I can tell you is that most of those elements are announced when we land on one and that we often use shortcut keys to jump to useful elements. We can quickly jump between headings, links, buttons, combo boxes, and form controls. If these things are not marked up properly, it can interfere with our ability to navigate the Page efficiently.

One of the most common accessibility barriers we face is actually unlabeled buttons. This is especially prevalent in mobile apps. It is not uncommon for me to download a new trendy app, only to open it and find that every single button in it is completely unlabeled so all I hear everywhere I touch is “button.” As you can imagine, this can make even the most simple apps completely unusable. Buttons must have accurate labels, not just the visual appearance of one. If the visual image on the button says submit, then the actual label should also say submit. This can also be a problem sometimes with unlabeled links.

Similarly, headings that are not actually marked as headings are a common issue. This is most common in documents rather than proper webpages—often times someone will make a word document and they will make a fake heading by just changing the font size to 40 without actually choosing the heading style. When a heading isn’t actually properly marked as a heading, this means that to a screen reader, all of that text is body text so we cannot use the heading shortcut to skip to different sections with different headings. Jumping between headings is a major way that many of us navigate webpages and documents quickly and get a sense of what kinds of information are present without having to manually arrow through all of it. It’s one of the closest things we have to skimming.

For things like side bars, these are often considered regions which we can also jump to with a shortcut. Sometimes these are also not correctly labeled or marked which can make them a little bit harder for us to find or understand what we are looking at when we are manually tabbing through links on it. However, if by sidebar you meant the visual divider, we do not interact with that element.

Dividers in general are not meant to be interacted with by a screen reader because it just adds clutter. One common piece of accessibility advice given is actually deliberately not to describe purely decorative dividers, such as a swirly line between paragraphs, because it adds unnecessary elements for us to move through and adds no functional benefit to us.

Beyond these things, my understanding of how it all works on a technical level comes to an end. I can tell you how I use a screen reader and I can tell you how I navigate websites in general terms, but I am definitely not a coder or web designer of any kind so I can’t get too far into the weeds of how it all works under the hood. I hope this is a useful enough explanation though to answer the broad strokes of your question.

[bugswags]

Headcanon

[thatneoncrisis]

been working myself up into a state of distress when i think about her. there is no cure

[discount-supervillain]

[blackoutbruh]

[norwegianfacecrusher]

My second ever paper pieced quilt friend! Lots of learning and seam ripping during the making of him, but I'm so proud of him! The blue fabrics are vintage bed sheets I inherited from my grandma, and his antenna and feet are a really pretty velveteen gifted by a friend.

This was also my first time trying out echo quiting and a new method of binding. But don't look at the back...

[tofusilken]

[ID: photos of a paper pieced quilt depicting a blue-grey isopod on a white background, bordered in blue. other photos show smaller pieces of the quilt coming together, and the echo quilting lines depicting the concentric shape of the isopod radiating out.]

[azulypink]

The last one

Ref💥