The ArcGIS Pro User Experience Team invites you to participate in a moderated Usability evaluation targeting one of four (4) specific areas: ArcGIS Pro Data Management (Fields, Domains, Subtypes, and Versioning), Licenses & License Management, ArcGIS Pro SDK, and developing for Accessibility. Continue reading
In previous posts, we’ve seen how to map the location and frequency of transit service in your city. However, frequent, nearby public transit service isn’t useful if that service doesn’t take you valuable destinations, like your job, your school, the grocery store, … Continue reading
Story Map Journal received several key enhancements related to accessibility in the December 2017 update. Most of these enhancements, like keyboard navigation and improved semantic structure, just work for all stories new and old. But the ability to add alternative text to media … Continue reading
Accessibility is an important goal at Esri, and in the last two ArcGIS Online updates (September and December 2017), the Story Map Journal app received significant enhancements related to accessibility. Read on to learn more about these new features and … Continue reading
Many of the configurable applications available in ArcGIS Online allow you to choose a custom color scheme for the application. This lets you customize the app color scheme to match your organization colors, fit your app theme or just pick your favorite colors.
When choosing colors for your app it’s a good idea to consider the color contrast ratio to ensure that there is enough contrast between the text color and background so people with low vision can read the text. This is especially important if your web application needs to conform to 508 or WCAG 2.0 standards. Continue reading
Public transit (like buses and subways) is a vital service that connects people with their jobs, schools, healthcare, recreation, and more. Consequently, if you’re studying access to healthcare, assessing an economic development project, trying to choose a new site for … Continue reading
In the United States, one in four Americans lives with a disability that affects their way of life, according to the Pew Research Center. Using the internet is a fundamental piece of most people’s lives – and we should strive to make an internet experience that tries to work for everyone. To that end, the W3C has authored Web Content Accessibility Guidelines (WCAG.) This is an international standard that helps keep technologies available to those with disabilities. The most recent version is WCAG 2.0. WCAG 2.0 AA is considered to be the new equivalent of Section 508 for those working with the United States government.
Frequently, as able-bodied web developers, designers, and content editors, we forget to add in the extra layer of accessibility that will help people navigate our apps because it’s low on our priority list, the documentation is overwhelming, and/or we’re just don’t know how. In this short series of posts, I will try to tackle the top five criteria that each of these roles should be considering. In this first post, I am approaching WCAG 2.0 AA from the mindset of a developer and offering the top criteria that will make the most difference to incorporate into your work now.