Sanette Tanaka

New York City Product Designer Joined about 4 years ago

  • 0 stories
  • 1 upvote
  • Posted to AMA: Vox Product Accessibility Guidelines, in reply to Mario Vasquez , Aug 31, 2016

    Great question. Testing is incredibly important, and we include a list of our favorite tools at the end of our checklist.

    Speaking for myself, I find it most helpful to test throughout my design process. So, for instance, I will test the contrast of color and type combinations in my Sketch files using a tool like Colour Contrast Analyser. Once the product is in production, I use the WAVE Chrome extension to check contrast and other accessibility best practices. I use Responsive Web Design Tester to test various screen sizes, and, if I have time, view it using Apple's built-in accessibility settings like grayscale.

    We include other testing plans for QA teams to run through in our checklist, but it's a good idea for others on a team to do the same. At minimum, we advise running a browser check like WAVE, navigating via tab navigation, and using a screen reader.

    0 points
  • Posted to AMA: Vox Product Accessibility Guidelines, in reply to Johnson Vino , Aug 31, 2016

    Hi Johnson! I think you're asking about why we chose to create the checklist tool listing all of our guidelines, rather than release our text docs. We considered releasing the docs as they were, but we realized that the role-specific docs worked for our company, but might be too prescriptive for other teams. At the same time, we had been experimenting with one-off checklists for some of our own projects and found them to be really helpful. The checklist tool makes it possible for teams to create their own slimmed down docs containing only the guidelines relevant to the project they're working on.

    1 point
  • Posted to AMA: Vox Product Accessibility Guidelines, in reply to Jonathan Shariat , Aug 31, 2016

    Hi Jonathan! Great questions. To answer your first question, we started out by learning just what accessibility means to a modern media company. We brought in an expert, Jeremy Fields from Viget, who has written extensively on accessibility, and consulted books and online resources. We then went through various best practice lists and figured out what which guidelines made sense for our specific products and processes. The guidelines we included are a combination of ones that are not currently reflected on our properties, as well as ones that we already follow.

    To your second question, we are fortunate to work in a company that’s incredibly supportive of these efforts, but we understand that isn’t the case at many places. My best piece of advice is to start small. Our first formalized push in accessibility started with a group of six people and two days of work. We tried to come up with something of value immediately—which in our case, was role-specific guidelines on how to advance accessibility in folks’ every day projects. That helped us demonstrate the value to our leadership teams immediately. Later, we built on that foundation by presenting internally to different teams, building out the checklist tool, and so forth, but it all started with a small amount of resources.

    2 points
Load more comments