This post never dies isn't it?
P.S. I am in the process of crafting a brand new offer for my newsletter, https://t.co/n4nq0wUOKm
Yes, a brand new offer, a brand new content.
Look, this is your chance to see if the brand new content suits you.
So if you want to see a glimpse of the brand new content, feel free to subscribe below.
If you don't like it, unsubscribing is also free.
No hard feelings.
Check it out:
Look! New promo vid for our newsletter,
Level Up! Founders @levelupfounders
Look how crisp the animations are and how inviting the video is. Awesome right? ๐ฅ
Big shout-out to Shariful's team in Vidiosa.
Thanks brother! ๐ซก
And guys, if you wanted to know more about Vidiosa, check the replies!
Level Up, Founders! monthly bulletin is dropping in a couple of hours ๐
From April Fools and the recent xz hacks, up to our usual dose of #buildinpublic monthly learnings, the monthly bulletin has everything you need to see!
Subscription is FREE: https://t.co/ASJUsRBChf
Here's an Easter surprise:
The Postman work is the start of something bigger:
Me optimizing my curation process for Level Up, Founders! Newsletter
Guess how it works?
Tomorrow's bulletin will reveal the sauce.
Best way to not miss it?
By subscribing๐https://t.co/ASJUsRB4rH
Big shoutout to my friend @pseudokid for featuring Budget Kanban in their latest newsletter bulletin! ๐
His newsletter is dedicated to helping beginner founders level up in their entrepreneurial journey! If you're just starting out or looking to grow, consider subscribing to https://t.co/7G1PGsKSSJ!
#indiehackers #buildinpublic
Level Up newsletter loves to have your feedback!
How?
1. Subscribe to https://t.co/HfoHN6Rlga
2. Wait for the 3rd bulletin in your inbox
3. Go to the section: "NEW: Have ideas for us?"
Or just watch the video below ๐
P.S.
Video made with MotionShot ๐ฝ๏ธ
Feedback board is powered by https://t.co/sDBUkvaZTH โ
One hour from now..
We are shipping Bulletin No. 2 of our newsletter Level Up, Founders
If you subscribe right now (link below), you'll get:
๐ฅ 1 new blog post
๐ฅ 5 handpicked community Twitter posts from the past 2 days
๐ฅ 6 tech news from the past 2 weeks
Subscribe to get it (link below) ๐
@starwardshar I am planning to feature products on my newsletter, Level Up, Founders!
Stay tuned because everyone is welcome on this ride!
Take a look ๐
https://t.co/fSsN7ppSMN
Did you know https://t.co/AJctansvym isn't just for landing pages?
I just dug into @pseudokid's new Level Up Founders! Newsletter and it scored 77%!
Before I offer some advice about what can be improved, let's look at what it is doing well (for you to copy?)
Headings & Lists
Heading heirarchy is clear and relevant. A h1 is provided that clearly explains the page's purpose and each section of content is introduced by the correctly nested headings.
Programmatic list elements are applied to both ordered and unordered lists throughout the page.
Why this is important?
Headings and clear structure of information relationships such as lists, allow for Assistive Technology (AT) users to navigate and understand your page's content effectively.
Clear bonus, it's essential for SEO to understand how relevant your page and content is to certain keywords.
Alright - What can be improved?
First Improvement: URLS
Most of the URLs in the article use the actual URL as the link text.
Why this is important?
Screenreader users hear a lot of unnecessary and confusing noise.
Sighted users can quickly parse a readable URL to extract the key information (Twitter, Pseudokid). Whereas screenreaders will read out the entire URL including "/1763104898940567914" - nobody wants that.
Voice-Assist users will also struggle to interact with the correct link, particularly when there are multiple similar links on a page as assistive technology will not understand which twitter post the user is referencing.
Wait, did I mention that SEO bonus again? Let search engines know the intent of a link, not just your users.
How do you fix it?
Give each link a clear name that lets your audience know where they'll end up in a readable format. For example "Check out my twitter post from February".
Ensure links that go to the same destination are given the same name!
Short URLs where the domain is the destination name like recaps . fyi are fine!
Second Improvement: Keyboard Focus
The menu navigation isn't accessible to keyboards and whilst emojis are given keyboard focus.
Why this is important?
Keyboard users, including but certainly not limited to screenreader users, are unable to explore the rest of your website :(
Whilst backlinks, and interactivity is provided to decorative emojis.
How do you fix it?
Mark up the menu as a native dropdown, ensuring aria-expanded attributes are correctly applied. (This is hard to share over a tweet - DM me for example).
Remove the unnecessary link mark-up from the emojis - no additional aria-label or mark-up is needed as screenreaders can understand and communicate emojis!
@pseudokid hope you enjoy your #a11y roast!
Any other #buildinpublic founders want one?
Yesterday, I launched my newsletter.
That newsletter has a blog.
Charlie @CharlieYalf audited my blog.
Charlie is a known advocate of accessibility, so his audit revolved around that. He pointed out which accessibility pointers I nailed, and which one I can improve on.
One of the things that needs improvement is me optimizing my blog for screen readers.
Of course, the curious side of me asked Charlie on how I can test my blog for screen readers.
We all know how generous Charlie is, so he made a crash course, not only for me, but for everyone in the community. ๐
The guide is free, and is quoted below.
Have a look and let us know what you think.
I launched my first newsletter bulletin yesterday.
๐จ 35 emails sent
๐ฉ 29/35 opened
๐ 10/35 clicked to check the article
Thank you for your support! ๐ซก
Question, tips on what to measure aside from the stuff below?
The very first bulletin of our newsletter is out! ๐ซฃ
To everyone who subbed, go check your inboxes!
We are at 30 strong! ๐ฅ๐ฅ
Thanks everyone! This is just the beginning.
#buildinpublic