Tag: Accessibility

The Linked List is a collection of interesting articles that I have recently read and found beneficial. Today's links cover web accessibility, TypeScript adoption, and React Hooks. Hey Domino’s, You’re Not Delivering: Recently Domino's petitioned the United States Supreme Court saying that they did not need to make their website accessible. This post breaks down how the current website experience affects real people and callouts for areas of improvement. An Intro To Screen Reader Testing for Sighted Developers: This is a great article and introduction into using a screen reader for accessibility verification. Automated testing cannot catch all accessibility errors, including focus management. Getting some time using a screen reader is a…

The Linked List is a collection of interesting articles that I have recently read and found beneficial. Today's links cover web accessibility, upcoming features to ECMAScript, breaking down imperative vs declarative programming, and why your GraphQL APIs should embrace nullability. When Is A Button Not A Button?: Buttons have a number of built in accessibility and user interactions built in. Learn more and the dangers of trying to substitute other elements for buttons. Optional Chaining in JavaScript: This past week optional chaining entered stage 3 for TC 39 consideration. This syntax enables cleaner code for drilling without a bunch of type guards. Check out the full proposal at the link above. If you’re interested in trying it out use…

The attribute is an essential part of the HTML element. It identifies the main language of the document's content. This is used by screen readers to determine the pronunciation of words. Screen readers have a default language setting, but will respect the language specified in the element if they differ. However, if this attribute is missing, and the language of the document is different than the screen reader's settings, the user will receive a subpar experience with incorrect pronunciations. For more information on the accessibility of this attribute, check out Deque University's detail page. React Helmet and JSX In many React development scenarios, the shell HTML template is not immediately available to the developer. In other…

I have used ESLint for a long time, often extending the recommended rules from various plugins. I only read a rule’s documentation if I wasn’t sure why it was being flagged in the linter. Last month I read through and manually set 381 ESLint rules, reading the accompanying docs for each rule. I discovered that ESLint is more than enforcing community guidelines on code quality. It also helps to shape use of the language as a whole and through project specific rule usage. Greater control for team objectives There are a number of rules the recommended configurations of ESLint or various plugins do not enable by default. These rules serve specific needs of a given project. They can be enabled and configured on a per project basis and provide…