49 Matching Annotations
  1. Last 7 days
    1. Different Conditions

      It would appear this section is about colorblindness, and nothing else. So could you just say that in the title instead of "Different Conditions". To differentiate this topic from #3, perhaps you can rename #3 to 'Choosing Colors for Contrast" and tip #4 "Choosing Colorblind Friendly Colors"

    2. Figure 3: Contrast Checker in WebAIIM

      These figures should be vertically aligned, either at the top or middle. Our IWP Tips and Tricks guide has a section on using Drupal utility classes to vertically align content using the CKEditor Bootstrap Grid (Robert or I can help).

    3. you can customize the fonts

      Consider adding an introductory sentence that introduces the idea that fonts are part of accessibility guidelines. It would also be nice to provide an overarching guiding principle (like simpler fonts are generally preferrable), or the take home message of the suggested posts (i.e., when in doubt, use one of the default fonts). As written now, the paragraph is simply a list of links to visit.

    4. the accessibility guidelines

      "The accessibility guidelines" suggests there is only one set of standards. This will be harder to interpret as time moves on. You could either make it general by dropping the word "the", or specify WCAG 2.1 if that's what you're referring to.

    5. StoryMaps

      Either here or in the title, I would add "ArcGIS" before the first occurrence of "StoryMaps", just to clarify what the post is providing tips for a specific product. It will also help with SEO.

    6. Ten Essential Ways to Make StoryMaps Accessible

      I like your choice of a square image for the post's primary image. It works well where the post appears in card view (example). The primary image doesn't work quite as well as the hero image (IMHO), where it appears ginormous and cropped across the top of the page. It might look better on a phone. You can of course omit the hero image if you'd like, or leave it as is if you like the look.

    7. Choice of basemaps

      This section is really short and doesn't say anything about the connection between basemaps and accessibility. Isn't there a recommendation to use one of the high contrast base maps?

    8. Figure 14

      Figure 14 shows a basemap, not a popup. Consider adding a sentence that provides useful info to the user, such as "The pop-up editor in the Web Map Viewer allows you to replace the default table with a custom text box that presents the attributes as formatted text."

    9. Map Viewer for accessibility

      The basemaps shown in Figure 13 look like the standard set of basemaps, but the caption suggests these have been approved for accessibility. Is that accurate?

    10. This

      To improve the logic of this section, consider adding a sentence along the lines of "Static maps can be more effective than interactive maps in directing the viewer's attention and conveying a message, especially when combined with accompanying text."

    11. Adding narration with static map images

      This is a little unclear. Do you mean adding narration to static map images? Or are you trying to stay that static map images operate as narration?

      Also, should the user add the narration to the static image using something like Photoshop (in which case it will be 'burned in' and not accessible to screen readers). Or does the Story Maps editor have the ability to overlay text onto a static PNG file?

    12. there are also tools

      This tip has much less text than all the others, seems unablanced. To contextualize why you're providing links to these two websites, would you want to say a sentence about color blindness as it relates to the WCAG standards, and how it differs from the contrast standards?

  2. May 2026
  3. Aug 2024
  4. Mar 2024