Ed C
@Frontend_Ed_
Frontend Ed 👨💻 Building React apps for B2B SaaS in AI and eCommerce 📈Sharing knowledge and sick tech picks in the process
You might like
First EVER YouTube, and hopefully the first of many to come 👨💻 watch this if you've a React/Next.js project that's got long-neglected ARIA issues coming up in Lighthouse youtube.com/watch?v=vCLF9i…
youtube.com
YouTube
ARIA Mastery 🪄 Tips and Tricks for Elevating Your React App's...
I'm only one module in and I'm absolutely loving @JoshWComeau's CSS course 🙌 Such a thorough approach to teaching, not shying away from but embracing the messiness of CSS. Best Black Friday money spent by far
Software is one of the least structured and constantly evolving paths, so its reassuring see thought leaders sharing their journey One takeaway: accessibility is often neglected by developers which creates a need for advocacy. Be patient, and bring people on the journey with you
Confession: I’ve been writing software for over 20 years, but I often learn things I feel like I should have stumbled across years ago. 🚫 I spent 5 years working with no source control (in the late 90’s, source control wasn’t as popular). 🚫 I spent 10 years thinking automated…
Even the wizard @mattpocockuk has to ignore Typescript sometimes, so don’t feel too bad if you do it too! However, how you suppress TS matters; ts-expect-error is preferable over ts-ignore as it will throw an error if the error itself goes away, prompting you to remove it 🧹
Sometimes, you just need to suppress an error in TypeScript to move on. Yes, we all do it. No shame there. When you do suppress errors, what's your preferred method?
Excellent article on React.memo by @TkDodo 🙌 It can be tempting to slap memo and useMemo all over your code base and consider perf optimisation complete 🚀 but there are many pitfalls that React devs are often not aware of. Highly recommended read 📖
So I wrote about why I think React.memo is worse than the other alternatives that exist to improve performance in a React app: tkdodo.eu/blog/the-uphil…
WCAG criteria for visible focus and drag-based interaction are changing in a big way 👀 Unlike most 2.1 AA level issues, these new criteria will be challenging to develop automated tests for, so developers need to upskill and complete more manual testing to ensure compliance 🏅
WCAG 2.2 is now published as a Web Standard (“W3C Recommendation”)! For an introduction to WCAG, see WCAG 2 Overview w3.org/WAI/standards-… There are a few updates in #WCAG 2 FAQ w3.org/WAI/standards-… And new "In briefs" in What's New in WCAG 2.2 w3.org/WAI/standards-…
#5 🎯 Without product-market-fit, it really doesn’t matter how well built your thing is. As a developer, you should feel comfortable asking tough product questions when changing roles
The 5 keys to successful software: 1. Well built 2. Well marketed 3. Well supported 4. Well documented 5. Solves the right problem 5 is the key. 1-4 are success multipliers. But if we solve the wrong problem, none of the other stuff matters.
Excellent episode and hopefully the start of a new Accessibility-focused mini-series from @syntaxfm @stolinski and @wesbos answer common and less common questions about heading levels and their importance for assistive tech
Can you actually have more than one h1 on a page? Should your logo be an h1? If I have an h2 heading is it ok to have an h4 directly below it? How do I establish a strategy for html headings? We answer all these questions and more on the latest Syntax. syntax.fm/show/674/a11y-…
Just had a stellar mentoring session with @KokoChris_dev on adplist.org 🙌 If you're looking for mentorship from experts, definitely give the platform a try, and hit Christos up if you're in the frontend world 👩💻
For a while I have been mentoring on adplist.org I have a few slots per week open. I would be very happy to be fully booked each week. This costs nothing btw. adplist.org/mentors/christ…
adplist.org
ADPList: Get mentored by Christos Kokolios on ADPList
Tech professional with more than a decade of Made the switch to software early in my career and never looked back.
How do you build an accessible component library for your SaaS? Starting with a headless UI library like @radix_ui gives you a huge head start: - easy-to-use API - great accessibility built-in - styling flexibility if you use primitives, or, - "bootstrap but good" with themes
If your app is client-side React, it's probably inaccessible ❌ SPAs, by nature of being single-page, provide a poor navigation experience for screen reader users OAF Project shows us a great solution, which I'll be demoing in an upcoming video 👀 github.com/oaf-project/oa…
NEW video time 🔔 join me in fixing a critical accessibility error in a popular UI library, and learn about ARIA roles and attributes for tabbed interfaces along the way youtube.com/watch?v=1b4jDW…
youtube.com
YouTube
Fixing a hidden accessibility KILLER in a hyped React & Tailwind UI...
United States Trends
- 1. Northern Lights 46.6K posts
- 2. #Aurora 10K posts
- 3. #hazbinhotelspoilers 2,333 posts
- 4. #chaggie 4,260 posts
- 5. #huskerdust 8,271 posts
- 6. Vaggie 5,443 posts
- 7. #DWTS 53.4K posts
- 8. Carmilla 2,434 posts
- 9. MIND-BLOWING 36K posts
- 10. AI-driven Web3 N/A
- 11. H-1B 37.1K posts
- 12. Superb 22.7K posts
- 13. Justin Edwards 2,557 posts
- 14. H1-B 4,292 posts
- 15. Sabonis 6,276 posts
- 16. SPECTACULAR 25.4K posts
- 17. Wike 224K posts
- 18. Gonzaga 3,021 posts
- 19. Cleto 2,672 posts
- 20. Justified 18.1K posts
Something went wrong.
Something went wrong.