Jennifer R "JR" Clark

My newest article on my publishing Substack shows authors how to get a strong start at gathering reviews from your release team and through pro reviewing sites. https://lnkd.in/gF7dA_7r

4

I’m seeing a worrying trend of archival conferences slowly transitioning into in-person only. At first they were digital, then they were hybrid, and then digital accommodations for presenters under extenuating circumstances. This was problematic enough as digital audiences began to be eliminated. Many of whom finally felt they were able to participate for the first time. Presenters also needed to disclose why they needed digital accommodations. Something that may make presenters quite uncomfortable to disclose. Me 10 years ago certainly wouldn’t have been able to. There are certainly exceptions, but I’ve noticed that we are getting to a stage where some conferences are eliminating language that even suggests digital accommodations in their callouts. Conferences heavily focus on networking and hosting in-person only eliminates those who may benefit from that networking most. Travel can be difficult for many of us. For myself, it’s health related. I also think of those who need to care for small children or sick relatives, students/early career professionals/those in the global south who cannot afford to travel because few stipends exist, and those who work in very small non-profits that are not awarded the time to be away. This is particularly troubling when so many conferences are themed around underrepresentation. I understand the difficulties that go into organizing a conference. I’ve been responsible for organizing events, including conferences in the past. I was organizing guest lectures during the pandemic. There are contractual obligations to sponsors and host sites but we need to be doing more. So, think about why certain demographics are more prevalent in our field. By returning to in-person only, we’ll always be stuck at the stage of “we need to be a more inclusive field.” Those voices that are necessary for such inclusion initiatives will never get to participate in the “here’s how”.

34

7 Comments

Oldie (2019, so not *that* old), but goodie: The Accessibility Tree by Ben Myers. I couldn’t agree more that it’s the job of a professional web developer to be a good steward of the accessibility tree. It starts with semantic HTML, but can get complex fast. I’ve seen plenty of developers gloss over the underlying constructs of the web in an effort just to get things done (e.g., by relying on frameworks without understanding what they’re actually doing). In the long run, knowing how browsers work makes you a more effective developer, so my advice is to invest time in building your understanding of the web as a platform. https://lnkd.in/gNtrramj

7

3 Comments

Manual critique vs. automated systems. As someone deeply invested in the value of nuanced insight, I firmly stand on the side of manual critique. Automated systems certainly have their merits, but they often lack the finesse and context that human reviewers bring to the table. Whether it's analyzing creative works, evaluating complex projects, or providing feedback on personal development, there's an irreplaceable depth that comes from human understanding. Let's champion the human touch in feedback processes. It's not just about catching errors; it's about understanding intent, context, and the unique nuances of each situation. Let's elevate the dialogue and ensure that our feedback processes are as rich and insightful as possible. #ManualCritique #FeedbackMatters #HumanTouch #ProfessionalDevelopment #LinkedInReflections

5

Today I mailed the latest issue of the Scalene newsletter to subscribers, examining the changing landscape of peer review in the age of AI. This week we’re looking at the Black Spatula Project, reviewing articles via voice, and moving the review process upstream to the point of authoring. Take a look here (link in comments) and sign up for next week’s update.

16

2 Comments

Some accessibility pros holler: "Always use plain language that a 5-year-old can understand." On the other hand, other accessibility pros argue: "Context and detail matter. Don't oversimplify." No wonder you're scratching your head! So how do you decide which accessibility advice will pay off for you as an inclusive brand? Well, it depends. Really. It depends-- on your audience. Who are they, and what do they need? on the content. What are you trying to convey? on the platform(s) you use. Don’t jump from one piece of advice to another without learning what works best for you. Sometimes, you have to mix a bit of both—simplicity and complexity—to get it just right. Remember this before you take any generic accessibility advice at face value! For more tips on making your accessibility journey as smooth as your morning cuppa joe, follow me for more tips and insights into accessibility and writing!

23

16 Comments

Accessibility news for American schools and universities... The US government has released new requirements. Today, the US Department of Justice (DoJ) officially published a final rule for the Americans with Disabilities Act (ADA) Title 2. In the past, the DoJ has confirmed that the ADA covers digital content and services. The final rule clarifies what that means for public schools and universities. I have provided a link to the full text of the rule in a comment. But here's a very brief summary. (1) Digital content and services must be accessible. (2) To be "accessible," a product must conform to the Web Content Accessibility Guidelines, Version 2.1, Level AA (WCAG 2.1 AA). This is a minimum requirement. (3) Fewer exceptions will be allowed. (4) Institutions will have 2 to 3 years to comply. For me, one of the biggest takeaways is that content must meet WCAG 2.1. Over the last two years, some state Departments of Education have transitioned to WCAG 2.1. Educational publishers have also moved in that direction. But many schools and universities still aim for WCAG 2.0. In part, the continued focus on WCAG 2.0 relates to US accessibility law. WCAG 2.0 AA is the standard defined in Revised Section 508 of the Rehabilitation Act of 1973. Section 508 doesn't specifically apply to educational institutions. But state funding and federal grant rules often require it. I'm not going to get into the weeds comparing WCAG 2.0 to 2.1. But here's one major difference. WCAG 2.1 has new standards for image contrast and reflow. These standards can significantly affect learning products such as digital textbooks, PDF journal articles, and graphics-heavy STEM content. Another big takeaway: The final rule also applies to content created by individual instructors. Not just officially procured products. How can institutions achieve accessibility at the instructor level? It's easy to say, "Invest in increased awareness-building, training, and instructional design support." But budgets and skilled staff are often limited. Schools may need outside partners to help build accessibility solutions for specific courses or instructors. Inevitably, there will be puzzles to solve as institutions respond to the final rule. But I applaud the DoJ for finally bringing some clarity to ADA Title 2. In the end, everyone benefits from clearer expectations and timelines. Image description: A notecard, eraser, and pencil lie on a desk. The following text is written on the notecard. A.D.A. Title 2, Final Rule. 1, Digital content must be accessible. 2, Accessible = WCAG 2.1 AA or more. 3, Fewer exceptions allowed. 4, Timeline = 2 to 3 years. #accessibility #inclusion #EdTech #HigherEd #education

