Eric Meyer

In addition to my talk at Write the Docs, I created the sketchnotes, which are posted here: https://lnkd.in/g5Jmej-v

33

3 Comments

This week, I came across Maggie Appleton's term "barefoot developer." The concept is as follows: non-tech folks have been pushed to learn how to code/program (e.g., doctors, teachers). These folks may not be interested or have the time to learn. On the other end of the spectrum are professional developers. In the middle are "barefoot developers" who use pre-existing software and tweak it to meet the needs of a small group. Their needs will never be fully met by commercial products nor can they hire a professional developer. The barefoot developer is the person who creates a "home-cooked" app to fill that gap. I work in a small library and fulfill this barefoot developer role. Some of my projects have included using * JotForm to develop readers' advisory tools * Coda.io to build an interface to manage book groups * Notion to create a dashboard/homescreen for book groups * Floorplanner to design 3D models to reuse elsewhere including in home-built kiosk software What do you think of this concept and are you a "barefoot developer" for your library? If yes, what projects have you been built? Read Maggie Appleton's conference notes at https://lnkd.in/eN6yjrxw

3

Tooltips and Toggle Tips experiment I recently developed a tooltip web component using data-attributes to enhance testing capabilities and ensure accessibility. Additionally, I created a toggle tip component as part of this experiment. This project is a deep dive into making these components as accessible as possible. While these are not yet production-ready, they are useful for testing purposes—if you like them, then feel free to use. 😁 Customisable tooltip web component (POC) https://lnkd.in/gBevSzzg Customised toggle tip web component (POC) https://lnkd.in/gvhYsPVe #WebDevelopment #Accessibility #WebComponents #Innovation #Testing

4

1 Comment

Creating an accessible website is essential for reaching a broader audience. Qualibooth.com provides detailed ADA and EAA compliance audits to help businesses achieve full accessibility. Get a free scan to see how your website's accessibility compliance rates at https://lnkd.in/gjfC_NBe #ADACompliance #EAACompliance #WebAccessibility #Qualibooth

1

Fundamentals of a Professional Development Plan https://lnkd.in/gtEdFwGz An Accendo Reliability webinar recording with Fred Schenkelberg. Let’s examine a few principles for development plans so you can learn and master what you desire to learn and master.

4

Weekly Tech Tip #6: Headings Hierarchy for Web Accessibility This week, we're diving into the world of headings hierarchy and its impact on web accessibility. Headings (H1, H2, H3, H4, H5, and H6.) aren't just for aesthetics! They create a clear structure, making your website understandable and navigable for everyone, including sighted users and those who rely on screen readers. Why Headings Matter for Accessibility: • Improved User Experience: Headings act like signposts, guiding users through the main points and sub-topics. This makes it easier for everyone to find the information they need quickly. • Screen Reader Friendly: Screen readers use headings to help users jump to specific sections of a webpage. A clear hierarchy ensures efficient navigation for users with visual impairments. • SEO Benefits: Search engines also use headings to understand your content's structure and relevance. A well-structured hierarchy can indirectly improve your search ranking. Building a Strong Heading Hierarchy: • H1: The Main Attraction: This is your single H1, the main topic that grabs attention and summarizes your webpage's content. • H2: Key Sections: Use H2s to break down your H1 into clear, digestible sections. Think of them as chapter titles within your webpage. • H3: Sub-points: Dive deeper within your H2 sections with H3s. These are great for highlighting key features, steps in a process, or benefits. Heres an example of some headings in HTML: ---------- <h1>Welcome to my page!</h1> <h2>Learn about me</h2> <p>Some information</p> <h3>Edgucation</h3> <p>...</p> <h3>Experience</h3> <p>...</p> <h2>My services</h2> ... ---------- Pro Tip: Most Content Management Systems (CMS) offer built-in heading options. Simply select the heading level (H1, H2, etc.) while formatting your text. Remember: Headings should be clear, concise, and accurately reflect the content they introduce. By implementing a strong heading hierarchy, you create a website that's inclusive and accessible to everyone. #WebAccessibility #Headings #ContentStructure #TechTips P.S. Stay tuned for next week's Tech Tip where we'll explore another accessibility best practice!

4

👁️   "What are the effects of component-based architectures? They mean that developers no longer have to know HTML to write HTML. When it comes to accessibility, this is not a good thing. The vast majority of accessibility lives in the markup. Not understanding which elements to use or what is even valid to do in the language is always going to cause accessibility barriers." #a11y #HTML #react #JavaScript https://lnkd.in/eyx3T4Aw

5

1 Comment

TGIF! Here are some tips for designing interactive emails on #figma from a rookie who thinks he knows what he is doing. 📌Avoid big blocks of information. 📌Break them down into small chunks. 📌Use headings for clarity of information. 📌Use center alignment for headings and keep it consistent. Left to right alignment is more legible. 📌Do not overdecorate your text especially if it is a block. 📌Add visuals to support your text. Use images, emojis, and icons to make the reading experience pleasant. You can also use videos. #Day12of14 #Linkedinpowerup #14dayslinkedinpowerupchallengewithAlice #TGIF #Emaildesign #Figma #Copywriting

28

20 Comments

Accessibility tip: Don't fall for the H2 subtitle trap. By "subtitle," I mean the secondary title that adds detail to the main title of a document. It can be tempting to assign Heading Level 2 to the subtitle. The main title already has Heading Level 1. The subtitle is often on another line. Its font is smaller. But we should always assign heading levels based what the heading identifies. Although it looks different, the subtitle also refers to the *whole* document. So, it should have an H1 tag. There may be exceptions. Some subtitles are so long that they resemble short paragraphs. In those cases, a Paragraph tag could be more appropriate. This might seem like a small detail. But often, small details can have a big impact on user experience. The good is they’re easy to implement. Image description: An excerpt from an essay. At the top of the page, the main title is centered above the smaller subtitle. The main title reads, "An H1 in Disguise." The subtitle reads, "The Truth about Subtitles." The opening paragraph summarizes the information from this post. #accessibility #gaad #EdTech #education #content #publishing

26

6 Comments

In recent time we've witnessed the emergence of communities, as a way of reaching of out to a larger audience more especially developers. Sadly most community moderators do not understand the role a community has to play in the life/career of an individual, and that promoted my research. so I came up with this beautiful blog: https://lnkd.in/dFUsJJei #developer_community #Commudle

2

3 Comments

Improving rendering performance with CSS content-visibility https://buff.ly/4ddS5HT If you’re not familiar, content-visibility is a new-ish CSS feature that allows you to “hide” certain parts of the DOM from the perspective of layout and paint. It largely doesn’t affect the accessibility tree (since the DOM nodes are still there), it doesn’t affect find-in-page (⌘+F/Ctrl+F), and it doesn’t require virtualization. All it needs is a size estimate of off-screen elements, so that the browser can reserve space there instead. Source: Improving rendering performance with CSS content-visibility | Read the Tea Leaves (https://buff.ly/3zvouMr)

41

1 Comment