65

10 Comments

All my guides and downloads about foresight are now available on Foresight in the Present - free of course.

247

21 Comments

New blog post on IndirReader.com

2

AI will aid and empower authors and editors, not replace them. This author captures some of the nuances of what we are trying to build at #Spines well

6

Accessibility is inside the tags *and* between the tags. Semantics, heading hierarchy, and reading order are essential. But good tagging can't replace good content design. Here are 10 tips for creating inclusive text content. Tip 1: Use plain language. "Plain language" means the text is as clear and simple as possible for the given subject and audience. Tip 2: Headings should be descriptive, consistently structured, and as brief as possible. Tip 3: Link text should identify the link's purpose or destination. Tip 4: In-line links should follow the text that provides context for them. In other words, put the link at the end of the sentence. Tip 5: User instructions should be *on the page* in an obvious location. Don't assume people will know what to do based on context clues. Tip 6: Don't get creative with tables and lists. Don't use a table when a list will do. If a list has paragraph-length list items, use paragraphs instead. By definition, a one-column table and a one-item list don't exist. Tip 7: Include figure descriptions in the body text. That way, everyone can benefit from them. Tip 8: Give alt text the same attention as the on-page content. The body text and alt text should form a cohesive whole. Tip 9: Use MathML for rendering equations. But be prepared to provide descriptions for the math in PDF. Tip 10: Avoid complex page layouts and overloading the page with content. Invest in creating the best content, not the most content. Often, blank space is our friend. Image description: Text states, Accessibility is inside the tags and between the tags. How can we make content more inclusive? The words, inside the tags, are in angle brackets. The words, between the tags, are between two empty pairs of angle brackets. #accessibility #UX #content #education #EdTech

19

1 Comment

Amazon has now made available the first three chapters of Exit Velocity under the "Look Inside" button. These give you an idea of the book's characters, subject matter, tone, and writing style. https://lnkd.in/gnwPaezG #books #newbooks #workingclassliterature

2

This type of AI assistant front end to documentation is likely the future of technical documentation. I don't think we're quite at the point where technical writers will be replaced. Someone has to write the content AI learns from. In fact, it's possible good technical writers could end up becoming more valuable since the documentation they write to teach AI could end up replacing a host of support representatives in the long run. https://lnkd.in/gaQzSECh

1

There's actually a fairly simple test against the argument that an LLM model doesn't actually store information - can you use that LLM to reproduce in whole or substantial part the content of a given document? If the answer is yes, then you are in effect stealing the work unless you have permission to use it, because that LLM becomes a publishing system. It is, admittedly, a lossy publishing system, because there are other pieces of information that get mapped in that share some similarity, but that's irrelevant here. If I copy a novel, but the copy machine is a little low on toner so there's noise in the output, that doesn't invalidate the fact that I have still copied the content without permission. This is part of the reason why I think that most American companies will not make anywhere near the money that they think they will on GenAI. Americans have no interest in copying Chinese content, while the Chinese are perfectly happy copying Western content. Does that validate American AI companies abuse of copyright? Not at all, it just means that in the end, they won't benefit from it. Eventually, of course, model corruption will end the whole fiasco, but that's a different issue.

16

3 Comments

An excellent follow-up to his previous post, "Show Me the Money: Making a Business Case for Accessibility in Small and Large Publishing Organisations," which I shared and commented on in my last newsletter. If you're not thinking about accessibility yet, Mellins is making a compelling case for why you should be, and how to approach it. Spoiler: Don't blindly fall for AI snake oil solutions. #accessibility #publishing #AI

2

1 Comment

AAPACN members only. Colleen Toebe MSN, CWCN, RAC-MTA, RAC-MT, DNS- MT and Jasmine Travers, PhD, MHS, AGPCNP-BC, RN address why flexible scheduling is so important in recruiting and retaining staff--and how to reap the most benefits from it. #longtermcare #nursinghomes #snf https://lnkd.in/ecYdaP87

1